CN110050434B

CN110050434B - Feedback transmission for hybrid services

Info

Publication number: CN110050434B
Application number: CN201880002928.XA
Authority: CN
Inventors: 刘进华; 王敏
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2017-11-14
Filing date: 2018-11-13
Publication date: 2022-07-22
Anticipated expiration: 2038-11-13
Also published as: EP3504824A4; CN110050434A; US11522665B2; EP3504824A1; US20210376987A1; WO2019096118A1

Abstract

An embodiment of the present application proposes a method for communication. The method comprises the following steps: configuration information is obtained from a network node. The configuration information relates to resource configurations for feedback transmission of data transmissions from the network node to a terminal device for different types of services. The method further comprises: determining a correspondence between the resource configuration and the different type of service based at least in part on the configuration information.

Description

Feedback transmission for hybrid services

Technical Field

The present disclosure relates generally to communication networks and, more particularly, to feedback transmission in communication networks.

Background

This section introduces various aspects that may help to better understand the disclosure. Accordingly, what is set forth in this section is to be read in this manner and should not be construed as an admission as to what is prior art or what is not prior art.

Communication service providers and network operators are continually challenged to deliver value and convenience to consumers (e.g., by providing compelling network services and capabilities). With the rapid development of networking and communication technologies, it may be assumed that wireless communication networks such as Long Term Evolution (LTE)/fourth generation (4G) networks or New Radio (NR)/fifth generation (5G) networks support multiple types of services within a common Radio Access Network (RAN), including, for example, enhanced mobile broadband (eMBB), large-scale machine type communication (mtc), and ultra-reliable and low-latency communication (URLLC), and the like. A terminal device in the network may receive multiple services simultaneously and needs to transmit feedback information for the received services. However, multiple services may have different quality of service (QoS) requirements in terms of latency, data rate, and packet loss. Thus, it is desirable to improve feedback transmission for hybrid services.

Disclosure of Invention

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.

Wireless communication networks such as NR or LTE may support multiple services for User Equipment (UE) with multiple requirements. For example, for physical downlink shared channel/physical uplink shared channel (PDSCH/PUSCH), the network may choose to use different sets of parameters (numerologies) or transmission durations in order to achieve service differentiation. On the other hand, hybrid automatic repeat request acknowledgement/negative acknowledgement (HARQ a/N) for PDSCH transmissions may be transmitted in the uplink via a Physical Uplink Control Channel (PUCCH) or multiplexed with data transmissions on the PUSCH. For delay tolerant services, a long PUCCH/PUSCH format with a relatively long transmission duration may be acceptable. However, for delay sensitive services, a long PUCCH/PUSCH format with a long transmission duration may not be suitable for HARQ a/N transmission due to the strict delay requirements. Therefore, it may be desirable to provide an efficient mechanism to enable differentiating the HARQ a/N transmission framework among multiple service scenarios.

The present disclosure proposes a feedback transmission mechanism for a communication network, which may enable a terminal device to implement differentiated feedback transmission in order to meet various requirements of multiple services.

According to a first aspect of the present disclosure, a method implemented by a terminal device is provided. The method comprises the following steps: configuration information is obtained from a network node. The configuration information relates to resource configurations for feedback transmission of data transmissions from the network node to the terminal device for different types of services. The method further comprises the following steps: determining a correspondence between the resource configuration and the different types of services based at least in part on the configuration information.

According to an exemplary embodiment, the method according to the first aspect of the present disclosure may further comprise: the method may include receiving a data transmission for a service from the network node, and identifying a type of the service by using metric information of the received data transmission.

According to an exemplary embodiment, the method according to the first aspect of the present disclosure may further comprise: determining a resource configuration for a feedback transmission of the received data transmission based at least in part on the identified service type and a correspondence between the resource configuration and the different types of services. Optionally, the method according to the first aspect of the present disclosure may further comprise: implementing the feedback transmission according to the determined resource configuration.

According to a second aspect of the present disclosure, an apparatus is provided. The device comprises: one or more processors, and one or more memories including computer program code. The one or more memories and the computer program code may be configured, with the one or more processors, to cause the apparatus to perform at least any of the steps of the method according to the first aspect of the disclosure.

According to a third aspect of the present disclosure, there is provided a computer readable medium having embodied thereon computer program code which, when executed on a computer, causes the computer to carry out any of the steps of the method according to the first aspect of the present disclosure.

According to a fourth aspect of the present disclosure, an apparatus is provided. The apparatus includes an acquisition unit and a determination unit. According to some exemplary embodiments, the obtaining unit is operable to perform at least the obtaining step of the method according to the first aspect of the present disclosure. The determination unit is operable to perform at least the determining step of the method according to the first aspect of the present disclosure.

According to a fifth aspect of the present disclosure, a method implemented by a network node is provided. The method comprises the following steps: determining configuration information relating to resource configurations of feedback transmissions for data transmissions from the network node to a terminal device for different types of services. The method further comprises the following steps: and providing the configuration information to the terminal equipment. The configuration information may indicate a correspondence between the resource configuration and the different types of services.

According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: data transmission for the service is carried out from the network node to the terminal device. Optionally, the method according to the fifth aspect of the present disclosure may further include: receiving a feedback transmission for the data transmission from the terminal device. The feedback transmission may be based on a resource configuration corresponding to the type of service.

According to a sixth aspect of the present disclosure, an apparatus is provided. The device comprises: one or more processors, and one or more memories including computer program code. The one or more memories and the computer program code may be configured, with the one or more processors, to cause the apparatus to perform at least any of the steps of the method according to the fifth aspect of the disclosure.

According to a seventh aspect of the present disclosure, there is provided a computer readable medium having embodied thereon computer program code which, when executed on a computer, causes the computer to carry out any of the steps of the method according to the fifth aspect of the present disclosure.

According to an eighth aspect of the present disclosure, an apparatus is provided. The apparatus includes a determination unit and a providing unit. According to some exemplary embodiments, the determining unit is operable to perform at least the determining step of the method according to the fifth aspect of the present disclosure. The providing unit is operable to perform at least the providing step of the method according to the fifth aspect of the present disclosure.

According to an exemplary embodiment, the correspondence between the resource configuration and the different types of services may indicate: radio resources spanning a relatively short duration in the time domain may be used for feedback transmission for a class of services having relatively high requirements for at least one of latency and reliability.

