Method, terminal device and network node for uplink transmission

Abstract

Disclosed are a method, a terminal device, and a network node for uplink transmission. According to one embodiment, the terminal device sends a transport block (TB) to the network node using a first configuration grant. The terminal device autonomously retransmits the TB to the network node using a second configuration grant.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to wireless communications, and more particularly to methods, terminal devices, and network nodes for uplink transmissions. Background Art

[0002] This section introduces aspects that may facilitate a better understanding of the present disclosure. Therefore, the statements in this section should be read in this light and should not be understood as admissions of what is or is not prior art.

[0003] The fifth generation of cellular systems, known as New Radio (NR), was developed to achieve maximum flexibility to support multiple and substantially different use cases. In addition to the typical mobile broadband use case, there are also machine type communications (MTC), ultra-low latency critical communications (ULLCC), sidelink device-to-device (D2D), and several other use cases.

[0004] In NR, the basic scheduling unit is called a slot. For a common cyclic prefix configuration, a slot consists of 14 orthogonal frequency division multiplexing (OFDM) symbols. NR supports many different subcarrier spacing (SCS) configurations, and at a 30kHz SCS, the OFDM symbol duration is approximately 33μs. As an example, for the same SCS, a slot with 14 symbols is 500μs long (including the cyclic prefix).

[0005] NR also supports flexible bandwidth configuration for different user equipment (UE) on the same serving cell. In other words, the bandwidth monitored by the UE and used for its control and data channels can be smaller than the carrier bandwidth. One or more bandwidth parts (BWPs) for each component carrier can be semi-statically notified to the UE, where a BWP consists of a set of contiguous physical resource blocks (PRBs). Reserved resources can be configured within the BWP. The bandwidth of the BWP is equal to or less than the maximum bandwidth capability supported by the UE.

[0006] NR targets both licensed and unlicensed bands. Allowing unlicensed networks, i.e. networks that operate in shared spectrum (or unlicensed spectrum) to efficiently use the available spectrum, is an attractive approach to increasing system capacity. Although unlicensed spectrum does not match the quality of the licensed regime, solutions that allow it to be used efficiently as a complement to licensed deployments have the potential to bring huge value to 3rd Generation Partnership Project (3GPP) operators and ultimately to the entire 3GPP industry. It is expected that some features in NR will need to be adapted to comply with the special characteristics of unlicensed bands and different regulations. For frequencies below 6 GHz, SCS of 15 kHz or 30 kHz are the most promising candidates for NR-based access (NR-U) OFDM parameter sets (numerology) for unlicensed spectrum.

[0007] When operating in unlicensed spectrum, many regions of the world require devices to sense the medium as idle before transmitting. This operation is often referred to as listen-before-talk, or LBT for short. It is designed for coexistence of unlicensed spectrum with other radio access technologies (RATs). For this mechanism in NR unlicensed spectrum, the radio device applies a clear channel assessment (CCA) check (i.e., channel sensing) before any transmission. The transmitter involves comparing energy detection (ED) over a period of time with a specific threshold (ED threshold) to determine whether the channel is idle. If the channel is determined to be occupied, the transmitter performs a random back-off within the contention window before the next CCA attempt. To protect acknowledgment (ACK) transmissions, the transmitter must delay for a period of time after each busy CCA slot before resuming the back-off. Once the transmitter has gained access to the channel, it is only allowed to perform transmissions for a maximum duration (i.e., maximum channel occupancy time (MCOT)). To differentiate quality of service (QoS), channel access priorities based on service type have been defined. For example, four LBT priority categories are defined to differentiate between contention window size (CWS) and MCOT between services.

[0008] There are many different flavors of LBT, depending on which radio technology the device uses and the type of data it wants to transmit at the time. What all flavors have in common is that sensing is performed in a specific channel (corresponding to a defined carrier frequency) and over a predefined bandwidth. For example, in the 5 GHz band, sensing is performed on a 20 MHz channel.

[0009] Many devices are capable of transmitting (and receiving) over a wide bandwidth that includes multiple sub-bands / channels, such as LBT sub-bands (i.e., a frequency portion with a bandwidth equal to the LBT bandwidth). Devices are only allowed to transmit on sub-bands where the medium is sensed as idle. Again, when multiple sub-bands are involved, there are different styles as to how sensing should be done.

[0010] In principle, there are two ways in which a device can operate on multiple sub-bands. In one approach, the transmitter / receiver bandwidth is changed depending on which sub-bands are sensed as idle. In this setup, there is only one component carrier (CC), and the multiple sub-bands are treated as a single channel with a larger bandwidth. In the other approach, the device operates a nearly independent processing chain for each channel. Depending on the degree of independence of the processing chains, this option can be called carrier aggregation (CA) or dual connectivity (DC). Summary of the Invention

[0011] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0012] One of the objects of the present disclosure is to provide an improved solution for uplink transmission.

[0013] According to a first aspect of the present disclosure, a method in a terminal device is provided. The method may include sending a transport block (TB) to a network node using a first configuration grant. The method may also include autonomously retransmitting the TB to the network node using a second configuration grant.

[0014] In an embodiment of the present disclosure, when a timer with a timer value equal to a predetermined maximum period expires, the autonomous retransmission of the TB may be stopped.

[0015] In an embodiment of the present disclosure, the second configuration grant may belong to a first configuration grant configuration. The method may further include autonomously retransmitting the TB to the network node using a third configuration grant belonging to the second configuration grant configuration.

[0016] In an embodiment of the present disclosure, the second configuration grant may belong to a first configuration grant configuration.The method may further include autonomously retransmitting the TB to the network node using a third configuration grant belonging to the first configuration grant configuration.

[0017] In an embodiment of the present disclosure, the first configuration permission may belong to the first configuration permission configuration or the second configuration permission configuration.

[0018] In an embodiment of the present disclosure, the first configuration permission may belong to a third configuration permission configuration.

[0019] In an embodiment of the present disclosure, the TB may be sent using a hybrid automatic repeat request (HARQ) process.

[0020] In an embodiment of the present disclosure, the autonomous retransmission of the TB may be performed one or more times using the same HARQ process.

[0021] In an embodiment of the present disclosure, the timer may be started at a time point related to the sending of the TB.

[0022] In an embodiment of the present disclosure, when the terminal device receives confirmation for the TB, the timer may be stopped.

[0023] In an embodiment of the present disclosure, the size of the TB may be determined based on the first configuration permission configuration, the second configuration permission configuration, or the third configuration permission configuration.

[0024] In an embodiment of the present disclosure, the first configuration-permitting configuration, the second configuration-permitting configuration, or the third configuration-permitting configuration may be received from the network node.

[0025] In an embodiment of the present disclosure, when the terminal device determines that autonomous retransmission permitted by the second configuration is allowed, the TB may be autonomously retransmitted by permitting the second configuration.

[0026] In an embodiment of the present disclosure, the autonomous retransmission of the TB may be performed multiple times. A first portion of the multiple autonomous retransmissions may be performed using the same HARQ process, and a second portion of the multiple autonomous retransmissions may be performed using another HARQ process.

[0027] In an embodiment of the present disclosure, the another HARQ process may be used when the terminal device has not received any HARQ feedback for the TB after a predetermined number of transmission attempts or a predetermined time period.

[0028] In an embodiment of the present disclosure, the second configuration grant may belong to the first configuration grant configuration.The method may further include autonomously retransmitting the TB to the network node using the second configuration grant and the third configuration grant.

[0029] In an embodiment of the present disclosure, the autonomous retransmission of the TB may stop when a predetermined maximum number of transmission attempts is reached or a predetermined maximum time period has elapsed.

