WO2022032212A1 - Configuration de répétition de canal de commande de liaison descendante physique et configuration de démarrage de canal partagé de liaison descendante physique et indication de temps de traitement - Google Patents

Configuration de répétition de canal de commande de liaison descendante physique et configuration de démarrage de canal partagé de liaison descendante physique et indication de temps de traitement Download PDF

Info

Publication number
WO2022032212A1
WO2022032212A1 PCT/US2021/045131 US2021045131W WO2022032212A1 WO 2022032212 A1 WO2022032212 A1 WO 2022032212A1 US 2021045131 W US2021045131 W US 2021045131W WO 2022032212 A1 WO2022032212 A1 WO 2022032212A1
Authority
WO
WIPO (PCT)
Prior art keywords
repetition
message
repetition count
dci
count
Prior art date
Application number
PCT/US2021/045131
Other languages
English (en)
Inventor
Debdeep CHATTERJEE
Gang Xiong
Bishwarup Mondal
Alexei Davydov
Avik SENGUPTA
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202180049031.4A priority Critical patent/CN115804056A/zh
Publication of WO2022032212A1 publication Critical patent/WO2022032212A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • Various embodiments generally may relate to the field of wireless communications, and in particular, to the field of communication in a cellular network compliant with one of more Third Generation Partnership Project (3GPP) specifications.
  • 3GPP Third Generation Partnership Project
  • Fig. 1 illustrates an inter-CORESET approach for PDCCH repetition and soft-combining, where different CORESETs are associated with different TCI states.
  • Fig. 2 illustrates an inter-CORESET approach for repetition or soft-combining.
  • Fig. 3 illustrates CCE aggregation performed as part of soft-combining where an overlapping search space is involved.
  • Fig. 4 illustrates an intra-CORESET approach for PDCCH repetition across monitoring occasions.
  • Fig. 5 illustrates an intra-CORESET approach for PDCCH based on SS sets, where different SS sets of a same CORESET are associated with different TCI states.
  • Fig. 6 illustrates a set of slots showing various possibilities for DCI being sent via one or two PDCCHs.
  • Fig. 7 illustrates a cross-slot repetition of DCI.
  • Fig. 8 illustrates an example of PDSCH processing time ambiguity due to PDCCH repetition.
  • Fig. 9 illustrates a wireless network in accordance with various embodiments.
  • Fig. 10 illustrates a User Equipment (UE) and a Radio Access Node (RAN) in wireless communication according to various embodiments.
  • UE User Equipment
  • RAN Radio Access Node
  • FIG. 11 illustrates components according to some example embodiments, the components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies discussed herein.
  • Fig. 12 illustrates a flow chart for a process according to a first embodiment.
  • Fig. 13 illustrates a flow chart for a process according to a second embodiment.
  • Some embodiments are related to the 5G New Radio (NR) Rel-17 multiple input multiple output (MIMO) enhancements work item (Wl) on Enhancements on physical downlink (DL) control channel (PDCCH).
  • Some embodiments pertain to mechanisms for PDCCH repetitions and mechanisms to map transmission configuration indicator (TCI) states to PDCCH.
  • NR New Radio
  • MIMO multiple input multiple output
  • TCI transmission configuration indicator
  • PDCCH repetition from different transmission reception points can be configured based on control resource sets (CORESETs), synchronization signal (SS)- sets or monitoring occasions.
  • CORESETs control resource sets
  • SS synchronization signal
  • Some embodiments herein allow the network to allocate PDCCH repetitions from different TRPs (different TCI states), building on the signaling framework that is existing in Rel-15 and Rel-16.
  • a selection diversity scheme is the case where a user equipment (UE) may receive multiple copies of the same downlink control information (DCI).
  • the network (NW) essentially transmits the same DCI using Rel-15/16 principles multiple times and each repetition may have different aggregation levels (ALs). There is no expectation that the UE should attempt soft- combination of the different repetitions and this is not accounted in blind decode (BD) limits.
  • selection diversity may be implemented where each BD candidate is treated in an identical manner as in Rel-15.
  • Soft combining schemes are cases where a UE is expected to attempt soft-combination of 2 PDCCH candidates and the soft-combination attempts are accounted in BD limits. At the UE side, soft-combining may mean additional storage and combining of PDCCH candidates and additional decoding attempts.
  • soft-combining schemes may be categorized into joint coding (similar to scheme 2a referred to below) or repetition (similar to scheme 2b referred to below, but including chase combining).
  • joint coding would be naturally limited to AL level 16 (AL16) performance. In terms of performance, no significant difference is to be expected between the two schemes.
  • PDCCH reliability schemes at a high-level can be classified into - 1) selection diversity 2a) soft-combining with joint coding 2b) soft combining with repetition.
  • CCE control channel element
  • SFN system frame number
  • Selection diversity selection diversity
  • Soft-combining selection diversity
  • SFN is considered specification transparent, as BD/CCE provisioning in SFN is identical to Rel-15.
  • the NW may choose (dynamically) to transmit only from TRP-1, only from TRP-2 or from both TRP-1 and TRP-2, but TRP transmission is transparent to the UE.
  • CCE provisioning can be considered to be generally additive between TRP-1 and TRP-2 since channel estimation cannot be re-used across TRPs.
  • channel estimation can be fully reused within the same TRP/CORESET across SS sets and ALs based on Rel-15 rules.
  • BD provisioning we may assume the same guiding principle that the NW may choose (dynamically) to transmit only from TRP-1, only from TRP-2 or from both TRP-1 and TRP-2.
  • TRP-1 may choose to transmit AL16 PDCCH without repetition, or transmit with two repetitions using AL8+AL8 from TRP-l+TRP-2 respectively in order to send a particular ultra-reliable low latency communication (URLLC) packet.
  • URLLC ultra-reliable low latency communication
  • BD provisioning for soft-combining schemes can vary based on the exact scheme being used.
  • the guiding principle of the NW being able to choose (dynamically) from 1-TRP or 2-TRP transmission may be followed, and, consequently, BD provisioning may be formulated according to some embodiments as follows:
  • BD candidates from TRP-1) + BD (candidates from TRP-2) + BD (soft-combining candidates from TRP-1, 2); or
  • TRP-2 may transmit PDCCH only when TRP-1 is also transmitting.
  • a PDCCH repetition scheme is to allow the NW to choose (dynamically) to transmit DCI from TRP-1 only or from TRP-2 only without repetition or from both TRP-1 and TRP-2 with repetition.
  • the following BD/CCE provisioning principles may be considered for repetitions:
  • CCE provisioning may involve CCE (TRP-1) + CCE (TRP-2);
  • BD provisioning for selection diversity may involve BD (candidates from TRP-1) + BD (candidates from TRP-2);
  • BD provisioning for soft-combining may involve BD (candidates from TRP-1) + BD (candidates from TRP-2) + BD (soft-candidates from TRP-1, TRP-2)
  • BD/CCE partitioning could be 80-20 between TRP-1 and TRP-2 , where TRP-1 assumes the role of a primary TRP for URLLC transmission.
  • BD/CCE count should not be simply doubled but should be able to be flexibly adjusted according to different deployment needs.
  • Modifications in the context of maximum reliability target may also be helpful, for example in determine whether AL16 type reliability is sufficient, whether a different AL level may be needed, and whether repetitions may span both within and across slots. For example a) AL8 (TRP-1)+ AL8 (TRP-2) or b) AL16 (TRP-l)+AL16(TRP-2) or c) higher repetitions including coverage (PDCCH repetition within slot or across slots)
  • Embodiment 1-1 Inter-CORESET approach
  • Fig. 1 shows inter-CORESET approach for PDCCH repetition and soft-combining, where different CORESETs are associated with different TCI states.
  • Fig. 1 shows a set 100 of two CORESETs 102 and 104, corresponding respectively to CORESET-1 and CORESET-2.
  • CORESET-1 corresponds to TRP1 and SS 1
  • CORESET-2 corresponds to TRP2 and SS 2.
  • Each CORESET includes 8 PDCCH candidates at AL2 and 8 PDCCH candidates at AL4.
  • each CORESET is associated with a different TRP (TCI-State).
  • TRP TCI-State
  • CORESET-1, SS set-1 and TCI-Stateld-1 are from TRP-1 and CORESET-2
  • SS set-2 and TCI-Stateld-2 are from TRP-2.
  • candidate m of a given value of SS- 1/AL4 can be combined with candidate m of the same value of SS-2/AL4.
  • the arrows between candidates m in Fig. 1 show examples of possible combinations according to the above regime.
  • Fig. 2 also pertains to an inter-CORESET approach for repetition or soft-combining.
  • a set 200 of CORESETs is shown including CORESET-1, 202 and CORESET-2, 204, each including 4 PDCCH candidates at AL4.
  • candidates from CORESET-1 and CORESET-2 may be subject to repetition 206 or soft-combined by way of joint coding to result in a soft-combined CORESET 208 with candidates at AL8.
  • a set of CORESETs 300 include CORESET-1 302 and CORESET-2 304, and CCE aggregation may be performed as part of soft-combining where an overlapping search space is involved.
  • candidates having the same m value and corresponding to the same AL levels, in this case, AL2 may be combined.
  • TDM-ed time division multiplexed
  • search space or CORESET overlap For selection diversity, no restriction on search space or CORESET overlap is necessary.
  • soft-combining if search spaces are non-overlapping it is fine (this could be typical case). It is possible to envision that search spaces are overlapping but BD candidates that are soft-combined are non-overlapping (hash function start position is CORESET dependent - an offset may be possible).
  • Embodiment l-2a - Intra-CORESET approach with Repetition across monitoring occasions [0045] Reference is now made to Fig. 4, which shows an intra-CORESET approach for PDCCH repetition across monitoring occasions, where a CORESET 400 including monitoring occasions (Mos) MO-1 and MO-2 associated with different TCI states, respectively, TCI-1 and TCI-2.
  • each monitoring occasion can be associated with a different TRP (TCI-State), while both monitoring occasions may be associated with the same SS-set/CORESET as shown.
  • TRP TCP
  • both monitoring occasions may be associated with the same SS-set/CORESET as shown.
  • the flexibility of distributing BD/CCE candidates across the two TPRs are naturally limited with the current signaling framework.
  • the embodiment of Fig. 4 consumes less UE resources in terms of CORESETs and SS-sets.
  • FIG. 5 shows an intra-CORESET approach for PDCCH based on SS sets, where different SS sets of a same CORESET are associated with different TCI states.
  • Fig. 5 shows a set 500 of two SS-sets 502 and 504, corresponding respectively to SS-1 and SS-2.
  • SS-1 corresponds to TRP1
  • SS-2 corresponds to TRP2.
  • Each SS set includes 8 PDCCH candidates at AL2 and 8 PDCCH candidates at AL4.
  • SS-1 and SS-2 have a same number of CCEs corresponding to candidates.
  • selection diversity can be supported, but is limited to the same CORESET (compared to the case of Inter-CORESET where there is no such limitation).
  • soft combining can be supported if SS-1 and SS-2 are non-overlapping.
  • a physically overlapping BD candidate as shown in Fig. 5 by the double-headed arrow, Otherwise BD candidate pairs with same AL will overlap in terms of physical resource and these BD candidates will be unavailable for PDCCH scheduling (especially larger ALs).
  • Some embodiments herein include support for one or more of the following PDCCH candidate repetition types:
  • a UE configured to expect DCI repetition from any of the above combinations.
  • a UE to which one or more of the following is indicated: SS sets, MOs, slots, DCIs, or BD candidates for repetition
  • MOs are implicit (same MOs), slots are implicit (same slot), DCIs are implicit (only common DCIs across SS sets), ALs are implicit (only common Als), or BD candidates are implicit (only common BD candidates).
  • BD candidate m of SS-1/AL4 can be combined with BD candidate m of SS-2/AL4 to create either joint coded AL8 (ordered by TRP-0 then TRP-1) or repetition of AL4.
  • BD candidate m of SS-1/AL4 can be combined with all BD candidates of SS-2/AL4 to create either joint coded AL8 (ordered by TRP-0 then TRP-1) or repetition of AL4 [0055] II.
  • Some embodiments are related to the 5G NR Release 17 MIMO enhancements work item on Enhancements on PDCCH. Some embodiments include methods to determine PDSCH starting and PDSCH processing time due to PDCCH repetitions.
  • PDSCH starting time ambiguity and PDSCH processing time ambiguity may be resolved by embodiments by way of indicating a repetition number using the DCI.
  • Some embodiments herein enable the network to allocate PDCCH repetitions from different TRPs (e.g., different TCI states) building on the signaling framework that is existing in Rel- 15 and Rel-16.
  • Fig. 6 shows a set of slots 602, 604 and 606, corresponding respectively to cases 1, 2 and 3 as will be explained in further detail below.
  • Rel-16 URLLC has introduced a (RRC configurable) PDSCH start reference changed to scheduling PDCCH starting symbol.
  • the different network operations in the latter context correspond to cases 1, 2 and 3 as follows: a. Case 1.
  • the network sends DCI only in PDCCH-1 (AL16), where, clearly, the PDSCH start reference should be PDCCH-1; b.
  • Case 2 The network sends DCI only in PDCCH-2 (AL16), where, clearly PDSCH reference should be PDCCH-2; and c.
  • Case 3 The network sends DCI in PDCCH-1 and PDCCH-2 (AL8 for each).
  • the UE may decode DCI from either PDCCH-1 or PDCCH-2 in which case PDSCH start reference will be ambiguous
  • the Rel-15 start and length indicator value (SLIV) reference is the slot boundary. Therefore, if duplicate DCI is received in PDCCH-1 and PDCCH-2 there is no ambiguity in the PDSCH start reference.
  • Rel-16 URLLC has introduced a (RRC configurable) PDSCH start reference that corresponds to the scheduling PDCCH starting symbol, Rel-16 introduces an ambiguity in terms of the PDSCH start time for duplicate DCIs.
  • the DCI field can include a "repetition" field that is set to 1 for Case 1 and 2 and set to 2 for Case 3.
  • a same principle may be used to associate PDSCH (even in the case of the Rel-15 SLIV reference noted above) to a unique monitoring occasion for PDSCH.
  • a UE is not expected to receive multiple repetitions of DCI 1_2 (or multiple repetitions with different starting symbols for monitoring occasions) when configured with a SLIV reference as a starting symbol of a PDSCH monitoring occasion.
  • the UE may be provided with indications of certain combinations of SS-sets, MOs within a slot, MO across slot, and/or candidates within each ALs that can be potentially used for repetition of DCI 1_2 where repetition is to take place. Examples of indications of possible 2 PDCCH repetitions for DCI may include the following combinations:
  • Combination -1 ⁇ SS set#l, MO#1 ⁇ — ⁇ SS set#2, MO#1 ⁇ is a repetition pair for a 2 TRP repetition;
  • a UE may use a fixed rule based on the above indications to determine monitoring occasions for PDSCH; for example, the UE's fixed rule may include a latest monitoring occasion in a slot within an indicated combination. The combination may be selected based on BD.
  • the DCI may indicate whether DCI repetition is used and if used, which type of repetition is used, for example in a repetition field, where a value of:
  • SLIV reference according to fixed rule is to be used based on an indicated combination corresponding to DCI repetitions.
  • the fixed rule may dictate using the latest MO within combination-1 to monitor for PDSCH;
  • SLIV reference according to fixed rule indicates repetition a SLIV reference according to fixed rule is to be used based on an indicated combination corresponding to DCI repetitions.
  • the fixed rule may dictate using the latest MO within combination-2 to monitor for PDSCH;
  • One embodiment may include using the principles outlined above to associate PDSCH (even with Rel-15 SLIV reference) to a unique monitoring occasion for HARQ-ACK bit positions in a dynamic codebook.
  • One embodiment may include using the principles outlined above to resolve processing time issues as suggested in Figs. 7 and 8.
  • Fig. 7 shows a set 700 of two consecutive slots 702 and 704 with cross-slot repetition of DCI. For example, there could be 4 repetitions of DCI with two in each slot, or 3 repetitions of DCI with one in slot 702 and two in slot 704, or any other configuration for repetitions. If there is no overlap between any of the repeated DCIs and the associated PDSCH monitoring occasion, there is no delay, as shown in the example of Fig. 7.
  • Fig. 8 shows an example of PDSCH processing time ambiguity due to PDCCH repetition.
  • DCI/PDCCH repetition may result in overlapping symbols for a DCI repetition and a PDSCH monitoring occasion, for example in the case of cross-slot repetition as shown in the context of Fig. 7.
  • Fig. 8 shows a slot 800 including repeating DCIs in PDCCH-1 and PDCCH-2, where a symbol of PDCCH-2 overlaps with a symbol of the PDSCH.
  • processing time of the PDSCH is delayed by the overlapping symbols, which, in the shown case, is the duration of the PDCCH-2.
  • a PDSCH were scheduled by PDCCH-1 then processing time would not be delayed
  • the network operate in any of the following ways:
  • a UE may be able to decode DCI from PDCCH-1 in both cases. However, this difference in NW operation may be indicated to the UE in order to not delay PDSCH processing time until the end of PDCCH-2 if the second option is used.
  • a solution according to one embodiment proposes including a "repetition" field as follow:
  • FIGs. 9-11 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • Fig. 9 illustrates a network 900 in accordance with various embodiments.
  • the network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 900 may include a UE 902, which may include any mobile or non-mobile computing device designed to communicate with a RAN 904 via an over-the-air connection.
  • the UE 902 may be communicatively coupled with the RAN 904 by a Uu interface.
  • the UE 902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 900 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 902 may additionally communicate with an AP 906 via an over-the-air connection.
  • the AP 906 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 904.
  • the connection between the UE 902 and the AP 906 may be consistent with any IEEE 902.11 protocol, wherein the AP 906 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 902, RAN 904, and AP 906 may utilize cel lu la r- WLAN aggregation (for example, LWA/LWIP).
  • Cellular-WLAN aggregation may involve the UE 902 being configured by the RAN 904 to utilize both cellular radio resources and WLAN resources.
  • the RAN 904 may include one or more access nodes, for example, AN 908.
  • AN 908 may terminate air-interface protocols for the UE 902 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 908 may enable data/voice connectivity between CN 920 and the UE 902.
  • the AN 908 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 908 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 908 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 904 may be coupled with one another via an X2 interface (if the RAN 904 is an LTE RAN) or an Xn interface (if the RAN 904 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 904 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 902 with an air interface for network access.
  • the UE 902 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 904.
  • the UE 902 and RAN 904 may use carrier aggregation to allow the UE 902 to connect with a plurality of component carriers, each corresponding to a Pcell or See II .
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 904 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCel Is/Scel Is.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 902 or AN 908 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 904 may be an LTE RAN 910 with eNBs, for example, eNB 912.
  • the LTE RAN 910 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 904 may be an NG-RAN 914 with gNBs, for example, gNB 916, or ng-eNBs, for example, ng-eNB 918.
  • the gNB 916 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 916 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 918 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 916 and the ng-eNB 918 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 914 and a UPF 948 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN914 and an AMF 944 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 914 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 902 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 902, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 902 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 902 and in some cases at the gNB 916.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 904 is communicatively coupled to CN 920 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 902).
  • the components of the CN 920 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 920 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 920 may be referred to as a network slice, and a logical instantiation of a portion of the CN 920 may be referred to as a network sub-slice.
  • the CN 920 may be an LTE CN 922, which may also be referred to as an EPC.
  • the LTE CN 922 may include MME 924, SGW 926, SGSN 928, HSS 930, PGW 932, and PCRF 934 coupled with one another over interfaces (or "reference points") as shown.
  • Functions of the elements of the LTE CN 922 may be briefly introduced as follows.
  • the MME 924 may implement mobility management functions to track a current location of the UE 902 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 926 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 922.
  • the SGW 926 may be a local mobility anchor point for inter- RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 928 may track a location of the UE 902 and perform security functions and access control. In addition, the SGSN 928 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 924; MME selection for handovers; etc.
  • the S3 reference point between the MME 924 and the SGSN 928 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 930 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the HSS 930 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 930 and the MME 924 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 920.
  • the PGW 932 may terminate an SGi interface toward a data network (DN) 936 that may include an application/content server 938.
  • the PGW 932 may route data packets between the LTE CN 922 and the data network 936.
  • the PGW 932 may be coupled with the SGW 926 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 932 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 932 and the data network YX 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 932 may be coupled with a PCRF 934 via a Gx reference point.
  • the PCRF 934 is the policy and charging control element of the LTE CN 922.
  • the PCRF 934 may be communicatively coupled to the app/content server 938 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 932 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCL
  • the CN 920 may be a 5GC 940.
  • the 5GC 940 may include an AUSF 942, AMF 944, SMF 946, UPF 948, NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, and AF 960 coupled with one another over interfaces (or "reference points") as shown.
  • Functions of the elements of the 5GC 940 may be briefly introduced as follows.
  • the AUSF 942 may store data for authentication of UE 902 and handle authentication- related functionality.
  • the AUSF 942 may facilitate a common authentication framework for various access types.
  • the AUSF 942 may exhibit an Nausf service-based interface.
  • the AMF 944 may allow other functions of the 5GC 940 to communicate with the UE 902 and the RAN 904 and to subscribe to notifications about mobility events with respect to the UE 902.
  • the AMF 944 may be responsible for registration management (for example, for registering UE 902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 944 may provide transport for SM messages between the UE 902 and the SMF 946, and act as a transparent proxy for routing SM messages.
  • AMF 944 may also provide transport for SMS messages between UE 902 and an SMSF.
  • AMF 944 may interact with the AUSF 942 and the UE 902 to perform various security anchor and context management functions.
  • AMF 944 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 904 and the AMF 944; and the AMF 944 may be a termination point of NAS (N 1) signaling, and perform NAS ciphering and integrity protection.
  • AMF 944 may also support NAS signaling with the UE 902 over an N3 IWF interface.
  • the SMF 946 may be responsible for SM (for example, session establishment, tunnel management between UPF 948 and AN 908); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 948 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 944 over N2 to AN 908; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 902 and the data network 936.
  • the UPF 948 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 936, and a branching point to support multi-homed PDU session.
  • the UPF 948 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to- QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 948 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 950 may select a set of network slice instances serving the UE 902.
  • the NSSF 950 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 950 may also determine the AMF set to be used to serve the UE 902, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 954.
  • the selection of a set of network slice instances for the UE 902 may be triggered by the AMF 944 with which the UE 902 is registered by interacting with the NSSF 950, which may lead to a change of AMF.
  • the NSSF 950 may interact with the AMF 944 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 950 may exhibit an Nnssf service-based interface.
  • the NEF 952 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 960), edge computing or fog computing systems, etc.
  • the NEF 952 may authenticate, authorize, or throttle the AFs.
  • NEF 952 may also translate information exchanged with the AF 960 and information exchanged with internal network functions. For example, the NEF 952 may translate between an AF-Service-ldentifier and an internal 5GC information.
  • NEF 952 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 952 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 952 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 952 may exhibit an Nnef servicebased interface.
  • the NRF 954 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 954 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 954 may exhibit the Nnrf service-based interface.
  • the PCF 956 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 956 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 958.
  • the PCF 956 exhibit an Npcf service-based interface.
  • the UDM 958 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 902. For example, subscription data may be communicated via an N8 reference point between the UDM 958 and the AMF 944.
  • the UDM 958 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 958 and the PCF 956, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 902) for the NEF 952.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 958, PCF 956, and NEF 952 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 958 may exhibit the Nudm service-based interface.
  • the AF 960 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 940 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 902 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 940 may select a UPF 948 close to the UE 902 and execute traffic steering from the UPF 948 to data network 936 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 960. In this way, the AF 960 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 960 to interact directly with relevant NFs. Additionally, the AF 960 may exhibit an Naf service-based interface.
  • the data network 936 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 938.
  • Fig. 10 schematically illustrates a wireless network 1000 in accordance with various embodiments.
  • the wireless network 1000 may include a UE 1002 in wireless communication with an AN 1004.
  • the UE 1002 and AN 1004 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 1002 may be communicatively coupled with the AN 1004 via connection 1006.
  • the connection 1006 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 1002 may include a host platform 1008 coupled with a modem platform 1010.
  • the host platform 1008 may include application processing circuitry 1012, which may be coupled with protocol processing circuitry 1014 of the modem platform 1010.
  • the application processing circuitry 1012 may run various applications for the UE 1002 that source/sink application data.
  • the application processing circuitry 1012 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 1014 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1006.
  • the layer operations implemented by the protocol processing circuitry 1014 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 1010 may further include digital baseband circuitry 1016 that may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuitry 1014 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 1010 may further include transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, and RF front end (RFFE) 1024, which may include or connect to one or more antenna panels 1026.
  • the transmit circuitry 1018 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 1020 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 1022 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 1024 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is time division multiplexed (TDM) or frequency division multiplexed (FDM), in mmWave or sub-6 gHz frequencies, etc.
  • TDM time division multiplexed
  • FDM frequency division multiplexed
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 1014 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 1026, RFFE 1024, RF circuitry 1022, receive circuitry 1020, digital baseband circuitry 1016, and protocol processing circuitry 1014.
  • the antenna panels 1026 may receive a transmission from the AN 1004 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1026.
  • a UE transmission may be established by and via the protocol processing circuitry 1014, digital baseband circuitry 1016, transmit circuitry 1018, RF circuitry 1022, RFFE 1024, and antenna panels 1026.
  • the transmit components of the UE 1004 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1026.
  • the AN 1004 may include a host platform 1028 coupled with a modem platform 1030.
  • the host platform 1028 may include application processing circuitry 1032 coupled with protocol processing circuitry 1034 of the modem platform 1030.
  • the modem platform may further include digital baseband circuitry 1036, transmit circuitry 1038, receive circuitry 1040, RF circuitry 1042, RFFE circuitry 1044, and antenna panels 1046.
  • the components of the AN 1004 may be similar to and substantially interchangeable with like-named components of the UE 1002.
  • the components of the AN 1008 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Fig. 11 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Fig. 11 shows a diagrammatic representation of hardware resources 1100 including one or more processors (or processor cores) 1110, one or more memory/storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry.
  • a hypervisor 1102 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1100.
  • the processors 1110 may include, for example, a processor 1112 and a processor 1114.
  • the processors 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 1120 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1120 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1130 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 or other network elements via a network 1108.
  • the communication resources 1130 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 1150 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1110 to perform any one or more of the methodologies discussed herein.
  • the instructions 1150 may reside, completely or partially, within at least one of the processors 1110 (e.g., within the processor's cache memory), the memory/storage devices 1120, or any suitable combination thereof.
  • any portion of the instructions 1150 may be transferred to the hardware resources 1100 from any combination of the peripheral devices 1104 or the databases 1106. Accordingly, the memory of processors 1110, the memory/storage devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Fig. 12 shows a process 1200 according to an embodiment.
  • the process includes encoding a message for a user equipment (UE), the message indicating a repetition count for a physical downlink control channel (PDCCH) carrying a downlink control information (DCI).
  • the process includes sending the message to communications resources of a gNB for transmission to the UE.
  • UE user equipment
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Fig. 13 shows a process 1300 according to an embodiment.
  • the process includes decoding a message from a NR Node B (gNB), the message indicating a repetition count for a physical downlink control channel (PDCCH) carrying a downlink control information (DCI).
  • the process includes determining the repetition count from the message.
  • gNB NR Node B
  • DCI downlink control information
  • Example 1 includes an apparatus of a New Radio (NR) user equipment (U E), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: decode a message from a NR Node B (gNB), the message indicating a repetition count for a physical downlink control channel (PDCCH) carrying a downlink control information (DCI); and determine the repetition count from the message.
  • NR New Radio
  • U E New Radio
  • Example 2 includes the subject matter of Example 1, the one or more processors to decode the PDDCH based on the repetition count.
  • Example 3 includes the subject matter of Example 1, wherein a repetition count of one is to indicate no repetition, and a repetition count of more than one is to indicate a number of repetitions corresponding to the repetition count.
  • Example 4 includes the subject matter of Example 1, wherein the message includes a radio resource control (RRC) message when the repetition count is more than one, and includes a DCI when the repetition count is one.
  • RRC radio resource control
  • Example 5 includes the subject matter of any one of Examples 1-4, the one or more processors to determine a starting position of a downlink communication to the UE based on the repetition count.
  • Example 6 includes the subject matter of Example 5, wherein the downlink communication is one of a physical downlink shared channel (PDSCH) or a hybrid automatic repeat request (HARQ) in dynamic codebook.
  • PDSCH physical downlink shared channel
  • HARQ hybrid automatic repeat request
  • Example 7 includes the subject matter of Example 5, the one or more processors to determine a processing time for the downlink communication based on the repetition count.
  • Example 8 includes the subject matter of Example 5, wherein the starting position corresponds to a symbol number or a slot number.
  • Example 9 includes the subject matter of Example 1, the message including an indication of a combination value corresponding to repetition information for the DCI, the repetition information including repetition information pairs, each repetition information pair including a synchronization signal set and a monitoring occasion, the pairs being different from one another, each pair corresponding to a repetition instance of the DCI.
  • Example 10 includes the subject matter of Example 9, wherein the combination value provides an indication of a number of transmission reception points (TRPs) corresponding to the repetition.
  • TRPs transmission reception points
  • Example 11 includes the subject matter of Example 9, the one or more processors to implement a fixed rule to determine a monitoring occasion for a downlink communication to the UE based on the combination value.
  • Example 12 includes the subject matter of any one of Examples 1-4, and 9-11, further including communications resources coupled to the one or more processors to communicate with the gNB.
  • Example 13 includes a method to be performed at an apparatus of a New Radio (NR) Node B (gNB), the method including: encoding a message for a user equipment (UE), the message indicating a repetition count for a physical downlink control channel (PDCCH) carrying a downlink control information (DCI); and sending the message to communications resources of the gNB for transmission to the UE.
  • NR New Radio
  • gNB New Radio Node B
  • UE user equipment
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Example 14 includes the subject matter of Example 13, wherein a repetition count of one is to indicate no repetition, and a repetition count of more than one is to indicate a number of repetitions corresponding to the repetition count.
  • Example 15 includes the subject matter of Example 13, wherein the message includes a radio resource control (RRC) message when the repetition count is more than one, and includes a DCI when the repetition count is one.
  • RRC radio resource control
  • Example 16 includes the subject matter of any one of Examples 13-15, the repetition count to correspond to a starting position of a downlink communication to the UE based on the repetition count.
  • Example 17 includes the subject matter of Example 16, wherein the downlink communication is one of a physical downlink shared channel (PDSCH) or a hybrid automatic repeat request (HARQ) in dynamic codebook.
  • PDSCH physical downlink shared channel
  • HARQ hybrid automatic repeat request
  • Example 18 includes the subject matter of Example 16, wherein the starting position corresponds to a symbol number or a slot number.
  • Example 19 includes the subject matter of Example 13, the message including an indication of a combination value corresponding to repetition information for the DCI, the repetition information including repetition information pairs, each repetition information pair including a synchronization signal set and a monitoring occasion, the pairs being different from one another, each pair corresponding to a repetition instance of the DCI.
  • Example 20 includes the subject matter of Example 19, wherein the combination value provides an indication of a number of transmission reception points (TRPs) corresponding to the repetition.
  • TRPs transmission reception points
  • Example 21 includes the subject matter of any one of Examples 13-15 and 19-20, further including communicating with the UE using the communications resources.
  • Example 22 includes an apparatus of a New Radio (NR) Node B (gNB), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: encode a message for a user equipment (UE), the message indicating a repetition count for a physical downlink control channel (PDCCH) carrying a downlink control information (DCI); and send the message to communications resources of the gNB for transmission to the UE.
  • NR New Radio
  • gNB New Radio
  • UE user equipment
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Example 23 includes the subject matter of Example 22, wherein a repetition count of one is to indicate no repetition, and a repetition count of more than one is to indicate a number of repetitions corresponding to the repetition count.
  • Example 24 includes the subject matter of Example 22, wherein the message includes a radio resource control (RRC) message when the repetition count is more than one, and includes a DCI when the repetition count is one.
  • RRC radio resource control
  • Example 25 includes the subject matter of any one of Examples 22-24, the repetition count to correspond to a starting position of a downlink communication to the UE based on the repetition count.
  • Example 26 includes the subject matter of Example 25, wherein the downlink communication is one of a physical downlink shared channel (PDSCH) or a hybrid automatic repeat request (HARQ) in dynamic codebook.
  • PDSCH physical downlink shared channel
  • HARQ hybrid automatic repeat request
  • Example 27 includes the subject matter of Example 25, wherein the starting position corresponds to a symbol number or a slot number.
  • Example 28 includes the subject matter of Example 22, the message including an indication of a combination value corresponding to repetition information for the DCI, the repetition information including repetition information pairs, each repetition information pair including a synchronization signal set and a monitoring occasion, the pairs being different from one another, each pair corresponding to a repetition instance of the DCI.
  • Example 29 includes the subject matter of Example 28, wherein the combination value provides an indication of a number of transmission reception points (TRPs) corresponding to the repetition.
  • TRPs transmission reception points
  • Example 30 includes the subject matter of any one of Examples 22-24 and 28-29, further including the communications resources coupled to the one or more processors.
  • Example 31 includes a method to be performed at an apparatus of a New Radio (NR) user equipment (UE), the method including: decoding a message from a NR Node B (gNB), the message indicating a repetition count for a physical downlink control channel (PDCCH) carrying a downlink control information (DCI); and determining the repetition count from the message.
  • NR New Radio
  • gNB NR Node B
  • DCI downlink control information
  • Example 32 includes the subject matter of Example 31, further including decode the PDDCH based on the repetition count.
  • Example 33 includes the subject matter of Example 31, wherein a repetition count of one is to indicate no repetition, and a repetition count of more than one is to indicate a number of repetitions corresponding to the repetition count.
  • Example 34 includes the subject matter of Example 31, wherein the message includes a radio resource control (RRC) message when the repetition count is more than one, and includes a DCI when the repetition count is one.
  • RRC radio resource control
  • Example 35 includes the subject matter of any one of Examples 31-34, further including determining a starting position of a downlink communication to the UE based on the repetition count.
  • Example 36 includes the subject matter of Example 35, wherein the downlink communication is one of a physical downlink shared channel (PDSCH) or a hybrid automatic repeat request (HARQ) in dynamic codebook.
  • PDSCH physical downlink shared channel
  • HARQ hybrid automatic repeat request
  • Example 37 includes the subject matter of Example 35, further including determining a processing time for the downlink communication based on the repetition count.
  • Example 38 includes the subject matter of Example 35, wherein the starting position corresponds to a symbol number or a slot number.
  • Example 39 includes the subject matter of Example 31, the message including an indication of a combination value corresponding to repetition information for the DCI, the repetition information including repetition information pairs, each repetition information pair including a synchronization signal set and a monitoring occasion, the pairs being different from one another, each pair corresponding to a repetition instance of the DCI.
  • Example 40 includes the subject matter of Example 39, wherein the combination value provides an indication of a number of transmission reception points (TRPs) corresponding to the repetition.
  • TRPs transmission reception points
  • Example 41 includes the subject matter of Example 39, further including implementing a fixed rule to determine a monitoring occasion for a downlink communication to the UE based on the combination value.
  • Example 42 includes the subject matter of any one of Examples 31-34, and 39-41, further including communicating with the gNB using communications resources of the UE.
  • Example 43 includes machine readable medium including code, which, when executed, is to cause a machine to perform the subject matter of any one of Examples 13-21 and 31-42.
  • Example 44 includes an apparatus including means to perform the subject matter of any one of Examples 13-21 and 31-42.
  • Example 1A may include the method of PDCCH repetitions from multiple TRPs
  • Example 2A may include the method of Example 1A or some other example herein, where one or more of following repetition types is supported: Inter CORESET for repetition across TRPs; Intra CORESET with repetition across SS sets; Intra CORESET with repetition across MOs.
  • Example 3A may include the method of Example 2A or some other example herein, where UE is configured that it can expect DCI repetition from any of the above combinations
  • Example 4A may include the method of Example 2A or some other example herein, where MOs are implicit (same MOs), slots are implicit (Same slot), DCIs are implicit (only common DCIs across SS sets), ALs are implicit (only common Als), candidates are implicit (only common candidates) across two PDCCHs that are to be combined.
  • Example 5A may include the method of Example 2A or some other example herein, where UE is indicated SS sets, MOs, slots, DCIs, candidates for repetition.
  • Example 6A may include the method of Example 2A or some other example herein, where for soft-combining, candidate m of SS-1/AL4 can be combined with candidate m of SS-2/AL4 to create either joint coded AL8 (ordered by TRP-0 then TRP-1) or repetition of AL4.
  • Example 7A may include the method of Example 2A or some other example herein, where for soft-combining, candidate m of SS-1/AL4 can be combined with all candidates of SS- 2/AL4 to create either joint coded AL8 (ordered by TRP-0 then TRP-1) or repetition of AL4.
  • Example 8A may include a method comprising: receiving configuration information for a CORESET; and monitoring for a DCI with repetitions based on the CORESET in one or more of the following repetition modes: Inter CORESET for repetition across TRPs; Intra CORESET with repetition across SS sets; and/or Intra CORESET with repetition across MOs.
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-8, or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-8, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-8, or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of examples 1-8, or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples 1-8, or portions or parts thereof.
  • Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.
  • Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Appareil d'équipement utilisateur (UE), système, procédé et support lisible par machine. L'appareil comprend un ou plusieurs processeurs pour décoder un message provenant d'un nœud B de prochaine génération (gNB) de nouvelle radio (NR), le message indiquant un nombre de répétitions pour un canal de commande de liaison descendante physique (PDCCH) portant des informations de commande de liaison descendante (DCI), et déterminer le nombre de répétitions à partir du message.
PCT/US2021/045131 2020-08-07 2021-08-07 Configuration de répétition de canal de commande de liaison descendante physique et configuration de démarrage de canal partagé de liaison descendante physique et indication de temps de traitement WO2022032212A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202180049031.4A CN115804056A (zh) 2020-08-07 2021-08-07 物理下行链路控制信道重复配置和物理下行链路共享信道起始配置及处理时间指示

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202063062877P 2020-08-07 2020-08-07
US202063063089P 2020-08-07 2020-08-07
US63/062,877 2020-08-07
US63/063,089 2020-08-07

Publications (1)

Publication Number Publication Date
WO2022032212A1 true WO2022032212A1 (fr) 2022-02-10

Family

ID=80118558

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/045131 WO2022032212A1 (fr) 2020-08-07 2021-08-07 Configuration de répétition de canal de commande de liaison descendante physique et configuration de démarrage de canal partagé de liaison descendante physique et indication de temps de traitement

Country Status (2)

Country Link
CN (1) CN115804056A (fr)
WO (1) WO2022032212A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170289899A1 (en) * 2016-04-04 2017-10-05 Lg Electronics Inc. Method and user equipment for receiving downlink control channel, and method and base station for transmitting downlink control channel
US20190230697A1 (en) * 2018-01-22 2019-07-25 Qualcomm Incorporated Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc)
WO2019183127A1 (fr) * 2018-03-22 2019-09-26 Qualcomm Incorporated Augmentation de la fiabilité pendant des transferts intercellulaires à multiples connectivités
US20200008235A1 (en) * 2018-06-29 2020-01-02 Qualcomm Incorporated Pdcch with repetition
WO2020013926A1 (fr) * 2018-07-12 2020-01-16 Qualcomm Incorporated Règle de détermination de créneau programmé de pdsch à répétition de pdcch

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170289899A1 (en) * 2016-04-04 2017-10-05 Lg Electronics Inc. Method and user equipment for receiving downlink control channel, and method and base station for transmitting downlink control channel
US20190230697A1 (en) * 2018-01-22 2019-07-25 Qualcomm Incorporated Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc)
WO2019183127A1 (fr) * 2018-03-22 2019-09-26 Qualcomm Incorporated Augmentation de la fiabilité pendant des transferts intercellulaires à multiples connectivités
US20200008235A1 (en) * 2018-06-29 2020-01-02 Qualcomm Incorporated Pdcch with repetition
WO2020013926A1 (fr) * 2018-07-12 2020-01-16 Qualcomm Incorporated Règle de détermination de créneau programmé de pdsch à répétition de pdcch

