Method for providing self-organized monitoring time for repeated authorization and user equipment power saving

Abstract

A method, an apparatus, and a computer program product are provided. In the context of a method, the method includes identifying one or more scheduled transmission intervals having a start time and an end time based on initial scheduling information received from a network node, the one or more scheduled transmission intervals are longer than a threshold duration for one or more uplink transmissions by the user equipment, where the one or more scheduled transmission intervals include a head-end portion and a tail-end portion, and the tail-end portion accommodates the monitoring period. The method comprises transmitting at least one subsequent uplink transmission corresponding to a respective subsequent scheduled transmission interval to the network node, respectively, within a monitoring period prior to the end time, in accordance with subsequent scheduling information received from the network node.

Description

Technical Field

[0001] An example embodiment is generally directed to providing a user device ad hoc monitoring time (or tail activity duration) for repeated or a series of granted transmission or reception assignments to save user device energy. Background Art

[0002] User devices are typically configured with grants prior to transmission. Typically, this can cause inefficiencies because the early grants allocated may not be appropriately sized and prioritized. For example, video traffic generated by an extended reality service in the uplink has periodic burst arrivals with variable burst sizes. It is difficult to determine in advance the correct size that the extended reality data will be, which can cause a waste of radio resources (due to the resource size of the repeated grant being too large) or an inability to achieve the delay budget (due to the insufficient size of the resource for the repeated grant). Currently, the discontinuous receive inactivity timer is started at the time of reception of a new physical downlink shared channel grant, so that additional data may be scheduled next. Compared to previous methods, a method is needed to provide grants closer to the time of transmission. Summary of the invention

[0003] In one or more embodiments, a user equipment (120) is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the processor, cause the user equipment (120) to identify (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) is also enabled to send (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) to the network node (140) within the monitoring period (610a..610n) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0004] In one or more embodiments, a network node (140) is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions, which when executed by the processor, causes the network node (140) to configure (1910) a user equipment (120) with parameters and indicators (1500), the parameters and indicators (1500) instructing the user equipment (120) to identify a first scheduled transmission interval (310a) having a start time (315) and an end time (316) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). One or more scheduled transmission intervals (310a..310n) of time (317), wherein according to initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the network node (140) is also caused to receive (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within the monitoring period (610) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0005] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (120) and includes identifying (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) is also enabled to send (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) to the network node (140) within the monitoring period (610a..610n) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0006] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (140) and includes configuring (1910) a user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify one or more scheduled transmissions having a start time (315) and an end time (317) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). intervals (310a..310n), wherein according to initial scheduling information (340a), one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by a user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the network node (140) is also caused to receive (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within the monitoring period (610) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0007] In one or more embodiments, a non-transitory computer-readable storage medium is provided, comprising computer instructions that, when executed by a user equipment (120), cause the user equipment (120) to identify (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) is also enabled to send (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) to the network node (140) within the monitoring period (610a..610n) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0008] In one or more embodiments, a non-transitory computer-readable storage medium is provided, comprising computer instructions that, when executed by a network node (140), cause the network node (140) to configure (1910) a user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify a first scheduled transmission interval (310a) having a start time (315) and an end time (316) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). 7), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head end portion (320) and a tail end portion (330), and the tail end portion (330) accommodates the monitoring period (610). In one or more embodiments, the network node (140) is also caused to receive (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within the monitoring period (610) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0009] In one or more embodiments, a user equipment (120) is provided, comprising means for identifying (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) further comprises means for sending (1920) to the network node (140) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to a corresponding subsequent scheduled transmission interval (310b..310n) within a monitoring period (610a..610n) before an end time (317) based on subsequent scheduling information (340b..340n) received from the network node (140).

[0010] In one or more embodiments, a network node (140) is provided, comprising means for configuring (1910) a user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify one or more scheduled transmission intervals (310a) having a start time (315) and an end time (317) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). a..310n), wherein according to the initial scheduling information (340a), one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates the monitoring period (610). In one or more embodiments, the network node (140) further comprises means for receiving (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to a corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within a monitoring period (610) before an end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140). BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Having generally described certain example embodiments of the present disclosure above, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0012] Figure 1 is a block diagram of a system including both a base station and a user equipment configured to communicate via at least uplink and downlink transmissions according to an example embodiment of the present disclosure.

[0013] Figure 2 According to an exemplary embodiment of the present disclosure Figure 1 Block diagram of an example communication system in which the system may be deployed.

[0014] Figure 3 The problem identified by the present disclosure during a first scheduled transmission interval is shown.

[0015] Figure 4 A scheduling problem identified by the present disclosure when repetition occurs during a first transmission interval is shown and is addressed by the present disclosure.

[0016] Figure 5 It is shown that a problem identified by the present disclosure occurs when the first scheduled transmission interval includes repetitions.

[0017] Figure 6 Issues identified by the present disclosure regarding retransmission scenarios after repetition are shown.

[0018] Figure 7 The problem identified by the present disclosure is shown when scheduling a first transmission interval may result from a configured grant.

[0019] Figure 8 The issues identified by the present disclosure regarding cell discontinuous transmission scenarios are illustrated.

[0020] Figures 9A to 9E Issues identified by the present disclosure regarding Physical Uplink Shared Channel (PUSCH) allocation are shown.

[0021] Fig.10 An example solution to the problem created by the first scheduled transmission interval according to an example embodiment of the present disclosure is shown.

[0022] Fig.11 An example solution to a problem resulting from a first scheduled transmission interval including repetitions according to an example embodiment of the present disclosure is shown.

[0023] Fig.12 An example solution to the problem in a retransmission scenario according to an example embodiment of the present disclosure is shown.

[0024] Fig.13 An example scenario is shown that can accommodate monitoring time according to an example embodiment of the present disclosure.

[0025] Figures 14A-14B An example retransmission scenario is shown that can accommodate monitoring time according to an example embodiment of the present disclosure.

[0026] Fig.15 An example solution is shown when the first scheduled transmission interval may be caused by a configured grant according to an example embodiment of the present disclosure.

[0027] Fig.16 An example solution in a cell discontinuous reception scenario according to an example embodiment of the present disclosure is shown.

[0028] Fig.17 According to an exemplary embodiment of the present disclosure Fig.12 The solution adds details to the illustration.

[0029] Fig.18 A solution to the physical uplink shared channel allocation problem according to an example embodiment of the present disclosure is shown.

[0030] Fig.19 is a flow chart illustrating the functionality of a user equipment and / or a network node according to an example embodiment of the present disclosure.

[0031] Fig. 20 is a signaling diagram illustrating between a user equipment and a network node according to an example embodiment of the present disclosure.

[0032] Fig.21 is a flow chart illustrating operations such as performed by UE 120 according to example embodiments of the present disclosure.

[0033] Fig. 22 is a flowchart illustrating operations performed by the NW node 140 according to an example embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] Some embodiments of the present disclosure will now be described more fully with reference to the accompanying drawings, some but not all of which are shown in the accompanying drawings. In fact, various embodiments may be embodied in many different forms and should not be construed as limited to the embodiments described herein; on the contrary, these embodiments are provided so that the present disclosure will satisfy applicable legal requirements. Similar reference numerals always represent similar elements. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data that can be sent, received, and / or stored in accordance with embodiments of the present disclosure. Therefore, the use of any such terms should not be viewed as limiting the spirit and scope of the embodiments of the present disclosure.

[0035] Additionally, as used herein, the term "circuitry" refers to (a) a hardware circuit implementation only (e.g., an implementation in analog circuitry and / or digital circuitry); (b) a combination of circuitry and (multiple) computer program products, including software and / or firmware instructions stored on one or more computer-readable memories, which work together to cause the device to perform one or more functions described herein; and (c) circuitry, such as, for example, (multiple) microprocessors or portions of (multiple) microprocessors, which require software or firmware to operate even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of the term herein, including in any claims. As a further example, as used herein, the term "circuitry" also includes an implementation including one or more processors and / or portions thereof and accompanying software and / or firmware. As another example, as used herein, the term "circuitry" also includes, for example, a baseband integrated circuit or application processor integrated circuit for a mobile phone or similar integrated circuits in a server, cellular network equipment, other network equipment (such as a core network device), a field programmable gate array, and / or other computing devices.