[0030] In an embodiment of the present disclosure, the predetermined maximum number of transmission attempts or the predetermined maximum time period may be based on a latency requirement of the related service data or the related one or more logical channels.

[0031] In an embodiment of the present disclosure, the method may further include: when the terminal device has not received an acknowledgment for the TB after reaching the predetermined maximum number of transmission attempts or the predetermined maximum time period has passed, sending a failure report for the TB to the network node.

[0032] In an embodiment of the present disclosure, the transmission attempt may include one or more transmission attempts missed due to LBT failure.

[0033] In an embodiment of the present disclosure, the predetermined maximum time period may include the time elapsed for one or more LBT operations.

[0034] In an embodiment of the present disclosure, the autonomous retransmission of the TB may be proactively performed when the predetermined maximum number of transmission attempts is about to be reached or the predetermined maximum time period is about to elapse.

[0035] In an embodiment of the present disclosure, autonomous retransmission of the TB may be proactively performed by performing autonomous retransmission of the TB without waiting for feedback for the TB or without waiting for expiration of a configuration grant retransmission timer. Expiration of the configuration grant retransmission timer may be used to trigger autonomous retransmission using a configuration grant.

[0036] In an embodiment of the present disclosure, when the terminal device receives a dynamic permission for retransmission of the TB, the timer may be stopped.

[0037] In an embodiment of the present disclosure, the timer may be started when one of the following events occurs: a media access control (MAC) protocol data unit (PDU) corresponding to the TB has been generated; a first LBT operation is initiated for a first transmission attempt for the TB; and a first potential transmission opportunity for the TB occurs.

[0038] In an embodiment of the present disclosure, a configuration permission timer may be reused as the timer.

[0039] In an embodiment of the present disclosure, the method may further include indicating to the network node the number of transmission attempts for the TB or the delay experienced by the transmission of the TB.

[0040] In an embodiment of the present disclosure, the number of transmission attempts or the delay experienced may be indicated by one or more of: a redundant version of the TB; uplink control information (UCI); radio resource control (RRC) signaling; MAC control element (CE); and layer 1 or layer 2 signaling.

[0041] In an embodiment of the present disclosure, the method may further include: receiving signaling instructing to terminate retransmission for the TB.

[0042] In an embodiment of the present disclosure, the method may further include: triggering an upper layer retransmission of the data corresponding to the TB in response to the signaling.

[0043] In an embodiment of the present disclosure, the method may further include providing user data, and forwarding the user data to the host via transmission to the base station.

[0044] According to a second aspect of the present disclosure, a method in a network node is provided. The method may include receiving information from a terminal device regarding one or more autonomous uplink retransmissions of a TB utilizing one or more configuration grants. The method may also include determining a scheduling policy or scheduling decision for the TB based on the information.

[0045] In an embodiment of the present disclosure, the method may further include: sending one or more configuration permission configurations to the terminal device.

[0046] In an embodiment of the present disclosure, the scheduling policy may be determined to ensure that the retransmission from the terminal device is completed within a predetermined maximum time period.

[0047] In an embodiment of the present disclosure, the scheduling decision may indicate termination of retransmission for the TB.

[0048] In an embodiment of the present disclosure, the method may further include: sending signaling indicating the scheduling decision to the terminal device.

[0049] In an embodiment of the present disclosure, the signaling may be sent as one or more of: layer 1 / layer 2 signaling; MAC CE; and RRC signaling.

[0050] In an embodiment of the present disclosure, the information may include one or more of the following: the number of transmission attempts for the TB or the delay experienced in the transmission of the TB; the HARQ process identifier for the TB; and a failure indication that the TB will not be autonomously retransmitted from the terminal device.

[0051] In an embodiment of the present disclosure, the scheduling strategy may include one or more of the following: the scheduling priority of the TB; the parameters of the physical downlink control channel (PDCCH) carrying the uplink grant for the retransmission of the TB; the duration length of the physical uplink shared channel (PUSCH) for the TB; the transmission power parameters for the TB; and the PUSCH preparation delay for the TB.

[0052] In an embodiment of the present disclosure, the method may further include: sending information indicating a predetermined maximum number of transmission attempts or a predetermined maximum time period to the terminal device. When the predetermined maximum number of transmission attempts is reached or the predetermined maximum time period has elapsed, the autonomous retransmission of the TB may stop.

[0053] In an embodiment of the present disclosure, the predetermined maximum number of transmission attempts or the predetermined maximum time period may be based on latency requirements of related service data or related one or more logical channels.

[0054] According to a third aspect of the present disclosure, a terminal device is provided. The terminal device may include at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the terminal device may be operable to send a traffic block (TB) to a network node using a first configuration permission. The terminal device may also be operable to autonomously retransmit the traffic block (TB) to the network node using a second configuration permission.

[0055] In an embodiment of the present disclosure, the terminal device may be operable to execute the method according to the first aspect above.

[0056] According to a fourth aspect of the present disclosure, a network node is provided. The network node may include at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the network node may be operable to receive information related to one or more autonomous uplink retransmissions of a TB using one or more configuration permissions from a terminal device. The network node may also be operable to determine a scheduling policy or scheduling decision for the TB based on the information.

[0057] In an embodiment of the present disclosure, the network node may be operable to perform the method according to the above second aspect.

[0058] According to a fifth aspect of the present disclosure, a computer program product is provided, which may include instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first and second aspects.

[0059] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided, which may contain instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first and second aspects.

[0060] According to a seventh aspect of the present disclosure, a terminal device is provided. The terminal device may include a sending module configured to send a TB to a network node using a first configuration permission. The terminal device may also include a retransmission module configured to autonomously retransmit the TB to the network node using a second configuration permission.

[0061] According to an eighth aspect of the present disclosure, a network node is provided. The network node may include a receiving module configured to receive, from a terminal device, information related to one or more autonomous uplink retransmissions of a TB utilizing one or more configuration permissions. The network node may also include a determining module configured to determine a scheduling policy or scheduling decision for the TB based on the information.

[0062] According to a ninth aspect of the present disclosure, a method implemented in a communication system including a host, a base station, and a terminal device is provided. The method may include: receiving, at the host, user data transmitted from the terminal device to the base station. The terminal device may transmit a traffic data transmission (TB) to the base station using a first configuration permission. The terminal device may autonomously retransmit the traffic data to the base station using a second configuration permission.

[0063] In an embodiment of the present disclosure, the method may further include: at the terminal device, providing the user data to the base station.

[0064] In an embodiment of the present disclosure, the method may further include: executing a client application at the terminal device to provide user data to be sent. The method may further include: executing a host application associated with the client application at the host.

[0065] In an embodiment of the present disclosure, the method may further include: executing a client application at the terminal device. The method may further include: receiving input data for the client application at the terminal device. The input data may be provided by executing a host application associated with the client application at the host. The user data to be sent may be provided by the client application in response to the input data.

[0066] According to a tenth aspect of the present disclosure, a communication system is provided. The communication system includes a host computer, the host computer including a communication interface configured to receive user data originating from a transmission from a terminal device to a base station. The terminal device may include a radio interface and processing circuitry. The processing circuitry of the terminal device may be configured to transmit a traffic data transmission (TB) to the base station using a first configuration permission. The processing circuitry of the terminal device may also be configured to autonomously retransmit the traffic data to the base station using a second configuration permission.

[0067] In an embodiment of the present disclosure, the communication system may further include the terminal device.

[0068] In an embodiment of the present disclosure, the communication system may further include the base station. The base station may include a radio interface configured to communicate with the terminal device, and a communication interface configured to forward the user data carried by the transmission from the terminal device to the base station to the host.