According to an exemplary embodiment, the correspondence between the resource configuration and the different types of services may indicate: radio resources having a transmission duration shorter than the duration threshold may be used for feedback transmission for a class of services for which the delay requirement for the service is less than the delay threshold.

According to an example embodiment, the correspondence between the resource configuration and the different types of services may indicate: radio resources having a transmission duration shorter than a duration threshold may be used for feedback transmission for a class of services requiring a reliability of the service higher than the reliability threshold.

According to an exemplary embodiment, the correspondence between the duration threshold and the delay threshold and/or the reliability threshold may be predefined or adaptively adjusted.

According to an exemplary embodiment, the different types of services may be identified by metric information of data transmissions from the network node to the terminal device.

According to an exemplary embodiment, the metric information of the data transmission from the network node to the terminal device may comprise at least one of: a transmission duration associated with radio resources granted for the data transmission, one or more parameters related to Downlink Control Information (DCI) for the data transmission, and a resource indicator related to the data transmission.

According to an example embodiment, the one or more parameters related to the DCI may include at least one of: a Downlink Assignment Index (DAI), a format of the DCI, a search space of the DCI, an indicator specifying a resource configuration for feedback transmission, a radio network identifier, and a data check sequence.

According to an example embodiment, the resource indicator may comprise at least one of: a bandwidth part (BWP) index, and an index of one or more Physical Resource Blocks (PRBs).

According to a ninth aspect of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE. The method can comprise the following steps: user data is provided at the host computer. Optionally, the method may comprise: at the host computer, initiating a transmission for the UE carrying the user data via a cellular network comprising the base station, which may implement any of the steps of the method according to the fifth aspect of the disclosure.

According to a tenth aspect of the present disclosure, there is provided a communication system including a host computer. The host computer may include: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The cellular network may include a base station having a radio interface and processing circuitry. The processing circuitry of the base station may be configured to implement any of the steps of the method according to the fifth aspect of the present disclosure.

According to an eleventh aspect of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE. The method can comprise the following steps: user data is provided at the host computer. Optionally, the method may comprise: at the host computer, initiating a transmission for the UE carrying the user data via a cellular network including the base station. The UE may implement any of the steps of the method according to the first aspect of the present disclosure.

According to a twelfth aspect of the present disclosure, there is provided a communication system including a host computer. The host computer may include: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to implement any of the steps of the method according to the first aspect of the present disclosure.

According to a thirteenth aspect of the present disclosure, there is provided a method implemented in a communication system, which may include a host computer, a base station, and a UE. The method can comprise the following steps: at the host computer, user data transmitted from the UE to the base station is received, the UE may implement any of the steps of the method according to the first aspect of the disclosure.

According to a fourteenth aspect of the present disclosure, there is provided a communication system including a host computer. The host computer may include a communication interface configured to receive user data originating from a transmission from a UE to a base station. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to implement any of the steps of the method according to the first aspect of the present disclosure.

According to a fifteenth aspect of the present disclosure, a method implemented in a communication system may include a host computer, a base station, and a UE. The method can comprise the following steps: at the host computer, receiving, from the base station, user data originating from transmissions that the base station has received from the UE. The base station may implement any of the steps of the method according to the fifth aspect of the present disclosure.

According to a sixteenth aspect of the present disclosure, there is provided a communication system, which may include a host computer. The host computer may include a communication interface configured to receive user data originating from a transmission from a UE 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 implement any of the steps of the method according to the fifth aspect of the present disclosure.

Drawings

The disclosure itself, as well as a preferred mode of use, further objectives, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

fig. 1 is a diagram illustrating an example of a set of mixing parameters with the same carrier according to an embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating a method according to an embodiment of the present disclosure;

FIG. 3 is a flow chart illustrating a method according to another embodiment of the present disclosure;

FIG. 4 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

FIG. 5 is a block diagram illustrating an apparatus according to an embodiment of the present disclosure;

FIG. 6 is a block diagram illustrating an apparatus according to another embodiment of the present disclosure;

FIG. 7 is a block diagram illustrating a telecommunications network connected to host computers via an intermediate network in accordance with some embodiments of the present disclosure;

FIG. 8 is a block diagram illustrating a host computer communicating with a UE over a partially wireless connection via a base station in accordance with some embodiments of the present disclosure;

fig. 9 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure;

fig. 10 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure;

fig. 11 is a flow chart illustrating a method implemented in a communication system in accordance with an embodiment of the present disclosure; and

fig. 12 is a flow chart illustrating a method implemented in a communication system in accordance with an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It is understood that these examples are discussed only to enable those skilled in the art to better understand and to implement the disclosure thereby, and are not intended to imply any limitations on the scope of the disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that: the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

As used herein, the term "wireless communication network" refers to a network that conforms to any suitable communication standard, such as NR, LTE-advanced, LTE, Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), etc. Further, communication between terminal devices and network nodes in a communication network may be implemented according to any suitable communication protocol, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), 4G, 4.5G, 5G communication protocols and/or any other protocol currently known or developed in the future.

The term "network node" refers to a network device in a communication network through which a terminal device accesses the network and receives services therefrom. A network node may refer to a Base Station (BS), an Access Point (AP), a multi-cell/Multicast Coordination Entity (MCE), a gateway, a server, a controller, or any other suitable device in a wireless communication network. The BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gdnodeb or gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, a low power node such as a femtocell, picocell, and so on.

Still other examples of network nodes include: an MSR radio such as a multi-standard radio (MSR) BS, a network controller such as a Radio Network Controller (RNC) or a Base Station Controller (BSC), a Base Transceiver Station (BTS), a transmission point, a transmission node, and/or a positioning node, among others. More generally, however, a network node may represent any suitable device (or group of devices) capable of, configured to, arranged and/or operable to enable and/or provide access by a terminal device to a wireless communication network or to provide some service to a terminal device that has access to a wireless communication network.

The term "terminal device" refers to any end device that can access a communication network and receive services therefrom. By way of example, and not limitation, terminal device may refer to a mobile terminal, UE, or other suitable device. The UE may be, for example, a subscriber station, a portable subscriber station, a Mobile Station (MS), or an Access Terminal (AT). Terminal devices may include, but are not limited to: portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, mobile phones, cellular phones, smart phones, tablet computers, wearable devices, Personal Digital Assistants (PDAs), vehicles, and the like.

