WANG JIBING (US)
NUGGEHALLI PAVAN (US)
| WO2020151641A1 | 2020-07-30 | |||
| WO2020119195A1 | 2020-06-18 | |||
| WO2020143298A1 | 2020-07-16 |
| What is claimed is: 1. A method in a UE for transmitting industrial Internet of Things (IIOT) data on a communication channel, the method comprising: generating, by processing hardware, a data packet having an associated timestamp, the data packet associated with a flow; scheduling, by the processing hardware, transmission of the data packet to a base station in accordance with the associated timestamp and a survival time period corresponding to a time period in which the flow can persist without messaging; and transmitting, by the processing hardware, the data packet in accordance with the scheduling. 2. The method of claim 1, wherein scheduling transmission of the data packet to a base station in accordance with the associated timestamp and the survival time period includes: receiving, by the processing hardware from the base station, an indication of a resource associated with a certain priority level; and in response to determining that the data packet or a logical channel including at least a portion of the data packet has the certain priority level and is pending for transmission for more than a threshold period of time relative to the survival time period, transmitting, by the processing hardware to the base station, a scheduling request for the data packet or the logical channel via the resource. 3. The method of claim 2, wherein: the scheduling request is a first scheduling request, the data packet is a first data packet, the logical channel is a first logical channel, the priority level is a first priority level; and the method further comprising: determining that the transmission of the first scheduling request would collide with a second scheduling request for transmitting a second data packet or on a second logical channel including at least a portion of the second data packet, the second data packet or second logical channel having a second priority level lower than the first priority level; transmitting, by the processing hardware to the base station, the first scheduling request having a higher priority level; and delaying, by the processing hardware to the base station, transmission of the second scheduling request. 4. The method of claim 1, further comprising: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and prioritizing, by the processing hardware, a buffer status report when the remaining survival time period is less than a threshold period of time. 5. The method of claim 1, wherein scheduling the transmission of the data packet comprises: setting, by the processing hardware, a priority level for the data packet in accordance with the associated timestamp and the survival time period; and scheduling, by the processing hardware, in accordance with the priority level. 6. The method of any one of claims 1-5, further comprising: receiving, by the processing hardware from the base station, an uplink grant; wherein the scheduling comprises determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and wherein the transmitting comprises transmitting, by the processing hardware to the base station, the data packet via the uplink grant when the remaining survival time period is less than a threshold period of time. 7. The method of any one of claims 1-5, wherein scheduling the transmission of the data packet comprises: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and performing one or more of: transmitting, by the processing hardware to the base station, an uplink scheduling request when the remaining survival time period is less than a threshold period of time; and/or adjusting, by the processing hardware, a transmit power when the remaining survival time period is less than the threshold period of time; and/or adjusting, by the processing hardware, a time delay between transmissions when the remaining survival time period is less than the threshold period of time, wherein adjusting the time delay includes adjusting, by the processing hardware, a physical random access channel (PRACH) backoff. 8. The method of claim 1, further comprising: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; adjusting, by the processing hardware, the flow to carriers having a lowest latency when the remaining survival time period is less than a threshold period of time; and transmitting, by the processing hardware to the base station, a preamble via a random access resource. 9. The method of any one of claims 1-5, wherein scheduling transmission of the data packet includes: transmitting, by the processing hardware to the base station, a medium access control (MAC) control element indicating a logical channel or priority level which has been pending for transmission for more than a threshold period of time relative to the survival time period. 10. The method of claim 1, wherein: the data packet is a first data packet, the timestamp is a first timestamp, the flow is a first flow; and the method further comprising: generating, by the processing hardware, a second data packet having a second associated timestamp, the second data packet associated with a second flow; determining, by the processing hardware, a first remaining survival time period based on the survival time period and the first timestamp; determining, by the processing hardware, a second remaining survival time period based on the survival time period and the second timestamp; scheduling, by the processing hardware, transmission of the first data packet to the base station based on the first remaining survival time period; and scheduling, by the processing hardware, transmission of the second data packet to the base station based on the second remaining survival time period. 11. The method of any of the preceding claims, wherein the associated timestamp indicates a previous instance in which an uplink data packet was transmitted or a downlink data packet was received. 12. The method of any of the preceding claims, further comprising: determining, by the processing hardware, the survival time period based on a time period for performing a listen-before-talk (LBT) procedure; and/or determining, by the processing hardware, the survival time period based on a channel occupancy time (COT) period; and/or determining, by the processing hardware, the survival time period based on a combination of the time period for performing the listen-before-talk LBT procedure and the COT period; and/or wherein the COT period is within a fixed frame in a frame based equipment (FBE) communication scheme in accordance with a fixed frame periodicity (FFP) configuration. 13. The method of any of the preceding claims, further comprising: determining, by the processing hardware, that data on a logical channel or radio bearer included in the data packet is pending for transmission; and starting, by the processing hardware, a timer set to a time period which is less than the survival time period; wherein scheduling the transmission of the data packet comprises: in response to determining that the timer expired without transmitting the data packet: transmitting, by the processing hardware to the base station, an uplink scheduling request or a preamble; and/or transmitting, by the processing hardware to the base station, a media access layer (MAC) control element (CE) to report the logical channel or radio bearer associated with the timer. 14. A method in a UE for transmitting industrial Internet of Things (IIOT) data on a communication channel, the method comprising: receiving, by processing hardware in a UE from a base station, an indication of a first fixed frame periodicity (FFP) configuration for a frame based equipment (FBE) communication scheme for a first respective physical or logical parameter; receiving, by the processing hardware from the base station, an indication of a second FFP configuration for a second respective physical or logical parameter, the second FFP configuration different from the first FFP configuration; and transmitting, by the processing hardware to the base station, data in accordance with the first FFP configuration for the first respective physical or logical parameter or the second FFP configuration for the second respective physical or logical parameter. 15. The method of claim 14, wherein transmitting data includes: performing, by the processing hardware, a listen-before-talk (EBT) procedure with the base station for the first respective physical or logical parameter; and optionally wherein performing the EBT procedure includes at least one of: performing, by the processing hardware, the LBT procedure for the first respective physical or logical parameter at a beginning of a fixed frame indicated by the first FFP configuration for the first respective physical or logical parameter; and/or performing, by the processing hardware, the LBT procedure for the first respective physical or logical parameter before a beginning of a fixed frame indicated by the first FFP configuration for the first respective physical or logical parameter; and/or performing, by the processing hardware, a first LBT procedure with the base station for the first respective physical or logical parameter; in response to determining the first LBT procedure has failed: not transmitting, by the processing hardware to the base station, the data in a first fixed frame indicated by the first FFP configuration; performing, by the processing hardware, a second LBT procedure with the base station after an end of the first fixed frame; and in response to determining that the second LBT procedure has succeeded, transmitting, by the processing hardware to the base station, the data in a second fixed frame indicated by the first FFP configuration. 16. The method of claim 15, wherein transmitting data further includes: in response to determining that the LBT procedure has succeeded, transmitting, by the processing hardware to the base station, the data in a fixed frame indicated by the first FFP configuration; and optionally wherein performing the LBT procedure includes: performing, by the processing hardware, a first LBT procedure with the base station for the first respective physical or logical parameter; and performing, by the processing hardware, a second LBT procedure with the base station for the second respective physical or logical parameter, the second LBT procedure performed independently of the first LBT procedure; and/or wherein the second LBT procedure is performed for the second respective physical or logical parameter during a fixed frame indicated by the second FFP configuration for the second respective physical or logical parameter that overlaps with a fixed frame indicated by the first FFP configuration for the first respective physical of logical parameter after the first LBT procedure has failed for the first respective physical or logical parameter. 17. The method of claim 15, further comprising: receiving, by the processing hardware from the base station, information indicating a change in the first FFP configuration for the first respective physical or logical parameter; and/or transmitting, by the processing hardware, one or more LBT conditions to the base station for determining a new FFP configuration based on the one or more LBT conditions, and optionally receiving, by the processing hardware from the base station, information indicating a change in a start position of fixed frames for the first respective physical or logical parameter; and/or wherein receiving information indicating a change in the first FFP configuration or a change in a start position of fixed frames for the first respective physical or logical parameter includes receiving: one or more radio resource control (RRC) messages; one or more messages containing downlink control information (DCI); or one or more messages including medium access control (MAC) control elements. 18. The method of claim 14, further comprising: receiving, by the processing hardware from the base station, a dynamic grant and an indication of a third FFP configuration; performing, by the processing hardware, an LBT procedure with the base station for the dynamic grant; in response to determining the LBT procedure has succeeded, determining, by the processing hardware, a beginning of a next fixed frame using the third FFP configuration; and transmitting, by the processing hardware, the data in the next fixed frame. 19. The method of claim 14, further comprising: receiving, by the processing hardware from the base station, an indication of a first configured grant having a first configured grant periodicity; and receiving an indication of a second configured grant having a second configured grant periodicity; and optionally wherein at least one of: the first configured grant periodicity is the same as or a multiple of the first FFP configuration, the second configured grant periodicity is the same as or a multiple of the second FFP configuration, or the second configured grant periodicity is a multiple of the first configured grant periodicity. 20. The method of claim 14, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first priority level; and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second priority level, and optionally further comprising: performing, by the processing hardware, an LBT procedure with the base station for the second priority level which is lower than the first priority level; and in response to determining that the LBT procedure has succeeded, transmitting, by the processing hardware, data having the first priority level in a fixed frame indicated by the second FFP configuration for the second priority level; and/or starting, by the processing hardware, a timer for the first priority level; receiving, by the processing hardware from the base station, information indicating a change in the first FFP configuration; and waiting, by the processing hardware, to change the first FFP configuration until the timer expires or stops running. 21. The method of claim 14, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first beam; and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second beam, and optionally further comprising: changing, by the processing hardware, from the first beam to the second beam; and determining, by the processing hardware, a next fixed frame using the second FFP configuration. 22. The method of claim 14, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first bandwidth part (BWP); and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second BWP, and optionally further comprising: changing, by the processing hardware, an active BWP from the first BWP to the second BWP; and determining, by the processing hardware, a next fixed frame using the second FFP configuration; and/or starting, by the processing hardware, a timer for an active BWP corresponding to the first or second BWP; receiving, by the processing hardware from the base station, information indicating a change in the first or second FFP configuration for the active BWP; and waiting, by the processing hardware, to change the first or second FFP configuration for the active BWP until the timer expires or stops running; and/or resetting, by the processing hardware, the timer in response to changing the active BWP, and/or starting, by the processing hardware, a first timer for the first BWP; starting, by the processing hardware, a second timer for the second BWP; receiving, by the processing hardware from the base station, information indicating a change in the first or second FFP configuration for the first or second BWP; and waiting, by the processing hardware, to change the first or second FFP configuration until the respective first or second timer expires or stops running. 23. The method of claim 14, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first cell; and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second cell, and optionally further comprising: starting, by the processing hardware, a timer for an active cell corresponding to the first or second cell; receiving, by the processing hardware from the base station, information indicating a change in the first or second FFP configuration for the active cell; and waiting, by the processing hardware, to change the first or second FFP configuration for the active cell until the timer expires or stops running; and/or resetting, by the processing hardware, the timer in response to changing an active BWP or deactivating the active cell. 24. A user device comprising processing hardware configured to execute a method according to any of one of claims 1-23. |
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to and the benefit of the filing date of U.S. Provisional Patent Application No. 63/104,081 entitled “Method of Supporting Industrial Internet of Things (IIOT) with Configured Uplink Grants on a Shared Spectrum,” filed on October 22, 2020, and U.S. Provisional Patent Application No. 63/104,198 entitled “Method of Supporting Industrial Internet of Things (IIOT) on a Shared Spectrum,” filed on October 22, 2020, the entire disclosures of each of which is hereby expressly incorporated by reference.
FIELD OF THE DISCLOSURE
[0002] This disclosure relates to wireless communications and, more particularly, to supporting transmission of industrial Internet of Things (IIOT) data in an unlicensed or otherwise shared spectrum.
BACKGROUND
[0003] This background description is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
[0004] Some wireless communication networks allow compatible devices to share an unlicensed carrier with other radio access technologies. In such cases, to promote fair use of the shared medium, devices operating in the unlicensed carrier typically need to perform channel access procedures before transmitting messages. In particular, a device may need to listen for other communications (i.e., detect energy) on the unlicensed carrier before using the carrier to transmit information, thereby reducing or eliminating interference with the communications of other networks/devices operating on that unlicensed carrier.
[0005] The 3rd Generation Partnership Project (3GPP) specification for fifth-generation (5G) radio access (“NR”) networks, and specifically 3GPP TR 38.899 vl6.0.0 (addressing the use of unlicensed carriers for 5G NR devices under what is commonly referred to as the “NR- U” study item), attempts to maintain fair co-existence with other radio access technologies such as WiFi® (IEEE 802.11) by requiring that 5G NR devices perform a “listen-before-talk” (LBT) procedure at the beginning of a fixed frame in a Frame Based Equipment (FBE) communication scheme before transmitting via the unlicensed carrier. An FBE communication scheme includes Fixed Frame Periods where transmissions can start only at the beginning of each Fixed Frame Period. The total time during which FBE can have transmissions on a given channel, without re-evaluating the availability of that channel, is defined as the channel occupancy time (COT). The COT is then followed by an idle period until the start of the next Fixed Frame Period.
[0006] Fig. 2 illustrates an example timing diagram 200 of an FBE communication scheme including fixed frame periods each having a COT and an idle period. As shown in Fig. 2, the FBE communication scheme includes fixed frames 210, 220. Within each fixed frame 210, 220, a portion of the fixed frame 210, 220 is dedicated to the COT 230, 240 where the UE may transmit data packets during this time period. Another portion of the fixed frame 210, 220 is an idle period 250, 260 where the UE may not transmit data. The UE may perform channel access procedures 270, 280, 290 during the idle period 250, 260. More specifically, the UE may perform a clear channel assessment (CCA) via an LBT procedure 280 during the idle period of the first fixed frame 210 to establish a COT 240 in the subsequent fixed frame 220.
[0007] This restriction on usage of the unlicensed carrier can be problematic for communications that would otherwise be synchronized or tightly scheduled. In NR-U, for example, a user device (e.g., a UE) must perform a successful LBT procedure to establish a COT before using the unlicensed carrier to send physical uplink control channel (PUCCH) information to a base station (e.g., a gNB).
[0008] If the LBT procedure fails, the UE may not transmit data in the fixed frame. If the LBT procedure is successful, the UE can transmit data in the fixed frame. However, a UE may have different Fixed Frame Periodicity (FFP) configurations for different physical or logical parameters such as configured grants (CGs), priority levels, beams, bandwidth parts (BWPs), cells, etc., because the different physical or logical parameters may have different traffic loads or traffic types.
[0009] Furthermore, the 3 GPP specification for 5G NR networks, and specifically 3 GPP TS 22.261 vl8.0.0 defines survival time as a quality of service (QoS) flow parameter which is the time span that an application consuming a communication service may continue without an anticipated message. However, the base station (e.g., a gNB) may not know the remaining survival time period linked to a pending uplink data packet from a user device (e.g., a UE). Thus, the base station might unknowingly schedule uplink transmission of the data packet (e.g., on either licensed or unlicensed carriers and/or to FBE) after expiration of the survival time period, which would disrupt the application.
SUMMARY
[0010] To support the survival time QoS parameter in 5G NR and notify a base station when the remaining survival time period for a pending uplink data packet is about to expire, a UE can adjust uplink scheduling priority based on the remaining survival time period. The UE may obtain an indication of a survival time period from the base station, which may be a time period in which the flow can persist without messaging (e.g., 60 seconds). The survival time period may begin at an activation time that may occur when a previous uplink or downlink transmission is received resetting the timer (e.g., 1:21:00 p.m.). The survival time period may end at a survival timeout which may be the sum of the survival time period and the timestamp activation time (e.g., 1:22:00 p.m.). The UE may associate a timestamp with each data packet indicating the activation time for the data packet, where the data packets are associated with QoS flows. The UE may then determine the survival timeout as the sum of the survival time period and the timestamp and may determine the amount of remaining survival time period for a data packet as the difference between the survival timeout and the current time. For example, if the survival timeout occurs at 1:22:00 p.m. and the current time is 1:21:55 p.m., the remaining survival time period is 5 seconds.
[0011] Then the UE may adjust the priority level for the data packet based on the remaining survival time period. For example, if the remaining survival time period is less than a threshold period of time, the UE may increase the priority level for the data packet. The UE may then transmit a scheduling request to schedule transmission of pending uplink data packets to the base station in accordance with their respective priority levels.
[0012] In some implementations, such as when uplink transmission is scheduled on unlicensed carriers, the threshold period of time may take into account CCA time periods such as the amount of time it takes to perform an LBT procedure, so that the data packet is scheduled for transmission with enough time to perform the LBT procedure. The threshold period of time may also take into account the COT time period, such that the threshold period of time may be the sum of the LBT time period and the COT time period. In other implementations, the threshold period of time may be the sum of two LBT time periods and two COT time periods so that there is enough time for one LBT failure, the sum of three LBT time periods and three COT time periods to account for two LBT failures, etc. A further additional or alternative variant uses multiple FFP configurations available at the UE to determine the threshold time period.
[0013] Furthermore, the survival time period may be determined based on the LBT time period and/or the COT time period, so that for example, the survival time period is longer than the sum of the LBT time period and the COT time period, the sum of two LBT time periods and two COT time periods, the sum of three LBT time periods and three COT time periods, etc.
[0014] In other implementations, the base station may transmit an uplink grant to the UE, where the uplink grant is conditioned such that the UE may not transmit a logical channel (LCH) or data packet via the uplink grant unless the remaining survival time period for the LCH or data packet is less than a threshold period of time. In yet other implementations, the UE may send scheduling requests for data packets to the base station when the remaining survival time period for the data packet is less than a threshold period of time. In another implementation, a logical channel having data is associated with a fixed priority level and a timer. The timer is set to a time period that is shorter than the survival time period. The UE starts the timer when the logical channel has data pending for transmission. The UE restarts the timer when the data on the logical channel is transmitted. The UE stops the timer if the logical channel has no data pending for transmission. If the timer expires, the UE transmits a scheduling request for scheduling transmission of the data on the logical channel or a preamble for the data to the base station.
[0015] Additionally, the UE may adjust LCH and MAC priority levels based on the remaining survival time period to allow data packets to be transmitted before expiration of the survival timer. For example, the data packets closest to survival timeout may be assigned to carriers having lower latency. In another example, the physical random access channel (PRACH) backoff and transmit power may be adjusted based on the remaining survival time period to increase transmission power and/or decrease backoff when the remaining survival time period approaches expiration. [0016] Still further, the base station may associate a first air interface resource (e.g., a time/frequency resource) with a first priority level. If first data and/or a first logical channel having the first priority level is pending for transmission for more than a threshold time (e.g., where the threshold time is based on the survival time period), the UE may transmit a scheduling request for the first data and/or first logical channel to the base station using the first resource. In another implementation, the base station may associate the first resource (e.g., a time/frequency resource) with a logical channel. If data on the logical channel is pending for transmission for more than a threshold time period (e.g., where the threshold time period is based on the survival time period), the UE transmits a scheduling request for the logical channel to the base station using the first resource.
[0017] The base station may also associate a first random access resource (e.g., a PRACH occasion, a preamble, etc.) with a first priority level. If first data and/or a first logical channel having the first priority level is pending for transmission for more than a threshold time (e.g., where the threshold time is based on the survival time period), the UE may transmit a first preamble to the base station using the first random access resource. In other implementations, the base station may also associate a first random access resource (e.g., a PRACH occasion, a preamble, etc.) with a logical channel. If the logical channel has data pending for transmission for more than a threshold time period (e.g., where the threshold time period is based on the survival time period), the UE may transmit a preamble to the base station for the data on the logical channel using the first random access resource. The preamble can be a dedicated preamble that is configured by the base station.
[0018] To comply with the requirement to perform an LBT procedure at the beginning of a fixed frame in an FBE communication scheme when operating in the unlicensed spectrum, a base station transmits a first FFP configuration having a frame size, a frame start position, and/or a frame period to a UE. Before the beginning of a fixed frame or at the beginning of the fixed frame according to the first FFP configuration, the UE performs the LBT procedure before transmitting data. If the LBT procedure fails, the UE is not allowed to transmit data in the fixed frame, and must wait to perform another LBT procedure. On the other hand, if the LBT procedure succeeds, the UE transmits data in the associated fixed frame.
[0019] As mentioned above, the UE may schedule transmission of the data when or before the remaining survival time period for the data is less than a threshold period of time. The threshold period of time may be based on CCA time periods such as the amount of time it takes to perform an LBT procedure, so that the data is scheduled for transmission with enough time to perform the LBT procedure. The threshold period of time may also take into account the COT time period, such that the threshold period of time may be the sum of the LBT time period and the COT time period. In other implementations, the threshold period of time may be the sum of two LBT time periods and two COT time periods, the sum of three LBT time periods and three COT time periods, etc.
[0020] In some implementations, the base station transmits a first FFP configuration and a second FFP configuration to the UE, where the first FFP configuration and the second FFP configuration are different (e.g., having a different frame size, start position, and/or periodicity). For example, the base station may transmit a first FFP configuration to the UE for a first configured grant and a second FFP configuration to the UE for a second configured grant, where each configured grant includes frequency resources, a modulation and coding scheme, and/or HARQ information for transmitting data. For the first CG, before the beginning of a first fixed frame or at the beginning of the first fixed frame according to the first FFP configuration, the UE performs the LBT procedure before transmitting data. If the LBT procedure fails, the UE is not allowed to transmit data in the first fixed frame, and must wait until the first fixed frame ends to perform another LBT procedure. On the other hand, if the LBT procedure succeeds, the UE transmits data in the first fixed frame. For the second CG, before the beginning of a second fixed frame or at the beginning of the second fixed frame according to the second FFP configuration, the UE performs the LBT procedure before transmitting data. If the LBT procedure fails, the UE is not allowed to transmit data in the second fixed frame, and must wait until the second fixed frame ends to perform another LBT procedure. On the other hand, if the LBT procedure succeeds, the UE transmits data in the second fixed frame.
[0021] The LBT processes for each CG may be independent of each other, such that the UE may perform the LBT procedure for the second CG during the first fixed frame for the first CG even when the LBT procedure fails for the first CG and the UE is unable to transmit data for the first CG in the first fixed frame.
[0022] In another example, the base station may transmit a first FFP configuration to the UE for a first priority level and a second FFP configuration to the UE for a second priority level (e.g., where the priority levels are assigned in accordance with the remaining survival time periods for corresponding data packets), the base station may transmit a first FFP configuration to the UE for a first beam and a second FFP configuration to the UE for a second beam, the base station may transmit a first FFP configuration to the UE for a first BWP and a second FFP configuration to the UE for a second BWP, or the base station may transmit a first FFP configuration to the UE for a first cell and a second FFP configuration to the UE for a second cell. More generally, the base station may transmit an FFP configuration for any suitable physical or logical parameter, such as physical and/or logical resources as well as priority levels.
[0023] The base station may also change the FFP configuration by transmitting information to the UE to change the FFP configuration. For example, the UE may report EBT conditions to the base station which may generate a new FFP configuration to reduce the amount of EBT failures for the UE.
[0024] One example embodiment of these techniques is a method in a user device (UE) for transmitting industrial Internet of Things (IIOT) data on a communication channel. The method can be implemented in the user device using processing hardware and includes generating a data packet having an associated timestamp, the data packet associated with a flow, scheduling transmission of the data packet to a base station in accordance with the associated timestamp and a survival time period corresponding to a time period in which the flow can persist without messaging, and transmitting the data packet in accordance with the scheduling.
[0025] Another example embodiment of these techniques is a method in a UE for transmitting IIOT data on a communication channel. The method can be implemented in the UE using processing hardware and includes receiving, from a base station, an indication of a first fixed frame periodicity (FFP) configuration for a frame based equipment (FBE) communication scheme for a first respective physical or logical parameter, and receiving, from the base station, an indication of a second FFP configuration for a second respective physical or logical parameter, the second FFP configuration different from the first FFP configuration. The method further includes transmitting, to the base station, data in accordance with the first FFP configuration for the first respective physical or logical parameter or second FFP configuration for the second respective physical or logical parameter.
[0026] Another example embodiment of these techniques is a user device with processing hardware and configured to execute the methods above. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Fig. 1 is a block diagram of an example wireless communication network that implements the survival time scheduling and UE-initiated channel occupancy time techniques of this disclosure;
[0028] Fig. 2 is a timing diagram of an FBE communication scheme including fixed frame periods each having a channel occupancy time (COT) and an idle period;
[0029] Fig. 3 is a messaging diagram of an example procedure for increasing the priority level for a data packet when the remaining survival time period is about to expire;
[0030] Fig. 4 is a messaging diagram of an example procedure for receiving an uplink grant from a base station which may only be used when the remaining survival time period for a data packet is about to expire, and transmitting the data packet via the uplink grant when the remaining survival time period is about to expire;
[0031] Fig. 5 is a messaging diagram of an example procedure for transmitting a scheduling request for a data packet when the remaining survival time period for the data packet is about to expire;
[0032] Fig. 6 is a messaging diagram of an example procedure for receiving a first resource associated with a first priority level from a base station, and transmitting a scheduling request for a data packet having the first priority level via the first resource when the remaining survival time period for the data packet is about to expire;
[0033] Fig. 7 is a messaging diagram of an example procedure for receiving a first random access resource associated with a first priority level from a base station, and transmitting a preamble for a data packet having the first priority level via the first random access resource when the remaining survival time period for the data packet is about to expire;
[0034] Fig. 8 is a messaging diagram of example procedure for determining that a first scheduling request transmission would collide with a second scheduling request transmission, and transmitting the scheduling request having the higher priority level;
[0035] Fig. 9 is a messaging diagram of example procedure for determining that a first preamble transmission would collide with a second preamble transmission, and transmitting using the preamble having the higher priority level; [0036] Fig. 10 is a messaging diagram of an example procedure for transmitting a MAC Control Element (CE) in a MAC PDU to notify a base station of an LCH or priority level having a remaining survival time period which is about to expire;
[0037] Fig. 11 is a timing diagram indicating the start positions of fixed frames in an FBE communication scheme relative to system frames;
[0038] Fig. 12 is a messaging diagram of an example procedure for UE-initiated COT;
[0039] Fig. 13 is a timing diagram of an LBT procedure and subsequent uplink transmission within fixed frames of an FBE communication scheme, where the LBT procedure is performed prior to the start position of a fixed frame;
[0040] Fig. 14 is a timing diagram of an LBT procedure and subsequent uplink transmission within fixed frames of an FBE communication scheme, where the LBT procedure is performed at the start position of a fixed frame;
[0041] Fig. 15 is a timing diagram of two LBT procedures and subsequent uplink transmissions for two respective physical or logical parameters each having a different FFP configuration, where the LBT processes are independent from each other such that if the LBT fails for a first physical or logical parameters, the UE can perform an LBT procedure for the second physical or logical parameter during the fixed frame for the first physical or logical parameter;
[0042] Fig. 16 is a timing diagram indicating the start positions of fixed frames in an FBE communication scheme when the base station transmits information to the UE to change the start position of fixed frames from a current fixed frame timing;
[0043] Fig. 17 is a flow diagram of an example method for survival time scheduling when transmitting industrial Internet of Things (IIOT) data on a communication channel, which can be implemented in the UE of Fig. 1; and
[0044] Fig. 18 is a flow diagram of an example method for UE-initiated COT when transmitting IIOT data on a communication channel, which can be implemented in the UE of Fig. 1. DETAILED DESCRIPTION OF THE DRAWINGS
[0045] Using the techniques of this disclosure, a communication device such as a UE performs procedures to support transmitting IIOT data on a shared carrier in a manner that reduces the delay in starting a transmission (e.g., an uplink transmission that requires configuration of the UE). As the term is used herein, a “carrier” may be any type of frequency spectrum or band, which corresponds to at least one channel in a given radio access network. Moreover, as used herein, a “shared” carrier may be an unlicensed carrier that is shared by different radio access networks and/or technologies, or a carrier that is shared in some other way and/or for some other reason (e.g., a carrier shared only among the multiple devices of a single radio access network).
[0046] These techniques are discussed below primarily with reference to 5G NR technologies, and more specifically with reference to operation of the 5G NR network over an unlicensed carrier (i.e., NR-U operation). However, the techniques of this disclosure can apply to other radio access technologies, and/or to other types of shared carriers (e.g., licensed bands that are shared by devices of a single radio access network). In the case of licensed bands, a channel access procedure of the type described below may or may not be performed.
[0047] Referring first to Fig. 1, a wireless communication network 100 includes a UE 102, which can be any suitable device capable of wireless communications, as further discussed below. The wireless communication network 100 also includes a base station 104 associated with an NR-U cell 106 and connected (directly or indirectly) to a 5G core network (5GC) 110. The base station 104 may operate as a 5G Node B (gNB), a distributed unit gNB (gNB- DU), or an integrated access backhaul (IAB) node, for example. While Fig. 1 depicts the base station 104 as serving only the cell 106, it is understood that the base station 104 may also cover one or more additional cells not shown in Fig. 1. In general, the wireless communication network 100 can include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells.
[0048] 5G NR UEs operating in the cell 106, including the UE 102, can utilize an unlicensed carrier as well as portions of the radio spectrum allocated specifically to the service provider that operates the base station 104 and the 5GC 110. When exchanging data using the 5G NR air interface, the UE 102 and base station 104 may share the unlicensed carrier with other devices of other radio access networks. For example, other UEs (not shown in Fig. 1) may be subscribers of the service provider that operates the base station 104 and the 5GC 110 and be capable of communicating with the base station 104 via the unlicensed carrier. In addition, or alternatively, other UEs utilizing the unlicensed carrier may communicate with a base station or network node other than the base station 104, using a different radio access technology. Fig. 1 depicts an example of one such scenario, in which the UE 102 and base station 104 coexist with an access point (AP) 112. The AP 112 can utilize spectrum that includes, or is included within, at least a portion of the unlicensed carrier when operating in a wireless local area network (WLAN) according to one of the IEEE 802.11 standards. The AP 112 may be configured to communicate with one or more other devices not shown in Fig. 1, such as other UEs, for example. In other implementations and/or scenarios, the UE 102 and base station 104 also, or instead, coexist with devices operating according to other radio access technologies. In still another implementation and/or scenario, the base station 104 does not connect to the 5GC 110, and can operate as an AP (e.g., similar to AP 112). Thus, for example, the wireless communication network 100 may omit the 5GC 110, or only use the 5GC 110 in certain scenarios.
[0049] The UE 102 is equipped with processing hardware 120, which may include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory storing instructions that the one or more general-purpose processors can execute. Additionally or alternatively, the processing hardware 120 may include special-purpose processing units, such as a wireless communication chipset, for example. The processing hardware 120 includes a survival time scheduling module 122, and a COT controller 124. The survival time scheduling module 122, and COT controller 124 may be implemented using any suitable combination of hardware, software, and/or firmware.
[0050] In operation, the survival time scheduling module 122 obtains an indication of a survival time period from the base station 104 or from a default survival time period stored at the UE 102. When the UE 102 generates data packets associated with QoS flows and associates the data packets/QoS flows with timestamps indicating activation times for the data packets/QoS flows, the survival time scheduling module 122 determines the remaining survival time period for a data packet/QoS flow based on the survival time period, the timestamp, and the current time. More specifically, the survival time scheduling module 122 may identify the survival timeout as the sum of the timestamp (e.g., the last time when the application transmitted/received a message) and the survival time period. The survival time scheduling module 122 may determine the difference between the survival timeout and the current time as the remaining survival time period. The survival time scheduling module 122 may transmit scheduling requests to the base station 104 for scheduling transmission of data packets/QoS flows in accordance with the remaining survival time period for the data packets. For example, the survival time scheduling module 122 may increase the priority levels of data packets/QoS flows having less than a threshold amount of remaining survival time period or may transmit scheduling requests using resources provided by the base station 104 indicating that the corresponding data packets/QoS flows have less than a threshold amount of remaining survival time period. In some implementations, such as when uplink transmission is scheduled on unlicensed carriers, the threshold period of time may take into account CCA time periods such as the amount of time it takes to perform an LBT procedure, so that the data packet is scheduled for transmission with enough time to perform the LBT procedure. The threshold period of time may also take into account the COT time period, such that the threshold period of time may be the sum of the LBT time period and the COT time period. The survival time scheduling module 122 may also adjust carriers, PRACH backoff, and transmission power for data packets/QoS flows based on the remaining survival time period to prevent the corresponding applications from timing out.
[0051] The COT controller 124 obtains FFP configurations from the base station 104 for example, via a system information block (SIB) or an RRC message, such as RRC Reconfiguration, RRC Setup, RRC Reestablishment, or RRC Resume, for example. The COT controller 124 then performs a channel access procedure, such as an LBT procedure, to gain access to the shared carrier in the NR-U cell 106. When the channel access procedure is successful, the COT controller 124 determines that the UE 102 has obtained or established a COT and accordingly can transmit various signals during the COT according to the FFP configuration.
[0052] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory storing instructions that the one or more general-purpose processors can execute. Additionally or alternatively, the processing hardware 130 may include special-purpose processing units, such as a wireless communication chipset, for example. The processing hardware 130 in the example implementation of Fig. 1 includes a survival time monitoring module 132, and a COT configuration module 134. [0053] The survival time monitoring module 132 transmits indications of resources such as random access resources which are associated with priority levels to the UE 102. When the survival time monitoring module 132 receives scheduling requests or preambles via these resources, the survival time monitoring module 132 is notified that the data packets/QoS flows corresponding to the scheduling requests or preambles are approaching survival timeout.
[0054] The COT configuration module 134 configures and transmits FFP configurations to the UE 102 via an SIB or an RRC message, such as RRC Reconfiguration, RRC Setup, RRC Reestablishment, or RRC Resume, for example. The FFP configurations may include a fixed frame start position, a fixed frame size, and/or a fixed frame period. The COT configuration module 134 may transmit different FFP configurations to the UE 102 for different physical or logical parameters, which may include physical or logical resources, such as configured grants, beams, BWPs, cells, etc., or priority levels. Then the UE 102 may transmit data packets to the base station 104 in accordance with an FFP configuration for a corresponding physical or logical parameter.
[0055] For simplicity, Fig. 1 does not depict various components of the UE 102 and the base station 104. In addition to the components mentioned above, for example, the UE 102 and the base station 104 include respective transceivers, which include various hardware, firmware, and/or software components configured to transmit and receive wireless signals. The processing hardware 120 and the processing hardware 130 can send commands and exchange information with the respective transceivers as needed to perform various connection establishment procedures, perform various RRC or mobility management (MM), or communicate with other network elements, etc.
Support for Survival Time QoS Parameter
[0056] Figs. 3-10 illustrate several example procedures for scheduling transmission of data packets associated with QoS flows in accordance with the remaining survival time period. Generally speaking, the UE 102 obtains an indication of the survival time period from the base station 104 or from a default survival time period stored at the UE 102. When the UE 102 generates a data packet associated with a QoS flow, the UE 102 determines the remaining survival time period for the data packet/QoS flow based on a timestamp associated with the data packet/QoS flow indicating an activation time, such as when a previous uplink or downlink transmission is received, the current time, and the survival time period. The UE 102 then transmits scheduling requests for the data packets/QoS flows or transmits the data packets/QoS flows to the base station in accordance with the remaining survival time period for each of the data packets/QoS flows.
[0057] Fig. 3 illustrates an example procedure 300 where the UE 102 obtains 302-1 an indication of the survival time period from a default survival time period stored at the UE 102 or obtains 302-2 the indication of the survival time period from the base station 104. The UE 102 starts 303 a survival timer at an activation time, such as when a previous uplink or downlink transmission is received resetting the survival timer or when any other suitable event occurs which could cause the survival timer to reset. Additionally, the UE 102 generates 304 a data packet which is associated with a QoS flow, and associates the data packet/QoS flow with a timestamp indicating the activation time.
[0058] The base station 104 transmits 305 an uplink grant to the UE 102 for example on a physical downlink control channel (PDCCH). In some implementations, the uplink grant may be indicated in a downlink control information (DCI) element.
[0059] The UE 102 then determines the remaining survival time period for the data packet/QoS flow based on the survival time period, the associated timestamp, and/or the current time. In response to determining 306 that the remaining survival time period is less than a threshold period of time, the UE 102 increases 308 the priority level for the data packet/QoS flow. The UE 102 transmits 310 scheduling requests for scheduling transmission of data packet/QoS flows to the base station 104 in accordance with the corresponding priority levels for the data packets/QoS flows. For example, scheduling requests for data packets/QoS flows having higher priority levels may be transmitted to the base station 104 before scheduling requests for data packets/QoS flows having lower priority levels. Based on these scheduling requests, the base station 104 can prioritize scheduling (not shown) of physical uplink shared channel (PUSCH) resources for the UE 102 so that the pending uplink data packet/QoS flow/LCH can be transmitted by the UE 102 prior to a survival timeout. The UE 102 then transmits 312 data packets/QoS flows using the PUSCH resources in accordance with the scheduling arranged by the base station 104.
[0060] In some implementations, such as when uplink transmission is scheduled on unlicensed carriers, the threshold period of time may take into account CCA time periods such as the amount of time it takes to perform an LBT procedure, so that the data packet is scheduled for transmission with enough time to perform the LBT procedure. The threshold period of time may also take into account the COT time period, such that the threshold period of time may be the sum of the LBT time period and the COT time period. In other implementations, the threshold period of time may be the sum of two LBT time periods and two COT time periods so that there is enough time for one LBT failure, the sum of three LBT time periods and three COT time periods to account for two LBT failures, etc.
[0061] Furthermore, the UE 102 and/or the base station 104 may determine the survival time period based on the LBT time period and/or the COT time period, so that for example, the survival time period is longer than the sum of the LBT time period and the COT time period, the sum of two LBT time periods and two COT time periods, the sum of three LBT time periods and three COT time periods, etc.
[0062] Fig. 4 illustrates an example procedure 400 similar to the procedure 300 of Fig. 3. Events in the procedure 400 similar to those discussed above with respect to the procedure 300 are labeled with similar reference numbers (e.g., with event 302-1 of Fig. 3 corresponding to event 402-1 of Fig. 4). With the exception of the differences shown in Fig.
4 and the differences described below, any of the alternative implementations discussed above with respect to the procedure 300 (e.g., for messaging and processing) may apply to the procedure 400.
[0063] In the procedure 400, the base station 104 transmits 405 an uplink grant to the UE 102 which may only be used if the data packet/QoS flow or LCH including at least some of the data in the data packet has a remaining survival time period that is less than a threshold period of time. In response to determining 406 that the remaining survival time period for the LCH/data packet/QoS flow is less than a threshold period of time, the UE 102 transmits 411 the LCH/data packet/QoS flow via the uplink grant.
[0064] Fig. 5 illustrates another example procedure 500 similar to the procedure 300 of Fig 3. In the procedure 500, the UE 102 may only transmit scheduling requests for data packets/QoS flows having a remaining survival time period that is less than a threshold period of time. In response to determining 506 that the remaining survival time period for the data packet/QoS flow is less than a threshold period of time, the UE 102 transmits 512 a scheduling request for transmitting the data packet/QoS flow to the base station 104. Based on the scheduling request, the base station 104 can schedule (not shown) physical uplink shared channel (PUSCH) resources for the UE 102 so that the pending uplink data packet/QoS flow can be transmitted by the UE 102 prior to a survival timeout. The UE 102 then transmits 512 data packets/QoS flows using the PUSCH resources in accordance with the scheduling arranged by the base station 104.
[0065] Fig. 6 illustrates a messaging diagram of an example procedure 600 for receiving a first resource associated with a first priority level from the base station 104, and transmitting a scheduling request for a data packet or logical channel having the first priority level via the first resource when the remaining survival time period for the data packet or logical channel is less than the threshold period of time. In the procedure 600, the base station 104 associates 602 a first resource with a first priority level. The first resource may be a time-frequency resource allocated to the UE 102. For example, the time-frequency resource may have one or more frequency ranges for a certain time duration (e.g., one, two, or three OFDM symbols).
[0066] The base station 104 transmits 604 an indication of the association between the first resource and the first priority level to the UE 102. Accordingly, the base station 104 receives a scheduling request from the UE 102 via the first resource, this inherently notifies the base station 104 that the remaining survival time period for the data packet/QoS flow is about to expire.
[0067] The UE 102 determines 606 that a data packet/QoS flow/LCH has the same priority level as the priority level associated with the first resource. The UE 102 also determines that the data packet/QoS flow/LCH has been pending for more than a threshold period of time, such that the remaining survival time period for the data packet/QoS flow/LCH is less than another threshold period of time. The UE 102 then transmits 608 a scheduling request for the data packet/QoS flow/LCH to the base station 104 via the first resource, notifying the base station 104 that the data packet/QoS flow/LCH is approaching survival timeout. Based on this notification, the base station 104 can prioritize scheduling (not shown) of physical uplink shared channel (PUSCH) resources for the UE 102 so that the pending uplink data packet/QoS flow/LCH can be transmitted by the UE 102 prior to a survival timeout. The UE 102 then transmits 612 the pending uplink data packet/QoS flow/LCH using the PUSCH resources in accordance with the scheduling arranged by the base station 104.
[0068] Fig. 7 illustrates another example procedure 700 similar to the procedure 600 of Fig 6. In the procedure 700, the base station 104 associates 703 a first random access resource with a first priority level and/or a logical channel. The first random access resource may be a PRACH occasion, a preamble, etc. In response to determining that a data packet/QoS flow/LCH has the same priority level as the priority level associated with the first random access resource and that the data packet/QoS flow/LCH has been pending for more than a threshold period of time, such that the remaining survival time period for the data packet/QoS flow/LCH is less than another threshold period of time, the UE 102 transmits 709 a preamble (e.g., a dedicated preamble) for the data packet/QoS flow/LCH to the base station 104 via the first random access resource. This random access transmission using this preamble inherently notifies the base station 104 that the data packet/QoS flow/LCH is approaching survival timeout.
[0069] Fig. 8 illustrates another example procedure 800 similar to the procedure 600 of Fig. 6. The UE 102 determines 810 that the transmission, via a first resource, of a first scheduling request for a first data packet/QoS flow having a first priority level would collide with the transmission, via a second resource, of a second scheduling request for a second data packet/QoS flow having a second priority level. The UE 102 may then determine which data packet/QoS flow has a higher priority level. The UE 102 transmits 812 the scheduling request for the data packet/QoS flow having the higher priority level. For example, a scheduling request that is triggered due to the remaining survival time period being less than a threshold time period or due to expiry of a timer has a higher priority level than a scheduling request that is triggered due to other causes such as data arrival of higher priority data. The UE 102 may also delay the transmission of the scheduling request for the data packet/QoS flow having the lower priority level. Based on these scheduling requests, the base station 104 can prioritize scheduling (not shown) of physical uplink shared channel (PUSCH) resources for the UE 102 so that the pending uplink data packet/QoS flow/LCH can be transmitted by the UE 102 prior to a survival timeout. The UE 102 then transmits 814 the pending uplink data packet/QoS flow/LCH using the PUSCH resources in accordance with the scheduling arranged by the base station 104.
[0070] Fig. 9 illustrates another example procedure 900 similar to the procedure 700 of Fig. 7. The UE 102 determines 911 that the transmission, via a first random access resource, of a first preamble for a first data packet/QoS flow having a first priority level would collide with the transmission, via a second random access resource, of a second scheduling request for a second data packet/QoS flow having a second priority level. The UE 102 may then determine which data packet/QoS flow has a higher priority level. The UE 102 transmits 913 the preamble for the data packet/QoS flow having the higher priority level. The UE 102 may also delay the transmission of the preamble for the data packet/QoS flow having the lower priority level.
[0071] Fig. 10 illustrates yet another example procedure 1000 similar to the procedure 600 of Fig. 6. In response to determining that a data packet/QoS flow has been pending for more than a threshold period of time, such that the remaining survival time period for the data packet/QoS flow is less than another threshold period of time, the UE 102 transmits 1016 a MAC CE in a MAC PDU to the base station 104 to notify the base station 104 of an LCH or priority level for a data packet/QoS flow approaching survival timeout. In some implementations, a unique LCH ID is included in the MAC PDU (e.g., in a subheader associated with the MAC CE) to identify the MAC CE.
[0072] In some implementations, the UE 102 may adjust a time delay between transmissions (e.g., a PRACH backoff), transmit power, or carriers for transmitting data packets/QoS flows based on the remaining survival time period. For example, the UE 102 may increase transmission power, decrease the time delay, or select carriers for the QoS flow with lower latency when the remaining survival time period approaches expiration.
[0073] Also in some implementations, the UE 102 may prioritize a buffer status report when the remaining survival time period approaches expiration. Still further, the UE 102 may schedule transmissions separately for different applications having different priorities. More specifically, for two data packets having first and second respective flows, the UE 102 may determine first and second remaining survival time periods for the first and second respective flows, and schedule transmission of the data packets based on the first and second remaining survival time periods. For example, when the first remaining survival time period is less than the second remaining survival time period, the UE 102 may schedule transmission of the data packet associated with the first respective flow before scheduling transmission of the data packet associated with the second respective flow.
[0074] In some implementations, the UE 102 may start a timer when data at a logical channel or radio bearer having a fixed priority level is pending. The timer may be set to a time period which is shorter than the survival time period. The UE 102 may use the timer to trigger transmission of a scheduling request or preamble after expiration of the timer but before expiration of the survival time period, so that the base station 104 may allocate uplink radio resources for the UE 102 to transmit data before expiration of the survival time period. If the data is transmitted before the timer expires, the UE 102 stops and/or restarts the timer. Additionally, if there is no data at the logical channel or radio bearer, the UE 102 stops the timer. If the timer expires before the data on the logical channel or radio bearer is transmitted, the UE 102 may transmit a scheduling request to schedule transmission of the data on the logical channel or radio bearer or a random access preamble for the data on the logical channel or radio bearer to the base station 104. Also if the timer expires before the data on the logical channel or radio bearer is transmitted, the UE 102 may transmit a MAC CE to the base station 104 in a Msg3 in a 4- step random access channel (RACH) procedure or in a MsgB in a 2-step RACH procedure to report the logical channel(s) or radio bearer(s) associated with the expired timer. The timer may span time periods which are equal to one or multiple fixed frame periods including COT periods.
Support for UE-Initiated Channel Occupancy Time for FBE Over an Unlicensed Carrier
[0075] As mentioned above, some wireless communication networks allow compatible devices to share an unlicensed carrier with other radio access technologies. In such cases, to promote fair use of the shared medium, devices operating in the unlicensed carrier typically need to perform channel access procedures before transmitting messages. In NR-U, for example, a user device (e.g., a UE) must perform a successful LBT procedure to establish a COT before using the unlicensed carrier to send PUCCH information to a base station (e.g., a gNB).
[0076] The base station 104 may transmit information to the UE 102 to configure the UE 102 with an FFP configuration which may include a fixed frame start position, a fixed frame size, and/or a fixed frame period. For example, the base station 104 may transmit the information in an SIB or a dedicated message such as RRC Setup, RRC Resume, RRC Reestablishment, or RRC Reconfiguration. The fixed frame start position may be an offset to the first OFDM symbol/slot/subframe of the first system frame. Each system frame has a number, and the offset may be N symbols/slots/subframes from system symbol/slot/subframe 0 of system frame 0. As shown in the timing diagram 1100 of Fig. 11, the fixed frame start position 1120 may be offset in the middle of the first system frame 1110 or a subsequent system frame. Also as shown in Fig. 11, the fixed frame size 1140 for a particular FFP configuration may be different from the system frame size 1130. In the timing diagram 1100, system frame 1 spans about four fixed frames from fixed frame 2 to fixed frame 6.
[0077] Fig. 12 illustrates an example procedure 1200 where the base station 104 determines 1202 to configure the UE 102 with FFP configurations each including a fixed frame start position, a fixed frame size, and/or a fixed frame period. Each FFP configuration may be different and may correspond to a different physical or logical parameter. The physical or logical parameters may include physical or logical resources, such as space/time/frequency resources, and/or may include priority levels. For example, the base station 104 may configure the UE 102 with a first FFP configuration for a first configured uplink grant and a second FFP configuration for a second configured uplink grant. In another example, the base station 104 may configure the UE 102 with a first FFP configuration for a first priority level and a second FFP configuration for a second priority level. In yet another example, the base station 104 may configure the UE 102 with a first FFP configuration for a first beam and a second FFP configuration for a second beam. In another example, the base station 104 may configure the UE 102 with a first FFP configuration for a first BWP and a second FFP configuration for a second BWP. In yet another example, the base station 104 may configure the UE 102 with a first FFP configuration for a first cell and a second FFP configuration for a second cell.
[0078] The base station 104 transmits 1204 the FFP configurations for respective physical or logical parameters to the UE 102. For example, the base station 104 may transmit the information in an SIB or a dedicated message such as RRC Setup, RRC Resume, RRC Reestablishment, or RRC Reconfiguration.
[0079] For a particular physical or logical parameter, the UE 102 performs 1206 an EBT procedure with the base station 104 at or prior to the beginning of a fixed frame for the particular physical or logical parameter according to the corresponding FFP configuration from the base station 104.
[0080] If the EBT procedure fails 1208, the UE 102 waits 1210 until the end of the fixed frame and does not transmit data using the particular physical or logical parameter during the fixed frame. Then, after the end of the fixed frame, the UE 102 may again perform 1206 the LBT procedure.
[0081] If the LBT procedure is successful 1212, the UE 102 transmits 1214 data using the particular physical or logical parameter in the fixed frame.
[0082] Fig. 13 illustrates an example timing diagram 1300 of an LBT procedure and subsequent uplink transmission within fixed frames of an FBE communication scheme, where the LBT procedure is performed prior to the start position of a fixed frame. As shown in Fig. 13, the UE 102 performs 1310, 1320 the LBT procedure immediately prior to the beginning of the fixed frame 1330, 1340. If the LBT procedure 1310 fails, the UE 102 may not transmit data in the fixed frame 1330 and waits until the end of the fixed frame to perform 1320 the LBT procedure again. If the LBT procedure 1320 is successful, the UE 102 transmits data during the COT period 1345 of the fixed frame 1340.
[0083] Fig. 14 illustrates another example timing diagram 1400 of an LBT procedure and subsequent uplink transmission within fixed frames of an FBE communication scheme, where the LBT procedure is performed at the beginning of a fixed frame. As shown in Fig.
14, the UE 102 performs 1410, 1420 the LBT procedure at the beginning of the fixed frame 1430, 1440. If the LBT procedure 1410 fails, the UE 102 may not transmit data in the fixed frame 1430 and waits until the beginning of the next fixed frame to perform 1420 the LBT procedure again. If the LBT procedure 1420 is successful, the UE 102 transmits data during the COT period 1445 of the fixed frame 1440. In some implementations, fixed frames begin at the symbol/slot/subframe in which the UE 102 has a configured uplink grant to transmit data.
[0084] LBT procedures for different physical or logical parameters may be independent of each other, such that a single UE may run multiple LBT processes at the same time, and the UE 102 may perform an LBT procedure for one physical or logical parameter even though the LBT procedure for another physical or logical parameter failed and the UE 102 is unable to transmit data during the fixed frame for the other physical or logical parameter.
[0085] Fig. 15 illustrates an example timing diagram 1500 of two sets of LBT procedures 1580, 1590 and subsequent uplink transmissions for two respective physical or logical parameters each having a different FFP configuration. The two sets of LBT processes 1580, 1590 are independent from each other such that if the LBT fails for a first physical or logical parameter, the UE 102 can perform an LBT procedure for the second physical or logical parameter during the fixed frame for the first physical or logical parameter. As shown in Fig.
15, the LBT procedure fails for the first physical or logical parameter, and the UE 102 does not transmit data via the first physical or logical parameter during the first fixed frame for the first physical or logical parameter. However, the UE 102 performs an LBT procedure for the second physical or logical parameter during the first fixed frame for the first physical or logical parameter. The LBT procedure is successful, and the UE 102 transmits data via the second physical or logical parameter during the first fixed frame for the second physical or logical parameter which also occurs during the first fixed frame for the first physical or logical parameter.
[0086] As described above, the base station 104 may transmit first and second CGs to the UE 102. The base station 104 may also transmit first and second CG periodicities to the UE 102 for the respective first and second CGs or the first and second CG periodicities may be predefined at the UE 102. In some implementations, the first CG periodicity is the same as the first FFP configuration or is a multiple of the first FFP configuration. Likewise, the second CG periodicity is the same as the second FFP configuration or is a multiple of the second FFP configuration. Also in some implementations, the period of the second CG periodicity is a multiple of the period of the first CG periodicity.
[0087] In some embodiments, the base station 104 may transmit a dynamic grant to the UE 102, for example on a PDCCH. The base station 104 may transmit a third FFP configuration to the UE 102 for the dynamic grant. If the LBT procedure for the dynamic grant fails, the UE 102 uses the third FFP configuration for the dynamic grant to determine the start of the next fixed frame. If the LBT procedure for the dynamic grant is successful, the UE 102 transmits data in the fixed frame indicated by the third FFP configuration for the dynamic grant. This is an independent process from the LBT processes for the configured grants, such that the UE 102 may perform LBT procedures for the configured grants at the same time as the UE 102 performs the LBT procedure for the dynamic grant.
[0088] The base station 104 also may configure the UE 102 with different FFP configurations for different priority levels. In some implementations, the priority level may be the priority level of a MAC PDU, where the priority level of the MAC PDU is the highest priority level of the LCH whose data is included in the MAC PDU. The base station 104 may assign a priority level to each LCH and a MAC PDU may multiplex data from multiple LCHs. For example, the priority levels for the MAC PDUs or the LCHs may be assigned in accordance with the remaining survival time periods for the MAC PDUs or the LCHs.
[0089] In other implementations, the priority level may be the priority level of an uplink grant. The base station 104 may indicate the priority level of an uplink grant in DCI or may transmit the priority level of an uplink grant (e.g., a configured grant) to the UE 102.
[0090] In some implementations, when the LBT procedure for a lower priority level succeeds and there is a higher priority MAC PDU pending for transmission, the UE 102 may transmit the higher priority MAC PDU in the fixed frame for the lower priority level. [0091] Also in some implementations, when the UE 102 receives an indication of an FFP configuration for a priority level or changes the FFP configuration for the priority level, the UE 102 starts a timer. When the timer is running, the UE 102 may not change the FFP configuration for the priority level. After the timer expires or is not running, the UE 102 may change the FFP configuration for the priority level, for example in response to receiving information indicating a change in the FFP configuration for the priority level. When the UE 102 changes the FFP configuration for the priority level, the UE 102 starts or restarts the timer.
[0092] Still further, the base station 104 may configure the UE 102 with a first beam and a second beam. The base station 104 may associate the first beam with the first FFP configuration and the second beam with the second FFP configuration, and may transmit information indicating the first beam, the first FFP configuration, the association between the first beam and the first FFP configuration, the second beam, the second FFP configuration, and the association between the second beam and the second FFP configuration to the UE 102. Because the beams may have different traffic loads, a different FFP configuration may be necessary for each beam.
[0093] In some implementations, the first and second beams are associated with first and second Synchronization Signal Blocks (SSBs), respectively. In other implementations, the first and second beams are associated with first and second Channel State Information Reference Signals (CSI-RSs), respectively. If the UE 102 changes from the first beam to the second beam, the UE 102 uses the second FFP configuration to determine the start of the next fixed frame. Eikewise, if the UE 102 changes from the second beam to the first beam, the UE 102 uses the first FFP configuration to determine the start of the next fixed frame.
[0094] Additionally, the base station 104 may configure the UE 102 with a first BWP and a second BWP. The base station 104 may associate the first BWP with the first FFP configuration and the second BWP with the second FFP configuration, and may transmit information indicating the first BWP, the first FFP configuration, the association between the first BWP and the first FFP configuration, the second BWP, the second FFP configuration, and the association between the second BWP and the second FFP configuration to the UE 102. Because the BWPs may have different traffic loads, a different FFP configuration may be necessary for each BWP. [0095] In some implementations, the first and second FFP configurations may be derived from the shortest periodicity of the CG that is configured for the first and second BWPs, respectively. If the UE 102 changes the active BWP from the first BWP to the second BWP, the UE 102 uses the second FFP configuration to determine the start of the next fixed frame. Likewise, if the UE 102 changes the active BWP from the second BWP to the first BWP, the UE 102 uses the first FFP configuration to determine the start of the next fixed frame.
[0096] The UE 102 may also start a first timer upon receiving the configuration of the first FFP configuration or changing the first FFP configuration for the first BWP and a second timer upon receiving the configuration of the second FFP configuration or changing the second FFP configuration for the second BWP. When the first timer is running, the UE 102 may not change the FFP configuration for the first BWP. Likewise, when the second timer is running, the UE 102 may not change the FFP configuration for the second BWP. After the first timer expires or is not running, the UE 102 may change the FFP configuration for the first BWP. After the second timer expires or is not running, the UE 102 may change the FFP configuration for the second BWP. When the UE 102 changes the active BWP, the UE 102 may reset the timer for the active BWP and stop the timer for the inactive BWP. In other implementations, the UE 102 starts a single timer for the active BWP. When the timer is running, the UE 102 may not change the FFP configuration for the active BWP. After the timer expires or is not running, the UE 102 may change the FFP configuration for the active BWP, for example in response to receiving information indicating a change in the FFP configuration for the active BWP. When the UE 102 changes the active BWP, the UE 102 may start or reset the timer.
[0097] The base station 104 may configure the UE 102 with a cell and the base station 104 may associate the cell with an FFP configuration and may transmit information indicating the cell, the FFP configuration, and the association between the cell and the FFP configuration. In some implementations, when the UE 102 activates the cell, the UE 102 starts a timer. When the timer is running, the UE 102 may not change the FFP configuration for the cell. After the timer expires or is not running, the UE 102 may change the FFP configuration for the cell, for example in response to receiving information indicating a change in the FFP configuration for the cell. When the UE 102 deactivates the cell, the UE 102 stops the timer. When the UE 102 changes the FFP configuration for the cell or changes the active BWP, the UE 102 starts or restarts the timer. [0098] To change the FFP configuration for a particular physical or logical parameter, the base station 104 may transmit information to the UE 102 indicating the change in the FFP configuration for a respective physical or logical parameter. More specifically, the base station 104 may transmit a MAC CE to the UE 102 including the indication of the new FFP configuration. In some implementations, a unique logical channel ID may be associated with the MAC CE for the UE 102 to identify the MAC CE. The MAC CE may include a new FFP configuration and a BWP/Cell ID in order to change FFP configuration for the BWP/Cell. In other implementations, the base station 104 may transmit a DCI that indicates a new FFP configuration. More specifically, the base station 104 may change the FFP configuration for a BWP/Cell by transmitting the DCI on the BWP/Cell. Alternatively, the base station 104 may transmit the DCI that is addressed to an RNTI. In yet other implementations, the base station 104 may transmit an RRC message that indicates a new FFP configuration.
[0099] To configure the UE 102 with an FFP configuration or to change the FFP configuration to a new FFP configuration for a physical or logical parameter, the base station 104 starts a timer. When the timer is running, the base station 104 cannot change the FFP configuration. After the timer expires or stops running, the base station 104 can change the FFP configuration.
[00100] In some implementations, the UE 102 may transmit LBT conditions to the base station 104, such as the number of LBT failures or the minimum energy level detected during one or more LBT time periods. The base station 104 may then determine a new FFP configuration based on the LBT conditions to reduce the amount of LBT failures for the UE.
[00101] In addition to changing the FFP configuration, the base station 104 may change the start of fixed frames. To change the start of the fixed frames, the base station 104 may transmit an offset to the start of the current fixed frame. For example, the offset can be N symbols/slots/subframes/frames, etc. from the current fixed frame. The offset can be an absolute position such as a specific symbol/slot/subframe/frame etc. which can be identified by a unique number. Additionally or alternatively, the offset may be a relative position compared to the position of the start of the next fixed frame. A positive value may delay the start of the next fixed frame by N symbols/slots/subframes/frames and a negative value moves the start of the next fixed frame N symbols/slots/subframes/frames earlier. Fig. 16 illustrates a timing diagram 1600 indicating the start positions of fixed frames in an FBE communication scheme when the base station 104 transmits information to the UE 102 to change the start position of fixed frames from a current fixed frame timing 1630. As shown in Fig. 16, the start of the next fixed frame may be moved up or delayed based on the offset 1610, 1620 provided by the base station 104.
[00102] Fig. 17 illustrates an example method 1700 for survival time scheduling when transmitting IIOT data on a communication channel. The method 1700 is implemented in a user device such as the UE 102 operating on either licensed on unlicensed bands. The UE 102 may obtain an indication of a survival time period from the base station 104 or from a default survival time period stored at the UE 102.
[00103] At block 1702, the UE 102 generates a data packet associated with a QoS flow having a timestamp associated with the data packet/QoS flow indicating an activation time, such as when a previous uplink or downlink transmission is received resetting a survival timer or when any other suitable event occurs which could cause the survival timer to reset (e.g., in event 304 in Fig. 3, event 404 in Fig. 4, and event 504 in Fig. 5). The UE 102 may also start the survival timer at the activation time, where the survival timer expires at the survival timeout when the survival time period elapses.
[00104] Then at block 1704, the UE 102 schedules transmission of the data packet/QoS flow to the base station 104 in accordance with the timestamp and the survival time period corresponding to the amount of time in which the flow can persist without messaging.
Scheduling the transmission of the data packet/QoS flow can include (a) transmitting a scheduling request that indicates a priority level for the pending uplink data that is reflective of the remaining survival time period and/or (b) transmitting the uplink data packet/QoS flow on an air interface resource prior to the survival timeout. In some implementations, the UE 102 determines the remaining survival time period for the data packet/QoS flow based on the survival time period, the associated timestamp, and/or the current time. More specifically, the UE 102 may identify a survival timeout as the sum of the timestamp and the survival time period. The UE 102 may determine the difference between the survival timeout and the current time as the remaining survival time period.
[00105] In some implementations, the UE 102 may increase the priority level for a data packet/QoS flow in response to determining that the remaining survival time period is less than a threshold period of time. The UE 102 then transmits scheduling requests for scheduling transmission of data packet/QoS flows to the base station 104 in accordance with the corresponding priority levels for the data packets/QoS flows. For example, scheduling requests for data packets/QoS flows having higher priority levels may be transmitted to the base station 104 before scheduling requests for data packets/QoS flows having lower priority levels.
[00106] In some implementations, such as when uplink transmission is scheduled on unlicensed carriers, the threshold period of time may take into account CCA time periods such as the amount of time it takes to perform an LBT procedure, so that the data packet is scheduled for transmission with enough time to perform the LBT procedure. The threshold period of time may also take into account the COT time period, such that the threshold period of time may be the sum of the LBT time period and the COT time period. In other implementations, the threshold period of time may be the sum of two LBT time periods and two COT time periods so that there is enough time for one LBT failure, the sum of three LBT time periods and three COT time periods, etc.
[00107] In other implementations, the UE 102 receives an uplink grant from the base station which may only be used if the data packet/QoS flow or LCHs including the data packet/QoS flow has/have a remaining survival time period that is less than a threshold period of time. In yet other implementations, the UE 102 transmits scheduling requests for data packets/QoS flows having a remaining survival time period that is less than a threshold period of time.
[00108] In yet other implementations, the UE 102 receives a resource associated with a priority level from the base station 104, where when data packets/QoS flows are transmitted from the UE 102 to the base station 104 via the resource, the base station 104 is notified that the remaining survival time period for the data packet/QoS flow is about to expire. For a data packet/QoS flow/LCH having the same priority level as the priority level associated with the resource and having a remaining survival time period that is less than a threshold period of time, the UE 102 transmits a scheduling request for the data packet/QoS flow/LCH to the base station 104 via the first resource or transmits a preamble to the base station 104 via the first resource when the first resource is a random access resource.
[00109] In any event, at block 1706, the UE 102 transmits data packets/QoS flows in accordance with the scheduling arranged by the base station 104 (e.g., in event 312 in Fig. 3, event 411 in Fig. 4, event 512 in Fig. 5, event 612 in Fig. 6, event 709 in Fig. 7, event 814 in Fig. 8, event 909 in Fig. 9, and event 1016 in Fig. 10). [00110] Fig. 18 illustrates an example method 1800 for UE-initiated COT when transmitting IIOT data on a communication channel. The method 1800 is implemented in a user device such as the UE 102 operating on either licensed on unlicensed bands. At block 1802, the UE 102 receives an indication from the base station 104 of a first FFP configuration for a first respective physical or logical parameter (e.g., in event 1204 of Fig. 12). The UE 102 may receive an SIB or a dedicated message such as RRC Setup, RRC Resume, RRC Reestablishment, or RRC Reconfiguration which includes the first FFP configuration. The first FFP configuration may include a first fixed frame start position, a first fixed frame size, and/or a first fixed frame period.
[00111] At block 1804, the UE 102 receives an indication from the base station 104 of a second FFP configuration for a second respective physical or logical parameter (e.g., in event 1204 of Fig. 12). The UE 102 may receive an SIB or a dedicated message such as RRC Setup, RRC Resume, RRC Reestablishment, or RRC Reconfiguration which includes the second FFP configuration. The second FFP configuration may be different from the first FFP configuration and may include a second fixed frame start position, a second fixed frame size, and/or a second fixed frame period, where any of the second fixed frame start position, a second fixed frame size, and/or a second fixed frame period may be different from the first fixed frame start position, first fixed frame size, and/or first fixed frame period.
[00112] Then at block 1806, the UE 102 transmits data in accordance with the first FFP configuration for the first respective physical or logical parameter or the second FFP configuration for the second respective physical or logical parameter. For the first respective physical or logical parameter, the UE 102 may transmit data in a first set of fixed frames according to the first FFP configuration using the first respective physical or logical parameter. For the second respective physical or logical parameter, the UE 102 may transmit data in a second set of fixed frames according to the second FFP configuration using the second respective physical or logical parameter.
[00113] More specifically, for each respective physical or logical parameter having an FFP configuration, the UE 102 performs a channel access procedure such as an LBT procedure (e.g., in event 1206 in Fig. 12) prior to or at the beginning of a fixed frame according to the FFP configuration. If the LBT procedure fails, the UE 102 does not transmit data using the particular physical or logical parameter during the fixed frame (e.g., in event 1210 in Fig. 12). Then, after the end of the fixed frame, the UE 102 may again perform the LBT procedure. On the other hand, if the LBT procedure is successful, the UE 102 transmits data to the base station 104 using the particular physical or logical parameter in the fixed frame during the COT for the fixed frame (e.g., in event 1214 in Fig. 12).
[00114] In some implementations, fixed frames begin at the symbol/slot/subframe in which the UE 102 has a configured uplink grant to transmit data. LBT procedures for different physical or logical parameters may be independent of each other, such that there may be multiple LBT processes running at the same time, and the UE 102 may perform an LBT procedure for one physical or logical parameter while the LBT procedure for another physical or logical parameter failed and the UE 102 is unable to transmit data during the fixed frame for the other physical or logical parameter.
[00115] Embodiments of the techniques described in the present disclosure may include any number of the following aspects, either alone or combination:
[00116] 1. A method in a UE for transmitting industrial Internet of Things (IIOT) data on a communication channel, the method comprising: receiving, by the processing hardware in a UE from a base station, an indication of a first fixed frame periodicity (FFP) configuration for a frame based equipment (FBE) communication scheme for a first respective physical or logical parameter; receiving, by the processing hardware from the base station, an indication of a second FFP configuration for a second respective physical or logical parameter, the second FFP configuration different from the first FFP configuration; and transmitting, by the processing hardware to the base station, data in accordance with the first FFP configuration for the first respective physical or logical parameter or the second FFP configuration for the second respective physical or logical parameter.
[00117] 2. The method according to aspect 1, wherein transmitting data includes: performing, by the processing hardware, a listen-before-talk (LBT) procedure with the base station for the first respective physical or logical parameter.
[00118] 3. The method according to any one of the preceding aspects, wherein performing the LBT procedure includes performing, by the processing hardware, the LBT procedure for the first respective physical or logical parameter at a beginning of a fixed frame indicated by the first FFP configuration for the first respective physical or logical parameter.
[00119] 4. The method according to any one of the preceding aspects, wherein performing the LBT procedure includes performing, by the processing hardware, the LBT procedure for the first respective physical or logical parameter before a beginning of a fixed frame indicated by the first FFP configuration for the first respective physical or logical parameter.
[00120] 5. The method according to any one of the preceding aspects, wherein performing the LBT procedure includes: performing, by the processing hardware, a first LBT procedure with the base station for the first respective physical or logical parameter; in response to determining the LBT procedure has failed: not transmitting, by the processing hardware to the base station, the data in a first fixed frame indicated by the first FFP configuration; performing, by the processing hardware, a second LBT procedure with the base station after an end of the first fixed frame; wherein in response to determining that the second LBT procedure has succeeded, transmitting, by the processing hardware to the base station, the data comprises transmitting in a second fixed frame indicated by the first FFP configuration.
[00121] 6. The method according to any one of the preceding aspects, wherein transmitting data further includes: in response to determining the LBT procedure has failed: not transmitting, by the processing hardware to the base station, the data in a fixed frame indicated by the first FFP configuration; and performing, by the processing hardware, another LBT procedure with the base station after an end of the fixed frame.
[00122] 7. The method according to any one of the preceding aspects, wherein transmitting data further includes: in response to determining that the LBT procedure has succeeded, transmitting, by the processing hardware to the base station, the data in a fixed frame indicated by the first FFP configuration.
[00123] 8. The method according to any one of the preceding aspects, wherein performing the LBT procedure includes: performing, by the processing hardware, a first LBT procedure with the base station for the first respective physical or logical parameter; and performing, by the processing hardware, a second LBT procedure with the base station for the second respective physical or logical parameter, the second LBT procedure performed independently of the first LBT procedure.
[00124] 9. The method according to any one of the preceding aspects, further comprising: in response to determining the first LBT procedure has failed for the first respective physical or logical parameter, performing, by the processing hardware, the second LBT procedure for the second respective physical or logical parameter during a fixed frame indicated by the second FFP configuration for the second respective physical or logical parameter that overlaps (in time) with a fixed frame indicated by the first FFP configuration for the first respective physical of logical parameter after the first LBT procedure has failed for the first respective physical or logical parameter.
[00125] 10. The method according to any one of the preceding aspects, further comprising: receiving, by the processing hardware from the base station, a dynamic grant and an indication of a third FFP configuration; performing, by the processing hardware, an LBT procedure with the base station for the dynamic grant; and in response to determining the LBT procedure has succeeded, determining, by the processing hardware, a beginning of a next fixed frame using the third FFP configuration; and transmitting, by the processing hardware, the data in the next fixed frame.
[00126] 11. The method according to any one of the preceding aspects, further comprising: receiving, by the processing hardware from the base station, information indicating a change in the first FFP configuration for the first respective physical or logical parameter.
[00127] 12. The method according to any one of the preceding aspects, further comprising: transmitting, by the processing hardware, LBT conditions to the base station for determining a new FFP configuration based on the LBT conditions.
[00128] 13. The method according to any one of the preceding aspects, further comprising: receiving, by the processing hardware from the base station, information indicating a change in a start position of fixed frames for the first respective physical or logical parameter.
[00129] 14. The method according to any one of the preceding aspects, wherein receiving information indicating a change in the first FFP configuration or a change in a start position of fixed frames for the first respective physical or logical parameter includes receiving: one or more radio resource control (RRC) messages; one or more messages containing downlink control information (DCI); or one or more messages including medium access control (MAC) control elements.
[00130] 15. The method according to any one of the preceding aspects, wherein the indication of the first or the second FFP configuration includes a frame size or a frame start position.
[00131] 16. The method according to any one of the preceding aspects, further comprising: receiving, by the processing hardware from the base station, an indication of a first configured grant having a first configured grant periodicity; and receiving an indication of a second configured grant having a second configured grant periodicity.
[00132] 17. The method according to any one of the preceding aspects, wherein at least one of: the first configured grant periodicity is the same as or a multiple of the first FFP configuration, the second configured grant periodicity is the same as or a multiple of the second FFP configuration, or the second configured grant periodicity is a multiple of the first configured grant periodicity.
[00133] 18. The method according to any one of the preceding aspects, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first priority level; and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second priority level.
[00134] 19. The method according to any one of the preceding aspects, further comprising: performing, by the processing hardware, an LBT procedure with the base station for the second priority level which is lower than the first priority level; and in response to determining that the LBT procedure has succeeded, transmitting, by the processing hardware, data having the first priority level in a fixed frame indicated by the second FFP configuration for the second priority level.
[00135] 20. The method according to any one of the preceding aspects, further comprising: starting, by the processing hardware, a timer for the first priority level; receiving, by the processing hardware from the base station, information indicating a change in the first FFP configuration; and waiting, by the processing hardware, to change the first FFP configuration until the timer expires or stops running.
[00136] 21. The method according to any one of the preceding aspects, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first beam; and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second beam. [00137] 22. The method according to any one of the preceding aspects, further comprising: changing, by the processing hardware, from the first beam to the second beam; and determining, by the processing hardware, a next fixed frame using the second FFP configuration.
[00138] 23. The method according to any one of the preceding aspects, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first bandwidth part (BWP); and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second BWP.
[00139] 24. The method according to any one of the preceding aspects, further comprising: changing, by the processing hardware, an active BWP from the first BWP to the second BWP; and determining, by the processing hardware, a next fixed frame using the second FFP configuration.
[00140] 25. The method according to any one of the preceding aspects, further comprising: starting, by the processing hardware, a timer for an active BWP corresponding to the first or second BWP; receiving, by the processing hardware from the base station, information indicating a change in the first or second FFP configuration for the active BWP; and waiting, by the processing hardware, to change the first or second FFP configuration for the active BWP until the timer expires or stops running.
[00141] 26. The method according to any one of the preceding aspects, further comprising: resetting, by the processing hardware, the timer in response to changing the active BWP.
[00142] 27. The method according to any one of the preceding aspects, further comprising: starting, by the processing hardware, a first timer for the first BWP; starting, by the processing hardware, a second timer for the second BWP; receiving, by the processing hardware from the base station, information indicating a change in the first or second FFP configuration for the first or second BWP; and waiting, by the processing hardware, to change the first or second FFP configuration until the respective first or second timer expires or stops running.
[00143] 28. The method according to any one of the preceding aspects, wherein: receiving an indication of a first FFP configuration for a first respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the first FFP configuration for a first cell; and receiving an indication of a second FFP configuration for a second respective physical or logical parameter includes receiving, by the processing hardware from the base station, the indication of the second FFP configuration for a second cell.
[00144] 29. The method according to any one of the preceding aspects, further comprising: starting, by the processing hardware, a timer for an active cell corresponding to the first or second cell; receiving, by the processing hardware from the base station, information indicating a change in the first or second FFP configuration for the active cell; and waiting, by the processing hardware, to change the first or second FFP configuration for the active cell until the timer expires or stops running.
[00145] 30. The method according to any one of the preceding aspects, further comprising: resetting, by the processing hardware, the timer in response to changing an active BWP or deactivating the active cell.
[00146] 31. A method in a UE for transmitting industrial Internet of Things (IIOT) data on a communication channel, the method comprising: generating, by the processing hardware, a data packet having an associated timestamp, the data packet associated with a flow; scheduling, by the processing hardware, transmission of the data packet to a base station in accordance with the associated timestamp and a survival time period corresponding to a time period in which the flow can persist without messaging; and transmitting, by the processing hardware, the data packet in accordance with the scheduling.
[00147] 32. The method according to aspect 31, wherein scheduling transmission of the data packet comprises: setting, by the processing hardware, a priority level for the data packet in accordance with the associated timestamp and the survival time period; and scheduling, by the processing hardware, in accordance with the priority level.
[00148] 33. The method according to either one of aspect 31 or aspect 32, further comprising: receiving, by the processing hardware from the base station, an uplink grant; wherein the scheduling comprises determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and wherein the transmitting comprises transmitting, by the processing hardware to the base station, the data packet via the uplink grant when the remaining survival time period is less than a threshold period of time. [00149] 34. The method according to any of the aspects 31-33, wherein scheduling the transmission of the data packet comprises: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and transmitting, by the processing hardware to the base station, an uplink scheduling request when the remaining survival time period is less than a threshold period of time
[00150] 35. The method according to any of the aspects 31-34, wherein: scheduling the transmission of the data packet comprises determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and transmitting the data packet comprises adjusting, by the processing hardware, a transmit power when the remaining survival time period is less than a threshold period of time.
[00151] 36. The method according to any of the aspects 31-35, wherein scheduling the transmission of the data packet comprises: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and adjusting, by the processing hardware, a time delay between transmissions when the remaining survival time period is less than a threshold period of time.
[00152] 37. The method according to any of the aspects 31-36, wherein adjusting the time delay includes adjusting, by the processing hardware, a physical random access channel (PRACH) backoff.
[00153] 38. The method according to any of the aspects 31-37, further comprising: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and adjusting, by the processing hardware, the flow to carriers having the lowest latency when the remaining survival time period is less than a threshold period of time.
[00154] 39. The method according to any of the aspects 31-38, wherein scheduling transmission of the data packet to a base station in accordance with the associated timestamp and the survival time period includes: receiving, by the processing hardware from the base station, an indication of a resource associated with a certain priority level; in response to determining that the data packet or a logical channel including at least a portion of the data packet has the certain priority level and is pending for transmission for more than a threshold period of time relative to the survival time period, transmitting, by the processing hardware to the base station, a scheduling request for the data packet or the logical channel via the resource.
[00155] 40. The method according to any of the aspects 31-39, wherein: the scheduling request is a first scheduling request, the data packet is a first data packet, the logical channel is a first logical channel, and the priority level is a first priority level; the method further comprising: determining that the transmission of the first scheduling request would collide with a second scheduling request for transmitting a second data packet or on a second logical channel including at least a portion of the second data packet, the second data packet or second logical channel having a second priority level lower than the first priority level; and transmitting, by the processing hardware to the base station, the first scheduling request having a higher priority level.
[00156] 41. The method according to any of the aspects 31-40, further comprising: delaying, by the processing hardware to the base station, transmission of the second scheduling request.
[00157] 42. The method according to any of the aspects 31-41, wherein the resource is a random access resource, and further comprising: transmitting, by the processing hardware to the base station, a preamble via the random access resource.
[00158] 43. The method according to any of the aspects 31-42, wherein scheduling transmission of the data packet includes: transmitting, by the processing hardware to the base station, a medium access control (MAC) control element indicating a logical channel or priority level which has been pending for transmission for more than a threshold period of time relative to the survival time period.
[00159] 44. The method according to any of the aspects 31-43, further comprising: determining, by the processing hardware, a remaining survival time period based on the survival time period and the associated timestamp; and prioritizing, by the processing hardware, a buffer status report when the remaining survival time period is less than a threshold period of time.
[00160] 45. The method according to any of the aspects 31-44, wherein: the data packet is a first data packet, the timestamp is a first timestamp, and the flow is a first flow; the method further comprising: generating, by the processing hardware, a second data packet having a second associated timestamp, the second data packet associated with a second flow; determining, by the processing hardware, a first remaining survival time period based on the survival time period and the first timestamp; determining, by the processing hardware, a second remaining survival time period based on the survival time period and the second timestamp; scheduling, by the processing hardware, transmission of the first data packet to the base station based on the first remaining survival time period; and scheduling, by the processing hardware, transmission of the second data packet to the base station based on the second remaining survival time period.
[00161] 46. The method of according to any of the aspects 31-45, wherein the associated timestamp indicates a previous instance in which an uplink or downlink data packet was received.
[00162] 47. The method according to any of the aspects 31-46, further comprising: determining, by the processing hardware, the survival time period based on a time period for performing a listen-before-talk (LBT) procedure.
[00163] 48. The method according to any of the aspects 31-47, further comprising: determining, by the processing hardware, the survival time period based on a channel occupancy time (COT) period.
[00164] 49. The method according to any of the aspects 31-48, further comprising: determining, by the processing hardware, the survival time period based on a combination of the time period for performing the listen-before-talk LBT procedure and the COT period.
[00165] 50. The method according to any of the aspects 31-49, wherein the COT period is within a fixed frame in a frame based equipment (FBE) communication scheme in accordance with a fixed frame periodicity (FFP) configuration.
[00166] 51. The method according to any of the aspects 31-49, further comprising: determining, by the processing hardware, that data on a logical channel or radio bearer included in the data packet is pending for transmission; starting, by the processing hardware, a timer set to a time period which is less than the survival timer period; wherein scheduling the transmission of the data packet comprises: in response to determining that the timer expired without transmitting the data, transmitting, by the processing hardware to the base station, an uplink scheduling request or a preamble.
[00167] 52. The method according to any of the aspects 31-51, wherein scheduling the transmission of the data packet further comprises: in response to determining that the timer expired without transmitting the data, transmitting, by the processing hardware to the base station, a media access layer (MAC) control element (CE) to report the logical channel or radio bearer associated with the timer.
[00168] 53. A user device comprising processing hardware configured to execute a method according to any of the preceding aspects.
[00169] The following additional considerations apply to the foregoing discussion.
[00170] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media- streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[00171] Certain implementations are described in this disclosure as including logic or a number of components or modules. Modules may can be software modules (e.g., code stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application- specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
[00172] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.
[00173] Upon reading this disclosure, those of skill in the art will appreciate, through the principles disclosed herein, still additional alternative structural and functional designs for supporting transmission of IIOT data. Thus, while particular implementations and applications have been illustrated and described, it is to be understood that the disclosed implementations are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those of ordinary skill in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.