Also Published As

Publication number Publication date
CN115804056A (zh) 2023-03-14

Similar Documents

Publication Publication Date Title
US11871436B2 (en) Apparatus for UE measurement delay and granularity for new radio positioning measurement
US11792814B2 (en) Techniques for cancelation of one or more uplink transmissions from a user equipment
EP4193794A1 (fr) Mécanismes pour activation/désactivation de groupe de cellules secondaires (scg) efficaces et mécanismes pour modification ou ajout de pscell conditionnelle
WO2022155108A1 (fr) Saut de fréquence inter-intervalles amélioré permettant une couverture de liaison montante dans des systèmes 5g
CN113766665A (zh) 用于多trp场景中基于码本的ul传输的装置和方法
US20230246689A1 (en) Support of simplified multiple input multiple output features for reduced capability user equipment in new radio systems
US20210258065A1 (en) Enhanced beam management for 5g systems
CN113766666A (zh) 用于多trp场景中基于非码本的ul传输的装置和方法
CN113285790A (zh) 反馈资源配置的方法
US11979894B2 (en) Soft resource availability indication for integrated access and backhaul (IAB) operation in paired spectrum
WO2022011527A1 (fr) Configuration et transmission de srs en multi-dci multi-trp et agrégation de porteuses
CN115694700A (zh) 用在无线通信系统中的装置
WO2022154962A1 (fr) Atténuation de chevauchements de domaine temporel impliquant un bloc de transport sur des transmissions à fentes multiples
WO2022032212A1 (fr) Configuration de répétition de canal de commande de liaison descendante physique et configuration de démarrage de canal partagé de liaison descendante physique et indication de temps de traitement
US11751228B2 (en) Methods and apparatuses for uplink spatial relation info switch
US20230164670A1 (en) Reduced complexity channel coding for reduced capability new radio user equipment
EP4239479A1 (fr) Orchestration de services informatiques et de ressources pour des systèmes de prochaine génération
EP4207666A1 (fr) Configuration d'occasions de surveillance de pdcch pour capacité de surveillance de pdcch à intervalles multiples
US20240187172A1 (en) Single trp and multiple trp dynamic switching for single dci based pusch transmissions
EP4193676A1 (fr) Rapport de défaillance de transfert conditionnel dans la minimisation des tests de conduite (mdt)
WO2023154921A1 (fr) Réception d'une commande et de données de service de multidiffusion et de diffusion (mbs) de nouvelle radio (nr) dans une liaison descendante
WO2022155505A1 (fr) Techniques de déclenchement d'un signal de référence de sondage (srs) apériodique et flexible
WO2022032158A1 (fr) Mécanismes pour la répétition à trp multiple de pusch et de pucch
WO2023033813A1 (fr) Transmission de csi-rs (signal de référence d'informations d'état de canal) basée sur un groupe
CN114499802A (zh) 用在用户设备中的装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21852417

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21852417

Country of ref document: EP

Kind code of ref document: A1