As yet another particular example, in an internet of things (IoT) scenario, a terminal device may represent a machine or other device that implements monitoring and/or measurements and transmits results of such monitoring and/or measurements to another terminal device and/or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a Machine Type Communication (MTC) device in a 3GPP context.

As one particular example, the terminal device may be a UE implementing the 3GPP narrowband internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, etc. In other scenarios, the terminal device may represent a vehicle or other device, such as a medical instrument capable of monitoring and/or reporting its operational status or other functions related to its operation.

As used herein, the terms "first," "second," and the like refer to different elements. The singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises," "comprising," "has," "having," "contains," "including," and/or "containing," when used herein, specify the presence of stated features, elements, and/or components, but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof. The term "based on" is to be understood as "based at least in part on". The terms "one embodiment" and "an embodiment" are to be read as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other definitions may be explicitly and implicitly included below.

As previously described, various types of services such as URLLC, eMBB, and mtc may be supported by wireless communication networks such as NR and LTE. Different services may have different QoS requirements in terms of latency, reliability, data rate, and packet loss. For example, URLLC services require low latency and/or high reliability, but typically it also has low data rates and sparse data transmission intervals. mtc services typically require long battery life but do not require low latency or high data rates, which are typically combined with a small number of infrequent packets. The eMBB service requires high data rates and its requirements for latency may be stringent, but is generally less stringent than the URLLC service.

In order to meet the requirements of different services, it may be beneficial to introduce support for the set of mixing parameters within one carrier, thereby enabling different sets of parameters to be used for the services to achieve different transmission delays. The term "parameter set" may be used to refer to some parameters related to the radio resources used for signal transmission, such as subcarrier spacing (SCS), length or duration of Cyclic Prefix (CP), length or duration of Orthogonal Frequency Division Multiplexing (OFDM) symbols, number of symbols contained in a slot and/or slot duration, etc.

In LTE, OFDM symbols are created by using 15kHz SCS, corresponding to a duration of 66.67 μ s (no CP). In NR, a similar reference is assumed, but various parameter sets with other frequency intervals are also allowed, such as 30kHz, 60kHz and 120kHz, and it is currently agreed to support 2 kHzⁿSCS at × 15kHz (n ═ 1,2, 3.). These parameter sets give shorter OFDM symbol duration, e.g. 66.67/2ⁿμ s. Thus, n is used>1, each OFDM symbol is shorter in time but wider in occupied bandwidth.

Fig. 1 is a diagram illustrating an example of a set of mixing parameters having the same carrier according to an embodiment of the present disclosure. In the example shown in fig. 1, two parameter sets are mixed in the same carrier, denoted "sub-band with narrow sub-carriers" and "sub-band with wide sub-carriers" respectively in fig. 1. It should be understood that fig. 1 is only schematically illustratedTwo types of SCS and corresponding micro-subframes are shown. Indeed, other 2 s may be supported by a wireless communication network such as an NRⁿSCS of 15kHz, and n may be configurable.

Furthermore, wireless communication networks such as NR may also support different PDSCH/PUSCH transmission durations using different time units such as slots and minislots. As an example, a slot may include 14 OFDM symbols, while a minislot may include 2, 4, or 7 OFDM symbols. The network may selectively use different sets of parameters or transmission durations to achieve service differentiation.

On the other hand, a terminal device, such as a UE, may receive multiple services associated with differentiated QoS requirements simultaneously. HARQ feedback transmission in the uplink for URLLC services may require strict latency and high transmission reliability compared to HARQ feedback transmission for eMBB services. Existing PUCCH transmissions carrying downlink HARQ acknowledgements may have a long PUCCH format that includes more OFDM symbols in the time domain, or a short PUCCH format that spans fewer OFDM symbols. The HARQ entities on the UE side and/or the network side can only see the HARQ process Identifiers (IDs) and do not know the service type associated with each HARQ feedback transmission. Therefore, HARQ acknowledgements cannot distinguish between service types. For example, the HARQ acknowledgement may represent feedback for data transmission for both delay sensitive and delay tolerant services. If the HARQ acknowledgement is carried over an inappropriate PUCCH format, the latency requirements of the latency sensitive service may be violated accordingly.

Therefore, it may be desirable to introduce an efficient solution to configure differentiated feedback transmissions for different services. In the proposed solution according to some of the example embodiments, a correspondence between resource configurations of feedback transmissions and different types of services may be established in order to meet different requirements, e.g. in terms of reliability and/or latency. According to example embodiments, a network node such as a gNB may facilitate establishing a correspondence between downlink data transmissions and their HARQ acknowledgements in the uplink (e.g., via PUCCH or multiplexed with data transmissions on PUSCH) for different types of services for a terminal device such as a UE. The correspondence may be set or determined according to Medium Access Control (MAC) and Physical (PHY) metrics, such as PDSCH duration, Downlink Assignment Index (DAI) range, Downlink Control Information (DCI) format, DCI search space, bandwidth part (BWP) index, special indicator in DCI, Radio Network Temporary Identifier (RNTI) and/or Cyclic Redundancy Check (CRC) sequence, etc. With knowledge of such correspondence, transmissions of downlink HARQ acknowledgements for different services may be handled differently.

It is noted that some embodiments of the present disclosure are described primarily with respect to LTE or NR specifications, which are used as non-limiting examples of specific example network configurations and system deployments. As such, the description of the exemplary embodiments presented herein refers specifically to the terminology directly associated therewith. Such terms are used only in the context of the presented non-limiting examples and embodiments, and naturally do not limit the disclosure in any way. Rather, any other system configuration or radio technology may be equally used, as long as the exemplary embodiments described herein are suitable.

Fig. 2 is a flow chart illustrating a method 200 according to an embodiment of the present disclosure. The method 200 shown in fig. 2 may be implemented by a network node or a device communicatively coupled to a network node. According to an example embodiment, a network node (such as a gNB) may support multiple services with various requirements for a terminal device (such as a UE). For example, the plurality of services may include eMBB, mtc, URLLC, and/or other services that may have different QoS requirements in terms of latency, reliability, data rate, and/or packet loss.