[0036] As used herein, the term "computer-readable medium" refers to non-transitory storage hardware, non-transitory storage devices, or non-transitory computer system memory that can be accessed by a controller, a microcontroller, a computing system, or a module of a computing system to store computer executable instructions or software programs thereon. Non-transitory "computer-readable medium" can be accessed by a computing system or a module of a computing system to obtain and / or execute computer executable instructions or software programs encoded on the medium. Examples of non-transitory computer-readable media can include, but are not limited to, one or more types of hardware memory, non-transitory tangible media (e.g., one or more magnetic storage disks, one or more optical disks, one or more universal synchronous bus (USB) flash drives), computer system memory, or random access memory (such as dynamic random access memory (DRAM), static random access memory (SRAM), extended data output random access memory (EDO RAM), etc.

[0037] like Figure 1 As shown, a system 100 is provided according to an example embodiment to facilitate uplink transmission from a user equipment 120. Although the system can be configured in various ways, the system of one embodiment is Figure 11 and includes a user equipment 120 and a network node 140 configured to communicate via uplink and downlink transmission and reception beams. Although one user equipment and one network node are depicted, the system may include and the user equipment 120 and / or the network node 140 may communicate with additional user equipment and network nodes. In one or more other embodiments, the user equipment 120 and the network node 140 may be configured to support, for example, 4G, 5G Advanced, or 6G. In one or more embodiments, the system 100 may support carrier aggregation and / or dual connectivity. As described below, the system is configured to send messages and reports, such as reconfiguration messages, radio resource control messages, MAC control unit messages, downlink control information messages, physical uplink shared channel messages, physical downlink control channel messages, etc.

[0038] The data transmitted via the uplink and downlink beams between the user equipment 120 and the network node 140 may be a variety of data, including but not limited to digital image data (including video data, audio data) and data provided by sensors, radars, telescopes, and radio receivers. In at least some cases, the data is encoded prior to transmission of the data via the uplink and downlink beams and decoded upon reception. The resulting data received may be used for a variety of purposes, including presentation to a user, storage of the data for subsequent use, and / or supplying the data to one or more applications, such as applications that perform statistical reasoning on the data for a variety of purposes, including object recognition, image classification, spectrum sensing, speech transcription, and / or prediction or detection of events.

[0039] Figure 1 The user equipment 120 (also referred to as UE, user equipment, user terminal, terminal device, etc.) shows a type of device where resources on the air interface are allocated and assigned. The user equipment 120 generally refers to a portable computing device, including wireless mobile communication devices that operate with or without a subscriber identity module (SIM), including but not limited to the following types of devices: mobile stations (mobile phones), smart phones, personal digital assistants (PDAs), mobile phones, devices using wireless modems (alarms or measuring devices, etc.), laptops and / or touch screen computers, tablets, game consoles, notebooks, and multimedia devices. The user equipment 120 may also be a device with the ability to operate in an Internet of Things (IoT) network, which is a scenario in which objects are provided with the ability to transmit data over a network without human-to-human or human-to-computer interaction. The user equipment 120 (or in some embodiments, a layer 3 relay node) is configured to perform one or more user equipment functions. The user equipment 120 may also be referred to as a subscriber unit, a mobile station, a remote terminal, an access terminal, a user terminal, or a user equipment (UE), to name just a few names or devices.

[0040] Figure 1 The network node 140 may include, for example, a remote radio head (RRH), a transmission reception point (TRP), an access point, a node base station (e.g., eNB, gNB) or other transmission sources. The network node 140 may be configured to communicate with the user equipment 120 via a network.

[0041] Figure 2 An example apparatus 200 is depicted that may be configured to function as a user equipment 120 or a network node 140. Figure 2 As shown, the device includes a processing circuit system 220, a memory 240 and a communication interface 260, which can be associated with or can communicate with the processing circuit system 220, the memory 240 and the communication interface 260. The processing circuit system 220 can communicate with the memory device 240 via a bus to transfer information between components of the device. The memory device can be non-transient and can include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device can be an electronic storage device (e.g., a computer-readable storage medium) including a gate configured to store data (e.g., bits), which can be obtained by a machine (e.g., a computing device such as a processing circuit system). The memory device can be configured to store information, data, content, applications, instructions, etc., so that the device can perform various functions according to the exemplary embodiments of the present disclosure. For example, the memory device can be configured to buffer input data for processing by the processing circuit system. Additionally or alternatively, the memory device can be configured to store instructions for execution by the processing circuit system.

[0042] In some embodiments, the device 200 may be embodied in the various computing devices described above. However, in some embodiments, the device may be embodied as a chip or a chipset. In other words, the device may include one or more physical packages (e.g., chips), including materials, components, and / or wires on a structural assembly (e.g., a substrate). The structural assembly may provide physical strength, size savings, and / or limitations on electrical interactions for the component circuitry included thereon. Therefore, in some cases, the device may be configured to implement an embodiment on a single chip or as a single "system on a chip." Therefore, in some cases, a chip or a collection of chips may constitute a component for performing one or more operations to provide the functionality described herein.

[0043] The processing circuit system 220 (also referred to as a processor) can be embodied in a variety of different ways. For example, the processing circuit system can be embodied as one or more of various hardware processing components, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuit systems, including integrated circuits, such as, for example, ASICs (application-specific integrated circuits), FPGAs (field programmable gate arrays), microcontroller units (MCUs), hardware accelerators, special-purpose computer chips, etc. Therefore, in some embodiments, the processing circuit system may include one or more processing cores configured to execute independently. Multi-core processing circuit systems can implement multi-processing within a single physical package. Additionally or alternatively, the processing circuit system may include one or more processors configured in series via a bus to implement independent execution, pipelining, and / or multi-threading of instructions.

[0044] In an example embodiment, the processing circuit system 220 may be configured to execute instructions stored in the memory device 240 or accessible by the processing circuit system. Additionally or alternatively, the processing circuit system may be configured to perform hard-coded functions. Therefore, whether configured by hardware or software methods, or by a combination thereof, the processing circuit system may represent an entity (e.g., physically embodied in a circuit system) that is capable of performing operations according to embodiments of the present disclosure while being configured accordingly. Therefore, for example, when the processing circuit system may be embodied as an ASIC, FPGA, etc., the processing circuit system may be specially configured hardware for performing the operations described herein. Alternatively, as another example, when the processing circuit system may be embodied as an executor of an instruction, the instruction may specifically configure the processor to perform the algorithm and / or operation described herein when the instruction is executed. However, in some cases, the processing circuit system may be a processor of a specific device (e.g., an image or video processing system) that is configured to adopt an embodiment by another configuration of the processing circuit system of instructions for performing the algorithm and / or operation described herein. The processing circuitry may include, among other things, a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processing circuitry.

[0045] The communication interface 260 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, and the communication interface 260 is configured to receive and / or send data, including media content in the form of video or image files, one or more audio tracks, etc. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communication with a wireless communication network. Additionally or alternatively, the communication interface may include a circuit system for interacting with (multiple) antennas to cause the transmission of signals via (multiple) antennas or the reception of signals received via (multiple) antennas. In some environments, the communication interface may alternatively or also support wired communications. Thus, for example, the communication interface may include a communication modem and / or other hardware / software to support communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.

[0046] Now go to Figure 3 , illustrating a problem identified by the present disclosure during a first scheduled transmission interval. In one or more embodiments, box 310 illustrates a first scheduled transmission interval 310a. The first scheduled transmission interval 310a may be a transmission interval that has been indicated / signaled (scheduled) to the UE, but the UE has not yet completed performing the transmission during the first scheduled transmission interval 310a. The user equipment 120 may be blocked from scheduling new transmissions during the first scheduled transmission interval 310a. The first scheduled transmission interval 310a has a start time 315a and an end time 317a. The first scheduled transmission interval 310a may have a long expected grant interval (LAGI). During the long expected grant interval (LAGI), the user equipment (UE) 120 may be blocked from new uplink or downlink transmissions due to already scheduled transmissions. In one example, the first scheduled transmission interval 310a may include a physical uplink shared channel repetition that performs a hybrid automatic repeat request (HARQ) process. In another example, the UE 120 may be blocked from performing new PUSCH transmissions during a time division duplex (TDD) time slot allocated for downlink (DL) transmissions ( 420 b - 420 n ).

[0047] The user equipment 120 may monitor scheduled transmission information (eg, uplink or downlink information) (340a) during a downlink control channel monitoring opportunity, and the user equipment 120 may receive downlink control information (DCI) 340a on a physical downlink control channel (PDCCH) to schedule future user equipment transmissions.

[0048] In one or more embodiments, after receiving the first scheduling information (e.g., downlink control information) 340a during the head portion 320 of the first scheduled transmission interval 310a, the UE may be blocked from performing new PUSCH transmissions (e.g., 420b to 420n), thereby reducing transmission efficiency. Therefore, when the first transmission scheduling information (i.e., downlink control information) 340a is received during the head portion 320 of the first scheduled transmission interval 310a, it may be necessary to advance uplink or downlink (UL / DL) scheduling. According to an embodiment of the present disclosure, it may be more efficient for the monitoring time to be scheduled during the tail portion 330 of the first scheduled transmission interval 310a. Such monitoring at the tail portion 330 can allow timely scheduling and also allow sufficient time to utilize new information to determine when to schedule subsequent physical uplink shared channels (e.g., 420b to 420n) for transmission.

[0049] Figure 4 The scheduling problem identified when repetition occurs during the first transmission interval is shown. Initially, during the physical downlink control channel monitoring opportunity 410 / 510 (i.e., in the head end portion 320 of the first scheduled transmission interval 310), the user equipment 120 may be scheduled to send a repetition beam during 420a to 420n after receiving an uplink scheduling grant from the network node 140. The discontinuous reception inactivity timer (IAT) may start at the physical downlink control channel grant. During the discontinuous reception inactivity timer (IAT), the user equipment 120 may monitor the transmission scheduling information. Subsequent (e.g., nth) repetition beams 420a to 420n may be scheduled long in advance. For example, the first repetition beam 420 may be scheduled at, for example, K2=2. The user equipment 120 may need to send multiple uplink hybrid automatic repeat request (HARQ) processes (e.g., due to multiple packets or packet fragments). Future repetition bundles 420 (such as PUSCH 420b to 420n) may be scheduled at, for example, K2=2+N*(8-1+12). However, as the number of repetition bundles 420 increases, they must be further scheduled (such as PUSCH 420b to 420n). Therefore, each physical uplink scheduling grant may schedule a repetition bundle 420 for transmission on a physical uplink shared channel (420b to 420n), which may block other new transmissions. In this case, the first scheduled transmission interval 310a may last until the end of the last repetition bundle 420. In this case, any downlink control monitoring opportunity 410 for scheduling PUSCH during the head portion 320 of the first scheduled transmission interval 310 may be inefficient due to the need to schedule it far in advance. Therefore, the present disclosure suggests that it may be more efficient to perform immediate monitoring and scheduling during the tail portion 330 of the first scheduled transmission interval 310 (rather than during the head portion 320).

[0050] Now go to Figure 5 , which illustrates a problem found when the first scheduled transmission interval may be caused by a grant scheduling repetition. For example, when the user equipment 120 may be in the monitoring period 510 until the end of the discontinuous reception inactivity timer. However, since the repetition bundle 420 is scheduled for the remainder of the first scheduled transmission time 310, scheduling it so far in advance may be inefficient. Additional monitoring time may not be scheduled during time periods 520 and 530. During time period 520, the monitoring time may be inefficient because it occurs during the head portion 320 of the first scheduled transmission interval 310. The present disclosure suggests that the monitoring time (for the additional PUSCH grant) can be (relatively) efficiently scheduled during time period 530 because this occurs in the tail portion 330 of the first scheduled transmission period 310a. During time period 540 ( Figure 6 The monitoring time may then occur during time period 550 when a retransmission of the first scheduled transmission interval 310a may be expected. For a physical downlink shared channel scenario, a retransmission may only be expected if a negative acknowledgement is sent by the user equipment 120.

[0051] Now go to Figure 6 , Figure 6 The problem of retransmission scenarios after repetition (e.g., PUSCH) identified by the present disclosure is shown. In one example, the user equipment 120 may receive first scheduling information 340a via downlink control information (DCI) and then send physical uplink shared channel (PUSCH) repetitions during the first scheduled transmission interval 310a. The user equipment 120 may also monitor new or subsequent scheduling information 340b during monitoring periods 510 and 511 until the inactivity timer expires. However, it may be inefficient for the user equipment to monitor subsequent scheduling information 340b (for subsequent PUSCH grants 420b to 420n) during the monitoring period 510. In contrast, it may be more efficient for the user equipment to monitor subsequent scheduling information 340b during the monitoring period 610 during the tail portion 330 of the first scheduled transmission interval 310a, so that the subsequent scheduling information 340b can be up to date.

[0052] After the end of the first scheduled transmission interval 310a, a discontinuous reception retransmission timer 630 (RTT timer) may start running in a subsequent or subsequent scheduled transmission interval 310b. Upon expiration of the discontinuous reception retransmission timer 630, a subsequent monitoring period 550 may occur, wherein the user equipment may monitor for subsequently received scheduling information 340b, such as subsequent downlink control information (DCI) 340a', indicating that a retransmission should be performed for the uncompleted scheduled transmission in the first scheduled transmission interval 310a. However, this may not be valid here because the user equipment 120 may have sent a physical uplink shared channel (PUSCH) repetition for a different hybrid automatic repeat request (HARQ) process in the subsequent scheduled transmission interval 310b. The monitoring period 550 is located in the head end portion 320 of the subsequent scheduled transmission interval 310b, so the user equipment 120 must wait until the end of the subsequent scheduled transmission interval 310b to complete performing the retransmission. Therefore, the present disclosure instead suggests that it may be more efficient for the monitoring time to occur during the tail portion 330 of the subsequent scheduled transmission interval 310b.

[0053] Now go to Figure 7 , the present disclosure points out a problem with a first scheduled transmission interval 310a caused by configured grants. In this case, each of blocks A, B, C, and D within the first scheduled transmission interval 310a can represent a configured grant (311A, 311B, 311C, 311D), where the user equipment 120 may be blocked (325) from performing new or subsequent (dynamic) transmissions on a physical uplink shared channel (PUSCH) 420b to 420n that has not yet been sent. The configured grants A to D can appear consecutively so that they create a long expected grant interval (LAGI), such as the first scheduled transmission interval 310a. The user equipment 120 can monitor the transmission scheduling information during a monitoring time 510, which occurs during the head end portion 320 of the first scheduled transmission interval 310a. However, this is not efficient because the user equipment 120 is blocked from making new transmissions (on the PUSCH) until the transmission of the configured grant D ends. It may be more efficient for the monitoring time to occur during the tail portion 330 of the first scheduled transmission interval 310a so that subsequent scheduling information 340b for the uplink can be received by the UE in time for starting a new transmission within the subsequent scheduled transmission interval 310b.

[0054] Now go to Figure 8 , Figure 8The problem of identification of a cell discontinuous transmission scenario is shown. In this example, the network node 140 may provide an uplink scheduling grant for a transmission by a user equipment 120 during a physical downlink control channel monitoring opportunity 410. This may cause multiple physical uplink shared channel repetition bundles 420a to 420n to be scheduled via dynamic and / or configured grants. In one example, the first scheduled transmission interval 310a may last until the final repetition bundle 420n has been sent. The network node 140 may be in a discontinuous transmission (cell DTX) state during the entire scheduled transmission interval 810 and then resume transmission during a subsequent scheduled transmission interval 820. The present disclosure suggests that it may be more efficient for the user equipment 120 to be able to receive a grant from the network node 140 during the tail portion 330 of the first scheduled transmission interval 310a.

[0055] Now go to Fig. 9A , for the present disclosure points out a problem that occurs in the allocation of a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH) during and after a first scheduled transmission interval 310a. In this scenario, the user equipment 120 may be scheduled to send a series of physical shared uplink channel repetition bundles 420a to 420n and receive downlink control information 340a via a physical downlink control channel (PDCCH), but this problem may occur when the user equipment 120 may be sending information via an uplink and / or receiving information via a downlink. During the monitoring period 510, the user equipment may be monitoring the transmission scheduling information. However, this monitoring time 510 may occur at the beginning of the first scheduled transmission interval 310. After the first scheduled transmission interval 310a, there may be an inactive period 540, where network delays are expected. After the inactive period 540, there may be a subsequent active period 550, where the user equipment 120 can monitor the downlink control information to signal retransmissions.

[0056] Figures 9B to 9D It is shown that the next activity period 550 is delayed until after the inactivity period 540. For example, Fig. 9B1. The situation in which the user equipment 120 may be delayed in a subsequent scheduled transmission interval 310b until determining whether a retransmission is required is shown. At the beginning of the active period 550, the user equipment 120 may receive downlink control information 340a' indicating that a retransmission of the first scheduled transmission 420a interval 310a should be performed. At the end of the retransmission, the user equipment 120 may receive another downlink control information 340b scheduling a subsequent scheduled transmission interval 310b. This situation is not ideal because the user equipment may not send anything during both the inactive period 540 and the beginning of the active period 550. In order to maximize the total user equipment transmission power, the user equipment 120 needs to transmit during each uplink time slot.

[0057] Fig. 9C A scenario is shown in which the retransmission of the first scheduled transmission interval 310a may be delayed. In this scenario, the user equipment may start the subsequent scheduled transmission interval 310b before the monitoring period 550. The user equipment 120 needs to first perform the retransmission of the first scheduled transmission interval 310a, but must wait until the subsequent scheduled transmission interval 310b is completed. This is inefficient because the user equipment 120 may need to send the retransmission quickly and avoid excessive delays before the retransmission is completed. In addition, the retransmission of the first scheduled transmission interval 310a may be delayed relative to the normal retransmission window, which may require additional monitoring opportunities.

[0058] Figures 9D to 9E 3 shows a scenario where a shorter subsequent scheduled transmission interval 310b can be used to avoid unnecessarily delaying the retransmission of the first scheduled transmission interval 310a. Fig.9D In , a retransmission of the first scheduled transmission interval 310a may be required. Fig.9E In this scenario, retransmissions of the first scheduled transmission interval 310a may not be needed. This scenario is also inefficient because the subsequent scheduled transmission interval 310b may be shorter than necessary. In this scenario, the network node 140 may not be able to dynamically select the number of repetitions for maximum physical uplink shared channel efficiency because the number of selected repetitions needs to be reduced in order to avoid delaying the retransmission bundle (420b to 420n). In addition, in Fig.9D In , additional downlink control information 910 (DCI) may be received via a physical downlink control channel (PDCCH) after the retransmission to schedule the repetition for the subsequent scheduled transmission interval 310b that was omitted in the previous grant. Fig.9E In the embodiment, the additional downlink control information 910 may be received after the subsequent scheduled transmission interval 310b, and then the remaining repetitions of the subsequent scheduled transmission interval 310b may be performed.

[0059] Now go to Fig.10, provides a high-level description of an example solution to this problem. In one or more embodiments, the user equipment 120 identifies a first scheduled transmission interval 310a. In one or more embodiments, the first scheduled transmission interval 310a may have a start time 315 and an end time 317.

[0060] In one or more embodiments, the user equipment may determine the head portion 320 and the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the user equipment 120 may determine the head portion 320 and the tail portion 330 based on the end time 317. For example, the user equipment 120 may use the tail offset time 1030 applied to the end time 317. In this example, the head portion 320 may end before the end time 317 until the time of the tail offset duration 1030. In this example, the tail portion 330 may start at the tail offset duration 1030 before the end time 317. In addition, in this example, the UE may additionally monitor the PDCCH grant during the tail active time duration (i.e., the subsequent Ad Hoc duration time interval) after the start time of the tail portion 330, so that the additional UE monitoring of the PDCCH grant may end at the end time 317 or may end before or after the end time 317.

[0061] In one or more embodiments, the user equipment 120 may determine the head portion 320 and the tail portion 330 using the tail offset time 1030 applied to the end time 317. In an embodiment, the user equipment 120 may then monitor the subsequent scheduling information 340b during the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the user equipment 120 may monitor the next scheduling information 340b for a monitoring duration 1020 that is equal to or up to the length of the tail portion 330. In one or more embodiments, the scheduled monitoring time is removed from the head portion 320 of the first scheduled transmission interval 310a and accommodated to the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the removed scheduled monitoring time for transmitting scheduling information during the head portion 320 of the first scheduled transmission interval 310a is caused by one or more previously scheduled physical uplink shared channel grants. In one or more embodiments, at least one of the one or more previously scheduled physical uplink shared channel grants includes repetitions 312a to 312n (see Fig. 9AIn one or more embodiments, when at least a portion of the initial uplink transmission 420a during the head portion 320 is skipped (not sent) by the user equipment 120, the user equipment 120 may monitor the initial transmission scheduling information 340a for the duration of the tail portion 330 updated to reflect the transmission skipped by the user equipment 120.

[0062] In one or more embodiments, the user equipment 120 adds the monitoring time to the tail portion 330 of the first scheduled transmission interval 310a only if the first scheduled transmission interval 310a is longer than the threshold duration 1010. In one or more embodiments, if the first scheduled transmission interval 310a is longer than the threshold duration 1010 (see Fig.10 ), the user equipment 120 may determine that it is more effective to wait until the end of the first scheduled transmission interval 310a and then monitor the transmission of the subsequent scheduling information 340b.

[0063] In one or more embodiments, the indicator downlink control information 1040 may be used to signal whether the user equipment 120 needs to monitor the transmission of subsequent scheduling information 340b during the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the indicator downlink control information 1040 indicates whether the transmission scheduling information will be sent by the network node 140 and / or received by the user equipment 120 during the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the indicator downlink control information 1040 may not be received by the user equipment 120 and / or sent by the network node 1040.

[0064] Now go to Fig.11 , shows an illustration of an example solution, where the first scheduled transmission interval 310a includes repetitions 312a to 312n. In one or more embodiments, the monitoring period 610 is accommodated at the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, during the monitoring period 610, the user equipment 120 monitors the transmission scheduling information. In one or more embodiments, at least a portion of the monitoring period 510 can be removed and accommodated in the monitoring period 610. In an alternative embodiment, the monitoring period 610 can be accommodated without removing any of the monitoring period 510.

[0065] Now go to Fig.12 , when targeting Figures 9A-9E, an illustration of an example solution is shown when addressing the physical uplink shared channel (PUSCH) or physical downlink shared channel (PDSCH) allocation problem presented in . In one or more embodiments, physical uplink shared channel (PUSCH) repetitions 312a to 312n can be performed during a first scheduled transmission interval 310a, and a discontinuous reception (RTT) retransmission timer 630 can be started at the end of the first scheduled transmission interval 310a while waiting for the network to determine whether a retransmission 340a' of the initial scheduling information is required and before the DCI schedules the retransmission. During this period, the next scheduled transmission interval can begin 310b. In one or more embodiments, upon expiration of the discontinuous reception retransmission timer 630, the user equipment 120 can monitor subsequent transmission scheduling information 340b, which is received during the monitoring period 550, to schedule a retransmission 340a' of the initial scheduling information during the first scheduled transmission interval 310a.

[0066] In one or more embodiments, operation 1210 may be performed by pausing (310b) after a portion (310b_1) of the subsequent scheduled transmission interval 310b / 420b to perform a retransmission 420a' of the initial scheduling information 340a of the first scheduled transmission interval 310a during the next subsequent scheduled transmission interval 310c. After the retransmission 340a', the subsequent scheduling information 340b may be resumed through the non-contiguous remaining portion (310b_2) of the subsequent scheduled transmission interval (310b) without requiring a separate DCI to schedule the resumption of the subsequent scheduled transmission interval 310b.

[0067] In one or more embodiments, operation 1210 is performed by pausing the next scheduled transmission interval 310b until after the retransmission 340a' of the first scheduled transmission interval 310a only if the remainder 310b_2 of the subsequent scheduled transmission interval 310b has a duration greater than the pause remainder threshold 1220. After the retransmission 340a', the remainder 310b_2 may be sent. However, if the remainder 310b_2 of the subsequent scheduled transmission interval 310b is less than the pause remainder threshold 1220, the user equipment 120 or the network node (e.g., gNB) 140 may determine that it may be more efficient to first complete the transmission of the next scheduled transmission interval 310b before performing the retransmission 340a' of the first scheduled transmission interval 310a. In this scenario, all uplink time slots in each transmission interval may be used while minimizing the number of DCIs.

[0068] Now go to Fig.13, an example scenario of a solution in which an inefficient monitoring period during the head portion 320 can be implemented is shown. In one or more embodiments, the monitoring period 510 can occur during the head portion 320 of the first scheduled transmission interval 310a, wherein the monitoring period 510 (or 511) can be removed from the head portion 320 of the first scheduled transmission interval 310a, such as removing the interval 511 portion of the monitoring period 510, wherein the inactivity timer (IAT) can be extended after the end of the on-duration. In one or more embodiments, the monitoring period 610 can be accommodated in the tail portion 330 of the first scheduled transmission interval 310a.

[0069] Now go to Fig.14A , Fig.14A An example solution in a retransmission scenario is provided. In one or more embodiments, the monitoring period 610 may be accommodated at the end of the first scheduled transmission interval 310a. In one or more embodiments, a subsequent downlink control information (DCI) indicating a subsequent transmission scheduling information 340b will be received during the monitoring period 610. In one or more embodiments, once the subsequent downlink control information or the subsequent scheduling information 340b is received, if the subsequent downlink control information 340b schedules the UE 120 with a long expected grant interval (LAGI), the remaining portion 1410 of the monitoring period 610 may be canceled and not monitored by the UE, so that the user equipment may avoid additional monitoring time until the tail end portion of the scheduled transmission interval 310b. In one or more embodiments, the remaining portion 1410 of the monitoring period 610 may be reallocated to the tail end portion 320 of the next scheduled transmission interval 310b. In one or more embodiments, during the head end portion 320 of the next scheduled transmission interval 310b, the user equipment 120 may not monitor the subsequent transmission scheduling information 340b. In one or more embodiments, in response to receiving new or subsequent uplink transmission information 340b for transmission 420b, the user equipment 120 may stop monitoring new or subsequent uplink transmission information 340c received during the remaining portion 1410 of the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, in response to receiving new or subsequent uplink transmission information 340b, the user equipment 120 may stop monitoring new or subsequent transmission information 340c until the tail portion 330 of the subsequent scheduled transmission interval 310b, and then more monitoring time may be accommodated in the tail portion 330 of the next scheduled transmission interval 310b. In the case when new or subsequent downlink control information 340b is not received, the user equipment 120 may stop monitoring uplink transmission information 420b at the beginning of the next scheduled transmission interval 310b.

[0070] Now go to Fig. 14B, Fig. 14B An example scenario is shown in which new or subsequent downlink control information may be received during the monitoring period 550. In one or more embodiments, operation 1950 a portion or all of the monitoring period 550 is not monitored during the head portion 320 of the subsequent scheduled transmission interval 310b. More specifically, the monitoring period 550 may be moved from the head portion 320 of the subsequent scheduled transmission interval 310b to the tail portion 330 of the subsequent scheduled transmission interval 310b. In one or more embodiments, the monitoring period 550 during the head portion 320 of the subsequent scheduled transmission interval 310b may be moved by increasing the discontinuous reception retransmission timer 630.

[0071] Now go to Fig.15 , in an example scenario, a configuration grant for PUSCH 311A-311D may create a first scheduled transmission interval 310a. In one or more embodiments, operations 1500 provide parameters and indicators to the user equipment 120 to perform a monitoring time during the tail portion 330. The example parameters and indicators may be received from the network node 140 on the downlink via radio resource control. In one or more embodiments, the monitoring period 510 may be shown as occurring during the head portion 320 of the first scheduled transmission interval 310a, wherein the monitoring time 510 may be moved to the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the monitoring period 610 may be accommodated in the tail portion 330 of the first scheduled transmission interval 310a so that the monitoring period 510 occurs more efficiently during the tail portion 330 so that new or subsequent uplink transmission information (420b) may be received prior to transmission.

[0072] Now go to Fig.16, an example solution is provided for a cell discontinuous transmission scenario. In one or more embodiments, during a physical downlink control channel monitoring opportunity 410, the network node 140 may provide an uplink scheduling grant (340a to 340n). In one or more embodiments, this causes a plurality of physical uplink shared channel (PUSCH) repetition bundles 420a to 420n to be scheduled. In one or more embodiments, the physical uplink shared channel repetition bundle may be scheduled via a dynamic and / or configured grant (340a to 340n). In one or more embodiments, the first scheduled transmission interval 310a may last until the final repetition bundle 420n has been sent. In one or more embodiments, the network node 140 may be in a state of discontinuous transmission during the time interval 810, and may resume transmission during the time interval 820. In one or more embodiments, the monitoring period 610 may be accommodated to the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the monitoring period 610 can be removed from the head portion 320 of the first scheduled transmission interval and accommodated in the tail portion 330 of the first scheduled transmission interval 310a. In one or more embodiments, the monitoring period 610 is responsive to uplink or downlink discontinuous reception inactivity or responsive to a retransmission timer for uplink or downlink traffic. This provides an example solution by allowing the network node 140 to wake up in time to schedule the user equipment to start uplink transmission immediately after the first scheduled transmission interval 310a.

[0073] Now go to Fig.17 , Fig.17 Provides a description of an example solution that Fig.12 The example solution shown in adds details. In one or more embodiments, the first scheduled transmission interval 310a can be retransmitted 420a' in the next subsequent transmission interval 310c. In one or more embodiments, the pause operation 1210 can be performed to perform a pause during the first part 310b_1 of the subsequent scheduled transmission interval 310b, and resumed later after the retransmission 340a' of the first scheduled transmission interval 310a. In one or more embodiments, the head end portion 320 and the tail end portion 330 can respectively cover the entire retransmission 420a' of the first scheduled transmission interval 310a, and complete the remaining transmission 420b_2 during the remaining part 310b_2 of the subsequent scheduled transmission interval 310b. In one or more embodiments, the monitoring period 513 can be from Fig.17 In one or more embodiments, the monitoring period 513 may be accommodated in Fig.17In one or more embodiments, at operation 1710, the monitoring period 513 may be moved from the head portion 320 to the tail portion 330. In one or more embodiments, this allows the transmission scheduling information to be received before the end of the subsequent scheduled transmission interval 310b, thereby allowing fresh information for future transmissions.

[0074] Now go to Fig.18 , an example solution is shown for physical uplink shared channel allocation timing. In one or more embodiments, the first scheduled transmission interval 310 including repetitions 312a to 312n may be performed in response to initial scheduling information 340a (downlink control information) on the physical downlink control channel. In one or more embodiments, upon expiration of the first scheduled transmission interval 310a, a subsequent scheduled transmission interval 310b is performed by the user equipment 120. During the subsequent scheduled transmission interval 310b and the monitoring period 550, the user equipment 120 may receive subsequent downlink control information 340b indicating that a retransmission 340a' of the first scheduled transmission interval 310a may be performed. The subsequent scheduled transmission interval 310b may be suspended, and a retransmission 340a' of the first scheduled transmission interval 310 may be performed. At time 1810, the retransmission 340a' of the first scheduled transmission interval 310 may end, and the next scheduled transmission interval 310b may resume without receiving the next or another scheduling information 340b or 340b_2 (downlink control information).

[0075] In one or more embodiments, the subsequent scheduled transmission interval 310b is only suspended if the remainder 310b_2 of the subsequent scheduled transmission interval 310b is greater than the pause remainder threshold 1220. In one or more embodiments, if the remainder 310b_2 of the subsequent scheduled transmission interval 310b (the length of the portion of the next retransmission interval 310b that has not yet been sent when 340b is received) is less than the pause remainder threshold 1220, the user equipment 120 or the network node gNB 140 may determine to complete the next scheduled transmission interval 310b first before retransmitting 340a' the first scheduled transmission interval 310a (because this may be more efficient).

[0076] Now go to Fig.19 , a sample flow chart is shown, Fig.19 Operations performed by, for example, user equipment 120 and / or network node 140 are depicted.

[0077] In one or more embodiments, at operation 1910, the network node 140 configures the user equipment with parameters or indications related to identifying an expected authorization interval that is long enough. In one or more embodiments, the expected authorization interval that is long enough is the first scheduled transmission interval. For example, the first scheduled transmission interval may already be the first scheduled transmission interval. For example, one or more physical uplink shared channel grants may have scheduled the user equipment 120 to transmit during the first scheduled transmission interval. In one or more embodiments, the user equipment 120 may not process additional transmission scheduling information that instructs the user equipment to transmit during the first scheduled transmission interval. In one or more embodiments, identifying the first scheduled transmission interval includes identifying that the user equipment is blocked from scheduling new transmissions within at least a threshold percentage of the first scheduled transmission interval. In one or more embodiments, the expected authorization interval that is long enough is the next transmission interval that is scheduled. In one or more embodiments, the expected authorization interval that is long enough may include a physical uplink shared channel transmission or a physical downlink shared channel transmission. In one or more embodiments, the network node 140 configures the user equipment with parameters and indications to identify an expected authorization interval that is long enough. For example, the network node 140 may configure the user equipment 120 to identify a first scheduled transmission interval and / or a scheduled next transmission interval having a length or a transmission percentage greater than a threshold amount.

[0078] In one or more embodiments, at operation 1920, the network schedules physical uplink shared channel and / or physical downlink shared channel transmissions. In one or more embodiments, the transmissions are scheduled by configured grants. In one or more embodiments, the transmissions are scheduled by dynamic grants. In one or more embodiments, the transmissions are scheduled by downlink control information. In one or more embodiments, operation 1920 may occur before or after operation 1910.

[0079] In one or more embodiments, at operation 1930, the user equipment 120 and / or the network node 140 may identify an expected grant interval that is long enough. For example, the user equipment 120 and / or the network node 140 may identify a first scheduled transmission interval and / or a scheduled next transmission interval that meets the criteria configured at operation 1910. In one or more embodiments, the expected grant interval that is long enough is caused by a physical uplink shared channel grant and / or a physical downlink shared channel grant. In one or more embodiments, the first scheduled transmission interval and / or the scheduled next transmission interval may be longer than a threshold duration received from the network node 140. In one or more embodiments, the threshold duration is received by the user equipment 120 via radio resource control.

[0080] In one or more embodiments, at operation 1940, the user equipment 120 and / or the network node 140 may determine when the tail portion 330 of the first scheduled transmission interval 310 or the scheduled next transmission interval 610 begins. In one or more embodiments, the user equipment 120 and / or the network node 140 determines the timing of the tail portion 330 based on at least one of the tail offset time 1030 and the tail activity time duration. In one or more embodiments, the user equipment 120 and / or the network node 140 identifies the head portion 320 and / or the tail portion 330 of the first scheduled transmission interval 310 or the scheduled next transmission interval 610. In one or more embodiments, at least one of the head portion 320 or the tail portion 330 includes a predetermined number of time slots.

[0081] In one or more embodiments, at operation 1950, the user equipment 120 and / or the network node 140 may determine not to monitor the transmission scheduling information during the head portion 20 of the first scheduled transmission interval 310a or the scheduled next transmission interval 310b. In one or more embodiments, the head portion 320 of the first scheduled transmission interval 310a or the scheduled next transmission interval 310b occurs before the tail portion 330 of the first scheduled transmission interval 310 or the scheduled next transmission interval 310b. For example, the user equipment 120 and / or the network node 140 may remove the monitoring time 510. In some embodiments, operation 1950 is skipped and proceeds directly to step 1960.

[0082] In one or more embodiments, at operation 1960, the user equipment 120 and / or the network node 140 may monitor the transmission scheduling information during the tail portion 330 of the first scheduled transmission interval 310 or the scheduled next transmission interval 610. For example, the user equipment 120 and / or the network node 140 may add the monitoring time 610 to the tail portion 330 of the first scheduled transmission interval 310 or the scheduled next transmission interval 610.

[0083] In one or more embodiments, at operation 1970, the user equipment 120 and / or the network node 140 determines whether the number of time slots remaining in the scheduled next transmission interval 420 is greater than the pause remainder threshold 1220. In one or more embodiments, if the number of time slots remaining in the scheduled next transmission interval 420 is less than the pause remainder threshold 1220, the user equipment 120 and / or the network node 140 completes performing the scheduled next transmission interval 610.

[0084] In one or more embodiments, at operation 1980, the user equipment 120 and / or the network node 140 determines that the remaining time slots in the first scheduled transmission interval or the scheduled next transmission interval 420 are greater than the pause remainder threshold 1210. In one or more embodiments, the user equipment 120 and / or the network node 140 pauses the first scheduled transmission interval or the scheduled next transmission interval 610. In one or more embodiments, the user equipment 120 and / or the network node 140 performs a retransmission of the first scheduled transmission interval 120.

[0085] In one or more embodiments, at operation 1990, the user equipment 120 and / or the network node 140 determines that the remaining time slots in the first scheduled transmission interval or the scheduled next transmission interval 420 are greater than the pause remainder threshold 1210. In one or more embodiments, the user equipment 120 and / or the network node 140 performs a retransmission of the first scheduled transmission interval 120. The node 140 resumes the first scheduled transmission interval or the scheduled next transmission interval 420 after the retransmission window. In one or more embodiments, the user equipment 120 can complete the execution of the next transmission interval 610 without receiving any downlink control information 340.

[0086] Now go to Fig.21 , an example flow chart is shown for a process 2100 performed by an apparatus embodied by, associated with, or otherwise in communication with user equipment 120 (hereinafter generally referred to as being embodied by user equipment 120) to send an uplink transmission to network node 140.

[0087] like Fig.21As shown in box 2110 of , the apparatus embodied by the user equipment 120 includes components, such as the processing circuit system 220, the communication interface 260, etc., for identifying (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from the network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head end portion (320) and a tail end portion (330), and the tail end portion (330) accommodates the monitoring period (610). In one or more embodiments, a scheduled transmission interval enables a user equipment (120) to transmit during a first scheduled transmission interval (310a) in accordance with one or more physical uplink shared channel (PUSCH) grants (311A to 311D). In one or more embodiments, the scheduled transmission interval enables the user equipment (120) to stop processing additional transmission scheduling information (325) that instructs the user equipment (120) to transmit during the first scheduled transmission interval (310a). In one or more embodiments, a first scheduled transmission interval (310) identified (1930) with a start time (315) and an end time (317) includes the user equipment (120) being configured to be blocked (325) from scheduling new transmissions for at least a percentage of a threshold duration (1010) of the first scheduled transmission interval (310). In one or more embodiments, at least one of a head portion (320) or a tail portion (330) of the first scheduled transmission interval (310) includes a predetermined number (1010) of time slots (312a..312n). In one or more embodiments, the user equipment (120) is also caused to receive (1910) the threshold duration (1010) from the network node (140). In one or more embodiments, the threshold duration (1010) is received via radio resource control.

[0088] like Fig.21As shown in box 2120 of , the device embodied by the user equipment 120 includes components, such as processing circuit system 220, communication interface 260, etc., for sending (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) to the network node (140) within the monitoring period (610a..610n) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140). In one or more embodiments, subsequent scheduling information (340b..340n) (i.e., DCI) is sent by the network node (140) to the user equipment (120) during a monitoring period (610) of a tail portion (330) before an end time (317) to allocate a subsequent scheduled transmission interval (310b...310n) for a subsequent uplink transmission (420b..420n) (PUSCH) by the user equipment (120). In one or more embodiments, the user equipment (120) is also caused to receive new transmission scheduling information (i.e., DCI) during a tail portion (330) of a first scheduled transmission interval (310a). Fig. 14B 340b in the figure). In one or more embodiments, in response to receiving the subsequent transmission scheduling information (340b), the user equipment (120) is also caused to stop monitoring the next subsequent transmission scheduling information (340c) during at least one of the following items: (i) (1410) the remaining portion of the tail portion (610 / 330) of the first scheduled transmission interval (310a), or (ii) the head portion (320) of the subsequent scheduled transmission interval (310b). In one or more embodiments, when the number of time slots remaining in the subsequent transmission interval (310b) (i.e., a portion of 312a to 312n) is greater than (1970) the number of pause threshold time slots (1220), the user equipment (120) is also caused to pause (1980) the subsequent scheduled transmission interval. In one or more embodiments, the user equipment (120) is also caused to resume (1990) the subsequent scheduled transmission interval (310b) after the retransmission of the first scheduled transmission (420a') in the next subsequent scheduled transmission interval.

[0089] like Fig.21As shown in the optional block 2130 of , the apparatus embodied by the user equipment 120 includes components, such as the processing circuit system 220, the communication interface 260, etc., for monitoring (1960) subsequent scheduling information (340b..340n) during the tail portion (330) of the first scheduled transmission interval (310a). In one or more embodiments in which the transmission of at least a portion (321) of the head portion (320) is skipped by the user equipment (9120), the user equipment (120) is also caused to monitor the subsequent scheduling information (340b) for the duration of the tail portion (330) of the first scheduled transmission interval (310a) updated to reflect the transmission of at least a portion (321) of the head portion (320) that has been skipped by the user equipment (120). In one or more embodiments, when the subsequent scheduled transmission interval (310b) begins, the user equipment (120) is also caused to stop monitoring the next subsequent transmission scheduling information (340c...340n).

[0090] like Fig.21 As shown in optional block 2140 of , an apparatus embodied by user equipment 120 includes components, such as processing circuit system 220, communication interface 260, etc., for removing (1950) a monitoring period (511 or 550 or 513) for subsequent uplink transmissions (420b...420n) from the head end portion (320) of the first scheduled transmission interval (310a). In one or more embodiments, the monitoring time (511 or 550 - see Fig. 14B ) is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a). In one or more embodiments, at least one previously scheduled PUSCH grant of the one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a..340n) schedules a corresponding PUSCH repetition.