[0069] In an embodiment of the present disclosure, the processing circuit of the host may be configured to execute a host application.The processing circuit of the terminal device may be configured to execute a client application associated with the host application, thereby providing the user data.

[0070] In an embodiment of the present disclosure, the processing circuit of the host may be configured to execute a host application to provide the request data, and the processing circuit of the terminal device may be configured to execute a client application associated with the host application to provide the user data in response to the request data.

[0071] According to an eleventh aspect of the present disclosure, a method implemented in a communication system including a host, a base station, and a terminal device is provided. The method may include: receiving, at the host, from the base station, user data originating from a transmission received by the base station from the terminal device. The base station may receive, from the terminal device, information related to one or more autonomous uplink retransmissions of a TB utilizing one or more configured grants. The base station may determine a scheduling policy or scheduling decision for the TB based on the information.

[0072] In an embodiment of the present disclosure, the method may further include: receiving the user data from the terminal device at the base station.

[0073] In an embodiment of the present disclosure, the method may further include: initiating, at the base station, transmission of the received user data to the host.

[0074] According to a twelfth aspect of the present disclosure, a communication system is provided. The communication system includes a host computer, which includes a communication interface configured to receive user data originating from a transmission from a terminal device to a base station. The base station may include a radio interface and processing circuitry. The processing circuitry of the base station may be configured to receive information from the terminal device regarding one or more autonomous uplink retransmissions of a TB utilizing one or more configuration permissions. The processing circuitry of the base station may also be configured to determine a scheduling strategy or scheduling decision for the TB based on the information.

[0075] In an embodiment of the present disclosure, the communication system may further include the base station.

[0076] In an embodiment of the present disclosure, the communication system may further include the terminal device. The terminal device may be configured to communicate with the base station.

[0077] In an embodiment of the present disclosure, the processing circuit of the host may be configured to execute a host application.The terminal device may be configured to execute a client application associated with the host application, thereby providing the user data to be received by the host.

[0078] According to a thirteenth aspect of the present disclosure, a method implemented in a communication system including a network node and a terminal device is provided. The method may include: at the terminal device, sending a TB to the network node using a first configuration permission. The method may also include: at the terminal device, autonomously retransmitting the TB to the network node using a second configuration permission. The method may also include: at the network node, receiving information related to one or more autonomous uplink retransmissions of the TB using one or more configuration permissions from the terminal device. The method may also include: at the network node, determining a scheduling strategy or scheduling decision for the TB based on the information.

[0079] According to a fourteenth aspect of the present disclosure, a communication system comprising a terminal device and a network node is provided. The terminal device may be configured to: send a traffic transmission (TB) to the network node using a first configuration grant; and autonomously retransmit the TB to the network node using a second configuration grant. The network node may be configured to: receive information from the terminal device regarding one or more autonomous uplink retransmissions of the TB using one or more configuration grants; and determine a scheduling policy or scheduling decision for the TB based on the information. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] These and other objects, features and advantages of the present disclosure will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.

[0081] Figure 1 is a flowchart illustrating a method implemented at a terminal device according to an embodiment of the present disclosure;

[0082] Figure 2 is a flowchart illustrating a method implemented at a terminal device according to another embodiment of the present disclosure;

[0083] Figure 3 is a flowchart illustrating a method implemented at a terminal device according to another embodiment of the present disclosure;

[0084] Figure 4 is a flowchart illustrating a method implemented at a terminal device according to another embodiment of the present disclosure;

[0085] Figure 5 is a flow chart illustrating a method implemented at a network node according to an embodiment of the present disclosure;

[0086] Figure 6 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the present disclosure;

[0087] Figure 7 is a block diagram illustrating a terminal device according to an embodiment of the present disclosure;

[0088] Figure 8 is a block diagram illustrating a network node according to an embodiment of the present disclosure;

[0089] Figure 9 is a diagram illustrating a telecommunications network connected to a host via an intermediary network according to some embodiments;

[0090] Figure 10 is a diagram illustrating a host communicating with a user equipment via a base station according to some embodiments;

[0091] Figure 11 is a flow chart illustrating a method implemented in a communication system according to some embodiments;

[0092] Figure 12 is a flow chart illustrating a method implemented in a communication system according to some embodiments;

[0093] Figure 13 is a flow chart illustrating a method implemented in a communication system according to some embodiments; and

[0094] Figure 14 is a flow chart illustrating a method implemented in a communication system according to some embodiments. DETAILED DESCRIPTION

[0095] For purposes of explanation, certain details are set forth in the following description in order to provide a thorough understanding of the disclosed embodiments. However, it is apparent to one skilled in the art that the embodiments can be practiced without these specific details or with an equivalent configuration.

[0096] In NR-U, both configuration scheduling and dynamic scheduling will be used. Configuration scheduling is used to allocate semi-static periodic allocations or grants to UEs. For the uplink, there are two types of configuration scheduling schemes: Type 1 and Type 2. For Type 1, the configuration grant is configured only via Radio Resource Control (RRC) signaling. For Type 2, a configuration process similar to the Semi-Persistent Scheduling (SPS) Uplink (UL) in Long Term Evolution (LTE) is defined, that is, some parameters are pre-configured via RRC signaling, and some physical layer parameters are configured via the Medium Access Control (MAC) scheduling process. The detailed process can be found in 3GPP Technical Specification (TS) 38.321 V15.4.0. Configuration uplink scheduling will also be used in NR unlicensed operation. For NR-U, configuration scheduling can improve the channel access probability for Physical Uplink Shared Channel (PUSCH) transmission because it avoids the additional LBT for Physical Downlink Control Channel (PDCCH) transmission for each UL grant, and the UE can use the configuration grant to acquire the channel for PUSCH transmission after the LBT is successful. In this uplink transmission process, only a single LBT process is required, compared to three LBT processes (one for Scheduling Request (SR) Transmission (TX), one for UL Grant PDCCH, and one for PUSCH TX) that rely on the SR / Buffer Status Report (BSR) process. This can significantly improve the channel access probability for PUSCH transmission.

[0097] As described in 3GPP Technical Report (TR) 38.889 V16.0.0, allowing for both continuous configuration of licensed resources in time (without any gaps between the resources) and (not necessarily periodic) non-contiguous configuration of licensed resources (with gaps between the resources) is beneficial and should be considered for NR in unlicensed spectrum.

[0098] For NR-U, some enhancements to configuration scheduling are required. For example, when an initial transmission using a configuration grant is determined by the UE to have failed, the UE can perform an automatic retransmission using another configuration grant. This enhanced configuration scheduling scheme is called autonomous uplink (AUL) transmission.

[0099] In order to support autonomous retransmission using configuration grant in the uplink, a new timer is introduced to protect the HARQ process so that the retransmission can use the same HARQ process as the initial transmission for retransmission. For the case where the TB was previously sent on the configuration grant, a new timer ("CG retransmission timer") is introduced for automatic retransmission on the configuration grant (i.e. timer expiration = HARQ NACK). The new timer is started when the TB is actually sent on the configuration grant and is stopped when HARQ feedback (e.g. dynamic feedback indicator (DFI)) or a dynamic grant is received for the HARQ process. The traditional configuration grant timer and behavior are retained to prevent the configuration grant from overriding a TB scheduled by a dynamic grant, i.e. the timer is (re)started when a PDCCH is received and when a transmission is made on a dynamically granted PUSCH.

[0100] With these consensuses, when using a configured grant for data transmission, a CG retransmission timer is started for the HARQ process configured with autonomous uplink (AUL) transmission, and when the CG retransmission timer expires, an autonomous retransmission using another configured grant is triggered.