According to the exemplary method 200 shown in fig. 2, the network node may determine configuration information for the terminal device, as shown at block 202. The configuration information may relate to resource configurations for feedback transmission of data transmissions from the network node to the terminal device for different types of services. According to an example embodiment, the resource configuration for feedback transmission may include PUCCH resource configuration for downlink HARQ acknowledgement and various types of Uplink Control Information (UCI). For example, the PUCCH resource configuration may be identified by one or more parameters including at least one of time-frequency resources, UCI format, demodulation reference signal (DMRS) configuration, Orthogonal Cover Code (OCC), and the like.

It may be appreciated that although some example embodiments of the present disclosure are primarily described in connection with HARQ a/N transmission via PUCCH, the resource configuration of the feedback transmission may include other types of radio resource configurations, e.g., PUSCH resource configurations where downlink HARQ acknowledgements are multiplexed with data transmission on the PUSCH. In this regard, the PUSCH resource configuration may be identified by one or more parameters associated with the PUSCH and/or data transmission on the PUSCH.

According to an example embodiment, the network node may provide configuration information to the terminal device, as shown at block 204. The configuration information may indicate a correspondence between the resource configuration and the different types of services. According to embodiments, the terminal device may provide a resource configuration, such as multiple PUCCH resource configurations for downlink HARQ acknowledgements and other types of information of UCI, by the network node. In particular, each resource configuration may be associated with at least one downlink logical channel and/or service. The PHY and HARQ entities may be informed of information of the at least one downlink logical channel and/or service from the MAC layer. Thus, a PUCCH resource configuration having a specific resource and format may be applied to feedback transmission of a specific downlink service.

According to an exemplary embodiment, the correspondence between the resource configuration and the different types of services may indicate: radio resources spanning a relatively short duration in the time domain may be suitable for feedback transmission for a class of services having relatively high requirements for at least one of latency and reliability. According to an embodiment, a short PUCCH spanning a short duration in the time domain (e.g., by including fewer OFDM symbols) may be used to carry HARQ a/N information and other UCI for latency and/or reliability sensitive services, while a long PUCCH spanning a long duration in the time domain (e.g., by including more OFDM symbols) may be used to carry HARQ a/N information and other UCI information for latency and/or reliability non-sensitive services.

According to an exemplary embodiment, the correspondence between the resource configuration and the different types of services may indicate: radio resources having a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service delay less than the delay threshold.

Alternatively or additionally, the correspondence between the resource configuration and the different types of services may indicate: radio resources with a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service reliability above the reliability threshold.

Optionally, at least one of the duration threshold, the delay threshold, and the reliability threshold may vary with different service types and/or resource configurations. For example, the duration threshold (and optionally the latency threshold and/or the reliability threshold) may be adjusted according to different combinations of resources available for feedback transmission.

According to an example embodiment, the latency threshold and/or reliability threshold may be adjusted for a type of service. For example, in case the network node supports a first type of service and a second type of service for the terminal device, while the first type of service requires less delay than the second type of service, the first radio resources having a transmission duration shorter than the duration threshold may be applicable for feedback transmission of the first type of service. In this case, the delay threshold may coincide with the delay required for the second type of service. In another example, the first radio resources may also be applicable for feedback transmission for a second type of service in case the network node supports the second type of service and a third type of service for the terminal device, while the second type of service requires a higher reliability than the third type of service. In this case, the reliability threshold may be consistent with the reliability required for the third class of service.

According to an exemplary embodiment, there may be a correspondence between the duration threshold and the delay threshold and/or the reliability threshold. For example, the first duration threshold may correspond to a first latency threshold and/or a first reliability threshold. This means that radio resources with a transmission duration shorter than the first duration threshold may be suitable for feedback transmission for a class of services where the required service delay is smaller than the first delay threshold and/or the required service reliability is higher than the first reliability threshold. Similarly, the second duration threshold may correspond to a second delay threshold and/or a second reliability threshold, the third duration threshold may correspond to a third delay threshold and/or a third reliability threshold, and so on.

According to an exemplary embodiment, the correspondence between the duration threshold and the delay threshold and/or the reliability threshold may be predefined or adaptively adjusted. For example, in case the network node supports a first type of service and a second type of service for the terminal device, while the required service delay for the first type of service compared to the second type of service is smaller than a second delay threshold, a second radio resource with a transmission duration shorter than the second duration threshold may be applicable for feedback transmission for the first type of service. Optionally, the second radio resource may also be adapted for feedback transmission for a second type of service in case the network node supports the second type of service and a third type of service for the terminal device, and the required service delay for the second type of service compared to the third type of service is smaller than a third delay threshold.

According to an exemplary embodiment, different types of services may be identified by metric information of data transmissions from the network node to the terminal device. The metric information may be related to one or more MAC and PHY metrics. According to an exemplary embodiment, the metric information of the data transmission from the network node to the terminal device may comprise at least one of: a transmission duration associated with a radio resource granted for data transmission; one or more parameters related to DCI for data transmission; and a resource indicator associated with the data transmission.

According to an exemplary embodiment, the type of service may be identified by a transmission duration associated with a radio resource granted for downlink data transmission of the service, in which embodiment a resource configuration for feedback transmission may be mapped to a class of downlink data transmissions associated with a range of transmission durations. In this embodiment, downlink logical channels and/or services having specific QoS requirements may be supported by using granted resources (grants), e.g., PDSCH, associated with transmission durations specific to QoS requirements. For example, downlink data for latency and/or reliability sensitive services may be transmitted utilizing granted resources associated with short transmission durations, while downlink data for latency and/or reliability tolerant services may be transmitted utilizing granted resources associated with long transmission durations. Accordingly, downlink HARQ a/N feedback for latency and/or reliability sensitive services may be transmitted utilizing granted resources associated with short transmission durations (such as PUCCH), while downlink HARQ a/N feedback for latency and/or reliability tolerant services may be transmitted utilizing granted resources associated with long transmission durations.

According to an example embodiment, where the type of service may be identified by one or more parameters related to DCI for downlink data transmission of the service, the resource configuration of the feedback transmission may be mapped to a type of downlink data transmission associated with the one or more parameters related to the DCI. According to an exemplary embodiment, the one or more parameters related to the DCI may include: the DAI, the format of the DCI, the search space of the DCI, an indicator specified for the resource configuration of the feedback transmission (e.g., which may be included in the DCI), a radio network identifier (such as RNTI), and/or a data check sequence (such as CRC sequence), among others.