[0091] like Fig.21 As shown in optional block 2150 of , the apparatus embodied by the user equipment 120 includes components, such as the processing circuit system 220, the communication interface 260, etc., for adding (1960) the monitoring period (610) to the tail portion (330) of the first scheduled transmission interval (310a). In one or more embodiments, the monitoring period (610) is accommodated to the tail portion (330) of the first scheduled transmission interval (310a) or to the subsequent scheduled transmission interval (310b) by increasing the discontinuous reception retransmission timer (630).

[0092] Now go to Fig. 22, an example flow diagram is shown for a process 2200 performed by an apparatus embodied by, associated with, or otherwise in communication with (hereinafter generally referred to as embodied) a network node 140 to receive an uplink transmission from a user equipment 120.

[0093] like Fig. 22 As shown in block 2210 of FIG. 1 , the apparatus embodied by the network node 140 includes components, such as the processing circuit system 220, the communication interface 260, etc., for configuring (1910) the user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify one or more scheduled transmission intervals having a start time (315) and an end time (317) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). The method of claim 100 , wherein one or more scheduled transmission intervals (310a..310n) are configured to transmit one or more scheduled transmission intervals (310a..310n) longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by a user equipment (120) according to initial scheduling information (340a), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the monitoring period (610) is accommodated to the tail portion (330) of the first scheduled transmission interval (310a), or to a subsequent scheduled transmission interval (310b), by increasing a discontinuous reception retransmission timer (630). In one or more embodiments, the scheduled transmission interval ( Fig.15 310) enables the user equipment (120) to perform at least one of the following: (i) transmit according to one or more physical uplink shared channel (PUSCH) grants (311A to 311D) during the first scheduled transmission interval (310a), or (ii) stop processing additional transmission scheduling information (325) transmitted by the instruction user equipment (120) during the first scheduled transmission interval (310a). In one or more embodiments, the first scheduled transmission interval (310) having a start time (315) and an end time (317) includes the user equipment (120) being configured to be blocked from scheduling new transmissions for at least a percentage of a threshold duration (1010) of the first scheduled transmission interval (310). In one or more embodiments, at least one of a head portion (320) or a tail portion (330) of the first scheduled transmission interval (310) includes a predetermined number of time slots (312a..312n). In one or more embodiments, the network node (140) is further caused to configure the user equipment (120) via radio resource control with a threshold duration (1010).