[0101] However, AUL was designed on top of the existing configuration grant framework in NR Release 15, where HARQ retransmissions are fully controlled or scheduled by the next-generation Node B (gNB). In other words, the gNB determines when to complete transmission for a HARQ process by providing a new grant to that HARQ process. AUL has introduced new functionality to support autonomous HARQ retransmissions when the CG retransmission timer expires. In this scenario, several issues may arise.

[0102] First, the gNB cannot know how many transmission attempts the UE has made, so the HARQ acknowledgement / non-acknowledgement (A / N) in the DFI may not be responded to by the gNB in a timely manner, which may cause additional waiting time for HARQ transmission.

[0103] Second, the UE may continuously initiate autonomous HARQ retransmissions for a HARQ process for a long period of time. However, due to poor radio channel quality or because the channel is rarely available due to LBT failure, the gNB may not be able to successfully receive the TB.

[0104] As a result, a significant delay may be generated for the HARQ process configured with AUL, which may further block the transmission window of upper layers such as the Radio Link Control (RLC) layer, the Packet Data Convergence Protocol (PDCP) layer, or the Transmission Control Protocol (TCP) layer.

[0105] The present disclosure proposes an improved solution for uplink transmission. The solution can be applied to a wireless communication system including a terminal device and a network node (such as a base station or any other node with similar functions). The terminal device can communicate with the base station via a radio access communication link. The base station can provide a radio access communication link to the terminal device in its communication service cell. It should be noted that communication can be performed between the terminal device and the base station according to any suitable communication standard and protocol. The terminal device may also be referred to as, for example, a device, an access terminal, a user equipment (UE), a mobile station, a mobile unit, a user station, etc. The terminal device may refer to any terminal device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may include a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a tablet computer, a wearable device, a personal digital assistant (PDA), etc.

[0106] In the context of the Internet of Things (IoT), a terminal device may refer to a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which in the 3GPP context may be referred to as a machine-type communication (MTC) device. Specific examples of such machines or devices may include sensors, metering equipment such as power meters, industrial machinery, bicycles, vehicles, or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (such as watches), and the like.

[0107] Several embodiments will now be described to explain the improved solution for uplink transmission. Although these embodiments will be described in the context of NR-U, the principles of the present disclosure can also be applied to other unlicensed operation scenarios (such as LTE LAA / eLAA / feLAA / MuLteFire) and licensed operation scenarios where autonomous uplink retransmissions using configured licenses can be employed. The term LAA refers to License Assisted Access, the term eLAA refers to Enhanced LAA, and the term feLAA refers to Further Enhanced LAA.

[0108] As a first embodiment, for a HARQ process configured with an AUL using a configuration grant, a maximum time period can be configured during which the UE is allowed to perform autonomous retransmissions. In other words, when the configured maximum time period expires, the UE stops retransmitting TBs for the corresponding HARQ process. In this way, autonomous retransmissions are only allowed within the delay budget. For example, the maximum time period can be configured based on the latency requirements of the associated service data or logical channel (LCH).

[0109] For example, a corresponding timer may be defined for this purpose. The timer may be started when any of the following events occurs: a first event, i.e., a MAC PDU is established and transmitted to the HARQ process; a second event, i.e., a first LBT operation is started for the first transmission attempt of a TB; and a third event, i.e., the first OFDM symbol of the first potential transmission opportunity for the TB occurs.

[0110] When the UE receives a HARQ ACK for the corresponding HARQ process, the timer may be stopped. If the timer expires without receiving a HARQ ACK, a HARQ failure for the HARQ process may be triggered and reported to upper layers above the MAC layer. Optionally, the report message may also include other information, such as the number of transmission attempts the UE has attempted, the HARQ process identifier (ID), and so on. The UE MAC may then notify upper layers (such as the RLC) to trigger a retransmission of the corresponding PDU. Optionally, the UE may also send a HARQ failure report to the gNB via signaling means (such as RRC, MAC CE, or Layer 1 / Layer 2 (L1 / L2) control signaling).

[0111] In this embodiment, the time length may include the time for LBT operation (such as the time when LBT failure occurs). The timer may be a newly defined timer, or an existing timer (such as configuredGrantTimer) may be reused as the timer. In the case where configuredGrantTimer is reused for controlling the maximum AUL retransmission attempts, when configuredGrantTimer expires, the UE may further check additional information to understand the reason for the timer expiration. For example, if the timer is not started / restarted due to the transmission of the configured grant for the HARQ process, the UE assumes a HARQ ACK for the associated HARQ process when the timer expires. Otherwise, the UE assumes a HARQ failure for the associated HARQ process when the timer expires. For example, the term "start" may refer to the timer being started for the first time or being started after the timer expires. The term "restart" may refer to the timer being started again before the timer expires.

[0112] In the case that the configuredGrantTimer is not reused, the UE may be configured not to start the configuredGrantTimer upon a new transmission for the associated HARQ process utilizing the configured grant. Instead, a new timer is started.

[0113] As a second embodiment, a maximum number of HARQ transmission attempts can be configured for HARQ processes configured with an AUL using a configuration grant. Similar to the first embodiment, the maximum number of HARQ transmission attempts can be configured based on the latency requirements of the associated service data or LCH. When the maximum number of HARQ transmission attempts is reached and the UE has not received a HARQ ACK, a HARQ failure for the HARQ process can be triggered and reported to upper layers above the MAC layer. Optionally, the report message can include other information, such as the number of transmission attempts attempted by the UE, the HARQ process ID, and so on. The UE MAC can then notify upper layers (such as the RLC) to trigger a retransmission for the corresponding PDU. Optionally, the UE can send a HARQ failure report to the gNB via signaling means (such as RRC, MAC CE, or L1 / L2 control signaling). In this embodiment, missed transmission attempts due to LBT failure can be taken into account.

[0114] As a third embodiment, the UE may explicitly or implicitly indicate the number of transmission attempts or the delay experienced for a TB. As an example, this information may be included in uplink control information (UCI) associated with a PUSCH transmission using a configuration grant. The UCI may be carried on the PUCCH or on the PUSCH (which may be multiplexed with the same data as the PUCCH-UCI sent on the PUSCH). As another example, the information may be included in RRC signaling, MAC CE, or L1 / L2 signaling. As yet another example, the number of transmission attempts may be implicitly indicated via the redundancy version (RVI) of the TB, which may be included in the UCI.

[0115] Upon receiving this information, for example, via UCI, the gNB can determine the delay experienced by the corresponding TB. The gNB can then determine the appropriate scheduling policy for the corresponding TB (such as scheduling priority, PDCCH parameters (to convey UL grants for retransmissions), PUSCH duration length (e.g., subcarrier spacing, number of OFDM symbols), transmit power parameters, and PUSCH preparation delay, etc.).

[0116] As an illustrative example, to meet a given latency threshold for a TB, the gNB may take at least one of the following actions to ensure that the UE completes the transmission of the associated HARQ process within a maximum time period that can be configured by the gNB:

[0117] 1) Give the TB a higher scheduling priority;

[0118] 2) Use a more reliable PDCCH format (e.g., high aggregation level) to send DCI for UL grant transmission;

[0119] 3) Scheduling resources for TB with high PUSCH transmission power and short PUSCH preparation (such as K2) / transmission duration.

[0120] In this way, autonomous uplink HARQ retransmission performance can be enhanced and at the same time latency requirements can be ensured.

