The present disclosure relates to codebook determination.
NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both downlink (i.e., from a network node, gNB, or base station, to a user equipment or UE) and uplink (i.e., from UE to gNB). DFT spread OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally sized subframes of 1 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 kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols.
Data scheduling in NR is typically in slot basis, an example is shown in
Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (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 ½μ ms.
In the frequency domain, a system bandwidth is divided into resource blocks (RBs), each corresponding to twelve 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 transmissions can be either dynamically scheduled in which the gNB transmits a DL assignment via Downlink Control Information (DCI) over PDCCH (Physical Downlink Control Channel) to a UE for each PDSCH transmission, or Semi-Persistent Scheduled (SPS) in which one or more DL SPS are semi-statically configured and each can be activated or deactivated by a DCI.
There are three DCI formats defined for scheduling PDSCH in NR, i.e., DCI format 1_0, DCI format 1_1, and DCI format 1_2. DCI format 1-0 has a smaller size and can be used when a UE is not fully connected to the network while DCI format 1_1 and DCI format 1_2 can be used for scheduling MIMO (Multiple-Input-Multiple-Output) transmissions with up to 2 transport blocks (TBs). The DCI formats are referred to as DL DCI formats.
A UE monitors a set of PDCCH candidates for potential PDCCHs. A PDCCH candidate consists of L∈[1,2,4,8,16] control-channel elements (CCEs) in a Control Resource Set (CORESET). A CCE consists of 6 resource-element groups (REGs) where a REG equals one RB during one OFDM symbol. L is referred to as the CCE aggregation level.
The set of PDCCH candidates is defined in terms of PDCCH search space (SS) sets. A SS set can be a Common Search Space (CSS) set or a UE Specific Search Space (USS) set. A UE can be configured with up to 10 SS sets per bandwidth part (BWP) for monitoring PDCCH candidates.
Each SS set is associated with a CORESET. A CORESET consists of NRBCORESET resource blocks in the frequency domain and NsymbCORESET∈{1,2,3} consecutive OFDM symbols in the time domain. In NR Rel-15, a UE can be configured with up to 3 CORESETs per bandwidth part.
For each SS set, a UE is configured with the following parameters:
A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set s, the UE determines that a PDCCH monitoring occasion(s) exists in slot ns,fμ in frame nf if (nf·Nslotframe,μ+ns,fμ−os) mod ks=0, where Nslotframe,μ is the number of slots per radio frame. The UE monitors PDCCH candidates for search space set s for Ts consecutive slots, starting from slot ns,fμ, and does not monitor PDCCH candidates for search space set s for the next ks−Ts consecutive slots.
A UE detects PDCCH in each PDCCH monitoring occasion. If a PDCCH is detected, the UE decodes the corresponding PDSCH based on the decoded control information in the PDCCH.
In Rel-16, to better support multiple PDCCH monitoring occasions in a slot, new PDCCH monitoring capabilities are defined at least in terms of the maximum number of non-overlapping CCEs for channel estimation. The new limit is discussed based on the concept of PDCCH monitoring span. In short, the PDCCH monitoring span definition provides a set of rules for UE and gNB to have the same understanding on PDCCH monitoring span pattern in a slot based on CORESET/search space configuration and UE capability signaling related to PDCCH monitoring. The UE signals a candidate value set which contains parameters related to span gap X (minimum gap in OFDM symbols between two consecutive spans) and span length Y in OFDM symbols. Together with the CORESET/search space configuration, the monitoring span pattern can then be derived. The span pattern may contain multiple spans in a slot is repeated over multiple slots.
When a PDCCH is detected by the UE, the decoding status of its scheduled PDSCH is sent back to the gNB in the form of Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) over a Physical Uplink Control Channel (PUCCH) resource. If the PUCCH overlaps with a PUSCH transmission by the same UE, HARQ ACK feedback can also be conveyed on PUSCH.
Similarly, when a DL SPS deactivation DCI or a DCI for Secondary cell (SCell) dormancy is received by the UE, a HARQ ACK is sent by the UE to acknowledge the reception of the DCI.
If the UE detects a DCI format scheduling a PDSCH reception ending in slot n or if the UE detects a DCI indicating a SPS PDSCH release or SCell dormancy through a PDCCH reception ending in slot n, the UE provides corresponding HARQ-ACK information in a PUCCH transmission in slot n+k, where k is indicated by a PDSCH-to-HARQ-timing-indicator field in the DCI format, if present, or provided by dl-DataToUL-ACK. k is also referred to as K1. For DCI format 1-0, k can be one of {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 1-1 and DCI format 1_2, k can be one of a set of values configured in dl-DataToUL-ACK. The set of values can be in the range of {0, 1, . . . , 15}. Up to eight values can be configured in the set.
In case of carrier aggregation (CA) with multiple carriers and/or TDD operation, multiple aggregated HARQ ACK/NACK bits may be sent in a single PUCCH resource.
In NR, up to four PUCCH resource sets can be configured to a UE. A PUCCH resource set with pucch-ResourceSetId=0 can have up to 32 PUCCH resources while for PUCCH resource sets with pucch-ResourceSetId=1 to 3, each set can have up to 8 PUCCH resources. A UE determines the PUCCH resource set in a slot based on the number of aggregated UCI (Uplink Control Information) bits to be sent in the slot. The UCI bits consists of HARQ ACK/NACK, scheduling request (SR), and channel state information (CSI) bits.
For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a PUCCH resource set. The PUCCH resource determination is based on a 3-bit PUCCH resource indicator (PRI) field in a DL DCI format.
If more than one DL DCI formats are received in the case of CA and/or TDD, the PUCCH resource determination is based on a PRI field in the last DCI among the multiple received DL DCIs that the UE detects. The multiple received DCIs have a value of a PDSCH-to-HARQfeedback timing indicator field indicating a same slot for the PUCCH transmission. For PUCCH resource determination, the detected DCI formats are first indexed in an ascending order across serving cell indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across PDCCH monitoring occasion indexes.
NR Rel-15 supports two types of HARQ codebooks, i.e., semi-static (type 1) and dynamic (type 2) codebooks, for HARQ Ack multiplexing for multiple serving cells in case of carrier aggregation (CA) or multiple DL slots in case of TDD. A UE can be configured to use either one of the codebooks for HARQ Ack/Nack feedback.
Type 1 HARQ codebook (CB) is determined based on a set of semi-statically configured parameters. The codebook size corresponds to the maximum number of HARQ Ack bits that may need to be fed back and it does not change dynamically. Therefore, the feedback overhead can be large.
Unlike Type 1 HARQ codebook, the size of Type 2 HARQ codebook changes dynamically based on the actual number of PDSCH receptions or SPS PDSCH releases or SCell dormancy associated with a same PUCCH resource for HARQ Ack feedback. For this purpose, a counter DAI (Downlink Assignment Indicator) field in the DCIs and in case of DCI format 1-1 and DCI format 1_2, also a total DAI field (if more than one serving cell are configured) are defined.
A value of the counter DAI field in DCI formats denotes the accumulative number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s), SPS PDSCH release, or SCell dormancy associated with the DCI formats that is present up to the current serving cell and current PDCCH monitoring occasion, first in ascending order of serving cell index c and then in ascending order of PDCCH monitoring occasion index m, where 0≤m<M and M is total number of PDCCH monitoring occasions.
The value of the total DAI, when present, in DCI formats denotes the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release or SCell dormancy associated with the DCI formats that is present, up to the current PDCCH monitoring occasion m and is updated from PDCCH monitoring occasion to PDCCH monitoring occasion.
An example is shown
For HARQ-ACK information transmitted in a PUCCH in slot n, the UE determines the HARQ-ACK information bits, õ0ACK, õ1ACK, . . . , õO
PDSCH transmission with multiple panels or transmission points (TRPs) has been introduced in NR Rel-16, in which a transport block may be repeated over multiple TRPs to increase PDSCH reliability.
In NR Rel-17, it has been proposed to enhance PDCCH reliability with multiple TRPs by repeating a PDCCH over different TRPs. An example is shown in
The PDCCH are repeated in two PDCCH candidates each associated with one of the two TRPs. The two PDCCH candidates are linked, i.e., the location of one PDCCH candidate can be obtained from the other PDCCH candidate. When performing PDCCH detection, a UE may detect PDCCH individually in each PDCCH candidate or jointly by soft combining of the two linked PDCCH candidates.
Improved systems and methods for codebook determination are needed.
Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first Physical Downlink Control Channel (PDCCH) occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected Downlink Control Information (DCI); and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes.
Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. A method is proposed to construct the codebook in the presence of PDCCH repetitions. The method comprises one or more of: defining a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying at the UE the first PDCCH occasion for each detected DCI; and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In some embodiments, the codebook comprises a Type 2 HARQ ACK codebook. In some embodiments, the counter field comprises a counter DAI field.
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.
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 a 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.
Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (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. In some embodiments a TRP may be a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. In some embodiments, in Multiple Transmit/Receive Point (multi-TRP) operation, a serving cell can schedule UE from two TRPs, providing better PDSCH coverage, reliability and/or data rates. There are two different operation modes for multi-TRP: single- Downlink Control Information (DCI) and multi-DCI. For both modes, control of uplink and downlink operation is done by both physical layer and MAC. In single-DCI mode, UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, UE is scheduled by independent DCIs from each TRP.
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.
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.
The base stations 602 and the low power nodes 606 provide service to wireless communication devices 612-1 through 612-5 in the corresponding cells 604 and 608. The wireless communication devices 612-1 through 612-5 are generally referred to herein collectively as wireless communication devices 612 and individually as wireless communication device 612. In the following description, the wireless communication devices 612 are oftentimes UEs, but the present disclosure is not limited thereto.
There currently exist certain challenges. In the presence of Physical Downlink Control Channel (PDCCH) repetition, how to construct Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook is an issue. For instance, consider an example where PDCCH #1 scheduling a PDSCH is repeated in PDCCH monitoring occasions m=0 and m=1, and there are other PDSCHs scheduled by PDCCHs in PDCCH monitoring occasion m=0, assume that PDCCH #1 is only detected in PDCCH monitoring occasion m=1. If the existing procedure for Type 2 HARQ ACK codebook construction is applied (i.e., the HARQ ACK bits are arranged first in ascending order of serving cell index and then in ascending order of PDCCH monitoring occasion index), the counter DAI and total DAI in DCI #1 in PDCCH monitoring occasion m=1 would result in an incorrect number of HARQ ACK bits and also incorrect mapping between the PDSCHs and the HARQ ACK bits. Improved systems and methods for codebook determination are needed.
Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected DCI; and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 HARQ ACK codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes.
In one embodiment, the counter DAI in a DCI is incremented only at the first PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the first PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs early in time. Only the first PDCCH occasion is considered for incrementing counter DAI and total DAI in subsequent DCIs.
The PDCCH monitoring occasions described in this invention disclosure can be either in a slot or a monitoring span. The different PDCCH monitoring occasions can be in different slots/monitoring spans or the same slot/monitoring span.
An example is shown in
In one embodiment, the counter DAI in a DCI is incremented only at the first PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the first PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs early in time. Only the first PDCCH occasion is considered for incrementing counter DAI and total DAI in subsequent DCIs.
If a PDCCH is repeated within a same PDCCH monitoring occasion in different PDCCH candidates of a same or different CORESETs or in a same or different SS sets, the first PDCCH occasion can be defined as one of
In the UE side, for each detected DCI, the associated first PDCCH occasion is determined. The existing Type 2 HARQ codebook procedure is then applied by considering only the determined first PDCCH occasion.
Using the example shown in
Assuming that only a single codeword is configured in the two serving cells, the resulting HARQ ACK information bits õ0ACK, õ1ACK, . . . , õO
The embodiment may be described by changes (highlighted in bold) in the existing pseudo code for Type 2 HARQ-Ack codebook below.
If the UE transmits HARQ-ACK information in a PUCCH in slot n and for any PUCCH format, the UE determines the õ0ACK, õ1ACK, . . . , õO
In an alternative embodiment, the counter DAI in a DCI is incremented only at the last PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the last PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs latest in time. Only the last PDCCH occasion is considered for incrementing counter DAI and total DAI.
An example is shown in
In the UE side, for each detected DCI, the associated last PDCCH occasion is determined. The existing Type 2 HARQ codebook procedure is then applied by considering only the determined last PDCCH occasions.
Using the example shown in
Assuming that only a single codeword is configured in the two serving cells, the resulting HARQ ACK information bits õ0ACK, õ1ACK, . . . , õO
The embodiment may be described by changes (highlighted in bold) in the existing pseudo code for Type 2 HARQ-Ack codebook below.
---start of proposed changes in 38.213 v16.4.0 section 9.1.3.1---
If the UE transmits HARQ-ACK information in a PUCCH in slot n and for any PUCCH format, the UE determines the õ0ACK, õ1ACK, . . . , õO
As used herein, a “virtualized” radio access node is an implementation of the radio access node 1500 in which at least a portion of the functionality of the radio access node 1500 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 1500 may include the control system 1502 and/or the one or more radio units 1510, as described above. The control system 1502 may be connected to the radio unit(s) 1510 via, for example, an optical cable or the like. The radio access node 1500 includes one or more processing nodes 1600 coupled to or included as part of a network(s) 1602. If present, the control system 1502 or the radio unit(s) are connected to the processing node(s) 1600 via the network 1602. Each processing node 1600 includes one or more processors 1604 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1606, and a network interface 1608.
In this example, functions 1610 of the radio access node 1500 described herein are implemented at the one or more processing nodes 1600 or distributed across the one or more processing nodes 1600 and the control system 1502 and/or the radio unit(s) 1510 in any desired manner. In some particular embodiments, some or all of the functions 1610 of the radio access node 1500 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) 1600. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1600 and the control system 1502 is used in order to carry out at least some of the desired functions 1610. Notably, in some embodiments, the control system 1502 may not be included, in which case the radio unit(s) 1510 communicate directly with the processing node(s) 1600 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 1500 or a node (e.g., a processing node 1600) implementing one or more of the functions 1610 of the radio access node 1500 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 1800 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 2000 is itself connected to a host computer 2016, 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 2016 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 2018 and 2020 between the telecommunication network 2000 and the host computer 2016 may extend directly from the core network 2004 to the host computer 2016 or may go via an optional intermediate network 2022. The intermediate network 2022 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 2022, if any, may be a backbone network or the Internet; in particular, the intermediate network 2022 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 2100 further includes a base station 2118 provided in a telecommunication system and comprising hardware 2120 enabling it to communicate with the host computer 2102 and with the UE 2114. The hardware 2120 may include a communication interface 2122 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 2100, as well as a radio interface 2124 for setting up and maintaining at least a wireless connection 2126 with the UE 2114 located in a coverage area (not shown in
The communication system 2100 further includes the UE 2114 already referred to. The UE's 2114 hardware 2134 may include a radio interface 2136 configured to set up and maintain a wireless connection 2126 with a base station serving a coverage area in which the UE 2114 is currently located. The hardware 2134 of the UE 2114 further includes processing circuitry 2138, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 2114 further comprises software 2140, which is stored in or accessible by the UE 2114 and executable by the processing circuitry 2138. The software 2140 includes a client application 2142. The client application 2142 may be operable to provide a service to a human or non-human user via the UE 2114, with the support of the host computer 2102. In the host computer 2102, the executing host application 2112 may communicate with the executing client application 2142 via the OTT connection 2116 terminating at the UE 2114 and the host computer 2102. In providing the service to the user, the client application 2142 may receive request data from the host application 2112 and provide user data in response to the request data.
The OTT connection 2116 may transfer both the request data and the user data. The client application 2142 may interact with the user to generate the user data that it provides.
It is noted that the host computer 2102, the base station 2118, and the UE 2114 illustrated in
In
The wireless connection 2126 between the UE 2114 and the base station 2118 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 2114 using the OTT connection 2116, in which the wireless connection 2126 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
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 2116 between the host computer 2102 and the UE 2114, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 2116 may be implemented in the software 2110 and the hardware 2104 of the host computer 2102 or in the software 2140 and the hardware 2134 of the UE 2114, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 2116 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 2110, 2140 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2116 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 2118, and it may be unknown or imperceptible to the base station 2118. 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 2102's measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 2110 and 2140 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2116 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.).
Embodiment 1: A method performed by a wireless device for constructing a codebook, the method comprising one or more of: defining (1300) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (1302) the first PDCCH occasion for each detected DCI; and constructing (1304) a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs.
Embodiment 2: The method of embodiment 1 wherein the codebook comprises a Type 2 HARQ ACK codebook.
Embodiment 3: The method of any of embodiments 1 to 2 wherein the counter field comprises a counter Downlink Assignment Indicator, DAI, field.
Embodiment 4: The method of any of embodiments 1 to 2 wherein the wireless device comprises a User Equipment, UE.
Embodiment 5: The method of any of embodiments 1 to 4, further comprising: receiving, from a network node, multiple search space sets and PDCCH repetition in a subset of the search space sets.
Embodiment 6: The method of any of embodiments 1 to 5, further comprising: monitoring the first and the second PDCCHs and if detected, decoding the corresponding PDSCH.
Embodiment 7: The method of any of embodiments 1 to 6, further comprising: determining a first PDCCH occasion for the first PDCCH when it is detected.
Embodiment 8: The method of any of embodiments 1 to 7, further comprising: constructing a Type 2 HARQ ACK codebook based on the first PDCCH occasion of the first PDCCH and/or the second PDCCH, and the decoding status of the first and the second PDSCH.
Embodiment 9: The method of any of embodiments 1 to 8 wherein receiving the multiple search space sets and the PDCCH repetition in a subset of the search space sets comprises: receiving multiple linked PDCCH candidates in a same or different search space sets over which a PDCCH may be repeated.
Embodiment 10: The method of any of embodiments 1 to 9 wherein the first PDCCH occasion corresponds to a linked PDCCH candidate that occurs first in time.
Embodiment 11: The method of any of embodiments 1 to 10 wherein the first PDCCH occasion corresponds to one of: a. a linked PDCCH candidate with a lower (or higher) PDCCH candidate index; b. a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID; and c. a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID.
Embodiment 12: The method of any of embodiments 1 to 11 wherein a value of the counter field in a DCI carried in a PDCCH repeated in multiple PDCCH occasions is determined based on the first PDCCH occasion in case of PDCCH repetition.
Embodiment 13: The method of any of embodiments 1 to 12 wherein constructing a Type 2 HARQ ACK codebook based on the first PDCCH occasion comprises allocating a HARQ ACK bit(s) to the first PDSCH scheduled by the first PDCCH transmitted in the first PDCCH occasion.
Embodiment 14: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.
Embodiment 15: A method performed by a base station for updating a counter, the method comprising one or more of: defining (1400) a first PDCCH occasion among multiple PDCCH occasions associated with a DCI; identifying (1402) the first PDCCH occasion; and incrementing (1404) the counter at the first PDCCH occasion and indicating the counter value in a counter field in the DCI.
Embodiment 16: The method of embodiment 1 wherein the PDCCH schedules a PDSCH, a SPS release, or a Scell dormancy.
Embodiment 17: The method of any of embodiments 15 to 16 wherein the counter field comprises a counter Downlink Assignment Indicator, DAI, field.
Embodiment 18: The method of any of embodiments 15 to 17 wherein the base station comprises a gNB.
Embodiment 19: The method of any of embodiments 15 to 18, further comprising: configuring a wireless device with multiple search space sets and PDCCH repetition in a subset of the search space sets.
Embodiment 20: The method of any of embodiments 15 to 19, further comprising: scheduling a first PDSCH with a first PDCCH which is repeated in multiple PDCCH occasions and a second PDSCH with a second PDCCH without repetition.
Embodiment 21: The method of any of embodiments 15 to 20, further comprising: determining a first PDCCH occasion for the first PDCCH.
Embodiment 22: The method of embodiment 1 where the incrementing the counter comprises adding one to the counter.
Embodiment 23: The method of any of embodiments 15 to 22 wherein configuring the wireless device with the multiple search space sets and the PDCCH repetition in a subset of the search space sets comprises: configuring the wireless device with multiple linked PDCCH candidates in a same or different search space sets over which a PDCCH may be repeated.
Embodiment 24: The method of any of embodiments 15 to 23 wherein the first PDCCH occasion corresponds to a linked PDCCH candidate that occurs first in time.
Embodiment 25: The method of any of embodiments 15 to 24 wherein the first PDCCH occasion corresponds to one of: a. a linked PDCCH candidate with a lower (or higher) PDCCH candidate index; b. a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID; and c. a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID.
Embodiment 26: The method of any of embodiments 15 to 25 wherein a value of the counter field in a DCI carried in a PDCCH repeated in multiple PDCCH occasions is determined based on the first PDCCH occasion in case of PDCCH repetition.
Embodiment 28: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.
Embodiment 29: A wireless device for constructing a codebook, 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 30: A base station for incrementing a counter, 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 31: A User Equipment, UE, for constructing a codebook, the UE 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 32: 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 33: The communication system of the previous embodiment further including the base station.
Embodiment 34: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
Embodiment 35: 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 36: 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 37: The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
Embodiment 38: 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 39: 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 40: 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 41: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
Embodiment 42: 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 43: 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 44: The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
Embodiment 45: 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 46: The communication system of the previous embodiment, further including the UE.
Embodiment 47: 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 48: 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 49: 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 50: 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 51: The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
Embodiment 52: 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 53: 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 54: 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 55: The communication system of the previous embodiment further including the base station.
Embodiment 56: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
Embodiment 57: 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 58: 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 59: The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
Embodiment 60: 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.
Some embodiments of the present disclosure could be implemented using one or more of the following proposals.
At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).
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 patent application Ser. No. 63/138,117, filed Jan. 15, 2021 and provisional patent application Ser. No. 63/138,721, filed Jan. 18, 2021, the disclosures of which are hereby incorporated herein by reference in their entireties.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/IB2022/050319 | 1/14/2022 | WO |
Number | Date | Country | |
---|---|---|---|
63138721 | Jan 2021 | US | |
63138117 | Jan 2021 | US |