[0094] like Fig. 22 As shown in box 2220, the device embodied by the network node 140 includes components, such as the processing circuit system 220, the communication interface 260, etc., for receiving (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) based on the subsequent scheduling information (340b..340n) received from the network node (140) within the monitoring period (610) before the end time (317). In one or more embodiments, during a monitoring period (610) of the tail portion (330) before the end time (317), subsequent scheduling information (340b..340n) (i.e., DCI) is sent by the network node (140) to the user equipment (120) to allocate a subsequent scheduled transmission interval (310b...310n) for a subsequent uplink transmission (420b..420n) (PUSCH) by the user equipment (120). In one or more embodiments, the network node (140) is also caused to send new transmission scheduling information (340b..340n) to the user equipment (120) during the tail portion (330) of the first scheduled transmission interval (310a). Fig. 14B 340b in the figure). In one or more embodiments, in response to receiving the subsequent transmission scheduling information (340b), the network node is also caused to stop monitoring the next subsequent transmission scheduling information (340c) during at least one of the following items: (i) (1410) the remaining portion of the tail portion (610 / 330) of the first scheduled transmission interval (310a), or (ii) the head portion (320) of the subsequent scheduled transmission interval (310b). In one or more embodiments, when the number of time slots remaining in the subsequent transmission interval (310b) (i.e., a portion of 312a to 312n) is greater than (1970) the number of pause threshold time slots (1220), the network node (140) is also caused to configure the user equipment to pause (1980) the subsequent scheduled transmission interval (310b). In one or more embodiments, the network node (140) is further caused to configure (1910) the user equipment (120) to resume (1990) the subsequent scheduled transmission interval (310b) after a retransmission of the first scheduled transmission (420a') in the next subsequent scheduled transmission interval (310c).

[0095] like Fig. 22As shown in optional block 2230 of , the apparatus embodied by the network node 140 includes components, such as the processing circuit system 220, the communication interface 260, etc., for removing (1950) a monitoring period (511 or 550) for subsequent uplink transmissions (420b...420n) from the head end portion (320) of the first scheduled transmission interval (310a). In one or more embodiments, the monitoring time (511 or 550) for subsequent transmissions of information (340b..340n) during the head end portion (320) of the first scheduled transmission interval (310a) is removed. Fig. 14B ) is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a). In one or more embodiments, at least one previously scheduled PUSCH grant of the one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a..340n) schedules a corresponding PUSCH repetition.