[0121] Alternatively, upon receiving information from the UE, the gNB may decide to terminate the transmission of the associated HARQ process, for example, if the gNB determines that the UE has used too many resources. The gNB may then reschedule the resources for other data. The termination of transmission may be signaled via any of a variety of signaling means, including but not limited to L1 / L2 signaling (such as DCI indications), MAC CEs, and RRC signaling. Upon receiving termination signaling for a HARQ process, the UE MAC may notify upper layers of this, and may further trigger upper layer retransmissions.

[0122] As a fourth embodiment, for a pending TB associated with a HARQ process, if the UE has not received any HARQ A / N for the TB from the gNB after a predetermined number of transmission attempts or a configured time period, the UE may transmit the TB using another HARQ process. In this case, a timer for the maximum time period associated with the new HARQ process may be started, while the old timer may be stopped.

[0123] The UE may also use dynamic grants to retransmit a TB using the same or different HARQ processes, and the timer may also be restarted. For subsequent transmission attempts, the pending TB may be treated by the UE as a separate new transmission.

[0124] As a fifth embodiment, when a timer is about to expire or the maximum number of transmission attempts is about to be reached, the UE can perform proactive retransmission for the corresponding TB without waiting for DFI feedback or the expiration of the CG retransmission timer. In this way, data transmission reliability can be improved when the waiting time budget is about to be exhausted.

[0125] As a sixth embodiment, for the corresponding HARQ process, the timer may be stopped when the UE has received a dynamic grant for retransmission of a TB. In this case, the gNB takes over the scheduling of the HARQ process.

[0126] As a seventh embodiment, the UE MAC may use the transmission opportunities / timings provided by different configuration grant configurations to send a pending TB that has been established based on a configuration grant belonging to another configuration grant configuration. In this way, more transmission opportunities / timings are available for the pending TB. The relevant description of the configuration grant configuration can be found in clause 6.3.2 (ConfiguredGrantConfig information element) of 3GPP TS 38.331 (RRC protocol) V15.5.1. As defined in this technical specification, the configuration grant configuration can be notified to the terminal device by the network.

[0127] In the following, reference will be made to Figures 1 to 14 The solution is further described. Figure 1 This is a flow chart illustrating a method implemented at a terminal device according to an embodiment of the present disclosure. At block 102, the terminal device transmits a traffic block (TB) to a network node using a first configured grant. The network node may be a base station or any other node with similar functionality. The TB may be transmitted using a HARQ process. At block 104, the terminal device autonomously retransmits the TB to the network node using a second configured grant. When the terminal device determines that autonomous retransmission using the second configured grant is permitted, the TB may be autonomously retransmitted using the second configured grant.

[0128] To limit the delay caused by autonomous uplink retransmissions, five options are available. As a first option, autonomous retransmission of a TB ceases when a predetermined maximum time period has elapsed. This predetermined maximum time period can be based on the latency requirements of the associated service data or one or more associated logical channels. Alternatively, the predetermined maximum time period can encompass the elapsed time of one or more LBT operations.

[0129] For example, a timer with a timer value equal to a predetermined maximum time period can be used so that the autonomous retransmission of the TB stops when the timer expires. The timer can be started at a time point related to the transmission of the TB. As an illustrative example, the timer can be started when one of the following events occurs: a first event, that is, a MAC PDU corresponding to the TB has been generated; a second event, that is, a first LBT operation is started for the first transmission attempt of the TB; and a third event, that is, the first potential transmission opportunity for the TB occurs. The timer can be stopped when the terminal device receives an acknowledgment for the TB or a dynamic permission for the retransmission of the TB. The timer can be a newly introduced timer. Alternatively, the configuration permission timer can be reused as the timer.

[0130] As a second option, autonomous retransmissions of the TB cease when a predetermined maximum number of transmission attempts is reached. For example, the predetermined maximum number of transmission attempts may be based on the latency requirements of the associated service data or one or more associated logical channels. Transmission attempts may include initial transmissions and subsequent retransmissions. Additionally, transmission attempts may include missed attempts (for initial transmissions and subsequent retransmissions) due to LBT failures.

[0131] In the first and second options above, when the terminal device has not received an acknowledgement for the TB after a predetermined maximum time period has elapsed or a predetermined maximum number of transmission attempts has been reached, the terminal device may optionally Figure 2 A failure report for the TB is sent to the network node at block 206. Alternatively, the terminal device may trigger an upper layer retransmission of the data corresponding to the TB. The upper layer refers to a layer above the MAC layer.

[0132] Optionally, autonomous retransmission of a TB can be proactively performed when a predetermined maximum time period is about to elapse or a predetermined maximum number of transmission attempts is about to be reached. For example, autonomous retransmission of a TB can be performed without waiting for feedback for the TB or without waiting for the expiration of a configured grant retransmission timer. The expiration of a configured grant retransmission timer can be used to trigger autonomous retransmission using a configured grant.

[0133] As a third option, Figure 3 At box 308 shown, the terminal device indicates to the network node the number of transmission attempts for the TB or the delay experienced by the transmission of the TB. For example, the number of transmission attempts or the delay experienced may be indicated by one or more of the following: a redundant version of the TB; UCI; RRC signaling; MAC CE; and L1 / L2 signaling. In this way, the network node can use the indicated information to improve the retransmission from the terminal device so that the retransmission can be completed within a predetermined maximum time period. Alternatively, the network node can make a scheduling decision to terminate the retransmission for the TB. Correspondingly, the terminal device may receive signaling at box 310 indicating the termination of retransmission for the TB. In response to the signaling, the terminal device may trigger an upper layer retransmission of the data corresponding to the TB at box 312.

[0134] As a fourth option, autonomous retransmission of the TB is performed multiple times. The first part of the multiple autonomous retransmissions is performed using the same HARQ process, and the second part of the multiple autonomous retransmissions is performed using another HARQ process. The first part or the second part can be one or more of the multiple autonomous retransmissions. For example, when the terminal device has not received any HARQ feedback for the TB after a predetermined number of transmission attempts or a predetermined time period, another HARQ process can be used. The fourth option can be used in combination with any one of the first to third options above. Alternatively, in any one of the first to third options above, the autonomous retransmission of the TB can be performed one or more times using the same HARQ process.

[0135] As described above, the UE MAC may use a transmission opportunity / opportunity provided by a different configuration permission configuration to send a pending TB that has been established according to a configuration permission belonging to another configuration permission configuration. Therefore, as a fifth option, the second configuration permission belongs to the first configuration permission configuration. Figure 4 At block 414 shown, the terminal device autonomously retransmits the TB to the network node using a third configuration license that belongs to the first configuration license configuration or the second configuration license configuration, or using the second configuration license and the third configuration license. In this case, it is possible that the first configuration license belongs to the first configuration license configuration or the second configuration license configuration. It is also possible that the first configuration license belongs to the third configuration license configuration. Therefore, the size of the TB can be determined based on the first configuration license configuration, the second configuration license configuration, or the third configuration license configuration. It should be noted that the first configuration license configuration, the second configuration license configuration, or the third configuration license configuration can be received from the network node, as described above. It should also be noted that any of the first to fifth options above can be used alone or in combination.

[0136] Figure 5 5 is a flow chart illustrating a method implemented at a network node according to an embodiment of the present disclosure. The network node may be a base station or any other node with similar functionality. At block 502, the base station receives information from a terminal device regarding one or more autonomous uplink retransmissions of a TB using one or more configured permissions. For example, the information may include one or more of the following: the number of transmission attempts for the TB, or the delay experienced by the transmission of the TB; a HARQ process identifier for the TB; and a failure indication that the TB will not be autonomously retransmitted from the terminal device.