In an exemplary embodiment where the service type may be identified by a DAI or a range of DAIs, the resource configuration for the feedback transmission may be mapped to a type of downlink data transmission associated with the range of DAIs. For example, where downlink PDSCH transmissions are scheduled through DCI including a DAI below or equal to a given threshold, it may be determined that the corresponding PDSCH transmission may carry data for delay tolerant services. The given threshold may be predefined or pre-configured by some Radio Resource Control (RRC) signaling. In the case where downlink PDSCH transmissions are scheduled through DCI including DAIs above a given threshold, it may be determined that the corresponding PDSCH transmission may carry data for a delay-sensitive service. In this way, downlink HARQ a/N feedback (and optionally other types of UCI) for different services may be transmitted with a more appropriate PUCCH resource configuration depending on the determined service type.

In an exemplary embodiment where the type of service may be identified by the format of the DCI, the resource configuration of the feedback transmission may be mapped to a type of downlink data transmission associated with a particular DCI format. For example, the network may configure: a scheduler at the network node may schedule services with low latency requirements and/or high reliability requirements through DCI type 1, while other services are scheduled using DCI type 2. As such, the service type may be determined based at least in part on the DCI type or format. Thus, according to the determined service type, feedback transmission for different services can be configured with more appropriate resources.

Alternatively or additionally, the service type may be identified by the DCI search space, and in this case, the resource configuration of the feedback transmission may be mapped to a type of downlink data transmission associated with the particular DCI search space. For example, different configurations of DCI search spaces may be assigned to multiple services with different QoS requirements. Thus, the type of service may be determined based at least in part on the specified DCI search space. Depending on the determined service type, appropriate radio resources may be configured for the respective feedback transmission.

According to some example embodiments, the service type may be identified by directly indicating a resource configuration of the feedback transmission using the DCI. For example, an indicator specified for the resource configuration of the feedback transmission may be included in DCI carrying a downlink assignment (assignment). A particular indicator may dynamically indicate which PUCCH resource configuration is available to carry the corresponding HARQ a/N feedback for downlink transmissions.

Alternatively or additionally, the service type may be identified by indirectly indicating the resource configuration of the feedback transmission using some DCI related information. For example, a different radio network identifier, such as RNTI or cell-RNTI (C-RNTIs), may be configured for DCI carrying a downlink assignment. Optionally, DCI may also be configured with a different data check sequence (such as a CRC sequence). Based at least in part on the RNTI and/or CRC sequences determined by decoding DCI on the PDCCH, the UE may determine which PUCCH resource configuration may be used to carry the corresponding HARQ a/N feedback and other types of UCI according to a predetermined correspondence between RNTI (and/or CRC sequences) and PUCCH resource configurations.

According to an example embodiment in which the type of service may be identified by a resource indicator related to downlink data transmissions, the resource configuration for feedback transmissions may be mapped to a type of downlink data transmission associated with the resource indicator. According to some example embodiments, the resource indicator may comprise at least one of: a bandwidth part (BWP) index, and an index of one or more Physical Resource Blocks (PRBs). In this case, the correspondence between the BWP index (and/or PRB index/PRB group index) and the PUCCH resource configuration may be pre-configured or predefined as needed. Thus, based at least in part on a given BWP index and/or PRB (or PRB group) index for a downlink data transmission, the UE may determine which PUCCH resource configuration may be used to carry the corresponding HARQ a/N feedback for the downlink data transmission, as well as other types of UCI.

Alternatively, the network node may implement data transmission for a service of the terminal device according to the exemplary method 200 shown in fig. 2. The terminal device may determine a resource configuration suitable for feedback transmission for the service because, as described in connection with block 204, the configuration information provided to the terminal device may indicate a correspondence between different resource configurations for feedback transmission and multiple types of services. Thus, the network node may receive a feedback transmission for the data transmission from the terminal device. The feedback transmission may be based on a resource configuration corresponding to the type of service. In this way, differentiated handling of feedback transmissions for different services can be efficiently achieved.

Fig. 3 is a flow chart illustrating a method 300 according to another embodiment of the present disclosure. The method 300 shown in fig. 3 may be implemented by a terminal device or an apparatus communicatively coupled to a terminal device. According to an example embodiment, a terminal device, such as a UE, may be served by a communication network that supports multiple services, such as eMBB, mtc, URLLC, and/or other services that may have different QoS requirements.

Corresponding to the operation of the exemplary method 200 as shown in fig. 2, a terminal device in the exemplary method 300 may obtain configuration information from a network node, as shown at block 302. As described in connection with fig. 2, the configuration information may relate to resource configurations of feedback transmissions for data transmissions from the network node to the terminal device for different types of services. For example, a terminal device such as a UE may be provided with multiple PUCCH resource configurations for downlink HARQ acknowledgements and other types of information of UCI by receiving configuration information from a network node such as a gNB.

Based at least in part on the configuration information, the terminal device may determine a correspondence between the resource configuration and the different types of services, as shown at block 304. According to the correspondence between the resource configuration and the different types of services, the terminal device may know that a radio resource spanning a relatively long duration in the time domain may be applicable to feedback transmission for a type of service having relatively low requirements for at least one of latency and reliability.

As illustrated with respect to fig. 2, the type of service may be identified by some metric information for the downlink data transmission (e.g., a transmission duration associated with a radio resource granted for the downlink data transmission, one or more parameters related to DCI for the downlink data transmission, a resource indicator related to the downlink data transmission, and/or any other suitable metric parameter).

Optionally, a terminal device, such as a UE, may receive a data transmission for a service (e.g., via PDSCH) from a network node, such as a gNB, as shown at block 306. Using the metric information of the received data transmission, the terminal device can identify the service type. Based at least in part on the identified service type and the correspondence between the resource configuration and the different types of services, the terminal device may determine a resource configuration for a feedback transmission with respect to the received data transmission.

Optionally, feedback transmission may be implemented by the terminal device according to the determined resource configuration, as shown at block 308. According to an example embodiment, a terminal device, such as a UE, may determine a PUCCH resource configuration for HARQ a/N feedback for PDSCH transmissions according to an association between the PDSCH transmissions and corresponding service types. The UE may then transmit HARQ a/N feedback to the gNB by using the determined PUCCH resource configuration.