[0096] like Fig. 22 As shown in optional block 2240 of , the apparatus embodied by the network node 140 includes components, such as the processing circuit system 220, the communication interface 260, etc., for adding (1960) a monitoring period (610) to the tail portion (330) of the first scheduled transmission interval (310a). In one or more embodiments, in the event that the transmission is skipped by the user equipment (120) for at least a portion (321) of the head portion (320), the user equipment (120) is also caused to monitor the subsequent scheduling information (340b) for the duration of the tail portion (330) of the first scheduled transmission interval (310a) updated to reflect that the transmission has been skipped by the user equipment (120) for at least a portion (321) of the head portion (320). In one or more embodiments, when the network node (140) monitors subsequent transmission scheduling information (340b...340n), the network node (140) also configures (1910) the user equipment (120) to stop monitoring the next subsequent transmission scheduling information (340c...340n) when the subsequent scheduled transmission interval (310b) starts.

[0097] Figures 21 to 22A flow chart of a method according to an example embodiment of the present disclosure is shown. It should be understood that each box in the flow chart and the combination of boxes in the flow chart can be implemented by various components, such as hardware, firmware, processors, circuit systems and / or other communication devices associated with the execution of software including one or more computer program instructions. For example, one or more of the above processes can be embodied by computer program instructions. In this regard, the computer program instructions embodying the above processes can be stored by the memory device 240 of the device using the embodiment and executed by the processor 220. It should be understood that any such computer program instructions can be loaded into a computer or other programmable device (e.g., hardware) to produce a machine so that the final computer or other programmable device implements the functions specified in the flowchart box. These computer program instructions can also be stored in a computer-readable memory, which can instruct a computer or other programmable device to operate in a specific manner so that the instructions stored in the computer-readable memory produce a manufactured product, and the execution of the manufactured product implements the functions specified in the flowchart box. The computer program instructions can also be loaded into a computer or other programmable device so that a series of operations are performed on the computer or other programmable device to produce a computer-implemented process so that the instructions executed on the computer or other programmable device provide operations for implementing the functions specified in the flowchart box.