[0137] At box 504, the network node determines a scheduling strategy or scheduling decision for the TB based on the information. The scheduling strategy can be determined to ensure that retransmissions from the terminal device are completed within a predetermined maximum time period. For example, the scheduling strategy may include one or more of the following: a scheduling priority for the TB (e.g., a higher scheduling priority can be determined); parameters of the PDCCH carrying the uplink grant for the retransmission of the TB (e.g., a more reliable PDCCH format can be determined); a PUSCH duration length for the TB (e.g., a short PUSCH duration length can be determined); a transmission power parameter for the TB (e.g., a high transmission power can be determined); and a PUSCH preparation delay for the TB (e.g., a short PUSCH preparation delay can be determined).

[0138] The scheduling decision may indicate the termination of retransmissions for a TB. For example, the network node may make this scheduling decision if the terminal device has already used too many resources. Signaling indicating this scheduling decision may be sent to the terminal device at block 506. This signaling may be sent as one or more of the following: L1 / L2 signaling; MAC CE; and RRC signaling.

[0139] Boxes 502 to 506 correspond to the third option described above. Alternatively or additionally, the network node may send information indicating a predetermined maximum number of transmission attempts or a predetermined maximum time period to the terminal device at box 501, which corresponds to the first and second options described above. When the predetermined maximum number of transmission attempts is reached or the predetermined maximum time period has passed, the autonomous retransmission of the TB stops. In addition, as described above, the configuration permission configuration may be notified to the terminal device by the network. Therefore, the above method implemented at the network node may further include sending one or more configuration permission configurations to the terminal device. It should also be noted that two boxes shown consecutively in the accompanying drawings may actually be executed substantially in parallel, or they may sometimes be executed in the opposite order, depending on the functions involved.

[0140] Based on the foregoing description, at least one aspect of the present disclosure provides a method implemented in a communication system including a network node and a terminal device. The method may include: at the terminal device, sending a Traffic Transaction (TB) to the network node using a first configuration grant. The method may also include: at the terminal device, autonomously retransmitting the TB to the network node using a second configuration grant. The method may also include: at the network node, receiving information from the terminal device regarding one or more autonomous uplink retransmissions of the TB using one or more configuration grants. The method may also include: at the network node, determining a scheduling policy or scheduling decision for the TB based on the information.

[0141] Figure 66 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the present disclosure. For example, any of the aforementioned terminal devices and network nodes may be implemented by apparatus 600. As shown, apparatus 600 may include a processor 610, a memory 620 for storing programs, and an optional communication interface 630 for communicating data with other external devices via wired and / or wireless communications.

[0142] The program includes program instructions that, when executed by the processor 610, enable the apparatus 600 to operate in accordance with the embodiments of the present disclosure, as discussed above. That is, the embodiments of the present disclosure may be implemented at least in part by computer software executable by the processor 610, or by hardware, or by a combination of software and hardware.

[0143] The memory 620 may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The processor 610 may be of any type suitable for the local technical environment and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0144] Figure 7 is a block diagram illustrating a terminal device according to an embodiment of the present disclosure. As shown, terminal device 700 includes a sending module 702 and a retransmitting module 704. Sending module 702 may be configured to send a TB to a network node using a first configuration permission, as described above with respect to block 102. Retransmitting module 704 may be configured to autonomously retransmit the TB to the network node using a second configuration permission, as described above with respect to block 104.

[0145] Figure 8 800 is a block diagram illustrating a network node according to an embodiment of the present disclosure. As shown, network node 800 includes a receiving module 802 and a determining module 804. Receiving module 802 may be configured to receive information from a terminal device regarding one or more autonomous uplink retransmissions of a TB utilizing one or more configured permissions, as described above with respect to block 502. Determining module 804 may be configured to determine a scheduling policy or scheduling decision for the TB based on the information, as described above with respect to block 504. The aforementioned modules may be implemented in hardware, software, or a combination of both.

[0146] Based on the foregoing description, at least one aspect of the present disclosure provides a communication system including a terminal device and a network node. The terminal device may be configured to send a traffic transmission (TB) to the network node using a first configuration grant, and autonomously retransmit the TB to the network node using a second configuration grant. The network node may be configured to receive information from the terminal device related to one or more autonomous uplink retransmissions of the TB using one or more configuration grants, and determine a scheduling policy or scheduling decision for the TB based on the information.

[0147] refer to Figure 9 According to one embodiment, a communications system includes a telecommunications network 3210, such as a 3GPP-type cellular network, including an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, and 3212c (such as NBs, eNBs, gNBs, or other types of wireless access points), each defining a corresponding coverage area 3213a, 3213b, and 3213c. Each base station 3212a, 3212b, and 3212c can be connected to the core network 3214 via a wired or wireless connection 3215. A first UE 3291 located in the coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a can wirelessly connect to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 3212.

[0148] The telecommunications network 3210 itself is connected to a host 3230, which can be embodied in the hardware and / or software of a standalone server, a cloud-enabled server, a distributed server, or as processing resources in a server farm. The host 3230 can be under the ownership or control of a service provider, or can be operated by or on behalf of a service provider. The connections 3221 and 3222 between the telecommunications network 3210 and the host 3230 can extend directly from the core network 3214 to the host 3230, or can extend via an optional intermediate network 3220. The intermediate network 3220 can be one of a public network, a private network, or a hosted network, or a combination of more than one; if present, the intermediate network 3220 can be a backbone network or the Internet; in particular, the intermediate network 3220 can include two or more subnetworks (not shown).

[0149] Figure 9The communication system as a whole implements connectivity between connected UEs 3291, 3292 and a host 3230. This connectivity can be described as an over-the-top (OTT) connection 3250. The host 3230 and the connected UEs 3291, 3292 are configured to communicate data and / or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate networks 3220, and possibly additional infrastructure (not shown) as intermediaries. The OTT connection 3250 can be transparent in the sense that the participating communication devices traversed by the OTT connection 3250 are unaware of the routing of uplink and downlink communications. For example, the base station 3212 may not or need not be informed of the past routing of incoming downlink communications with data originating from the host 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, base station 3212 does not need to be aware of the future routing of uplink communications originating from UE 3291 toward host 3230.

[0150] Now refer to Figure 10 Describe an example implementation of the UE, base station, and host discussed in the previous paragraphs according to one embodiment. In the communication system 3300, the host 3310 includes hardware 3315, which includes a communication interface 3316, which is configured to establish and maintain a wired or wireless connection of an interface with different communication devices of the communication system 3300. The host 3310 also includes a processing circuit 3318, which may have storage and / or processing capabilities. In particular, the processing circuit 3318 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The host 3310 also includes software 3311, which is stored in the host 3310 or accessible by the host 3310 and can be executed by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as a UE 3330 connected via an OTT connection 3350 terminating at the UE 3330 and the host 3310. In providing services to the remote user, the host application 3312 may provide user data transmitted using the OTT connection 3350.

[0151] The communication system 3300 also includes a base station 3320, which is provided in the telecommunications system and includes hardware 3325 that enables it to communicate with the host 3310 and the UE 3330. The hardware 3325 may include a communication interface 3326 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 3300, and for establishing and maintaining connections with the base station 3320 in the coverage area ( Figure 10The communication interface 3326 may be configured to facilitate a connection 3360 to the host 3310. The connection 3360 may be direct, or the connection 3360 may pass through a core network (e.g., a core network of a telecommunications system) of the telecommunications system. Figure 10 3320) and / or traverse one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0152] The communication system 3300 also includes the UE 3330 mentioned above. Its hardware 3335 may include a radio interface 3337, which is configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 also includes processing circuitry 3338, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The UE 3330 also includes software 3331, which is stored in the UE 3330 or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide services to human or non-human users via the UE 3330 with the support of the host 3310. In the host 3310, a host application 3312 executing therein can communicate with a client application 3332 executing therein via an OTT connection 3350 terminating between the UE 3330 and the host 3310. In providing a service to a user, the client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 can transmit both the request data and the user data. The client application 3332 can interact with the user to generate the user data it provides.

