Patent Application
20230309109
The present disclosure relates to multiple Transmission/Reception Point (TRP) uplink channel transmission in a cellular communications system.
Third Generation Partnership Project (3GPP) New Radio (NR) uses Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) in both downlink (DL) (i.e., from a network node, gNB, or base station, to a user equipment or UE) and uplink (UL) (i.e., from UE to gNB). Discrete Fourier Transform (DFT) spread Orthogonal Frequency Division Multiplexing (OFDM) is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally sized subframes of 1 millisecond (ms) each. A subframe is further divided into multiple slots of equal duration. The slot length depends on subcarrier spacing. For subcarrier spacing of Δf=15 kilohertz (kHz), there is only one slot per subframe, and each slot consists of 14 OFDM symbols.
Data scheduling in NR is typically on slot basis, an example is shown in
Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values, which are also referred to as different numerologies, are given by Δf = (15 × 2µ) kHz where ∈ {0,1,2,3,4} . Δf = 15 kHz is the basic subcarrier spacing. The slot durations at different subcarrier spacings is given by
In the frequency domain, a system bandwidth is divided into Resource Blocks (RBs), each corresponds to twelve (12) contiguous subcarriers. The RBs are numbered starting with 0 from one end of the system bandwidth. The basic NR physical time-frequency resource grid is illustrated in
Downlink (DL) and uplink (UL) data transmissions can be either dynamically or semi-persistently scheduled by a gNB. In case of dynamic scheduling, the gNB may transmit, in a downlink slot, Downlink Control Information (DCI) to a UE on Physical Downlink Control Channel (PDCCH) about data carried on a downlink PDSCH to the UE and/or data on an uplink PUSCH to be transmitted by the UE. In case of semi-persistent scheduling, periodic data transmission in certain slots can be configured and activated/deactivated.
For each transport block data transmitted over PDSCH, a Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) / Negative ACK (NACK) is sent in a UL Physical Uplink Control Channel (PUCCH) to indicate whether it is decoded successfully or not. An ACK is sent if it is decoded successfully, and a NACK is sent otherwise.
PUCCH can also carry other Uplink Control Information (UCI) such as Scheduling Request (SR) and DL Channel State Information (CSI).
Five PUCCH formats are defined in NR, i.e., PUCCH formats 0 to 4. A UE transmits UCI in a PUCCH using PUCCH format 0 if:
A UE transmits UCI in a PUCCH using PUCCH format 1 if:
A UE transmits UCI in a PUCCH using PUCCH format 2 if:
A UE transmits UCI in a PUCCH using PUCCH format 3 if:
A UE transmits UCI in a PUCCH using PUCCH format 4 if:
PUCCH formats 0 and 2 use one or two OFDM symbols while PUCCH formats 1, 3, and 4 can span from 4 to 14 symbols. Thus, PUCCH formats 0 and 2 are referred to as short PUCCH while PUCCH formats 1, 3, and 4 are referred to as long PUCCH.
A PUCCH format 0 resource can be one or two OFDM symbols within a slot in the time domain and one RB in the frequency domain. UCI is used to select a cyclic shift of a computer-generated length 12 base sequence which is mapped to the RB. The starting symbol and the starting RB are configured by Radio Resource Control (RRC). In case in which two symbols are configured, the UCI bits are repeated in two consecutive symbols.
A PUCCH format 2 resource can be one or two OFDM symbols within a slot in the time domain and one or more RBs in the frequency domain. UCI in PUCCH format 2 is encoded with Reed-Muller (RM) codes (≤11 bit UCI+CRC) or Polar codes (>11 bit UCI+CRC) and scrambled. In the case in which two symbols are configured, UCI is encoded and mapped across two consecutive symbols.
Intra-slot frequency hopping (FH) may be enabled in the case in which two symbols are configured for PUCCH formats 0 and 2. If FH is enabled, the starting Physical Resource Block (PRB) in the second symbol is configured by RRC. Cyclic shift hopping is used when two symbols are configured such that different cyclic shifts are used in the two symbols.
A PUCCH format 1 resource is 4 - 14 symbols long and 1 PRB wide per hop. A computer-generated length 12 base sequence is modulated with UCI and weighted with time-domain Orthogonal Cover Code (OCC) code. Frequency-hopping with one hop within the active UL bandwidth part (BWP) for the UE is supported and can be enabled/disabled by RRC. Base sequence hopping across hops is enabled in case of FH and across slots in case of no FH.
A PUCCH Format 3 resource is 4 - 14 symbols long and one or multiple PRB wide per hop. UCI in PUCCH Format 3 is encoded with RM codes (≤11 bit UCI+CRC) or Polar codes (>11 bit UCI+CRC) and scrambled.
A PUCCH Format 4 resource is also 4 - 14 symbols long but 1 PRB wide per hop. It has a similar structure as PUCCH format 3 but can be used for multi-UE multiplexing.
For PUCCH formats 1, 3, or 4, a UE can be configured a number of slots,
for repetitions of a PUCCH transmission by respective nrofSlots. For
In NR Rel-16, sub-slot based PUCCH transmission was introduced so that HARQ-ACK associated with different types of traffic can be multiplexed in a same UL slot, each transmitted in a different sub-slot. The sub-slot size can be higher layer configured to either 2 symbols or 7 symbols. In case of a sub-slot configuration in which each sub-slot has 2 symbols, there are 7 sub-slots in a slot. In case of a sub-slot configuration in which each sub-slot has 7 symbols, there are two sub-slots in a slot.
Spatial relation is used in NR to refer to a relationship between an UL reference signal (RS) such as PUCCH Demodulation Reference Signal (DMRS) and another RS, which can be either a DL RS (i.e., Channel State Information Reference Signal (CSI-RS) or Synchronization Signal Block (SSB)) or an UL RS (i.e., Sounding Reference Signal (SRS)).
If an UL RS is spatially related to a DL RS, it means that the UE should transmit the UL RS in the opposite (reciprocal) direction from which it previously received the DL RS. More precisely, the UE should apply the “same” transmit (Tx) spatial filtering configuration for the transmission of the UL RS as the receive (Rx) spatial filtering configuration it used to previously receive the spatially related DL RS. Here, the terminology “spatial filtering configuration” may refer to the antenna weights that are applied at either the transmitter or the receiver for data/control transmission/reception. The DL RS is also referred as the spatial filter reference signal.
On the other hand, if a first UL RS is spatially related to a second UL RS, then the UE should apply the same Tx spatial filtering configuration for the transmission for the first UL RS as the Tx spatial filtering configuration it used to transmit the second UL RS previously.
In NR Rel-16, a UE can be RRC configured with a list of up to 64 spatial relations for PUCCH. For a given PUCCH resource, one of the spatial relations is activated via a Media Access Control (MAC) Control Element (CE) message. The UE adjusts the Tx spatial filtering configuration for the transmission on that PUCCH resource according to the activated signaled spatial relation.
In NR Rel-16, PDSCH transmission over multiple Transmission/Reception Points (TRPs) has been introduced for Ultra-Reliable Low Latency (URLLC) type of applications to improve PDSCH reliability, in which a PDSCH is repeated over two TRPs in either Spatial Division Multiplexing (SDM), Frequency Domain Multiplexing (FDM), or Time Domain Multiplexing (TDM) manner. In NR Rel-17, it has been proposed to further introduce PUCCH enhancement with multiple TRPs. One possible approach is to repeat a PUCCH towards different TRPs.
Systems and methods are disclosed herein for timing enhancements related to uplink channel repetitions toward multiple transmission/reception points (TRPs). In one embodiment, a method of uplink transmission, performed by a wireless communication device in a wireless communication network that includes two or more TRPs each associated with a spatial relation or Transmission Configuration Indication (TCI) state, comprises receiving, from a base station in the wireless communication network, a configuration of a first spatial relation or a first TCI state and a second spatial relation or a second TCI state for an uplink channel, and an indication of a number of transmission repetitions of the uplink channel. The method further comprises transmitting the uplink channel a number of times, according to the number of transmission repetitions, in a first set of resources according to the first spatial relation or the first TCI state, and in a second set of resources according to the second spatial relation or the second TCI state. The method further comprises receiving a Physical Downlink Shared Channel (PDSCH) carrying a Media Access Control (MAC) control element (CE) command from the base station. The method further comprises transmitting a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) associated with the PDSCH in the uplink channel, and applying the MAC CE command according to a timing that is based on a slot or sub-slot over which a last transmission repetition of the uplink channel is transmitted.
In one embodiment, each of the first and second TCI states is one of: a unified TCI state that can be used for both downlink and uplink channel transmissions, and an uplink TCI state that can be used only for uplink channel transmissions.
In one embodiment, the uplink channel is a physical uplink control channel (PUCCH).
In one embodiment, the timing is based on a slot or sub-slot over which a last transmission repetition of the uplink channel that carries a corresponding HARQ feedback associated with the MAC CE command is transmitted.
In one embodiment, the uplink channel is a PUCCH configured to carry HARQ feedback, and the MAC CE command is a MAC CE command that activates a TCI state. In one embodiment, applying the MAC CE command according to a timing that is based on the slot or sub-slot over which the last transmission repetition of the uplink channel is transmitted comprises applying the MAC CE command that activates the TCI state in a first slot that is after
where: k is a slot over which a last transmission repetition of the PUCCH that carries HARQ feedback with ACK for the PDSCH that carried the MAC CE command that activates the TCI state is transmitted, µ is the subcarrier spacing configuration for the PUCCH, and
is the number of slots in a subframe with a subcarrier spacing µ.
In one embodiment, the uplink channel is a PUCCH configured to carry HARQ feedback, and the MAC CE command is a MAC CE command that activates a spatial relation for a PUCCH resource. In one embodiment, applying the MAC CE command according to a timing that is based on the slot or sub-slot over which the last transmission repetition of the uplink channel is transmitted comprises applying the MAC CE command that activates the spatial relation for a PUCCH resource in a first slot that is after
where: k is a slot over which a last transmission repetition of the PUCCH that carries HARQ feedback with ACK corresponding to a physical downlink shared channel, PDSCH, that carried the MAC CE command is transmitted, µ is the subcarrier spacing configuration for the PUCCH, and
is the number of slots in a subframe with a subcarrier spacing µ.
In one embodiment, the uplink channel is a PUCCH configured to carry HARQ feedback, and the MAC CE command is a MAC CE command that activates a Semi-Persistent (SP) Zero-Power (ZP) Channel State Information Reference Signal (CSI-RS) resource set. In one embodiment, applying the MAC CE command according to a timing that is based on the slot or sub-slot over which the last transmission repetition of the uplink channel is transmitted comprises applying the MAC CE command that activates the SP ZP CSI-RS resource set in a first slot that is after
where: k is a slot over which a last transmission repetition of the PUCCH that carries HARQ feedback with ACK corresponding to a PDSCH carrying the MAC CE command that activates the SP ZP CSI-RS is transmitted, µ is the subcarrier spacing configuration for the PUCCH, and
is the number of slots in a subframe with a subcarrier spacing µ.
In one embodiment, the uplink channel is a PUCCH configured to carry HARQ feedback, and the MAC CE command is any one of: a MAC CE command for enhanced TCI states activation or deactivation, a MAC CE for SP CSI reporting on PUCCH activation or deactivation, a MAC CE for SP CSI-RS or Channel State Information for Interference Measurement (CSI-IM) resource set activation or deactivation, a MAC CE for SP Sounding Reference Signal (SRS) activation or deactivation, a MAC CE for SP positioning SRS activation or deactivation, or a MAC CE for SP or aperiodic SRS spatial relation indication.
In one embodiment, the first set of resources is a first set of time and frequency domain resources, and the second set of resources is a second set of time and frequency domain resources.
In one embodiment, the first set of resources is a first set of sub-slots within a slot, and the second set of resources is a second set of sub-slots within the slot. In one embodiment, a total number of sub-slots in the first set of sub-slots and the second set of sub-slots is equal to the number of transmission repetitions.
In one embodiment, each of the first and second sets of resources comprises time and frequency resources in one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols.
In one embodiment, the first set of resources and the second set of resources are non-overlapping in time.
In one embodiment, the first set resources and the second set of resources are in a same slot.
In one embodiment, time-frequency resource allocations for the number of repetitions of the uplink channel in the first and second sets of resources have a same pattern.
In one embodiment, the uplink channel is one of PUCCH formats 0 to 4.
In one embodiment, the method further comprises receiving, from the base station, a configuration of one or more gap symbols between adjacent transmission repetitions.
In one embodiment, the method further comprises receiving, from the base station, a second configuration of multiple numbers of transmission repetitions for the uplink channel, wherein which of the multiple numbers of transmission repetitions to use depends on whether one or more of the following conditions are met: whether two TCI states are indicated in a transmission configuration indication field of a downlink control information (DCI) scheduling a PDSCH for which an associated HARQ feedback is to be sent via the uplink channel, whether a downlink multi-TRP PDSCH scheme is used for the PDSCH for which an associated HARQ feedback is to be sent via the uplink channel, a priority indicator field of the DCI is set to “1”, whether the associated PDSCH is scheduled by DCI format 1_2, whether an associated physical uplink control channel, PUCCH, resource is activated with two TCI states, or an uplink control information (UCI) type carried by the uplink channel.
In one embodiment, the method further comprises receiving, from the base station, a second configuration of multiple numbers of transmission repetitions for the uplink channel, wherein which of the multiple numbers of transmission repetitions to use depends on a traffic type with which the uplink channel is associated.
In one embodiment, the method further comprises receiving, from the base station, one or more configurations for determining the number of transmission repetitions, wherein one of the one or more configurations is dynamically indicated in DCI.
In one embodiment, the method further comprises dropping a particular transmission repetition of the uplink channel that overlaps with another uplink channel with a higher priority.
In one embodiment, the method further comprises multiplexing a particular transmission repetition of the uplink channel with an overlapping uplink channel with a same priority.
In one embodiment, the method further comprises discarding or delaying a particular transmission repetition of the uplink channel that collides with an invalid symbol. In one embodiment, discarding or delaying the particular transmission repetition of the uplink channel that collides with an invalid symbol comprises delaying the particular transmission repetition of the uplink channel until enough valid symbols are available to transmit the particular transmission repetition or a timing limit has been reached.
Corresponding embodiments of a wireless communication device are also disclosed. In one embodiment, a wireless communication device for uplink transmission in a wireless communication network that includes two or more TRPs each associated with a spatial relation or TCI state is adapted to receive, from a base station in the wireless communication network, a configuration of a first spatial relation or a first TCI state and a second spatial relation or a second TCI state for an uplink channel, and an indication of a number of transmission repetitions of the uplink channel. The wireless communication device is further adapted to transmit the uplink channel a number of times, according to the number of transmission repetitions, in a first set of resources according to the first spatial relation or the first TCI state and in a second set of resources according to the second spatial relation or the second TCI state. The wireless communication device is further adapted to receive a PDSCH carrying a MAC CE command from the base station. The wireless communication device is further adapted to transmit a HARQ-ACK associated with the PDSCH in the uplink channel, and apply the MAC CE command according to a timing that is based on a slot or sub-slot over which a last transmission repetition of the uplink channel is transmitted.
In one embodiment, a wireless communication device for uplink transmission in a wireless communication network that includes two or more TRPs each associated with a spatial relation or TCI state comprises one or more transmitters, one or more receivers, and processing circuitry associated to the one or more transmitters and the one or more receivers. The processing circuitry is configured to cause the wireless communication device to receive, from a base station in the wireless communication network, a configuration of a first spatial relation or a first TCI state and a second spatial relation or a second TCI state for an uplink channel, and an indication of a number of transmission repetitions of the uplink channel. The processing circuitry is further configured to cause the wireless communication device to transmit the uplink channel a number of times, according to the number of transmission repetitions, in a first set of resources according to the first spatial relation or the first TCI state and in a second set of resources according to the second spatial relation or the second TCI state. The processing circuitry is further configured to cause the wireless communication device to receive a PDSCH carrying a MAC CE command from the base station. The processing circuitry is further configured to cause the wireless communication device to transmit a HARQ-ACK associated with the PDSCH in the uplink channel, and apply the MAC CE command according to a timing that is based on a slot or sub-slot over which a last transmission repetition of the uplink channel is transmitted.
The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.
Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device.
Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.
Transmission/Reception Point (TRP): In some embodiments, a TRP may be a network node, radio head, a spatial relation, or a Transmission Configuration Indication (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states.
Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.
There currently exist certain challenge(s). Various Physical Uplink Control Channel (PUCCH) repetition methods towards multiple TRPs have been proposed including intra-slot PUCCH repetition for PUCCH formats 0 and 2 and inter-slot repetitions for PUCCH formats 1, 3, and 4. In addition to PUCCH reliability, low latency is also required for some Ultra-Reliable Low-Latency Communication (URLLC) applications. Although PUCCH reliability for PUCCH formats 1, 3, and 4 can be increased with inter-slot repetition over multiple TRPs, this repetition also introduces extra delays. Thus, one issue that needs to be addressed is how to balance between reliability and latency. Further, when mixed enhanced Mobile Broadband (eMBB) and URLLC traffic are served, the corresponding required reliability and latency are different. Thus, another issue that needs to be addressed is how to determine the number of repetitions for each type of traffic in such a mixed traffic scenario.
Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. In this disclosure, embodiments of a method of intra-slot PUCCH repetitions towards two TRPs are disclosed. In one embodiment of this method, a PUCCH is repeated two or more times within a slot, each toward a TRP, and a different PUCCH repetition may be associated with a different TRP. An association between a PUCCH transmission and a TRP for reception can be made using a spatial relation or a unified TCI state.
In addition, embodiments of a method of applying different number of PUCCH repetitions based on the associated Physical Downlink Shared Channel (PDSCH) (i.e., the PDCCH that generated the Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK)/Negative ACK (NACK) are also disclosed, in which different number of PUCCH repetitions may be used for different traffic types (e.g., PDSCH with different priorities, eMBB or URLLC) that a PUCCH is associated with.
Certain embodiments may provide one or more of the following technical advantage(s). For example, a benefit of intra-slot PUCCH repetition towards different TRPs is improved PUCCH reliability in case that the channel to the TRP is blocked while at the same time keeping the latency low. Using a different number of PUCCH repetitions for different traffic types is beneficial in case of mixed eMBB and URLLC traffic being served simultaneously, where eMBB traffic and URLLC traffic have different reliability requirements and hence different number of repetitions. In this case, a small number of repetitions or even no repetition may be used for a PUCCH associated with eMBB traffic to save PUCCH resources and potentially UE battery power consumption.
The base stations 702 and the low power nodes 706 provide service to wireless communication devices 712-1 through 712-5 in the corresponding cells 704 and 708. The wireless communication devices 712-1 through 712-5 are generally referred to herein collectively as wireless communication devices 712 and individually as wireless communication device 712. In the following description, the wireless communication devices 712 are oftentimes UEs and as such sometimes referred to herein as UEs 712, but the present disclosure is not limited thereto.
In this embodiment, an Uplink Control Information (UCI) (also referred to herein as a “UCI message”) carried by one of the PUCCH formats is repeated within a slot multiple times each toward a different TRP. In other words, the UCI carried by one of the PUCCH formats is repeated within a slot multiple times, where each repetition is toward a different TRP.
Note that, as used herein, “transmission toward” in this aspect means that the UE 712 is adjusting its direction of large or maximum radiation and/or transmit power and/or transmission timing for an intended reception by a given TRP. For example, the UE 712 transmits a beam pointing in the direction of the desired TRP or the UE 712 selects a directive antenna panel for transmission that is facing towards a certain desired direction towards a TRP. Also note that a certain TRP can be described in specifications by a spatial relation, a unified TCI state (a TCI state that can be used for both DL and UL indication), or an UL TCI state. Hence “transmission toward” TRP#1 and TRP#2 can equivalently be described as using, e.g., spatial relation #1 and #2 for the PUCCH transmission, respectively.
It should also be noted that even in Rel-15 of NR, reception of an uplink signal by multiple TRPs is possible since which node that receives a certain message in uplink is transparent to the UE. It may be so that an uplink transmitted by a Rel-15 UE is received by two TRPs. The distinction here is that by introducing the framework of “transmission toward”, the UE 712 is “made aware” that its multiple transmissions are intended for more than one TRP, and hence by specification, the transmission can be optimized, in terms of beam direction, power control, and timing.
An example is shown in
In some embodiments, a gap symbol(s) as shown
If the parameter ‘startingSymbolOffset’ is enabled, then a gap symbol(s) is present between the first transmission occasion and the second transmission occasion as shown in
Note that, in some other embodiments, the gap between the two PUCCH transmission occasions may be a configurable number of integer symbols. In this embodiment, the parameter ‘startingSymbolOffset’ can be an integer between 0 and a non-negative integer K. Then, the starting symbol of the second PUCCH transmission occasion has K symbol offset relative to the last symbol of the first PUCCH transmission occasion.
In this embodiment, a PUCCH may be repeated in sub-slot level. An example is shown in
The number of sub-slot based repetitions can be more than two. In that case, the patterns towards (keep in mind that “toward” may be specified by spatial relation or UL or unified TCI state) different TRPs can be alternated among the TRPs (i.e., cyclic based). An example of this is shown in
In NR Rel-15, the number of slot-based PUCCH repetitions is configured by higher layers (such as RRC signaling between gNB and UE) for each PUCCH format. Considering mixed traffic types for a UE 712 where different traffic types may have different reliability and latency requirements, different number of repetitions (either slot-based or sub-slot based) may be needed for PUCCH associated with different traffic types.
In one embodiment, for each PUCCH format, multiple numbers of repetitions may be configured and, depending on the traffic type a PUCCH is associated with (or the physical layer priority of the UCI carried by PUCCH), a different repetition number may be used.
In another embodiment, the number of repetitions for the associated PUCCH varies with the UCI content type, where the UCI content type can be: HARQ-ACK, Scheduling Request (SR), Channel State Information (CSI) where the CSI can be further divided into CSI-part1 and CSI-part2, or two or more of HARQ-ACK/SR/CSI multiplexed together.
For example, one RRC parameter signaled from the base station 702 (e.g., gNB in the case of NR) to the UE 712 provides the number of repetitions for PUCCH carrying SR, and a different parameter provides the number of repetitions for PUCCH carrying HARQ-ACK. The various types of UCI can be provided with physical layer priority level as well, e.g., SR of high priority and SR of low priority. Then, the number of PUCCH repetitions may depend on UCI type and/or the physical layer priority of the UCI, where the UCI is carried by the PUCCH. If the PUCCH carries a mixture of various UCI types, then the number of PUCCH repetitions may be determined by the most important UCI being carried. For example, if UCI types are ranked from more important to less important by: HARQ-ACK > SR > CSI with HARQ-ACK and SR having higher priority and CSI having lower priority, then the number of PUCCH repetitions is determined by that of HARQ-ACK (i.e., the most important UCI being carried, since HARQ-ACK is more important than SR), if the PUCCH carries a mixture of {SR, HARQ-ACK}.
In another embodiment, if a PUCCH carrying a UCI type (e.g., HARQ-ACK) is scheduled by a DCI, then the scheduling DCI can include a field, where the DCI field dynamically indicates the number of repetitions of the PUCCH. The dynamically signaled number of PUCCH repetitions may depend on UCI type, and/or the physical layer priority of the UCI, where the UCI is carried by the PUCCH. The DCI field size (including 0 bit, i.e., absence of the DCI field) for indicating the number of repetitions of the PUCCH may be configurable by a higher layer parameter.
In another embodiment, an existing DCI field may be used to indicate the number of PUCCH repetitions. For instance, the ‘PUCCH resource indicator’ field in DCI can be used to indicate the number of repetitions for PUCCH. For instance, one codepoint in a PUCCH resource indicator field in DCI may be configured with one number of PUCCH repetitions while another codepoint in the PUCCH resource indicator field in DCI may be associated with another number of PUCCH repetitions. Some codepoints of the PUCCH resource indicator field may be associated with a single PUCCH (i.e., number of PUCCH repetitions is 1). In another embodiment, the PUCCH resource indicator field in DCI may be partitioned into two sub-fields where a first sub-field is used to indicate the number of PUCCH repetitions while the second sub-field is used to indicate the PUCCH resource to be used for PUCCH transmission.
In one example embodiment, a repetition number value (the 1st repetition number) is configured to be used for UCI feedback for URLLC based traffic (or high physical layer priority) and another (the second repetition number value) for eMBB traffic (or low physical layer priority). While PUCCH can carry various types of UCI content (HARQ-ACK, SR, CSI, or a combination thereof), here PUCCH carrying HARQ-ACK is used as an illustration.
Now, to perform dynamic switching between the 1st and 2nd repetition number values (which are configured by higher layers), some mechanism is needed to indicate this switching to the UE 712 as the gNB and UE 712 must be aligned in the number of repetitions to use for PUCCH. Some embodiments on how to accomplish this follows here: If a PUCCH carries a HARQ-ACK associated with a PDSCH which is scheduled with one or more of the following criteria, then the first repetition number may be used for PUCCH transmission.
Otherwise, the second repetition number may be used. In yet another embodiment, which repetition to use may be dynamically indicated in DCI.
One or more of the PUCCH repetitions may overlap in time with other uplink channels and/or signals, including another PUCCH, PUSCH, Sounding Reference Signal (SRS), or Physical Random Access Channel (PRACH). Then multiplexing and/or prioritization procedures apply to resolve the collision. The collision resolution procedure takes into account of the relative physical layer priority of the colliding uplink channels/signals, if different levels of physical layer priority are provided.
In one embodiment, if the UE 712 is scheduled to transmit a PUCCH repetition as well as another overlapping UL channel signal with a same priority to a same TRP #j, then the UE 712 multiplexes them before transmitting to TRP #j. Note here that toward the same TRP means the PUCCH and the other UL channel have same spatial relation reference, or use the same unified TCI state, or use the same UL TCI state.
In another embodiment, if the UE 712 is scheduled to transmit a PUCCH repetition as well as another overlapping UL channel signal to a same TRP #j, then the UE selects the channel (or signal) with higher priority to transmit, while dropping the channel (or signal) of lower priority.
In case that the UE 712 is scheduled to transmit a PUCCH repetition to TRP#1 and another overlapping UL channel with lower priority to either TRP #1 or TRP #2, then the other channel is dropped. If the overlapping UL channel has a higher priority, the PUCCH is dropped.
In another embodiment, if the UE 712 is scheduled to transmit a PUCCH repetition to either TRP #1 or TRP #2 and another overlapping PUSCH with a same priority to either TRP #2, then the PUCCH is multiplexed with the PUSCH and transmitted to TRP #2. In one embodiment, the uplink multiplexing and prioritization procedure is applied for the procedure of transmission toward each TRP (e.g., each spatial relation) separately and independently.
In another embodiment, uplink multiplexing and prioritization procedure considers the transmission to multiple TRP jointly. For example, if a PUCCH (with repetitions) and a PUSCH (with repetitions) overlap on both TRPs, then PUCCH may be selected for transmission towards TRP #1 (and PUSCH to TRP #1 is dropped), and PUSCH may be selected for transmission towards TRP #2 (and PUCCH to TRP #2 is dropped). Examples are shown in
In another embodiment, collision of PUCCH with other UL channels/signals are handled separately for each PUCCH repetition (sub-slot-based repetition or slot-based repetition), also separately for each TRP.
For PUCCH repetitions, it may happen that the resource intended for a transmission is an invalid resource. A resource may be an OFDM symbol or a resource element in this context.
The UE 712 can determine or identify invalid symbol(s) for PUCCH repetitions due to numerous reasons. In principle, any symbols that cannot be counted as available for uplink transmission are invalid for PUCCH repetitions.
For Multi-TRP (M-TRP) PUCCH transmission, while the PUCCH can be transmitted towards multiple TRPs for diversity, there are still scenarios where certain symbols cannot be used for PUCCH transmission. These symbols are called invalid symbols in discussion below. For a given invalid symbol, if it would otherwise have been used for PUCCH transmission for M-TRP #j, then this PUCCH repetition may be dropped or delayed, affecting the overall PUCCH transmission towards M-TRP #j.
In the following, numerous scenarios that cause symbols unavailable for uplink transmission (hence unavailable for PUCCH repetitions) are described for M-TRP. With “M-TRP” means that the UE 712 is configured for uplink transmission where reception is intended for more than one TRP, i.e. using multiple spatial relations, multiple UL TCI states, or multiple unified TCI states.
In one example, a symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is considered as an invalid symbol for PUCCH repetitions.
In another example, for operation in unpaired spectrum, symbols indicated by ssb-PositionsInBurst in System Information Block 1 (SIB1) or ssb-PositionsInBurst in ServingCellConfigCommon for reception of Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks are considered as invalid symbols for PUCCH repetitions.
In another example, for operation in unpaired spectrum, symbol(s) indicated by pdcch-ConfigSIB1 in the Master Information Block (MIB) for a Control Resource Set (CORESET) for Type0-PDCCH Common Search Space (CSS) set are considered as invalid symbol(s) for PUCCH repetitions.
In another example, for operation in unpaired spectrum, if numberInvalidSymbolsForDL-UL-Switching is configured, numberInvalidSymbolsForDL-UL-Switching symbol(s) after the last symbol that is indicated as downlink in each consecutive set of all symbols that are indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered as invalid symbol(s) for PUCCH repetitions. The symbol(s) given by numberInvalidSymbolsForDL-UL-Switching are defined using the reference SCS configuration referenceSubcarrierSpacing provided in tdd-UL-DL-ConfigurationCommon.
In another example, if the UE 712
In another example, a symbol is considered as an invalid symbol in any of the multiple serving cells for PUCCH repetitions if the UE 712 is configured by higher layers to receive PDCCH, PDSCH, or CSI-RS on the reference cell in the symbol.
In another example, a symbol on a shared spectrum is considered as invalid if the UE 712 has not obtained access to the channel, when required.
In another example, a symbol on a shared spectrum is considered as invalid if the symbol overlaps with the idle period corresponding to semi-static channel access procedure.
If a PUCCH repetition overlaps with any invalid symbols, then the overlapping PUCCH repetition cannot be transmitted as is.
When PUCCH repetition is configured or indicated via DCI to be sent over multiple slots, the reference to PUCCH transmission slots shall be referring to the last slot of PUCCH repetition. For MAC CE based activation command, e.g., for beam switch (i.e., TCI state update), being received in PDSCH, the time at which the UE 712 applies the command, e.g., the TCI state provided in the activation command, is based on the last slot among the multiple slots in which PUCCH is repeated.
For example, if PUCCH repetition is configured by higher layers or indicated via DCI to carry HARQ-ACK, and the UE receives a MAC CE command activating a TCI state, the UE 712 shall apply the command according to the timing described below:
In another example, if PUCCH repetition is used to carry HARQ ACK, and when a UE receives a MAC CE command to activate a spatial relation for a PUCCH resource, the UE shall apply the command according to the timing described below:
Similarly, in another embodiment, when PUCCH repetition is configured by higher layers or indicated via DCI, the time at which the UE applies the PDSCH RE mapping corresponding to the activated Zero Power (ZP) CSI-RS resource(s) provided by the ‘SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE’ activation command in 3GPP TS 38.321 is based on the last slot among multiple slots in which PUCCH is repeated. The following is an example of how to capture this embodiment in 3GPP specifications: For a UE configured with a list of ZP-CSI-RS-ResourceSet(s) provided by higher layer parameter sp-ZP-CSI-RS-ResourceSetsToAddModList:
Although the above embodiment is written with respect to ‘SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE’ activation command, the embodiment can also be extended to the cases of the following MAC CE activation commands in 3GPP TS 38.321:
In addition, the base station 702 also provides and the UE 712 also receives a second configuration of multiple numbers of the transmission repetitions for the uplink channel (step 1602), wherein which repetition number to use depends on whether one or more of the following conditions are met:
As discussed above, in one embodiment, the repetition number to use for the uplink channel may also depend on a traffic type the uplink channel is associated with.
As discussed above, in one embodiment, the UE 712 may also receive, from the base station 702, one or more configurations for determining the number of transmission repetitions, wherein one of the one or more configurations is dynamically indicated in downlink control information, DCI (step 1602A).
The UE 712 then transmits the uplink channel a number of times according to the number of transmission repetitions in a first set of sub-slots according to the first spatial relation, and in a second set of sub-slots according to the second spatial relation (step 1604). The total number of sub-slots in the first set and the second set of sub-slots equals to the number of repetitions, where each sub-lot includes a number of OFDM symbols. In one embodiment, the first set and the second set of sub-slots are non-overlapping in time. In one embodiment, the first set and the second set of sub-slots are in a same slot. In one embodiment, the first set and the second set of sub-slots are either explicitly or implicitly configured. In one embodiment, time and frequency resource allocations in each sub-slot of the first set and the second set of sub-slots are the same (i.e., with a relative same starting symbol within a sub-slot, a same number of symbols and same resource blocks).
As discussed above, in one embodiment, the UE 712 may drop one transmission repetition when it is overlapping with another UL channel with a higher priority (step 1604A). It should be understood that this dropping of one transmission repetition when it is overlapping with another UL channel with a higher priority can be part of or otherwise associated with the transmitting step 1604.
As discussed above, in one embodiment, the UE 712 may multiplex one transmission repetition with an overlapping UL channel with a same priority (step 1604A). It should be understood that this multiplexing of one transmission repetition when with an overlapping UL channel with the same priority can be part of or otherwise associated with the transmitting step 1604.
As discussed above, in one embodiment, the UE 712 may omit a corresponding transmission occasion if the UE 712 collides with an invalid symbol or may delay the corresponding transmission occasion until enough valid symbols are available (step 1604B). It should be understood that this omitting or delaying of a corresponding transmission occasion if the UE 712 collides with an invalid symbol (e.g., if the PUCCH repetition that would have been transmitted on the corresponding transmission occasion would collide with an invalid symbol) can be part of or otherwise associated with the transmitting step 1604.
As discussed above, in one embodiment, the UE 712 may receive a Media Access Control (MAC) control element (CE) command from the base station 702 (step 1606). The UE 712 may transmit a HARQ-ACK associated with the PDSCH in the uplink channel (step 1607). And then, the UE 712 may adjust timing in applying the MAC CE command according to the slot or sub-slot over which the last PUCCH transmission carrying a corresponding HARQ-ACK associated with the MAC CE command is transmitted (step 1608).
As used herein, a “virtualized” radio access node is an implementation of the radio access node 1700 in which at least a portion of the functionality of the radio access node 1700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 1700 may include the control system 1702 and/or the one or more radio units 1710, as described above. The control system 1702 may be connected to the radio unit(s) 1710 via, for example, an optical cable or the like. The radio access node 1700 includes one or more processing nodes 1800 coupled to or included as part of a network(s) 1802. If present, the control system 1702 or the radio unit(s) are connected to the processing node(s) 1800 via the network 1802. Each processing node 1800 includes one or more processors 1804 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1806, and a network interface 1808.
In this example, functions 1810 of the radio access node 1700 described herein are implemented at the one or more processing nodes 1800 or distributed across the one or more processing nodes 1800 and the control system 1702 and/or the radio unit(s) 1710 in any desired manner. In some particular embodiments, some or all of the functions 1810 of the radio access node 1700 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1800. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1800 and the control system 1702 is used in order to carry out at least some of the desired functions 1810. Notably, in some embodiments, the control system 1702 may not be included, in which case the radio unit(s) 1710 communicates directly with the processing node(s) 1800 via an appropriate network interface(s).
In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 1700 or a node (e.g., a processing node 1800) implementing one or more of the functions 1810 of the radio access node 1700 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 2000 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
With reference to
The telecommunication network 2200 is itself connected to a host computer 2216, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 2216 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 2218 and 2220 between the telecommunication network 2200 and the host computer 2216 may extend directly from the core network 2204 to the host computer 2216 or may go via an optional intermediate network 2222. The intermediate network 2222 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 2222, if any, may be a backbone network or the Internet; in particular, the intermediate network 2222 may comprise two or more sub-networks (not shown).
The communication system of
Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to
The communication system 2300 further includes a base station 2318 provided in a telecommunication system and comprising hardware 2320 enabling it to communicate with the host computer 2302 and with the UE 2314. The hardware 2320 may include a communication interface 2322 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 2300, as well as a radio interface 2324 for setting up and maintaining at least a wireless connection 2326 with the UE 2314 located in a coverage area (not shown in
The communication system 2300 further includes the UE 2314 already referred to. The UE’s 2314 hardware 2334 may include a radio interface 2336 configured to set up and maintain a wireless connection 2326 with a base station serving a coverage area in which the UE 2314 is currently located. The hardware 2334 of the UE 2314 further includes processing circuitry 2338, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 2314 further comprises software 2340, which is stored in or accessible by the UE 2314 and executable by the processing circuitry 2338. The software 2340 includes a client application 2342. The client application 2342 may be operable to provide a service to a human or non-human user via the UE 2314, with the support of the host computer 2302. In the host computer 2302, the executing host application 2312 may communicate with the executing client application 2342 via the OTT connection 2316 terminating at the UE 2314 and the host computer 2302. In providing the service to the user, the client application 2342 may receive request data from the host application 2312 and provide user data in response to the request data. The OTT connection 2316 may transfer both the request data and the user data. The client application 2342 may interact with the user to generate the user data that it provides.
It is noted that the host computer 2302, the base station 2318, and the UE 2314 illustrated in
In
The wireless connection 2326 between the UE 2314 and the base station 2318 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 2314 using the OTT connection 2316, in which the wireless connection 2326 forms the last segment. More precisely, the teachings of these embodiments may improve the utilization of PUCCH, and thereby provide benefits such as enhancing reliability of the PUCCH, keeping the latency low, and/or saving UE power consumption.
A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2316 between the host computer 2302 and the UE 2314, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 2316 may be implemented in the software 2310 and the hardware 2304 of the host computer 2302 or in the software 2340 and the hardware 2334 of the UE 2314, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 2316 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 2310, 2340 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2316 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 2318, and it may be unknown or imperceptible to the base station 2318. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer 2302′s measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 2310 and 2340 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2316 while it monitors propagation times, errors, etc.
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).
Some example embodiments of the present disclosure are as follows:
Embodiment 1: A method of uplink transmission, performed by a user equipment, UE, (712) in a wireless communication network that includes two or more transmission/reception points, TRPs, each associated with a spatial relation or TCI state, the method comprising: receiving (1600), from a base station (702) in the wireless communication network, a configuration of a first spatial relation and a second spatial relation for a uplink channel, and an indication of a number of transmission repetitions in the uplink channel; and transmitting (1604) the uplink channel a number of times according to the number of transmission repetitions in a first set of sub-slots of the uplink channel according to the first spatial relation, and in a second set of sub-slots of the uplink channel according to the second spatial relation.
Embodiment 2: The method of embodiment 1 wherein the uplink channel is a physical uplink control channel, PUCCH.
Embodiment 3: The methods of embodiments 1-2, wherein a total number of sub-slots in the first set and the second set of sub-slots equal to the number of transmission repetitions.
Embodiment 4: The methods of embodiments 1-3, wherein each sub-slot in a slot, which comprises the first set and the second set of sub-slots, comprises a number of OFDM symbols.
Embodiment 5: The method of embodiments 1-4, wherein the first set and the second set of sub-slots are non-overlapping in time.
Embodiment 6: The method of embodiments 1-5, wherein the first set and the second set of sub-slots are in a same slot.
Embodiment 7: The method of embodiments 1-6, wherein time and frequency resource allocations in each sub-slot of the first set and the second set of sub-slots have a same pattern.
Embodiment 8: The method of embodiments 1-7, wherein the uplink channel is one of physical uplink control channel, PUCCH, formats 0 to 4.
Embodiment 9: The method of embodiment 1-8 further comprising receiving (1600A), from the base station (702), another configuration of a gap symbol between adjacent transmission repetitions.
Embodiment 10: The method of embodiment 1-9 further comprising receiving (1602), from the base station (702), a second configuration of multiple numbers of the transmission repetitions for the uplink channel, wherein which repetition number to use depends on whether one or more of the following conditions are met: 2 TCI states are indicated in the Transmission configuration indication field (if present) of the DCI scheduling the PDSCH; one of the DL multi-TRP PDSCH schemes (i.e., configured by a higher layer parameter RepetitionSchemeConfig-r16) is used for an associated PDSCH; the Priority indicator field (if present) of the DCI is set to “1”; the PDSCH is scheduled by DCI format 1_2; the PUCCH resource is activated with 2 TCI states; and certain UCI type carried by the PUCCH.
Embodiment 11: The method of embodiment 1-9 further comprising: receiving (1602), from the base station (702), a second configuration of multiple numbers of the transmission repetitions for the uplink channel, wherein which repetition number to use depends on a traffic type the uplink channel is associated with.
Embodiment 12: The method of embodiment 1-9 further comprising receiving (1602A), from the base station (702), one or more configurations for determining the number of transmission repetitions, wherein one of the one or more configurations is dynamically indicated in downlink control information, DCI.
Embodiment 13: The method of embodiment 1-12 further comprising dropping (1604A) one transmission repetition when it is overlapping with another uplink channel with a higher priority.
Embodiment 14: The method of embodiment 1-12 further comprising multiplexing (1604A) one transmission repetition with an overlapping uplink channel with a same priority.
Embodiment 15: The method of embodiment 1-12 further comprising omitting a corresponding transmission repetition if the UE (712) collides with an invalid symbol.
Embodiment 16: The method of embodiment 1-12 further comprising, if the UE (712) collides with an invalid symbol, delaying a corresponding transmission repetition until enough valid symbols are available (step 1604B).
Embodiment 17: The method of embodiment 1-16 further comprising receiving (1606) a Media Access Control (MAC) control element (CE) command from the base station (702).
Embodiment 18: The method of embodiment 17 further comprising adjusting (1608) timing in applying the MAC CE command according to the slot or sub-slot over which the last transmission repetition carrying a corresponding HARQ-ACK associated with the MAC CE command is transmitted.
Embodiment 19: A method of uplink transmission, performed by a base station (702), in a wireless communication network that includes two or more transmission/reception points, TRPs, each associated with a spatial relation or TCI state, the method comprising: providing (1600), to a user equipment, UE, (712) in the wireless communication network, a configuration of a first spatial relation and a second spatial relation for a uplink channel, and an indication of a number of transmission repetitions in the uplink channel.
Embodiment 20: The method of embodiment 19 wherein the uplink channel is a physical uplink control channel, PUCCH.
Embodiment 21: The method of embodiment 19-20 further comprising providing (1600A), to the UE (712), another configuration of a gap symbol between adjacent transmission repetitions.
Embodiment 22: The method of embodiment 19-21 further comprising providing (1602), to the UE (712), a second configuration of multiple numbers of the transmission repetitions for the uplink channel, wherein which repetition number to use depends on whether one or more of the following conditions are met: 2 TCI states are indicated in the Transmission configuration indication field (if present) of the DCI scheduling the PDSCH; one of the DL multi-TRP PDSCH schemes (i.e., configured by a higher layer parameter RepetitionSchemeConfig-r16) is used for an associated PDSCH; the Priority indicator field (if present) of the DCI is set to “1”; the PDSCH is scheduled by DCI format 1_2; the PUCCH resource is activated with 2 TCI states; and certain UCI type carried by the PUCCH.
Embodiment 23: The method of embodiment 19-21 further comprising providing (1602), to the UE (712), a second configuration of multiple numbers of the transmission repetitions for the uplink channel, wherein which repetition number to use depends on a traffic type the uplink channel is associated with.
Embodiment 24: The method of embodiment 19-21 further comprising providing (1602A), to the UE (712), one or more configurations for determining the number of transmission repetitions, wherein one of the one or more configurations is dynamically indicated in downlink control information, DCI.
Embodiment 25: The method of embodiment 19-24 further comprising providing (1606), to the UE (712), a Media Access Control (MAC) control element (CE) command.
Embodiment 26: A wireless device for uplink transmission in a wireless communication network that includes two or more transmission/reception points, TRPs, each associated with a spatial relation or TCI state, the wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.
Embodiment 27: A base station for uplink transmission in a wireless communication network that includes two or more transmission/reception points, TRPs, each associated with a spatial relation or TCI state, the base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station.
Embodiment 28: A User Equipment, UE, for uplink transmission in a wireless communication network that includes two or more transmission/reception points, TRPs, each associated with a spatial relation or TCI state comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
Embodiment 29: 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, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
Embodiment 30: The communication system of the previous embodiment further including the base station.
Embodiment 31: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
Embodiment 32: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
Embodiment 33: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
Embodiment 34: The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
Embodiment 35: The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
Embodiment 36: A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.
Embodiment 37: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE; wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
Embodiment 38: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
Embodiment 39: The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
Embodiment 40: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
Embodiment 41: The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
Embodiment 42: A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
Embodiment 43: The communication system of the previous embodiment, further including the UE.
Embodiment 44: The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
Embodiment 45: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
Embodiment 46: The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
Embodiment 47: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
Embodiment 48: The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
Embodiment 49: The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.
Embodiment 50: The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data.
Embodiment 51: A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
Embodiment 52: The communication system of the previous embodiment further including the base station.
Embodiment 53: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
Embodiment 54: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
Embodiment 55: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
Embodiment 56: The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
Embodiment 57: The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.
Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.
This application claims the benefit of Provisional Pat. Application Serial No. 63/063,035, filed Aug. 7, 2020, the disclosure of which is hereby incorporated herein by reference in its entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2021/057283 | 8/6/2021 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63063035 | Aug 2020 | US |