It will be appreciated that the parameters, variables, information elements and settings related to the various services and the corresponding feedback transmissions described herein are merely examples. Other suitable parameter settings, related configuration parameters and specific values thereof may also be suitable for implementing the proposed method.

The proposed solution according to one or more exemplary embodiments may enable to handle feedback transmissions (such as HARQ acknowledgements) for different services differently. With the proposed resource configuration mechanism, a correspondence may be established between downlink data transmissions and their HARQ acknowledgements in the uplink (e.g. via PUCCH or multiplexed with data transmissions on PUSCH) for different types of services for a UE. In this way, the UE can implement differentiated HARQ a/N feedback transmissions in order to meet various latency and/or reliability requirements for different services.

The various blocks shown in fig. 2-3 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements configured to perform the associated functions. The schematic flow chart diagrams that have been described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of particular embodiments of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

Fig. 4 is a block diagram illustrating an apparatus 400 according to various embodiments of the present disclosure. As shown in fig. 4, apparatus 400 may comprise one or more processors (e.g., processor 401) and one or more memories (e.g., memory 402 storing computer program code 403). Memory 402 may be a non-transitory machine/processor/computer-readable storage medium. In some implementations, the one or more memories 402 and the computer program code 403 may be configured, with the one or more processors 401, to cause the apparatus 400 to perform at least any of the operations of the method as described in connection with fig. 2. In other implementations, the one or more memories 402 and the computer program code 403 may be configured, with the one or more processors 401, to cause the apparatus 400 to perform at least any of the operations of the method as described in connection with fig. 3.

Alternatively or additionally, the one or more memories 402 and the computer program code 403 may be configured, with the one or more processors 401, to cause the apparatus 400 to perform at least more or less operations in order to implement the methods presented in accordance with the exemplary embodiments of this disclosure.

Fig. 5 is a block diagram illustrating an apparatus 500 according to an embodiment of the present disclosure. As shown in fig. 5, the apparatus 500 may include an obtaining unit 501 and a determining unit 502. In an exemplary embodiment, the apparatus 500 may be implemented at a terminal device such as a UE. The obtaining unit 501 is operable to perform the operations in block 302, and the determining unit 502 is operable to perform the operations in block 304. Optionally, the obtaining unit 501 and/or the determining unit 502 may be operable to perform more or less operations to implement the proposed method according to an exemplary embodiment of the present disclosure.

Fig. 6 is a block diagram illustrating an apparatus 600 according to another embodiment of the present disclosure. As shown in fig. 6, the apparatus 600 may comprise a determining unit 601 and a providing unit 602. In an example embodiment, apparatus 600 may be implemented at a network node, such as a gNB. The determining unit 601 is operable to perform the operations in block 202, and the providing unit 602 is operable to perform the operations in block 204. Optionally, the determining unit 601 and/or the providing unit 602 may be operable to perform more or less operations to implement the proposed method according to an exemplary embodiment of the present disclosure.

Figure 7 is a block diagram illustrating a telecommunications network connected to host computers via an intermediate network, according to some embodiments of the present disclosure.

Referring to fig. 7, according to an embodiment, the communication system comprises a telecommunications network 710 (such as a 3 GPP-type cellular network) comprising an access network 711 (such as a radio access network) and a core network 714. The access network 711 includes a plurality of

base stations

712a, 712b, 712c, such as NBs, enbs, gnbs, or other types of wireless access points, each defining a

respective coverage area

713a, 713b, 713 c. Each

base station

712a, 712b, 712c may be connected to a core network 714 through a wired or wireless connection 715. A first UE791 located in coverage area 713c is configured to wirelessly connect to a respective base station 712c or be paged by the respective base station 712 c. A second UE 792 in coverage area 713a may wirelessly connect to the respective base station 712 a. Although

multiple UEs

791, 792 are shown in this example, the disclosed embodiments are equally applicable where only one UE is in the coverage area or where only one UE is connected to a respective base station 712.

The telecommunications network 710 is itself connected to a host computer 730, and the host computer 730 may be embodied in hardware and/or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 730 may be under the ownership or control of the service provider, or may be operated by or on behalf of the service provider. The

connections

721 and 722 between the telecommunications network 710 and the host computer 730 may extend directly from the core network 714 to the host computer 730, or may traverse an optional intermediate network 720. The intermediate network 720 may be one of a public network, a private network, or a hosted network, or a combination of more of these; the intermediate network 720 (if any) may be a backbone network or the internet; in particular, the intermediate network 720 may include two or more sub-networks (not shown).

The communication system of fig. 7 generally enables connection between connected

UEs

791, 792 and a host computer 730. The connection may be described as an over-the-top (ott) connection 750. The host computer 730 and the connected

UEs

791, 792 are configured to communicate data and/or signaling via the OTT connection 750 using the access network 711, the core network 714, any intermediate networks 720 and possibly other infrastructure (not shown) as intermediaries. OTT connection 750 may be transparent to the extent that the participating communication devices through which OTT connection 750 is in transit are not aware of the routing of uplink and downlink communications. For example, the base station 712 may not be informed or need not be informed about the past route of the inbound downlink communication with data from the host computer 730 to be forwarded (e.g., handed over) to the connected UE 791. Similarly, the base station 712 need not know the future route of the outgoing uplink communication from the UE791 towards the host computer 730.

Fig. 8 is a block diagram illustrating a host computer communicating with a UE over a partially wireless connection via a base station in accordance with some embodiments of the present disclosure.

An example implementation of the UE, base station and host computer discussed in the preceding paragraphs according to an embodiment will now be described with reference to fig. 8. In the communication system 800, the host computer 810 includes hardware 815, the hardware 815 includes a communication interface 816, and the communication interface 816 is configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 800. The host computer 810 further includes: processing circuitry 818, which may have storage and/or processing capabilities. In particular, the processing circuit 818 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of such components (not shown) adapted to execute instructions. The host computer 810 also includes software 811 that is stored in the host computer 810 or is accessible by the host computer 810 and executable by the processing circuitry 818. Software 811 includes a host application 812. Host application 812 is operable to provide services to a remote user (e.g., UE 830 connected via OTT connection 850 terminating UE 830 and host computer 810). In providing services to remote users, the host application 812 may provide user data that is transported using the OTT connection 850.