[0153] It should be noted that Figure 10 The host 3310, base station 3320 and UE 3330 shown in FIG can be respectively Figure 9 The host 3230, one of the base stations 3212a, 3212b, 3212c, and one of the UEs 3291, 3292 are similar or identical. That is, the internal workings of these entities can be similar to Figure 10 shown, and independently, the surrounding network topology can be Figure 9 The surrounding network topology.

[0154] exist Figure 10 In the figure, an OTT connection 3350 has been abstractly drawn to illustrate communication between a host 3310 and a UE 3330 via a base station 3320, without explicit reference to any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from the UE 3330, or from the service provider operating the host 3310, or both. When the OTT connection 3350 is active, the network infrastructure can also make decisions by which the network infrastructure dynamically changes the routing (e.g., based on load balancing considerations or network reconfiguration).

[0155] The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of over-the-top (OTT) services provided to the UE 3330 using the OTT connection 3350, with the wireless connection 3370 forming the final leg of the OTT connection 3350. More specifically, the teachings of these embodiments can improve latency, thereby providing benefits such as reduced user wait time.

[0156] The measurement process may be provided for the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments. An optional network function may also be provided for reconfiguring the OTT connection 3350 between the host 3310 and the UE 3330 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 3350 may be implemented in the software 3311 and hardware 3315 of the host 3310, or in the software 3331 and hardware 3335 of the UE 3330, or in both. In some embodiments, sensors (not shown) may be deployed in or associated with the communication device through which the OTT connection 3350 passes; the sensors may participate in the measurement process by supplying values for the monitored quantities exemplified above, or for supplying values for other physical quantities from which the software 3311, 3331 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, and the like; the reconfiguration need not affect the base station 3320 and may be unknown or imperceptible to the base station 3320. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurement of throughput, propagation time, latency, etc., by the host 3310. The measurements may be achieved because the software 3311 and 3331 cause messages (particularly, empty messages or 'dummy' messages) to be transmitted using the OTT connection 3350 while the software 3311 and 3331 monitor propagation time, errors, etc.

[0157] Figure 11is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which may be reference Figure 9 and 10 For the sake of brevity of this disclosure, only the Figure 11 Reference to the accompanying drawings. In step 3410, the host provides user data. In sub-step 3411 of step 3410 (which may be optional), the host provides the user data by executing a host application. In step 3420, the host initiates a transmission carrying the user data to the UE. In step 3430 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host to the UE. In step 3440 (which may be optional), the UE executes a client application associated with the host application executed by the host.

[0158] Figure 12 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which may be reference Figure 9 and 10 For the sake of brevity of this disclosure, only the Figure 12 Reference is made to the accompanying drawings of the method. In step 3510 of the method, the host provides user data. In an optional sub-step (not shown), the host provides the user data by executing a host application. In step 3520, the host initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission can be performed via a base station. In step 3530 (which may be optional), the UE receives the user data carried in the transmission.

[0159] Figure 13 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which may be reference Figure 9 and 10 For the sake of brevity of this disclosure, only the Figure 13Reference to the accompanying drawings. In step 3610 (which may be optional), the UE receives input data provided by the host. Additionally or alternatively, in step 3620, the UE provides user data. In sub-step 3621 of step 3620 (which may be optional), the UE provides user data by executing a client application. In sub-step 3611 of step 3610 (which may be optional), the UE executes a client application that provides user data as a reaction to the received input data provided by the host. In the process of providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step 3630 (which may be optional), the UE initiates transmission of user data to the host. In step 3640 of the method, the host receives user data sent from the UE in accordance with the teachings of the embodiments described in the entire disclosure.

[0160] Figure 14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which may be reference Figure 9 and 10 For the sake of brevity of this disclosure, only the Figure 14 Reference to the accompanying drawings. In step 3710 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 3720 (which may be optional), the base station initiates a transmission of the received user data to the host. In step 3730 (which may be optional), the host receives the user data carried in the transmission initiated by the base station.

[0161] In general, various exemplary embodiments may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be shown and described as block diagrams, flow charts, or using some other graphical representation, it should be well understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controller, or other computing device, or some combination thereof.