[0098] Therefore, the blocks in the flowchart support the combination of components for performing the specified functions and the combination of operations for performing the specified functions. It should also be understood that one or more blocks in the flowchart and the combination of blocks in the flowchart can be implemented by a computer system based on special-purpose hardware that performs the specified functions or a combination of special-purpose hardware and computer instructions.

[0099] In one or more embodiments, a user equipment (120) is provided, comprising at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (120) to identify (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) is also enabled to send (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) to the network node (140) within the monitoring period (610a..610n) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0100] In one or more embodiments, the user equipment (120) is further caused to monitor (1920) subsequent scheduling information (340b..340n) during a tail portion (330) of the first scheduled transmission interval (310a).

[0101] In one or more embodiments, subsequent scheduling information (340b..340n) (i.e., DCI) is sent by the network node (140) to the user equipment (120) during a monitoring period (610) of the tail portion (330) before the end time (317) to allocate subsequent scheduled transmission intervals (310b...310n) for subsequent uplink transmissions (420b..420n) (PUSCH) by the user equipment (120).

[0102] In one or more embodiments, the user equipment (120) is further caused to remove (1950) the monitoring period (511 or 550 or 513) used for subsequent uplink transmissions (420b ... 420n) from the head portion (320) of the first scheduled transmission interval (310a). In one or more embodiments, the user equipment (120) is further caused to add (1960) the monitoring period (610) to the tail portion (330) of the first scheduled transmission interval (310a).

[0103] In one or more embodiments, the monitoring period (610) is accommodated to the tail portion (330) of the first scheduled transmission interval (310a) or to the subsequent scheduled transmission interval (310b) by increasing the discontinuous reception retransmission timer (630).

[0104] In one or more embodiments, the scheduled transmission interval ( Fig.15 310) enables the user equipment to perform at least one of the following: (i) transmit in accordance with one or more physical uplink shared channel (PUSCH) grants (311A to 311D) during the first scheduled transmission interval (310a), or (ii) stop processing additional transmission scheduling information (325) sent by the instruction user equipment (120) during the first scheduled transmission interval (310a).

[0105] In one or more embodiments, the monitoring time (511 or 550 - see Fig. 14B ) is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a).

[0106] In one or more embodiments, at least one previously scheduled physical uplink shared channel (PUSCH) grant of the one or more previously scheduled PUSCH grants (340a..340n) schedules a corresponding PUSCH repetition.

[0107] ( Fig.15 ) In one or more embodiments, a first scheduled transmission interval (310) identified (1930) having a start time (315) and an end time (317) includes a user device (120) being configured to be blocked (325) from scheduling new transmissions for at least a percentage of a threshold duration (1010) of the first scheduled transmission interval (310).

[0108] (See Fig.11 Elements 1010 and 312a..312n, (or Fig.12 , 13 , 14)) In one or more embodiments, at least one of the head portion (320) or the tail portion (330) of the first scheduled transmission interval (310) includes a predetermined number (1010) of time slots (312a..312n).

[0109] (See Fig. 14B ) In one or more embodiments, the user equipment (120) is further configured to receive new transmission scheduling information ( Fig. 14BIn one or more embodiments, the user equipment (120) is further configured to stop monitoring the next subsequent transmission scheduling information (340c) in response to receiving the subsequent transmission scheduling information (340b) during at least one of the following: (i) (1410) the remaining portion of the tail portion (610 / 330) of the first scheduled transmission interval (310a), or (ii) the head portion (320) of the subsequent scheduled transmission interval (310b).

[0110] (See Fig. 14B ) In one or more embodiments, the user equipment (120) is also caused to receive (1910) the threshold duration (1010) from the network node (140).

[0111] In one or more embodiments, the threshold duration (1010) is received (1910) via radio resource control.

[0112] (See Fig. 14B / 321) In one or more embodiments, in the event that a transmission is skipped by a user device for at least a portion (321) of a head-end portion (320), the user device (120) is also caused to monitor subsequent scheduling information (340b) during the duration of a tail portion (330) of a first scheduled transmission interval (310a) that is updated to reflect that the transmission has been skipped by the user device (120) for at least a portion (321) of the head-end portion (320).

[0113] In one or more embodiments, when the user device (120- Fig. 14B ) when monitoring the subsequent transmission scheduling information (340b..340n), the user equipment (120) also stops monitoring the next subsequent transmission scheduling information (340c..340n) when the subsequent scheduling transmission interval (310b) starts.

[0114] ( Figure 17-18 12) In one or more embodiments, when the number of time slots remaining in the subsequent transmission interval (310b) (i.e., a portion of 312a to 312n) is greater than (1970) the number of pause threshold time slots (1220), the user equipment (120) is also caused to pause (1980) the subsequent scheduled transmission interval. In one or more embodiments, the user equipment (120) is also caused to resume (1990) the subsequent scheduled transmission interval (310b) after the retransmission of the first scheduled transmission (420a') in the next subsequent scheduled transmission interval (310c).

[0115] In one or more embodiments, a network node (140) is provided, comprising at least one processor, at least one memory, the at least one memory storing instructions, the instructions when executed by the processor causing the network node (140) to configure (1910) a user equipment (120) with parameters and indicators (1500), the parameters and indicators (1500) instructing the user equipment (120) to identify a first scheduled transmission interval (310a) having a start time (315) and an end time (316) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). The invention relates to a method for transmitting a monitoring period (610) comprising: transmitting at least one scheduled transmission interval (310a..310n) of a first transmission interval (317) and a second transmission interval (317), wherein according to initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates the monitoring period (610). In one or more embodiments, the network node (140) is also caused to receive (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within the monitoring period (610) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0116] In one or more embodiments, during a monitoring period (610) of the tail portion (330) prior to an end time (317), subsequent scheduling information (340b..340n) (i.e., DCI) is sent by the network node (140) to the user equipment (120) to allocate subsequent scheduled transmission intervals (310b...310n) for subsequent uplink transmissions (420b..420n) (PUSCH) by the user equipment (120).

[0117] In one or more embodiments, the first scheduling information (340a) configures (1910) the user equipment (120) to (i) remove (1950) a monitoring period (511 or 550) for subsequent uplink transmissions (420b…420n) from a leading portion (320) of a first scheduled transmission interval (310a), and (ii) add (1960) a monitoring period (610) to a trailing portion (330) of the first scheduled transmission interval (310a).

[0118] In one or more embodiments, the monitoring period (610) is accommodated to the tail portion (330) of the first scheduled transmission interval (310a) or to the subsequent scheduled transmission interval (310b) by increasing the discontinuous reception retransmission timer (630).

[0119] In one or more embodiments, the scheduled transmission interval ( Fig.15 310) enables the user equipment to perform at least one of the following: (i) transmit in accordance with one or more physical uplink shared channel (PUSCH) grants (311A to 311D) during the first scheduled transmission interval (310a), or (ii) stop processing additional transmission scheduling information (325) sent by the instruction user equipment (120) during the first scheduled transmission interval (310a).

[0120] In one or more embodiments, the monitoring time (511 or 550 - see Fig. 14B ) is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a).

[0121] In one or more embodiments, at least one previously scheduled physical uplink shared channel (PUSCH) grant of the one or more previously scheduled PUSCH grants (340A-340D) schedules a corresponding PUSCH repetition.

[0122] In one or more embodiments, identifying (1930) a first scheduled transmission interval (310) having a start time (315) and an end time (317) includes the user equipment (120) being configured to be blocked from scheduling new transmissions for at least a percentage of a threshold duration (1010) of the first scheduled transmission interval (310).

[0123] In one or more embodiments, at least one of a leading portion (320) or a trailing portion (330) of the first scheduled transmission interval (310) includes a predetermined number of time slots (312a..312n).

[0124] In one or more embodiments, the network node (140) is further configured to send new transmission scheduling information (i) to the user equipment (120) during the tail portion (330) of the first scheduled transmission interval (310a). Fig. 14BIn one or more embodiments, the network node (140) is further configured to, in response to receiving the subsequent transmission scheduling information (340b), stop monitoring the next subsequent transmission scheduling information (340c) during at least one of the following: (i) (1410) the remaining portion of the tail portion (610 / 330) of the first scheduled transmission interval (310a), or (ii) the head portion (320) of the subsequent scheduled transmission interval (310b).

[0125] In one or more embodiments, the network node (140) is further caused to configure (1910) the user equipment (120) via radio resource control with a threshold duration (1010).

[0126] In one or more embodiments, in the event that a transmission is skipped by a user device for at least a portion (321) of a head-end portion (320), the user device (120) is also caused to monitor subsequent scheduling information (340b) for the duration of a tail portion (330) of a first scheduled transmission interval (310a) that is updated to reflect that the transmission has been skipped by the user device (120) for at least a portion (321) of the head-end portion (320).

[0127] In one or more embodiments, when the network node (140) monitors subsequent transmission scheduling information (340b...340n), the network node (140) also configures (1910) the user equipment (120) to stop monitoring the next subsequent transmission scheduling information (340c...340n) at the beginning of the subsequent scheduled transmission interval (310b).