The communication system 800 also includes a base station 820 provided in the telecommunication system, the base station 820 including hardware 825 enabling it to communicate with the host computer 810 and the UE 830. Hardware 825 may include a communications interface 826 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of communication system 800, and a radio interface 827 for establishing and maintaining at least a wireless connection 870 with a UE 830 located in a coverage area (not shown in fig. 8) served by base station 820. Communication interface 826 may be configured to facilitate a connection 860 to host computer 810. The connection 860 may be direct or it may traverse a core network of the telecommunication system (not shown in fig. 8) and/or traverse one or more intermediate networks outside the telecommunication system. In the illustrated embodiment, the hardware 825 of the base station 820 also includes processing circuitry 828, which processing circuitry 828 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station 820 also has software 821 stored internally or accessible through an external connection.

The communication system 800 also includes the UE 830 that has been cited. Its hardware 835 may include a radio interface 837, the radio interface 837 configured to establish and maintain a wireless connection 870 with a base station serving the coverage area in which the UE 830 is currently located. The hardware 835 of the UE 830 also includes processing circuitry 838, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these components (not shown) adapted to execute instructions. The UE 830 also includes software 831 that is stored in the UE 830 or is accessible to the UE 830 and executable by the processing circuitry 838. Software 831 includes client application 832. The client application 832 is operable to provide services to human or non-human users via the UE 830, under the support of the host computer 810. In the host computer 810, the executing host application 812 can communicate with the executing client application 832 via an OTT connection 850 terminated by the UE 830 and the host computer 810. In providing services to the user, client application 832 may receive request data from host application 812 and provide user data in response to the request data. The OTT connection 850 may carry both request data and user data. Client application 832 may interact with a user to generate user data that it provides.

It is noted that the host computer 810, base station 820, and UE 830 shown in fig. 8 may be similar to or the same as the host computer 730, one of the

base stations

712a, 712b, 712c, and one of the

UEs

791, 792, respectively, of fig. 7. That is, the internal workings of these entities may be as shown in fig. 8, and independently, the surrounding network topology may be that of fig. 7.

In fig. 8, OTT connection 850 has been abstractly drawn to illustrate communication between host computer 810 and UE 830 via base station 820 without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure may determine a route that may be configured to hide the route from the UE 830 or the service provider operating the host computer 810, or both. When OTT connection 850 is active, the network infrastructure may further make decisions to dynamically change routing (e.g., based on load balancing considerations or reconfiguration of the network).

The wireless connection 870 between the UE 830 and the base station 820 is in accordance with the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 830 using the OTT connection 850, where the wireless connection 870 forms the last segment. More specifically, the teachings of the embodiments may improve latency and power consumption, providing advantages such as lower complexity, reduced time required to access a cell, better responsiveness, extended battery life, and the like.

A measurement process may be provided to monitor data rate, latency, and other factors improved by one or more embodiments. There may also be optional network functions for reconfiguring the OTT connection 850 between host computer 810 and UE 830 in response to changes in the measurements. The measurement procedures and/or network functions for reconfiguring the OTT connection 850 may be implemented in the software 811 and hardware 815 of the host computer 810, or in the software 831 and hardware 835 of the UE 830, or both. In embodiments, sensors (not shown) may be disposed in or associated with the communication device through which OTT connection 850 passes; the sensor may participate in the measurement process by providing the values of the monitored quantity exemplified above, or by providing values of other physical quantities from which the

software

811, 831 may calculate or estimate the monitored quantity. The reconfiguration of OTT connection 850 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect the base station 820 and the base station 820 may not be aware or aware of the reconfiguration. These processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host computer 810. The measurement can be achieved as follows:

software

811 and 831 use OTT connection 850 when it monitors propagation times, errors, etc. to cause messages, particularly null messages or "dummy" messages, to be transmitted.

Fig. 9 is a flow diagram illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 7 and 8. To simplify the present disclosure, only the drawing reference to fig. 9 is included in this section. In step 910, the host computer provides user data. In sub-step 911 (which may be optional) of step 910, the host computer provides user data by executing a host application. In step 920, the host computer initiates a transmission carrying user data for the UE. In step 930 (which may be optional), the base station transmits user data carried in a transmission initiated by the host computer to the UE in accordance with the teachings of embodiments described throughout this disclosure. In step 940 (which may also be optional), the UE executes a client application associated with a host application executed by the host computer.

Fig. 10 is a flow diagram illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 7 and 8. To simplify the present disclosure, only the drawing reference to fig. 10 is included in this section. In step 1010 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1020, the host computer initiates a transmission carrying user data for the UE. The transmission may pass through a base station according to the teachings of embodiments described throughout this disclosure. In step 1030 (which may be optional), the UE receives the user data carried in the transmission.

Fig. 11 is a flow diagram illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 7 and 8. To simplify the present disclosure, only the drawing reference to FIG. 11 is included in this section. In step 1110 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1120, the UE provides user data. In sub-step 1121 of step 1120 (which may be optional), the UE provides user data by executing a client application. In sub-step 1111 of step 1110 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host computer. The executed client application may also take into account user input received from the user when providing the user data. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 1130 (which may be optional). In step 1140 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of embodiments described throughout this disclosure.

Fig. 12 is a flow diagram illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 7 and 8. To simplify the present disclosure, only the drawing reference to fig. 12 is included in this section. In step 1210 (which may be optional), the base station receives user data from the UE in accordance with the teachings of embodiments described throughout this disclosure. In step 1220 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1230 (which may be optional), the host computer receives user data carried in a transmission initiated by the base station.

In general, the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, 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 which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of the exemplary embodiments of the present disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of the present disclosure may be implemented in an apparatus embodied as an integrated circuit, which may include at least circuitry (and possibly firmware) for embodying one or more of a data processor, a digital signal processor, baseband circuitry, and radio frequency circuitry that may be configured to operate in accordance with the exemplary embodiments of the present disclosure.

It should be understood that at least some aspects of the exemplary embodiments of this disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, Random Access Memory (RAM), etc. The functionality of the program modules may be combined or distributed as desired in various embodiments, as will be appreciated by those skilled in the art. Further, the functions described may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, Field Programmable Gate Arrays (FPGAs), etc.

The disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, 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 this disclosure.

Claims

1. A method (300) implemented by a terminal device, comprising:

obtaining (302) configuration information from a network node, wherein the configuration information relates to a resource configuration for feedback transmission of data transmissions from the network node to the terminal device for different types of services; and

determining (304) a correspondence between a resource configuration of the feedback transmission and the different type of service based at least in part on the configuration information,

wherein the different types of services are identified by metric information of data transmissions from the network node to the terminal device, the metric information of data transmissions from the network node to the terminal device comprising: a resource indicator related to the data transmission; the resource indicator includes: one or more physical resource block indices;

receiving, from the network node, a downlink data transmission for a service and a resource indicator related to the received downlink data transmission;

identifying a type of the service by using a resource indicator of the received downlink data transmission;

determining a resource configuration for a feedback transmission of the received downlink data transmission based at least in part on the identified service type and a correspondence between the resource configuration and the different type of service; and

implementing the feedback transmission on resources of an uplink shared channel or an uplink control channel according to the determined resource configuration.

2. The method of claim 1, wherein a correspondence between the resource configuration and the different types of services indicates: radio resources having a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service delay less than the delay threshold.

3. The method of claim 1 or 2, wherein the correspondence between the resource configuration and the different types of services indicates: radio resources with transmission durations shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service reliability above the reliability threshold.

4. The method of claim 1, wherein the metric information for data transmission from the network node to the terminal device further comprises:

a transmission duration associated with a radio resource granted for the data transmission.

5. An apparatus (400), comprising:

one or more processors (401); and

one or more memories (402) including computer program code (403),

the one or more memories (402) and the computer program code (403) are configured to, with the one or more processors (401), cause the apparatus (400) to at least:

obtaining configuration information from a network node, wherein the configuration information relates to a resource configuration for feedback transmission of data transmissions from the network node to the apparatus for different types of services; and

determining a correspondence between a resource configuration of the feedback transmission and the different type of service based at least in part on the configuration information,

wherein the different types of services are identified by metric information of data transmissions from the network node to the apparatus, the metric information of data transmissions from the network node to the apparatus comprising: a resource indicator related to the data transmission; the resource indicator includes: one or more physical resource block indices;

determining a resource configuration for a feedback transmission of the received downlink data transmission based at least in part on the identified service type and a correspondence between the resource configuration and the different types of services; and

6. The apparatus of claim 5, wherein a correspondence between the resource configuration and the different types of services indicates: radio resources having a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service delay less than the delay threshold.

7. The apparatus of claim 5 or 6, wherein a correspondence between the resource configuration and the different types of services indicates: radio resources with transmission durations shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service reliability above the reliability threshold.

8. The apparatus of claim 5, wherein the metric information for the data transmission from the network node to the apparatus further comprises:

9. A method (200) implemented by a network node, comprising:

determining (202) configuration information relating to a resource configuration for feedback transmission of data transmissions from the network node to a terminal device for different types of services; and

providing (204) the configuration information to the terminal device, wherein the configuration information indicates a correspondence between a resource configuration of the feedback transmission and the different types of services,

-implementing a data transmission for a service from the network node to the terminal device; and

receiving a feedback transmission from the terminal device for the data transmission, wherein the feedback transmission is based on a resource configuration corresponding to the type of service.

10. The method of claim 9, wherein a correspondence between the resource configuration and the different types of services indicates: radio resources having a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service delay less than the delay threshold.

11. The method of claim 9 or 10, wherein the correspondence between the resource configuration and the different types of services indicates: radio resources with a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service reliability above the reliability threshold.

12. The method of claim 9, wherein the metric information for the data transmission from the network node to the terminal device further comprises:

13. An apparatus (400), comprising:

one or more processors (401); and

one or more memories (402) including computer program code (403),

determining configuration information relating to a resource configuration for feedback transmission of data transmissions from the apparatus to a terminal device for different types of services; and

providing the configuration information to the terminal device, wherein the configuration information indicates a correspondence between a resource configuration of the feedback transmission and the different types of services,

wherein the different types of services are identified by metric information of data transmissions from the apparatus to the terminal device, the metric information of data transmissions from the apparatus to the terminal device comprising: a resource indicator related to the data transmission; the resource indicator includes: one or more physical resource block indices;

implementing a data transmission for a service from the apparatus to the terminal device; and

14. The apparatus of claim 13, wherein a correspondence between the resource configuration and the different types of services indicates: radio resources having a transmission duration shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service delay less than the delay threshold.

15. The apparatus of claim 13 or 14, wherein a correspondence between the resource configuration and the different type of service indicates: radio resources with transmission durations shorter than the duration threshold are suitable for feedback transmission for a class of services requiring a service reliability above the reliability threshold.

16. The apparatus of claim 13, wherein metric information for data transmissions from the apparatus to the terminal device comprises:

17. A computer readable medium having embodied thereon computer program code (403), which when executed on a computer causes the computer to implement the method according to any one of claims 1-4.

18. A computer readable medium having embodied thereon computer program code (403), which when executed on a computer causes the computer to implement the method according to any one of claims 9-12.

19. An apparatus (500), comprising:

an obtaining unit (501) configured to obtain configuration information from a network node, wherein the configuration information relates to a resource configuration of a feedback transmission for data transmission from the network node to the apparatus for different types of services; and

a determining unit (502) configured to determine a correspondence between a resource configuration of the feedback transmission and the different types of services based at least in part on the configuration information,

20. An apparatus (600), comprising:

a determining unit (601) configured to determine configuration information relating to a resource configuration for feedback transmission of data transmissions from the apparatus to a terminal device for different types of services; and

a providing unit (602) configured to provide the configuration information to the terminal device, wherein the configuration information indicates a correspondence between a resource configuration of the feedback transmission and the different types of services,

21. A method implemented in a communication system comprising a host computer, a base station, and a user equipment, the method comprising:

providing user data at the host computer; and

at the host computer, initiating a transmission carrying the user data to the user equipment via a cellular network comprising the base station, wherein the base station implements the method of any of claims 9-12.

22. A communication system including a host computer, comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward the user data to a cellular network for transmission to a user equipment,

wherein the cellular network comprises a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to implement the method of any of claims 9-12.