[0162] Thus, it should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be practiced in various components such as integrated circuit chips and modules. Thus, it should be understood that the exemplary embodiments of the present disclosure can be implemented in a device embodied as an integrated circuit, wherein the integrated circuit can include circuits (and possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit that can be configured to operate according to the exemplary embodiments of the present disclosure.

[0163] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure may be embodied in computer-executable instructions executed by one or more computers or other devices, such as embodied in one or more program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. Computer-executable instructions may be stored on a computer-readable medium, such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, a RAM, etc. It will be understood by those skilled in the art that the functions of the program modules may be combined or distributed as needed in various embodiments. In addition, the functions may be embodied in firmware or hardware equivalents (such as integrated circuits, field programmable gate arrays (FPGAs), etc.) in whole or in part.

[0164] References in this disclosure to "one embodiment," "an embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with one embodiment, it is within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0165] It should be understood that although the terms "first", "second", etc. can be used in this article to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element without departing from the scope of this disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0166] The terms used herein are only used to describe the purpose of specific embodiments, and are not intended to limit the present disclosure. As used herein, the singular "a, an" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "include," "have," and / or "comprise" when used herein refer to stated features, elements, and / or components, and do not exclude the presence or addition of one or more other features, elements, components, and / or their combination. The term "connection" used herein covers the direct and / or indirect connection between two elements.

[0167] The present disclosure includes any novel feature or combination of features disclosed herein, either explicitly or in any generalized form thereof. In view of the foregoing description, various modifications and adaptations of the above-described exemplary embodiments of the present disclosure will become apparent to those skilled in the relevant art when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure.

Claims

1. A method in a terminal device, comprising: Sending (102) a transport block TB to a network node using a first configuration grant; as well as autonomously retransmitting (104) the TB to the network node using a second configuration grant; When a timer whose value is equal to a predetermined maximum time period expires, the autonomous retransmission of the TB stops.

2. The method according to claim 1, wherein The second configuration permission belongs to the configuration of the first configuration permission; and The method further comprises autonomously retransmitting (414) the TB to the network node using a third configuration permission configured according to the second configuration permission.

3. The method according to claim 1, wherein The second configuration permission belongs to the configuration of the first configuration permission; and The method further comprises autonomously retransmitting (414) the TB to the network node using a third configuration permission configured according to the first configuration permission.

4. The method according to claim 2 or 3, wherein: The first configuration permission belongs to the first configuration permission configuration or the second configuration permission configuration.

5. The method according to claim 2 or 3, wherein: The first configuration permission belongs to the third configuration permission configuration.

6. The method according to any one of claims 1 to 3, wherein The TB is sent using a hybrid automatic repeat request (HARQ) process.

7. The method according to any one of claims 1 to 3, wherein The autonomous retransmission of the TB is performed one or more times using the same HARQ process.

8. The method according to any one of claims 1 to 3, wherein The timer is started at a time point related to the transmission of the TB.

9. The method according to any one of claims 1 to 3, wherein When the terminal device receives an acknowledgement for the TB, the timer is stopped.

10. The method according to claim 3, wherein: The size of the TB is determined based on the first configuration permission configuration, the second configuration permission configuration, or the third configuration permission configuration.

11. The method according to claim 3, wherein: The first configuration-permitting configuration, the second configuration-permitting configuration, or the third configuration-permitting configuration is received from the network node.

12. The method according to any one of claims 1 to 3, wherein When the terminal device determines that autonomous retransmission permitted by the second configuration is allowed, the terminal device autonomously retransmits the TB by permitting the second configuration.

13. The method according to claim 6, wherein: Autonomous retransmission of the TB is performed multiple times; and A first portion of the plurality of autonomous retransmissions is performed using a same HARQ process, and a second portion of the plurality of autonomous retransmissions is performed using another HARQ process.

14. The method according to claim 13, wherein The another HARQ process is used when the terminal device has not received any HARQ feedback for the TB after a predetermined number of transmission attempts or a predetermined time period.

15. The method according to any one of claims 1 to 3, wherein The second configuration permission belongs to the configuration of the first configuration permission; and The method further comprises autonomously retransmitting (414) the TB to the network node using the second configuration permission and the third configuration permission.

16. The method according to any one of claims 1 to 3, wherein When a predetermined maximum number of transmission attempts is reached or a predetermined maximum time period has elapsed, autonomous retransmission of the TB stops.

17. The method according to claim 16, wherein The predetermined maximum number of transmission attempts or the predetermined maximum time period is based on latency requirements of the associated service data or the associated one or more logical channels.

18. The method according to claim 16, further comprising: When the terminal device has not received an acknowledgement for the TB after the predetermined maximum number of transmission attempts has been reached or the predetermined maximum time period has elapsed, a failure report for the TB is sent (206) to the network node.

19. The method according to claim 16, wherein The transmission attempts include one or more transmission attempts missed due to a listen-before-talk (LBT) failure; or The predetermined maximum time period includes the time elapsed for one or more LBT operations.

20. The method according to claim 16, wherein When the predetermined maximum number of transmission attempts is about to be reached or the predetermined maximum time period is about to elapse, autonomous retransmission of the TB is proactively performed.

21. The method according to claim 20, wherein Autonomous retransmission of the TB is performed proactively by: performing autonomous retransmission of the TB without waiting for feedback for the TB or waiting for expiration of a configured grant retransmission timer; and The expiration of the configuration grant retransmission timer is used to trigger autonomous retransmission of the configuration grant.

22. The method according to any one of claims 1 to 3, wherein When the terminal device receives a dynamic grant for retransmission of the TB, the timer is stopped.

23. The method according to claim 22, wherein The timer is started when one of the following events occurs: A media access control MAC protocol data unit (PDU) corresponding to the TB has been generated; A first transmission attempt for the TB initiates a first LBT operation; as well as A first potential transmission opportunity for the TB occurs.

24. The method according to any one of claims 1 to 3, wherein The configuration permission timer is reused as the timer.

25. The method according to any one of claims 1 to 3, further comprising: The number of transmission attempts for the TB or the delay experienced in the transmission of the TB is indicated (308) to the network node.

26. The method according to claim 25, wherein The number of transmission attempts or the delay experienced is indicated by one or more of the following: A redundant version of the TB; Uplink control information UCI; Radio Resource Control (RRC) signaling; MAC Control Element CE; and Layer 1 or Layer 2 signaling.

27. The method of claim 25, further comprising: Signaling indicating termination of retransmission for the TB is received (310).

28. The method according to claim 27, further comprising: In response to the signaling, upper layer retransmission of data corresponding to the TB is triggered (312).

29. A method in a network node, comprising: receiving (502) information from a terminal device relating to one or more autonomous uplink retransmissions of a transport block TB using one or more configured grants; as well as determining (504) a scheduling strategy or scheduling decision for the TB based on the information; The scheduling decision indicates termination of retransmission for the TB.

30. The method of claim 29, further comprising: One or more configuration permission configurations are sent to the terminal device.

31. The method according to claim 29 or 30, wherein The scheduling policy is determined to ensure that the retransmission from the terminal device is completed within a predetermined maximum time period.

32. The method according to claim 29 or 30, further comprising: Signaling indicating the scheduling decision is sent (506) to the terminal device.

33. The method according to claim 32, wherein The signaling is sent as one or more of the following: Layer 1 / Layer 2 signaling; MAC CE; and RRC signaling.

34. The method according to claim 29 or 30, wherein The information includes one or more of the following: the number of transmission attempts for the TB or the delay experienced in the transmission of the TB; A hybrid automatic repeat request (HARQ) process identifier for the TB; as well as A failure indication that the TB will not be autonomously retransmitted from the terminal device.

35. The method according to claim 29 or 30, wherein The scheduling strategy includes one or more of the following: The scheduling priority of the TB; Parameters of a physical downlink control channel (PDCCH) carrying an uplink grant for retransmission of the TB; Duration length of the physical uplink shared channel PUSCH used for the TB; a transmission power parameter for the TB; and PUSCH preparation delay for the TB.

36. The method according to claim 29 or 30, further comprising: sending (501) information indicating a predetermined maximum number of transmission attempts or a predetermined maximum time period to a terminal device; as well as Therein, when the predetermined maximum number of transmission attempts is reached or the predetermined maximum time period has passed, the autonomous retransmission of the TB stops.

37. The method according to claim 36, wherein The predetermined maximum number of transmission attempts or the predetermined maximum time period is based on latency requirements of the associated service data or the associated one or more logical channels.

38. A terminal device (600), comprising: at least one processor (610); as well as at least one memory (620), the at least one memory (620) containing instructions executable by the at least one processor (610), whereby the terminal device (600) is operable to: sending a transport block TB to the network node using the first configured grant; as well as autonomously retransmitting the TB to the network node using a second configuration grant, When a timer whose value is equal to a predetermined maximum time period expires, the autonomous retransmission of the TB stops.

39. The terminal device (600) according to claim 38, wherein: The terminal device (600) is operable to perform the method according to any one of claims 2 to 28.

40. A network node (600), comprising: at least one processor (610); as well as at least one memory (620), the at least one memory (620) containing instructions executable by the at least one processor (610), whereby the network node (600) is operable to: receiving, from a terminal device, information relating to one or more autonomous uplink retransmissions of a transport block TB using one or more configured grants; as well as determining a scheduling strategy or scheduling decision for the TB based on the information, The scheduling decision indicates termination of retransmission for the TB.

41. The network node (600) of claim 40, wherein: The network node (600) is operable to perform a method according to any one of claims 30 to 37.

42. A method implemented in a communication system including a network node and a terminal device, comprising: At the terminal device, sending (102) a transport block TB to the network node using a first configuration grant; autonomously retransmitting (104) the TB to the network node using a second configuration permission at the terminal device; wherein, when a timer value equal to a predetermined maximum time period expires, autonomous retransmission of the TB stops; receiving (502), at the network node, from a terminal device, information relating to one or more autonomous uplink retransmissions of a transport block TB with one or more configured grants; and determining (504) at the network node a scheduling strategy or a scheduling decision for the TB based on the information, The scheduling decision indicates termination of retransmission for the TB.

43. A communication system comprising: A terminal device configured to: send a transport block (TB) to a network node using a first configuration grant, and autonomously retransmit the TB to the network node using a second configuration grant; wherein the autonomous retransmission of the TB stops when a timer having a timer value equal to a predetermined maximum time period expires; and A network node configured to: receive information related to one or more autonomous uplink retransmissions of the TB using one or more configuration permissions from the terminal device, and determine a scheduling strategy or scheduling decision for the TB based on the information, wherein the scheduling decision indicates termination of retransmissions for the TB.

44. A computer-readable storage medium comprising instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 37.

Images