[0128] In one or more embodiments, the network node (140) is further configured (1910) to configure the user equipment (120) to suspend (1980) the subsequent scheduled transmission interval (310b) when the number of time slots remaining in the subsequent scheduled transmission interval (310b) (i.e., a portion of 312a to 312n) is greater than (1970) the number of suspension threshold time slots (1220). In one or more embodiments, the network node (140) is further configured (1910) to configure the user equipment (120) to resume (1990) the subsequent scheduled transmission interval (310b) after a retransmission of the first scheduled transmission (420a') in the next subsequent scheduled transmission interval (310c).

[0129] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (120) and includes identifying (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the computer-implemented method further comprises, based on subsequent scheduling information (340b..340n) received from the network node (140), sending (1920) to the network node (140) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to a corresponding subsequent scheduled transmission interval (310b..310n) within a monitoring period (610a..610n) prior to an end time (317).

[0130] In one or more embodiments, the computer-implemented method further includes monitoring (1960) subsequent scheduling information (340b..340n) during a tail portion (330) of the first scheduled transmission interval (310a).

[0131] In one or more embodiments, subsequent scheduling information (340b..340n) (i.e., DCI) is sent by the network node (140) to the user equipment (120) during a monitoring period (610) of the tail portion (330) before the end time (317) to allocate subsequent scheduled transmission intervals (310b...310n) for subsequent uplink transmissions (420b..420n) (PUSCH) by the user equipment (120).

[0132] In one or more embodiments, the computer-implemented method further comprises removing (1950) a monitoring period (511 or 550 or 513) for subsequent uplink transmissions (420b ... 420n) from a leading portion (320) of the first scheduled transmission interval (310a). In one or more embodiments, the computer-implemented method further comprises adding (1960) the monitoring period (610) to a trailing portion (330) of the first scheduled transmission interval (310a).

[0133] In one or more embodiments, the monitoring period (610) is accommodated to the tail portion (330) of the first scheduled transmission interval (310a), or the subsequent scheduled transmission interval (310b) by increasing the discontinuous reception retransmission timer (630).

[0134] In one or more embodiments, the computer-implemented method further comprises at least one of: (i) transmitting in accordance with one or more physical uplink shared channel (PUSCH) grants (311A to 311D) during the first scheduled transmission interval (310a), or (ii) ceasing to process additional transmission scheduling information (325) transmitted by the instruction user equipment (120) during the first scheduled transmission interval (310a).

[0135] In one or more embodiments, the monitoring time (511 or 550 - see Fig. 14B ) is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a).

[0136] In one or more embodiments, at least one previously scheduled physical uplink shared channel (PUSCH) grant of the one or more previously scheduled PUSCH grants (340a..340n) schedules a corresponding PUSCH repetition.

[0137] ( Fig.15 ) In one or more embodiments, an identifier (1930) of a first scheduled transmission interval (310) having a start time (315) and an end time (317) includes a user device (120) being configured to be blocked (325) from scheduling new transmissions for at least a percentage of a threshold duration (1010) of the first scheduled transmission interval (310).

[0138] (See Fig.11 Elements 1010 and 312a..312n, (or Fig.12 , 13 , 14)) In one or more embodiments, at least one of the head portion (320) or the tail portion (330) of the first scheduled transmission interval (310) includes a predetermined number (1010) of time slots (312a..312n).

[0139] (See Fig. 14B ) In one or more embodiments, the computer-implemented method further comprises receiving new transmission schedule information ( Fig. 14BIn one or more embodiments, the computer-implemented method further comprises, in response to receiving the subsequent transmission scheduling information (340b), ceasing to monitor the next subsequent transmission scheduling information (340c) during at least one of: (i) (1410) a remaining portion of the tail portion (610 / 330) of the first scheduled transmission interval (310a), or (ii) a head portion (320) of the subsequent scheduled transmission interval (310b).

[0140] (See Fig. 14B ) In one or more embodiments, the computer-implemented method further includes receiving ( 1910 ) the threshold duration ( 1010 ) from the network node ( 140 ).

[0141] In one or more embodiments, the threshold duration (1010) is received (1910) via radio resource control.

[0142] (See Fig. 14B / 321) In one or more embodiments, in the event that a transmission is skipped by a user device for at least a portion (321) of a head-end portion (320), the computer-implemented method further includes monitoring subsequent scheduling information (340b) during the duration of a tail portion (330) of a first scheduled transmission interval (310a) that is updated to reflect that the transmission has been skipped by the user device (120) for at least a portion (321) of the head-end portion (320).

[0143] In one or more embodiments, when the user device (120- Fig. 14B ) when monitoring the subsequent transmission scheduling information (340b..340n), the computer-implemented method also includes stopping monitoring the next subsequent transmission scheduling information (340c..340n) when the subsequent scheduled transmission interval (310b) begins.

[0144] ( Figure 17-18 12) In one or more embodiments, when the number of time slots remaining in the subsequent transmission interval (310b) (i.e., a portion of 312a to 312n) is greater than (1970) the number of pause threshold time slots (1220), the computer-implemented method further includes pausing (1980) the subsequent scheduled transmission interval. In one or more embodiments, the user equipment is further caused to resume (1990) the subsequent scheduled transmission interval (310b) after a retransmission of the first scheduled transmission (420a') in the next subsequent scheduled transmission interval (310c).

[0145] In one or more embodiments, a computer-implemented method is provided, the method being performed by a network node (140), comprising configuring (1910) a user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify one or more scheduled transmission intervals having a start time (315) and an end time (317) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). The method comprises: providing a plurality of scheduled transmission intervals (310a..310n) for transmitting a first transmission of the first uplink transmission to the user equipment (120); wherein, based on the initial scheduling information (340a), one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120); wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates the monitoring period (610). In one or more embodiments, the computer-implemented method further comprises receiving (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to a corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within a monitoring period (610) prior to an end time (317) based on subsequent scheduling information (340b..340n) received from the network node (140).

[0146] In one or more embodiments, during a monitoring period (610) of the tail portion (330) prior to an end time (317), subsequent scheduling information (340b..340n) (i.e., DCI) is sent by the network node (140) to the user equipment (120) to allocate subsequent scheduled transmission intervals (310b...310n) for subsequent uplink transmissions (420b..420n) (PUSCH) by the user equipment (120).

[0147] In one or more embodiments, the first scheduling information (340a) configures (1910) the user equipment (120) to (i) remove (1950) a monitoring period (511 or 550) for subsequent uplink transmissions (420b…420n) from a leading portion (320) of a first scheduled transmission interval (310a), and (ii) add (1960) a monitoring period (610) to a trailing portion (330) of the first scheduled transmission interval (310a).

[0148] In one or more embodiments, the monitoring period (610) is accommodated to the tail portion (330) of the first scheduled transmission interval (310a) or to the subsequent scheduled transmission interval (310b) by increasing the discontinuous reception retransmission timer (630).

[0149] In one or more embodiments, the scheduled transmission interval ( Fig.15 310) enables the user equipment to perform at least one of the following: (i) transmit in accordance with one or more physical uplink shared channel (PUSCH) grants (311A to 311D) during the first scheduled transmission interval (310a), or (ii) stop processing additional transmission scheduling information (325) sent by the instruction user equipment (120) during the first scheduled transmission interval (310a).

[0150] In one or more embodiments, the monitoring time (511 or 550 - see Fig. 14B ) is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants (340a).

[0151] In one or more embodiments, at least one previously scheduled physical uplink shared channel (PUSCH) grant of the one or more previously scheduled PUSCH grants (340A-340D) schedules a corresponding PUSCH repetition.

[0152] In one or more embodiments, an identification (1930) of a first scheduled transmission interval (310) having a start time (315) and an end time (317) includes the user equipment (120) being configured to be blocked from scheduling new transmissions for at least a percentage of a threshold duration (1010) of the first scheduled transmission interval (310).

[0153] In one or more embodiments, at least one of a leading portion (320) or a trailing portion (330) of the first scheduled transmission interval (310) includes a predetermined number of time slots (312a..312n).

[0154] In one or more embodiments, the computer-implemented method further comprises sending new transmission scheduling information ( Fig. 14BIn one or more embodiments, the computer-implemented method further comprises, in response to receiving the subsequent transmission scheduling information (340b), ceasing to monitor the next subsequent transmission scheduling information (340c) during at least one of: (i) (1410) a remaining portion of the tail portion (610 / 330) of the first scheduled transmission interval (310a), or (ii) a head portion (320) of the subsequent scheduled transmission interval (310b).

[0155] In one or more embodiments, the computer-implemented method further includes configuring (1910) the user equipment (120) via radio resource control with the threshold duration (1010).

[0156] In one or more embodiments, in the event that a transmission is skipped by a user device for at least a portion (321) of a head-end portion (320), the user device (120) is also caused to monitor subsequent scheduling information (340b) during the duration of a tail portion (330) of a first scheduled transmission interval (310a) that is updated to reflect that the transmission has been skipped by the user device (120) for at least a portion (321) of the head-end portion (320).

[0157] In one or more embodiments, when the network node (140) monitors subsequent transmission scheduling information (340b...340n), the computer-implemented method also includes configuring (1910) the user equipment (120) to stop monitoring the next subsequent transmission scheduling information (340c...340n) when the subsequent scheduled transmission interval (310b) begins.

[0158] In one or more embodiments, the computer-implemented method further comprises configuring (1910) the user equipment (120) to suspend (1980) the subsequent scheduled transmission interval (310b) when the number of time slots remaining in the subsequent scheduled transmission interval (310b) (i.e., a portion of 312a to 312n) is greater than (1970) the number of pause threshold time slots (1220). In one or more embodiments, the computer-implemented method further comprises configuring (1910) the user equipment (120) to resume (1990) the subsequent scheduled transmission interval (310b) after a retransmission of the first scheduled transmission (420a') in a subsequent subsequent scheduled transmission interval (310c).

[0159] In one or more embodiments, a non-transitory computer-readable storage medium is provided, comprising computer instructions that, when executed by a user equipment (120), cause the user equipment (120) to identify (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein according to the initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) is also enabled to send (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) to the network node (140) within the monitoring period (610a..610n) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0160] In one or more embodiments, a non-transitory computer-readable storage medium is provided, comprising computer instructions that, when executed by a network node (140), cause the network node (140) to configure (1910) a user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify a first scheduled transmission interval (310a) having a start time (315) and an end time (317) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). ), wherein according to initial scheduling information (340a), the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) performed by the user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates the monitoring period (610). In one or more embodiments, the network node (140) is also caused to receive (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to the corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within the monitoring period (610) before the end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0161] In one or more embodiments, a user equipment (120) is provided, comprising means for identifying (1930) one or more scheduled transmission intervals (310a..310n) having a start time (315) and an end time (317) based on initial scheduling information (340a) received from a network node (140), wherein the one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) by the user equipment (120) according to the initial scheduling information (340a), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the user equipment (120) further comprises means for sending (1920) to the network node (140) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to a corresponding subsequent scheduled transmission interval (310b..310n) within a monitoring period (610a..610n) before an end time (317) based on subsequent scheduling information (340b..340n) received from the network node (140).

[0162] In one or more embodiments, a network node (140) is provided, comprising means for configuring (1910) a user equipment (120) with parameters and indicators (1500) that instruct the user equipment (120) to identify one or more scheduled transmission intervals (310a) having a start time (315) and an end time (317) based on initial scheduling information (340a) of a first scheduled transmission interval (310a) received from the network node (140). 0a..310n), wherein according to initial scheduling information (340a), one or more scheduled transmission intervals (310a..310n) are longer than a threshold duration (1010) for one or more uplink transmissions (420a..420n) by a user equipment (120), wherein the one or more scheduled transmission intervals (310a..310n) include a head portion (320) and a tail portion (330), and the tail portion (330) accommodates a monitoring period (610). In one or more embodiments, the network node (140) further comprises means for receiving (1920) at least one subsequent uplink transmission (420b..420n) (i.e., PUSCH) corresponding to a corresponding subsequent scheduled transmission interval (310b..310n) from the user equipment (120) within a monitoring period (610) before an end time (317) based on the subsequent scheduling information (340b..340n) received from the network node (140).

[0163] Many modifications and other embodiments described herein will occur to those skilled in the art after having benefited from the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that the present disclosure is not limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims.

[0164] In addition, although the above description and the associated drawings describe example embodiments in the context of certain example combinations of elements and / or functions, it should be understood that different combinations of elements and / or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, combinations different from those elements and / or functions explicitly described above are also contemplated, as may be set forth in some of the appended claims. Although specific terms are used herein, they are used only in a general and descriptive sense, and not for limiting purposes.

[0165] legend:

[0166] 120 User Equipment

[0167] 140 network nodes

[0168] 310a First scheduled transmission interval

[0169] 310b…310n Subsequent scheduled transmission interval

[0170] 310b_1 The first part of the subsequent scheduled transmission interval sent before suspending the retransmission of the first scheduled transmission interval

[0171] 310b_2 The subsequent part of the subsequent scheduled transmission interval sent after suspending the retransmission of the first scheduled transmission interval

[0172] 310c The next scheduled transmission interval

[0173] 311A…311D PUSCH transmission (generated by configured grant)

[0174] 312a…312n Repeat

[0175] 315 Start time

[0176] 317 End Time

[0177] 320 Head end

[0178] 321 Skipped section (detected)

[0179] 320 Head end

[0180] 330 tail section

[0181] 340a Initial Scheduling Information

[0182] 340b…340n Subsequent scheduling information

[0183] 410 Physical downlink control channel monitoring opportunity

[0184] 420a Initial uplink transmission

[0185] 420a' Retransmission of initial uplink transmission

[0186] 420b…420n Subsequent uplink transmission

[0187] 510 Monitoring period

[0188] 512 Monitoring period not caused by previous UL grant / transmission (e.g., only due to OnDuration)

[0189] Monitoring period after 513 550

[0190] - 550 is used for scheduling retransmission,

[0191] - and 513 in Fig.17 is used to show the active time of the move after a retransmission is scheduled, causing the pause function.

[0192] 520 Monitoring time periods where scheduling may be inefficient

[0193] 530 Monitoring time may be (relatively) efficient scheduling time period

[0194] 511, 550 The monitoring period is caused by the previous UL grant / transmission (eg, only due to the inactivity timer and retransmission timer respectively, not due to OnDuration).

[0195] 610 Monitoring period

[0196] 630 Discontinuous Retransmission Timer (DRX) drx-HARQ-RTT-TimerUL timer

[0197] 810 The time interval during which the network node is in a discontinuous transmission state

[0198] 820 Network node resumes transmission time interval

[0199] 1010 Threshold Duration

[0200] 1020 (Ad Hoc) monitoring duration, for example, a length of 610 in some embodiments (wherein the monitoring time length is not reduced after receiving the DCI that the UE is scheduled to transmit during the next / subsequent interval)

[0201] 1030 tail offset time 1030( Fig.10 ), which is the start time of 610

[0202] 1210 Pause restore operation

[0203] 1220 Remaining Threshold

[0204] 1410 Remaining part of monitoring period

[0205] 1500 Parameters and indicators from the network, instructing the user equipment to identify one or more scheduled transmission intervals according to the present invention

[0206] 1501 Configured (and dynamic) grants signaled to UE

Claims

1. A user equipment, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the processor, cause the user device to: identifying, based on initial scheduling information received from a network node, one or more scheduled transmission intervals having a start time and an end time, wherein the one or more scheduled transmission intervals are longer than a threshold duration for one or more uplink transmissions by the user equipment according to the initial scheduling information, wherein the one or more scheduled transmission intervals include a head portion and a tail portion, and the tail portion accommodates a monitoring period; as well as According to the subsequent scheduling information received from the network node, at least one subsequent uplink transmission corresponding to the corresponding subsequent scheduled transmission interval is sent to the network node within the monitoring period before the end time.

2. The user equipment according to claim 1, further causing the user equipment to perform at least one of the following items: (a) monitoring the subsequent scheduling information during a tail portion of a first scheduled transmission interval; (b) receiving the threshold duration from the network node; (c) removing the monitoring period for the subsequent uplink transmission from the leading portion of the first scheduled transmission interval and adding the monitoring period to the trailing portion of the first scheduled transmission interval; (d) receiving new transmission scheduling information during the tail portion of the first scheduled transmission interval; and in response to receiving the subsequent transmission scheduling information, stopping monitoring the next subsequent transmission scheduling information during at least one of the following: the remaining part of the tail part of the first scheduled transmission interval; or the head portion of the subsequent scheduled transmission interval; (e) receiving the threshold duration via radio resource control; or (f) pausing the subsequent scheduled transmission interval when the number of time slots remaining in the subsequent scheduled transmission interval is greater than the number of pause threshold time slots; and resuming the subsequent scheduled transmission interval after retransmission of the first scheduled transmission in the next subsequent scheduled transmission interval.

3. The user equipment according to claim 1, wherein the subsequent scheduling information is sent by the network node to the user equipment during the monitoring period of the tail part before the end time to allocate the subsequent scheduled transmission interval to the subsequent uplink transmission performed by the user equipment.

4. The user equipment according to claim 1, wherein the monitoring period is accommodated to the tail part of the first scheduled transmission interval or to the subsequent scheduled transmission interval by increasing a discontinuous reception retransmission timer.

5. The user equipment of claim 1 , wherein the scheduled transmission interval enables the user equipment to perform at least one of the following: transmitting during the first scheduled transmission interval in accordance with one or more physical uplink shared channel (PUSCH) grants; or The processing of additional transmission scheduling information is stopped, wherein the additional transmission scheduling information instructs the user equipment to transmit during the first scheduled transmission interval.

6. The user equipment of claim 1, wherein the removal of the monitoring time for the subsequently transmitted information during the head portion of the first scheduled transmission interval is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants.

7. The user equipment of claim 6, wherein at least one previously scheduled physical uplink shared channel (PUSCH) grant of the one or more previously scheduled PUSCH grants schedules a corresponding PUSCH repetition.

8. The user equipment of claim 1, wherein identifying the first scheduled transmission interval having the start time and the end time comprises: The user equipment is configured to be blocked from scheduling new transmissions for at least a percentage of the threshold duration of the first scheduled transmission interval.

9. The user equipment of claim 1, wherein at least one of the leading portion or the trailing portion of the first scheduled transmission interval comprises a predetermined number of time slots.

10. The user equipment according to claim 1, wherein in case that transmission for at least a part of the head-end part is skipped by the user equipment, the user equipment is further caused to: The subsequent scheduling information is monitored for a duration of the tail portion of the first scheduled transmission interval updated to reflect that the transmission has been skipped by the user equipment for the at least a portion of the head portion.

11. The user equipment according to claim 1, wherein when the user equipment monitors the subsequent transmission scheduling information, the user equipment is further caused to: When the subsequent scheduled transmission interval starts, stop monitoring the next subsequent transmission scheduling information.

12. A network node, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the processor, cause the network node to: configuring a user equipment with parameters and indicators that instruct the user equipment to identify one or more scheduled transmission intervals having a start time and an end time based on initial scheduling information of a first scheduled transmission interval received from a network node, wherein the one or more scheduled transmission intervals are longer than a threshold duration for one or more uplink transmissions by the user equipment according to the initial scheduling information, wherein the one or more scheduled transmission intervals include a head portion and a tail portion, and the tail portion accommodates a monitoring period; as well as According to the subsequent scheduling information received from the network node, at least one subsequent uplink transmission corresponding to a corresponding subsequent scheduled transmission interval is received from the user equipment within the monitoring period before the end time.

13. The network node according to claim 12, wherein the subsequent scheduling information is sent by the network node to the user equipment during the monitoring period of the tail part before the end time to allocate the subsequent scheduled transmission interval to the subsequent uplink transmission by the user equipment.

14. The network node according to claim 12, wherein the first scheduling information configures the user equipment to: removing the monitoring period for the subsequent uplink transmission from the leading portion of the first scheduled transmission interval; and The monitoring period is added to the trailing portion of the first scheduled transmission interval.

15. The network node of claim 14, wherein the removal of the monitoring time for the subsequently transmitted information during the head portion of the first scheduled transmission interval is caused by one or more previously scheduled physical uplink shared channel (PUSCH) grants.

16. The network node of claim 13, wherein identifying the first scheduled transmission interval having the start time and the end time comprises: The user equipment is configured to be blocked from scheduling new transmissions for at least a percentage of the threshold duration of the first scheduled transmission interval.

17. The network node of claim 13, wherein at least one of the leading portion or the trailing portion of the first scheduled transmission interval comprises a predetermined number of time slots.

18. The network node of claim 12, further causing the network node to perform at least one of the following: (a) during the tail portion of the first scheduled transmission interval, sending new transmission scheduling information to the user equipment; and In response to receiving the subsequent transmission scheduling information, stopping monitoring of the next subsequent transmission scheduling information during at least one of the following: the remaining part of the tail part of the first scheduled transmission interval; or the head portion of the subsequent scheduled transmission interval; (b) configuring the user equipment with the threshold duration via radio resource control; or (c) configuring the user equipment to: When the number of time slots remaining in the subsequent scheduled transmission interval is greater than the number of pause threshold time slots, pausing the subsequent scheduled transmission interval; and After the retransmission of the first scheduled transmission in the next subsequent scheduled transmission interval, the subsequent scheduled transmission interval is resumed.

19. The network node according to claim 13, in case that transmission for at least a part of the head-end part is skipped by the user equipment, further causing the user equipment to: The subsequent scheduling information is monitored for a duration of the tail portion of the first scheduled transmission interval updated to reflect that the transmission has been skipped by the user equipment for the at least a portion of the head portion.

20. The network node according to claim 13, wherein when the network node monitors the subsequent transmission scheduling information, the network node is further caused to: The user equipment is configured to stop monitoring the next subsequent transmission scheduling information when the subsequent scheduled transmission interval starts.

Images