DE102021103592A1 - SYSTEMS, PROCEDURES AND EQUIPMENT FOR TRANSMIT AND RECEIVE CHANNEL (PDCCH) - Google Patents

Abstract

A device for a new radio (NR) user equipment (UE) can have a circuit which is set up to receive configuration information for a control resource group (CORESET) which contains a plurality of CORESETs, a transmission of the same physical downlink control channel ( PDCCH) to be received via one or more CORESETs within a configured CORESET group; and decode the PDCCH according to the configurations.

Description

Related registration (s)

This application claims priority from U.S. Patent Application No. 62 / 978,171 , filed February 18, 2020, and further claims priority to U.S. Patent Application No. 62 / 984,091, filed March 2, 2020, which is incorporated herein by reference in its entirety.

Technical area

The present disclosure relates to radio communication devices and methods therefor.

background

Various aspects of the present disclosure may generally relate to the field of wireless communications. New Radio (NR) supports the physical control channel (PDCCH), which transmits the planning decision for both DL and UL through DCI.

In particular according to the “Third Generation Partnership Project; Technical Specification Group Radio Access Network; NO; Physical Channels and Modulation (Issue 16) ”(hereinafter“ TS 38.211 ”), a physical downlink control channel (PDCCH) consists of one or more control channel elements (CCEs), as specified in the following table. Table: Supported PDCCH aggregation levels. Aggregation level Number of CCEs 1 1 2 2 4th 4th 8th 8th 16 16

Ressourcenblöcken im Frequenzbereich und $N_{\text{symb}}^{\text{CORESET}}$

∈ {1,2,3} Symbole im Zeitbereich. Ein Steuerungskanal-Element besteht aus 6 Ressource-Element-Gruppen (REGs), wobei eine Ressource-Element-Gruppe einem Ressourcenblock während eines OFDM-Symbols entspricht. Ressource-Element-Gruppen innerhalb einer Steuerungseinheit werden zeitlich aufsteigend nummeriert, beginnend mit 0 für das erste OFDM-Symbol und dem Ressourcenblock mit der niedrigsten Nummer in der Steuerungseinheit.Furthermore, according to TS 38.211, there is a control resource unit (KERNSATZ) $N_{\text{RB}}^{\text{CORESET}}$

Resource blocks in the frequency domain and $N_{\text{symb}}^{\text{CORESET}}$

∈ {1,2,3} symbols in the time domain. A control channel element consists of 6 resource element groups (REGs), with a resource element group corresponding to a resource block during an OFDM symbol. Resource element groups within a control unit are numbered in ascending order, starting with 0 for the first OFDM symbol and the resource block with the lowest number in the control unit.

• - REG-Bündel i ist definiert als REGs {iL,iL+1,...,iL+L-1} wobei L die REG-Bündelgröße ist, i = 0,1, ..., $N_{REG}^{\text{CORESET}}/L-\mathrm{1,}$
  
  und $N_{\text{REG}}^{\text{CORESET}}=N_{\text{RB}}^{\text{CORESET}}{N}_{\text{symb}}^{\text{CORESET}}$
  
  die Anzahl von REGs in dem KERNSATZ ist.
• - CCE j besteht aus REG-Bündeln {f(6j/L),f(6j/L + 1),...,f(6j/L + 6/L-1)} wobei /(.) ein Interleaver ist.

According to TS 38.211, a UE can be set up with several control resource sets. Each control resource set is associated with only one CCE-to-REG mapping. TS 38.211 also specifies that the CCE-to-REG mapping for a control resource set can be interleaved or non-interleaved and is described by REG bundles:

• - REG bundle i is defined as REGs {iL, iL + 1, ..., iL + L-1} where L is the REG bundle size, i = 0,1, ..., $N_{\mathrm{R.}\mathrm{E.}G}^{\text{CORESET}}/\mathrm{L.}-\mathrm{1,}$
  
  and $N_{\text{REG}}^{\text{CORESET}}=N_{\text{RB}}^{\text{CORESET}}{N}_{\text{symb}}^{\text{CORESET}}$
  
  is the number of REGs in the CORE SET.
• - CCE j consists of REG bundles {f (6j / L), f (6j / L + 1), ..., f (6j / L + 6 / L-1)} where / (.) Is an interleaver .

For a non-nested CCE-to-REG mapping, L = 6 and f (x) = x.

= 1 und L ∈ $N_{\text{symb}}^{\text{CORESET}}$

6} für $N_{\text{symb}}^{\text{CORESET}}$

∈ {2,3}. Der Interleaver ist definiert durch $$\begin{array}{l}f\left(x\right)=\left(rC+c+n_{\text{shift}}\right)\text{mod}\left(N_{\text{REG}}^{\text{CORESET}}/L\right)\\ x=cR+r\\ r=\mathrm{0,1,}\dots ,R-1\\ c=\mathrm{0,1,}\dots ,C-1\\ C=N_{\text{REG}}^{\text{CORESET}}/\left(LR\right)\end{array}$$

wobei R ∈ {2,3,6}.For a nested CCE-to-REG mapping, L ∈ {2,6} for $N_{\text{symb}}^{\text{CORESET}}$

= 1 and L ∈ $N_{\text{symb}}^{\text{CORESET}}$

6} for $N_{\text{symb}}^{\text{CORESET}}$

∈ {2,3}. The interleaver is defined by $$\begin{array}{l}f\left(x\right)=\left(r\mathrm{C.}+c+n_{\text{shift}}\right)\text{mod}\left(N_{\text{REG}}^{\text{CORESET}}/\mathrm{L.}\right)\\ x=c\mathrm{R.}+r\\ r=\mathrm{0.1,}...,\mathrm{R.}-1\\ c=\mathrm{0.1,}...,\mathrm{C.}-1\\ \mathrm{C.}=N_{\text{REG}}^{\text{CORESET}}/\left(\mathrm{L.}\mathrm{R.}\right)\end{array}$$

where R ∈ {2,3,6}.

• - $N_{\text{RB}}^{\text{CORESET}}$
  
  ist gegeben durch den Höhere-Schicht-Parameter frequencyDomainResources;
• - $N_{\text{symb}}^{\text{CORESET}}$
  
  ist gegeben durch den Höhere-Schicht-Parameter duration, wobei $N_{\text{symb}}^{\text{CORESET}}$
  
  = 3 nur unterstützt wird, wenn der Höhere-Schicht-Parameter dmrs-TypeA-Position gleich 3 ist;
• - Verschachtelt- oder Nicht-Verschachtelt-Abbildung ist gegeben durch den Höhere-Schicht-Parameter cce-REG-MappingType;
• - L ist gleich 6 für Nicht-Verschachtelt-Abbildung und ist gegeben durch den Höhere-Schicht-Parameter reg-BundleSize for interleaved mapping;
• - R ist gegeben durch den Höhere-Schicht-Parameter interleaverSize;
• - n_shift ∈ {0,1,... ,274} ist gegeben durch den Höhere-Schicht-Parameter shfitInde, wenn vorgesehen, sonst n_shift = $N_{\text{ID}}^{\text{cell}};$
  
• - für Verschachtelt- als auch Nicht-Verschachtelt-Abbildung kann das UE annehmen,
  • - dass innerhalb eines REG-Bündels die gleiche Vorcodierung verwendet wird, wenn der Höhere-Schicht-Parameter precoderGranularity gleich ist sameAsREG-bundle;
  • - dass die gleiche Vorcodierung in allen Ressourc-Enelement-Gruppen innerhalb des Satzes von zusammenhängenden Ressourcenblöcken im CORESET verwendet wird und dass keine Ressourcenelemente im CORESET mit einem SSB- oder LTE-Zellen-spezifischen Referenzsignal überlappen, wie durch den Höhere-Schicht-Parameter Ite-CRS-ToMatchAround oder additionalLIE-CRS-ToMatchAroundList angegeben, wenn der Höhere-Schicht-Parameter precoderGranularity gleich allContiguousRBs ist.

Furthermore, according to TS 38.211, the UE is not expected to handle configurations which result in the quantity C being not an integer. For a CORESET that is set up with the ControlResourceSet IE:

• - $N_{\text{RB}}^{\text{CORESET}}$
  
  is given by the higher-layer parameter frequencyDomainResources;
• - $N_{\text{symb}}^{\text{CORESET}}$
  
  is given by the higher-layer parameter duration, where $N_{\text{symb}}^{\text{CORESET}}$
  
  = 3 is only supported if the higher-layer parameter dmrs-TypeA-Position is equal to 3;
• - Interleaved or non-interleaved mapping is given by the higher-layer parameter cce-REG-MappingType;
• - L is equal to 6 for non-interleaved mapping and is given by the higher-layer parameter reg-BundleSize for interleaved mapping;
• - R is given by the higher-layer parameter interleaverSize;
• - n _shift ∈ {0,1, ..., 274} is given by the higher-layer parameter shfitInde, if provided, otherwise n _shift = $N_{\text{ID}}^{\text{cell}};$
  
• - for nested as well as non-nested mapping, the UE can assume
  • - that the same precoding is used within a REG bundle if the higher-layer parameter precoderGranularity is equal to sameAsREG-bundle;
  • - that the same precoding is used in all resource en-element groups within the set of contiguous resource blocks in the CORESET and that no resource elements in the CORESET overlap with an SSB or LTE cell-specific reference signal, as is the case with the higher-layer parameter Ite -CRS-ToMatchAround or additionalLIE-CRS-ToMatchAroundList specified if the higher-layer parameter precoderGranularity is equal to allContiguousRBs.

• - $N_{\text{RB}}^{\text{CORESET}}$
  
  und $N_{\text{symb}}^{\text{CORESET}}$
  
  sind definiert durch Klausel 13 von [5, TS 38.213];
• - das UE kann Verschachtelt-Abbildung annehmen
• - L = 6;
• - R = 2;
• - n_shift = $N_{\text{ID}}^{\text{cell}};$
  
• - das UE kann ein normales zyklisches Präfix annehmen, wenn CORESET 0 ist konfiguriert durch MIB oder SIB1;
• - das UE kann annehmen, dass die gleiche Vorcodierung verwendet wird innerhalb eines REG-Bündels.

For CORESET 0 configured by the ControlResourceSetZero IE:

• - $N_{\text{RB}}^{\text{CORESET}}$
  
  and $N_{\text{symb}}^{\text{CORESET}}$
  
  are defined by clause 13 of [5, TS 38.213];
• the UE can accept interleaved mapping
• - L = 6;
• - R = 2;
• - n _shift = $N_{\text{ID}}^{\text{cell}};$
  
• the UE can adopt a normal cyclic prefix if CORESET 0 is configured by MIB or SIB1;
• - The UE can assume that the same precoding is used within a REG bundle.

That means, as shown above, PDCCH in Release 16 NR only supports fixed CCE-to-REG interleaving. In addition, precoding bundling is only supported via PRBs in the frequency domain.

Figure list

• 1 ein Netzwerk gemäß verschiedenen Aspekten der vorliegenden Offenbarung zeigt.
• 2 schematisch ein Drahtlos-Netzwerk gemäß verschiedenen Aspekten der vorliegenden Offenbarung zeigt.
• 3 ein Blockdiagramm ist zur Darstellung von Hardwareressourcen gemäß Aspekten der vorliegenden Offenbarung.
• 4 ein Diagramm zeigt, das eine CORESET-Gruppe gemäß verschiedenen Aspekten der vorliegenden Offenbarung aufweist.
• 5 einen beispielhaften Prozess zeigt gemäß verschiedenen Aspekten der vorliegenden Offenbarung.
• 6 ein beispielhaftes Verfahren zeigt gemäß verschiedenen Aspekten der vorliegenden Offenbarung.
• 7 eine Darstellung der Zuordnung von CCEs zu PDCCH-Kandidaten mit unterschiedlichen Aggregationsstufen ist.
• 8 eine Darstellung der Zuordnung von CCEs zu TCI-Zuständen für verschiedene Aggregationsstufen ist.

In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis generally on illustrating the example principles of the disclosure. In the following description, various aspects of the disclosure are described with reference to the following drawings, in which:

• 1 Figure 8 shows a network in accordance with various aspects of the present disclosure.
• 2 schematically shows a wireless network according to various aspects of the present disclosure.
• 3 FIG. 13 is a block diagram illustrating hardware resources in accordance with aspects of the present disclosure.
• 4th Figure 12 shows a diagram comprising a CORESET group in accordance with various aspects of the present disclosure.
• 5 FIG. 10 shows an exemplary process in accordance with various aspects of the present disclosure.
• 6th shows an exemplary method in accordance with various aspects of the present disclosure.
• 7th is a representation of the assignment of CCEs to PDCCH candidates with different levels of aggregation.
• 8th is an illustration of the assignment of CCEs to TCI states for different aggregation levels.

description

The following detailed description refers to the accompanying drawings, which show, for purposes of illustration, exemplary details and aspects in which aspects of the present disclosure can be practiced.

1-3 illustrate various systems, devices, and components in which aspects of the disclosed embodiments can be implemented.

1 illustrates a network 100 according to various embodiments. The network 100 can be operated in a way that corresponds to the technical specifications of the 3rd Generation Partnership Project (3GPP) for Long-Term Evolution (LTE) or Fifth Generation / New Radio (5G / NR) systems. the However, exemplary embodiments are not limited in this regard and the described embodiments can also apply to other networks that benefit from the principles described here, such as future 3GPP systems or the like.

The network 100 can a UE 102 which may include any mobile or non-mobile computing device designed to be connected to a radio access network (RAN) 104 communicate via an over-the-air connection. The user device (UE) 102 a smartphone, a tablet computer, a portable computer device, a desktop computer, a laptop computer, an infotainment device in the vehicle, an entertainment device in the vehicle, an instrument cluster, a head-up display device, an onboard diagnostic device, be a dashtop mobile device, a mobile data terminal, but is not limited to, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control unit, engine management system, networked device, machine-type communication device, machine-to-machine - (M2M) or device-to-device (D2D) device, Internet-of-Things (IoT) device, etc.

In some embodiments, the network 100 have a plurality of UEs that are directly connected to one another via a sidelink interface. The UEs can be M2M / D2D devices that communicate via physical sidelink channels, such as, but not limited to, Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Downlink Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control (PSCCH), Physical Sidelink Feedback Channel (PSFCH), etc.

In some embodiments, the UE 102 additionally with an access point (AP) 106 communicate over an over-the-air connection. The AP 106 can manage a wireless local area network (WLAN) connection, which can serve to take part / all of the network traffic from the RAN 104 to relieve. The connection between the UE 102 and the AP 106 can conform to any IEEE 802.11 protocol, with the AP 106 could be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE 102 , the RAN 104 and the AP 106 use a cellular WLAN aggregation (e.g. LTE-WLAN-Aggregation (LWA) / LTE / WLAN Radio Level Integration with IPsec Tunnel (LWIP)). With cellular WLAN aggregation, the UE 102 through the RAN 104 Be set up to use both cellular and WiFi resources.

The RAN 104 can have one or more access nodes, e.g. the access network (AN) 108 . ON 108 can use air interface protocols for the UE 102 terminate by using access layer protocols including radio resource control (RRC), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and layer 1 (L1) - Provides logs. In this way, the AN 108 a data / voice connection between the CN 120 and the UE 102 make possible. According to some embodiments, the AN 108 be implemented in a discrete device or as one or more software units running on server computers, for example as part of a virtual network that can be referred to as a Cloud RAN (CRAN) or a virtual baseband unit pool. The AN 108 Can be used as a base station (BS), next generation NodeB (gNB), RAN node, evolved NodeB (eNB), ng-eNB, NodeB, Road Side Unit (RSU), transmission / reception point, Transmission Reception Point (TRxP, TRP) , etc. are designated. The AN 108 may be a macro cell base station or a low power base station to provide femtocells, picocells or similar cells that have smaller coverage areas, lower user capacity or higher bandwidth compared to macro cells.

In embodiments where the RAN 104 has a plurality of ANs, these can be accessed via an X2 interface (if the RAN 104 is an LTE-RAN) or an Xn interface (if the RAN 104 a 5G-RAN) must be coupled to one another. Via the X2 / Xn interfaces, which in some embodiments can be divided into control / user plane interfaces, the ANs can communicate information relating to handover, data / context transfer, mobility, load management, interference coordination and so on.

The ANs of the RAN 104 can each manage one or more cells, cell groups, component carriers, etc. to the UE 102 provide an air interface for network access. The UE 102 may be connected to a plurality of cells simultaneously from the same or different ANs of the RAN 104 to be provided. For example, the UE 102 and the RAN 104 Use carrier aggregation to provide the UE 102 to enable the connection to a plurality of component carriers, each corresponding to a primary cell (Pcell) or secondary cell (Scell). In dual connectivity scenarios, a first AN can be a master node providing a master cell group (MCG), and a second AN can be a secondary node providing a secondary cell group. Group (SCG) provides. The first / second ANs can be any combination of eNB, gNB, ng-eNB, etc.

The RAN 104 can provide the air interface via a licensed spectrum or an unlicensed spectrum. For operation in the unlicensed spectrum, the nodes can use Licensed Assisted Access (LAA), Enhanced LAA (eLAA) and / or further improved (feLAA) mechanisms based on carrier aggregation (CA) technology with PCells / Scells. Before access to the unlicensed spectrum, the nodes can carry out a media / carrier detection, which is based, for example, on a listen-before-talk (LBT) protocol.

In Vehicle-to-Everything (V2X) scenarios, the UE 102 or AN 108 be or act as an RSU, which can refer to any traffic infrastructure unit used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a “UE-Type RSU”; an eNB can be referred to as "eNB type RSU"; a gNB can be referred to as "gNB type RSU"; and the same. In one example, an RSU is a computing device that is coupled to radio frequency circuitry located on the roadside that provides connectivity to the UEs of passing vehicles. The RSU may also have internal data storage circuitry to store intersection geometry, traffic statistics, media, and applications / software for capturing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide the very low latency communication required for high speed events such as accident avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU can be housed in a weatherproof housing suitable for outdoor installation and can have a network interface control unit to provide a wired connection (e.g. Ethernet) to a traffic light controller or a backhaul network.

In some embodiments, the RAN 104 an LTE-RAN 110 with eNBs, e.g. B. eNB 112 , be. The LTE RAN 110 can provide an LTE air interface with the following features: subcarrier spacing (SCS) of 15 kHz; Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform for downlink (DL) and single carrier frequency division multiple access (SC-FDMA) waveform for uplink (UL); Turbo codes for data and Tail-Biting Convolutional Codes (TBCC) for control; etc. The LTE air interface can rely on the CSI reference signal (CSI-RS) for the acquisition of the channel status information (CSI) and the radiation management; the PDSCH / PDCCH demodulation reference signal (DMRS) for the PDSCH / PDCCH demodulation; and to the cell reference signal (CRS) for cell search and initial acquisition, channel quality measurements and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can work in sub-6 GHz bands.

In some embodiments, the RAN 104 a next generation RAN (NG-RAN) 114 with gNBs, for example gNB 116 , or ng-eNBs, for example ng-eNB 118 , be. The gNB 116 can connect to 5G-capable UEs via a 5G NR interface. The gNB 116 can connect to a 5G core via a next generation (NG) interface, which can have an N2 interface or an N3 interface. The ng-eNB 118 can also connect to the 5G core via an NG interface, but can be connected to a UE via an LTE air interface. The gNB 116 and the ng-eNB 118 can connect to each other via an Xn interface.

In some embodiments, the NG interface can be split into two parts, an NG-U interface (NG-U), which carries traffic data between the nodes of the NG-RAN 114 and a user plane function (UPF) 148 (eg N3 interface) transmits, and an NG-C interface (NG-C), which is a signaling interface between the nodes of the NG-RAN 114 and an Access and Mobility Management Function (AMF) 144 (e.g., N2 interface).

The NG-RAN 114 can provide a 5G NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and Discrete Fourier Transformation Spreading OFDM (DFT-s-OFDM) for UL; Polar, repetition, simplex and reed-Muller codes for control and low-density parity check (LDPC) for data. Similar to the LTE air interface, the 5G-NR air interface can be based on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface cannot use a CRS, but can use Physical Broadcast Channel (PBCH) DMRS for PBCH demodulation, phase tracking reference signals (PTRS) for phase tracking for PDSCH and tracking reference signal for time tracking. The 5G NR air interface can operate in frequency range 1 (FR1) bands, which have bands below 6 GHz, or in frequency range 2 (FR2) bands, the bands from 24.25 GHz to 52.6 GHz exhibit. The 5G NR air interface may comprise an SSB, which is a portion of a downlink resource grid that comprises a primary synchronization signal / sideband synchronization signal / physical broadcast channel (PSS / SSS / PBCH).

In some embodiments, the 5G NR air interface may use Bandwidth Parts (BWP) for various purposes. For example, BWP can be used to dynamically adapt the SCS. For example, the UE 102 be set up with several BWPs, each BWP configuration having a different SCS. If the UE 102 a BWP change is indicated, the SCS of the transfer is also changed. Another use case example for BWP relates to energy saving. In particular, several BWPs can be used for the UE 102 be set up with a different number of frequency resources (e.g. physical resource blocks (PRBs)) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with a low traffic load and at the same time enables power savings at the UE 102 and in some cases at the gNB 116. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic loads.

The RAN 104 is communicative with the core network (CN) 120 coupled, which has network elements, the various functions to support data and telecommunication services for customers / subscribers (e.g. users of the UE 102 ) provide. The components of the CN 120 can be implemented in a physical node or in separate physical nodes. In some embodiments, Network Functions Virtualization (NFV) may be used to implement some or all of the functions performed by the network elements of the CN 120 provided to virtualize on physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 120 can be referred to as a network slice, and a logical instantiation of part of the CN 120 can be referred to as a network sub-slice.

According to some embodiments, the CN 120 an LTE CN 122 which can also be referred to as Evolved Packet Core (EPC). The LTE CN 122 can a Mobility Management Entity (MME) 124 , a Serving Gateway (SGW) 126 , a Serving GPRS Support Node (SGSN) 128 , a home subscriber server (HSS) 130 , a packet data network gateway (PGW) 132 and a Policy Control and Charging Rules Function (PCRF) 134 that are coupled to one another via interfaces (or "reference points"), as shown. The functions of the elements of the LTE CN 122 can be briefly introduced as follows.

The MME 124 can implement mobility management functions to a current location of the UE 102 track to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

The SGW 126 can terminate an S1 interface to the RAN and data packets between the RAN and the LTE CN 122 forward onto. The SGW 126 can be a local mobility anchor point for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include compliant interception, billing, and some policy enforcement.

The SGSN 128 can find the location of the UE 102 track and perform security functions and access control. In addition, the SGSN 128 perform inter-EPC node signaling for mobility between different Radio Access Technology (RAT) networks; the selection of the packet data network (PDN) and the S-GW according to the specification of the MME 124 ; the MME selection for handover; etc. The S3 reference point between the MME 124 and the SGSN 128 can enable the exchange of user and bearer information for mobility between 3GPP access networks in the idle / active state.

The HSS 130 may have a database for network users, including subscription-related information, to aid in the handling of communication sessions by the network entities. The HSS 130 can provide support for routing / roaming, authentication, authorization, name / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 130 and the MME 124 can transfer subscription and authentication data for authentication / authorization of user access to the LTE CN 120 make possible.

The PGW 132 can be an SGi interface to a data network (DN) 136 complete an application / content server 138 may have. The PGW 132 can send data packets between the LTE CN 122 and the data network 136 forward onto. The PGW 132 can with the SGW 126 be coupled via an S5 reference point in order to facilitate tunneling at the user level and tunnel management. The PGW 132 may also have a node for the enforcement of policies and the collection of charge data (e.g. Policy and Charging Enforcement Function (PCEF)). In addition, the SGi reference point between the PGW 132 and the data network 136 an operator-external public, a private PDN or an operator-internal packet data network, e.g. for the provision of IMS services. The PGW 132 can use a Gx reference point with a PCRF 134 be coupled.

The PCRF 134 is the policy and charge control unit of the LTE CN 122 . The PCRF 134 can communicate with the app / content server 138 be coupled in order to determine suitable quality of service (QoS) and charging parameters for service flows. The PCRF 132 can provide associated rules in a PCEF (via the Gx reference point) with a suitable traffic flow template (TFT) and QoS Class of Identifier (QCI).

In some embodiments, the CN 120 a 5GC 140 be. The 5GC 140 an Authentication Server Function (AUSF) 142 , AMF 144 , Session Management Function (SMF) 146 , User Plane Function (UPF) 148 , Network Slice Selection Function (NSSF) 150 , Network Exposure Function (NEF) 152 , Network Function (NF) Repository Function (NRF) 154 , Policy control function (PCF) 156 , Unified Data Management (UDM) 158 and application function (AF) 160 that are coupled to one another via interfaces (or "reference points"), as shown. The functions of the elements of the Fifth Generation Core Network (5GC) 140 can be briefly introduced as follows.

The AUSF 142 can provide data for the authentication of the UE 102 store and handle authentication-related functions. The AUSF 142 can enable a common authentication framework for different types of access. In addition to communicating with other elements of the 5GC 140 Via reference points, as shown, the AUSF 142 have a Nausf service based interface.

The AMF 144 there can be other functions of the 5GC 140 enable with the UE 102 and the RAN 104 to communicate and notify of mobility events related to the UE 102 to subscribe. The AMF 144 can be used for registration management (e.g. for the registration of the UE 102 ), connection management, availability management, mobility management, lawful interception of AMF-related events and access authentication and authorization. The AMF 144 can be the transport for Session Management (SM) messages between the UE 102 and the session management function (SMF) 146 and act as a transparent proxy for routing SM messages. AMF 144 can also transport Short Message Service (SMS) messages between the UE 102 and an SMS function (SMSF). AMF 144 can with the AUSF 142 and the UE 102 interact to perform various security anchor and context management functions. In addition, AMF 144 be a termination point of a RAN Control Plane (CP) interface, which is an N2 reference point between the RAN 104 and AMF 144 can have or be; and AMF 144 can be a termination point of the NAS ( N1 ) Signaling and performing NAS encryption and integrity protection. The AMF 144 can also do Non-Access Stratum (NAS) signaling with the UE 102 support via an N3 interworking function (IWF) interface.

The SMF 146 can be responsible for SM (e.g. session setup, tunnel management between user level function (UPF) 148 and on 108 ); Assignment and management of UE IP addresses (including optional authorization); Selection and control of the user level (UP) function; Configuration of the traffic control on the UPF 148 to get traffic to the right destination; Termination of interfaces in the direction of policy control functions; Control parts of policy enforcement, billing and QoS; legally compliant interception (for SM events and the interface to the shift indicator (LI) system); Termination of SM parts of NAS messages; Downlink data notification; Initiation of AN-specific SM information that is sent via AMF 144 via N2 to AN 108 be sent; and determining the session and service continuity mode (SSC) of a session. SM can refer to the management of a Protocol Data Unit (PDU) session, and a PDU session or "session" can refer to a PDU link service which enables the exchange of PDUs between the UE 102 and the data network 136 provides or enables.

The UPF 148 Can be used as an anchor point for intra-RAT and inter-RAT mobility, as an external PDU session connection point to the data network 136 and serve as a branch point to support multi-homed PDU sessions. The UPF 148 can also perform packet routing and forwarding, perform packet inspection, enforce the user level part of the policy rules, intercept packets lawfully (UP collection), create traffic usage reports, perform QoS treatment for a user level (e.g. packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g. service data flow-to-QoS (SDF-to-QoS) flow mapping), perform packet marking on the transport level in the uplink and downlink and downlink packet buffering and Perform downlink data notification triggering. UPF 148 may have an uplink classifier to support the routing of traffic flows to a data network.

The NSSF 150 can select a set of network slice instances that the UE 102 serve. The NSSF 150 can also determine allowed network slice selector information (NSSAI) and the assignment to the subscribed individual NSSAIs (S-NSSAIs), if necessary. The NSSF 150 can also determine the AMF rate required to operate the UE 102 to be used, or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 154 . The selection of a set of network slice instances for the UE 102 can through the AMF 144 be triggered in which the UE 102 by interacting with the NSSF 150 is registered, which can lead to a change in the AMF. The NSSF 150 can with the AMF 144 interact via an N22 reference point; and can communicate with another NSSF on a visited network through an N31 reference point (not shown). In addition, the NSSF 150 have an Nssf service based interface.

The network exposure function (NEF) 152 can services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g. AF 160 ), Edge computing or fog computing systems etc. securely deploy. In such embodiments, the NEF 152 authenticate, authorize or throttle the AFs. The NEF 152 can also provide information related to the AF 160 and translate information exchanged with internal network functions. For example, the NEF 152 Translate between an AF service identifier and internal 5GC information. The NEF 152 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be found in the NEF 152 be stored as structured data or in a data-storing NF using standardized interfaces. The stored information can then be used by the NEF 152 passed on to other NFs and AFs or used for other purposes, such as analysis. In addition, the NEF 152 have an Nnef service-based interface.

The NRF 154 can support service discovery functions, receive NF discovery requests from NF entities and provide the information of the discovered NF entities to the NF entities. The NRF 154 also manages information about available NF instances and their supported services. As used herein, the terms “instantiating”, “instantiating” and the like can refer to the creation of an instance, and an “instance” can refer to a specific occurrence of an object that can occur, for example, during the execution of program code. In addition, the NRF 154 have the nnrf service based interface.

The Policy Control Function (PCF) 156 can control plane functions provide policy rules to enforce them, and can also support a unified policy framework for regulating network behavior. The PCF 156 Can also implement a front end to access subscription information that is used for policy decisions in a Unified Data Repository (UDR) of Unified Data Management (UDM) 158 are relevant. In addition to communicating with functions via reference points, as shown, the PCF 156 an npcf service based interface.

The UDM 158 can manage subscription-related information to aid in the handling of communication sessions by the network entities and subscription data of the UE 102 to save. For example, subscription data can be shared between the UDM 158 and the AMF 144 communicated. The UDM 158 can have two parts, an application front end and a UDR. The UDR can store subscription data and policy data for the UDM 158 and the PCF 156 and / or structured data for exposure and application data (including PFDs for application discovery, application requirement information for multiple UEs 102 ) for the NEF 152 exhibit. The Nudr service-based interface can be used by the UDR 221 issued to the UDM 158 , the PCF 156 and the NEF 152 enable access to a specific set of stored data as well as reading, updating (e.g. adding, changing), deleting and subscribing to notifications of relevant data changes in the UDR. The UDM may have a UDM front end (UDM-FE) that is responsible for processing credentials, site management, subscription management, and so on. Several different front ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs the processing of authentication credentials, the handling of the user identification, the access authorization, the management of the registration / mobility and the subscription management. In addition to communicating with other NFs via reference points, as shown, the UDM 158 have the Nudm service based interface.

The AF 160 can provide an application impact on traffic routing, access to Enable NEFs and interact with the policy framework to control policies.

In some embodiments, the 5GC 140 Enable edge computing by selecting operator / third party services to be geographically close to a point where the UE 102 connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 140 can use a UPF 148 near the UE 102 Select and route traffic from the UPF 148 to the data network 136 Carry out via the N6 interface. This can be based on the subscription data of the UE, the location of the UE and information provided by the AF 160 are provided. In this way, the AF 160 affect UPF (re-) selection and traffic routing. Based on the deployment of the network operator, if AF 160 is considered a trusted entity, AF 160 allow you to interact directly with relevant NFs. In addition, the AF 160 have an NF service-based interface.

The data network 136 may have various network operator services, Internet access, or third-party services that may be provided by one or more servers, including an application / content server, for example 138 .

2 schematically illustrates a wireless network 200 according to various embodiments. The wireless network 200 can a UE 202 that is in wireless communication with an AN 204 stands. The UE 202 and the AN 204 may be similar and substantially interchangeable with like components described elsewhere herein.

The UE 202 can have a connection 206 with the AN 204 be communicatively coupled. The connection 206 is shown as an air interface to enable communicative coupling and can be consistent with cellular communication protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 202 can be a host platform 208 having that with a modem platform 210 is coupled. The host platform 208 can be an application processing circuit 212 having that with the protocol processing circuit 214 the modem platform 210 can be coupled. The application processing circuit 212 can have different applications for the UE 202 execute that generate / record application data. The application processing circuit 212 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations can have transport (eg UDP) and Internet (eg IP) operations.

The protocol processing circuit 214 may implement one or more layer operations to facilitate the transmission or reception of data over the link 206 to facilitate. The one from the protocol processing circuit 214 implemented layer operations can have, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 210 can also have a digital baseband circuit 216 that can implement one or more layer operations that are “below” layer operations that are performed by the protocol processing circuit 214 run on a network protocol stack. These operations can include, for example, PHY operations, including one or more HARQ-ACK functions, scrambling / descrambling, coding / decoding, layer mapping / de-mapping, modulation symbol mapping, receive symbol / bit metric determination, precoding / decoding of multiple antenna connections, which can have one or more space-time, space-frequency or spatial codes, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding and other related functions .

The modem platform 210 can also have a transmission circuit 218 , a receiving circuit 220 , an RF circuit 222 and an RF front end (RFFE) 224 have one or more antenna fields 226 may have or be connected to them. In short, the transmission circuit can 218 a digital-to-analog converter, a mixer, intermediate frequency components, etc. The receiving circuit 220 can have an analog-to-digital converter, mixer, IF components, etc.; the RF circuit 222 may include a low noise amplifier, a power amplifier, power tracking components, etc .; the RFFE 224 can have filters (e.g. surface / bulk acoustic wave filters), switches, antenna tuners, beam shaping components (e.g. phase array antenna components), etc. The selection and arrangement of the components of the transmission circuit 218 , the receiving circuit 220 , the RF circuit 222 , the RFFE 224 and the antenna fields 226 (commonly referred to as "transmit / receive components") can be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components can be arranged in several parallel transmit / receive chains, they can be housed in the same or in different chips / modules, etc.

In some embodiments, the protocol processing circuit 214 have one or more instances of control circuits (not shown) in order to provide control functions for the transmitting / receiving components.

UE reception can be through and via the antenna fields 226 who have favourited RFFE 224 who have favourited RF circuit 222 , the receiving circuit 220 who have favourited digital baseband circuit 216 and the protocol processing circuit 214 getting produced. In some embodiments, the antenna panels 226 a transfer from the contractor 204 by receive beamforming of signals received from a plurality of antenna / antenna elements of the one or more antenna arrays 226 be received.

A UE transmission can be to and from the protocol processing circuit 214 who have favourited digital baseband circuit 216 , the transmission circuit 218 who have favourited RF circuit 222 who have favourited RFFE 224 and the antenna fields 226 being constructed. In some embodiments, the transmission components of the UE 204 apply a spatial filter to the data to be transmitted in order to form a transmit beam that is emitted by the antenna elements of the antenna arrays 226 is sent out.

Similar to the UE 202 can do that 204 a host platform 228 having that with a modem platform 230 is coupled. The host platform 228 can be an application processing circuit 232 having that with a protocol processing circuit 234 the modem platform 230 is coupled. The modem platform can also have a digital baseband circuit 236 , a transmission circuit 238 , a receiving circuit 240 , an RF circuit 242 , an RFFE circuit 244 and antenna fields 246 exhibit. The components of the contractor 204 can be similar and essentially interchangeable with components of the UE of the same name 202 be. In addition to performing data transmission / reception as described above, the components of the AN 208 perform various logic functions that have, for example, RNC functions, such as radio bearer management, dynamic management of uplink and downlink radio resources, and data packet planning.

3 FIG. 13 is a block diagram showing components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing one or more of the methods discussed herein, in accordance with some embodiments. In particular shows 3 a schematic representation of hardware resources 300 that have one or more processors (or processor cores) 310 , one or more storage / storage devices 320 and one or more communication resources 330 each of which has a bus 340 or other interface circuits can be communicatively coupled. In embodiments using node virtualization (e.g., NFV), a hypervisor 302 be executed in order to provide an execution environment for one or more network slices / sub-slices to the hardware resources 300 to use.

The processors 310 can eg use a processor 312 and a processor 314 exhibit. The processors 310 For example, a central processing unit (CPU), a RISC processor (reduced instruction set arithmetic), a CISC processor (Kompolexer instruction set arithmetic), a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, an RFIC (Radio Frequency Integrated Circuit), other processor (including those discussed herein), or any suitable combination thereof.

The storage / storage devices 320 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 320 can have 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 memory, etc. but not limited to that.

The communication resources 330 can control units, components or other suitable devices for communication with one or more peripheral devices 304 or one or more databases 306 or other network elements over a network 308 exhibit. For example, the communication resources 330 have 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.

The instructions 350 can be software, a program, an application, an applet, an app or other executable code to at least one of the processors 310 cause one or more of the methods discussed here to be performed. The instructions 350 can be fully or partially in at least one of the processors 310 (e.g. in the processor's cache memory), in the storage / storage devices 320 or in a suitable combination thereof. In addition, any part of the instructions can 350 from any combination of the peripheral devices 304 or the databases 306 to the hardware resources 300 be transmitted. The memory of the processors are accordingly 310 who have favourited Storage / Storage Devices 320 who have favourited peripheral devices 304 and the databases 306 Examples of computer readable and machine readable media.

In some embodiments, the electronic device (s), network (s), system (s), chip (s), or component (s), or parts or implementations thereof the 1-3 or any other figure herein may be adapted to perform one or more processes, techniques, or methods as described herein, or parts thereof.

New radio (New Radio -NR) supports the physical control channel (PDCCH), which transmits the planning decision for both DL and UL via DCI. PDCCH is sent over a control resource unit (CORESET). CORESETs are set up in units of six PRBs (one PRB corresponds to 12 resource elements) in the frequency domain and one, two or three successive OFDM symbols in the time domain.

A resource element group (REG) consists of a resource block and an OFDM symbol in the time domain. A REG bundle has several REGs, the size of the REG bundle being determined by the parameter L, which is configured by RRC.

For CORESET with 1 OFDM symbol the REG bundle is 6x1 neighboring REGs in the time domain, for 2 OFDM symbols CORESET the REG bundle is either 1x2 neighboring REGs in the time domain or 3x2 neighboring REGs in frequency and time, for 3 OFDM symbols CORESET the REG bundle is 1x3 neighboring REGs in the time domain or 2x3 neighboring REGs in frequency and time.

A control channel element (CCE) consists of several REGs. The number of REG bundles within a CCE varies. For the CCE-to-REG mapping, a REG bundle is defined as L successive REGs. The CCE consists of nested or non-nested '6 / L' REG bundles. The CCE-to-REG interleaver is defined by block interleaving. Block interleaving is a function that performs interleaving by writing the sequence line by line into the block and reading the output (interleaved) sequences column by column. Depending on the implementation, the interleaving can also be carried out the other way round, in that the input sequence is written column by column and the output sequence (nested sequence) is read line by line. The start position of the write or read sequence can be shifted further cyclically for additional randomization. A block interleaver is defined by the interleaver size, which for CCE-to-REG interleaving can be a value from the set R ∈ {2, 3, 6). This parameter defines the number of columns or the number of rows of the block interleaver, depending on the implementation. The remaining dimension of the block interleaver is determined from the input sequence length by dividing it by the first dimension R. The parameter shift for the CCE-to-REG interleaver is defined in the range nshift ∈ {0,1, ..., 274}.

Furthermore, PRB trunking precoding for PDCCH is supported in the frequency domain. More specifically, the UE can assume that the precoder is constant over a set of PRBs. More precisely, according to TS 38.211, the granularity of the precoding is defined according to the following rules:

Both interleaved and non-interleaved mapping can be accepted by the UE
- That the same precoding is used within a REG bundle if the higher-layer parameter precoderGranularity is equal to sameAsREG-bundle;
- that the same precoding is used in all resource element groups within the set of contiguous resource blocks in the CORESET and that no resource elements in the CORESET overlap with an SSB or LTE cell-specific reference signal, as specified according to the higher-layer parameter lte-CRS-ToMatchAround , if the higher-layer parameter precoderGranularity is equal to allContiguousRBs.

In accordance with aspects of the present disclosure, the use of the common interleaver assumption can be used to improve channel estimation performance by performing the channel estimation over a greater number of DM-RS resource elements. In Rel-16 NR (e.g. TS 38.211), PDCCH only supports fixed CCE-to-REG nesting. In addition, precoding bundling is only supported through PRBs in the frequency domain.

Therefore, in the cases or scenarios with PDCCH repetition, the channel estimation performance can be further improved by using the assumption that the same precoding assignment is used over PRBs in the time domain. For example, time-varying CCE-REG interleaving can provide additional diversity for the occupied CCEs.

Aspects of the present disclosure relate to the use of time-dependent or repetition-dependent CCE-to-REG interleaving. In addition, aspects of the present disclosure relate to the use of precoding trunking across PDCCH repetitions to improve PDCCH decoding performance for PDCCH transmissions from the same TRP.

$$x=cR+r$$

$$r=\mathrm{0,1,}\dots ,R-1$$

$$c=\mathrm{0,1,}\dots ,C-1$$

$$C=N_{\text{REG}}^{\text{CORESET}}/\left(LR\right)$$

wobei n_shift = l · $N_{ID}^{cell},$

wobei l das erste OFDM-Symbol des CORESET innerhalb eines Slots oder innerhalb eines Teilrahmens oder innerhalb eines Rahmens ist.In accordance with at least one aspect of the present disclosure, the CCE-to-REG interleaving may be different for different slots or CORESET transmission occasions within the slot. More specifically, if a CORESET corresponds to the same CORESET pool index or corresponds to the same TCI (Transmission Control Indicator) status, the CCE-to-REG interleaving pattern may be different. For example, CCEj can consist of REG bundles {f (6j / L), f (6j / L + 1) .... f (6j / L + 6 / L-1), where f () is an interleaver function that can be defined by $$f\left(x\right)=\left(r\mathrm{C.}+c+n_{\text{shift}}\right)\text{mod}\left(N_{\text{REG}}^{\text{CORESET}}/\mathrm{L.}\right)$$

$$x=c\mathrm{R.}+r$$

$$r=\mathrm{0.1,}...,\mathrm{R.}-1$$

$$c=\mathrm{0.1,}...,\mathrm{C.}-1$$

$$\mathrm{C.}=N_{\text{REG}}^{\text{CORESET}}/\left(\mathrm{L.}\mathrm{R.}\right)$$

where n _shift = l $N_{\mathrm{I.}\mathrm{D.}}^{cell},$

where l is the first OFDM symbol of the CORESET within a slot or within a sub-frame or within a frame.

In accordance with another aspect of the present disclosure, a UE may adopt the same precoding for REG bundles that correspond to different CORESETs with the same TCI state that correspond to the same PRBs. The precoding bundling across CORESETs is limited to the CORESET configuration within the same slot, subframe or frame. In another example of this aspect, a CORESET group can be configured with the same precoding.

The precoding bundling for a CORESET that has a CORESET grouping can be configured by higher layers. 4th shows a diagram representing a CORESET group 400 for precoding bundling.

5 provides an exemplary procedure 500 according to at least one aspect of the present disclosure. For example, at 501, the process may include receiving configuration information for a control resource group (CORESET) that includes a plurality of CORESETs. The process may further include at 502, based on the configuration information, decoding a same downlink physical control channel (PDCCH) over one or more CORESETs within the CORESET group. In various embodiments, the process can be performed by a UE or a part thereof (eg baseband switching of the UE).

6th illustrates another exemplary process 600 in accordance with various aspects of the present disclosure. For example, the process 600 from 6th at 601, encoding configuration information for a group of control resources (CORESET) configuring a plurality of CORESETs for transmission to a user equipment (UE). The process may further include, at 602, encoding a same downlink physical control channel (PDCCH) over one or more CORESETs within the CORESET group for transmission to the UE based on the configuration information. In various embodiments, the process can 600 from 6th be performed by a gNB or a part of it (e.g. baseband switching of the gNB).

wobei $Y_{p,n_s}=0$

für CSS und $Y_{p,n_s}$

pseudo-zufällige Variablen für USS sind, L eine Aggregationsstufe ist, $$j_{p,m}^{\left(L\right)}=\lfloor \frac{m\cdot N_{CCE,p}}{L\cdot M^{\left(L\right)}}\rfloor ,$$

wobei M^(L) die Anzahl von PDCCH-Kandidaten ist mit Aggregationsstufe L, m=0, ..., M^(L)-1, i=0,..., L-1,
N_CCE,p ist die Anzahl von CCEs, nummeriert von 0 bis N_CCE,p -1, in CORESET p.In accordance with another aspect of the present disclosure, the UEs described herein may blindly decode PDCCH for a particular set of CCEs referred to as a search space (SS). 5G NR can support two types of SS sentences: the common SS sentence (CSS) which is jointly monitored by a group of UEs in the cell and the UE-specific SS sentence (USS) which is monitored by a single UE . The number of CCEs belonging to an SS can be determined with the help of a hash function. The hash function randomizes the assignment of the PDCCH candidates within CORESET p in slot ns. This can be done according to the equation $$\mathrm{L.}\cdot \left\{\left(Y_{p,n_s}+j_{p,m}^{\left(\mathrm{L.}\right)}\right)\text{mod}\frac{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}}{\mathrm{L.}}\right\}+i$$

whereby $Y_{p,n_s}=0$

for CSS and $Y_{p,n_s}$

are pseudo-random variables for USS, L is an aggregation level, $$j_{p,m}^{\left(\mathrm{L.}\right)}=\lfloor \frac{m\cdot N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}}{\mathrm{L.}\cdot {\mathrm{M.}}^{\left(\mathrm{L.}\right)}}\rfloor ,$$

where M ^{(L) is} the number of PDCCH candidates with aggregation level L, m = 0, ..., M ^(L) -1, i = 0, ..., L-1,
N _{CCE, p} is the number of CCEs numbered from 0 to N _{CCE, p} -1, in CORESET p.

An example of an assignment of the CCEs to PDCCH candidates with different aggregation levels AL is in 7th for a CORESET that has 16 CCEs.

In such cases, each CORESET can be configured with a single TCI (Transmission Configuration Indicator) state that includes source reference signals (RS) and quasi-cooperation parameters (QCL) such as Doppler and delay shifts, Doppler and delay spreading, and spatial Rx parameters (only for FR2). The configured RS can be used to support the demodulation of the PDCCH in the CORESET.

According to the previous explanations, PRB trunking precoding is supported for PDCCH in the frequency domain. More precisely, the UE can assume that the precoder is constant over the set of PRBs. Again according to TS 38.211, the granularity of the precoding is defined according to the following rule:

Again, for both interleaved and non-interleaved mapping, the UE can assume that
the same precoding is used within a REG bundle if the higher-layer parameter precoderGranularity is equal to sameAsREG-bundle;
- the same precoding is used in all resource element groups within the set of contiguous resource blocks in the CORESET and that no resource elements in the CORESET overlap with an SSB or LTE cell-specific reference signal, as is the case with the higher-layer parameter lte-CRS -ToMatchAround specified if the higher-layer parameter precoderGranularity is equal to allContiguousRBs.

wobei K ein fester Parameter ist oder K ein Parameter ist, der von RRC konfiguriert wird.In accordance with at least one aspect of the present disclosure, multi-TRP transmission can be supported within a single CORESET. According to at least one example, more than one TCI status NTCI, p (eg NTCI, p = 2) can be set up for a CORESET. Furthermore, a total number of NCCE, p CCEs can be associated with established TCI states according to the following equation: $$T\mathrm{C.}{\mathrm{I.}}_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}=\text{mod}\left(\lfloor i\frac{K}{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}}\rfloor ,N_{T\mathrm{C.}\mathrm{I.},p}\right),i=\mathrm{0,}...,N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}-1$$

where K is a fixed parameter or K is a parameter configured by RRC.

An illustration of the TCI assignment to the CCEs is in 8th for different values of the parameter K.

In cases where multiple TCI states are established for PRB, the precoding granularity can be determined within CCEs / REG bundles associated with the same TCI state (for both interleaved and non-interleaved mapping). In such cases, the UE can assume that the same precoding is used within a REG bundle if the higher-layer parameter precoderGranularity is the sameAsREG-bundle, with the same precoding for all resource element groups within the set of contiguous resource blocks are used that are connected to the same TCI status in the CORESET, and that no resource elements in the CORESET overlap with an SSB or LTE cell-specific reference signal, as in accordance with the higher-layer parameter Ite-CRS-ToMatchAround specified if the higher-layer parameter precoderGranularity is equal to allContiguousRBs.

$$L\cdot \left\{\left(Y_{p_2,n_s}+j_{p_2,m_2}^{\left(L\right)}\right)\text{mod}\frac{N_{CCE,p_2}}{L}\right\}+i_2,\text{ if }i=L,\dots \mathrm{,2}\cdot L-1$$

und i₁ = i, i₂ = i, i - L.In another aspect of the present disclosure, multi-TRP transmission is supported by using multiple CORESETs (CORESET bundles), each CORESET being able to be set up with a TCI state. According to one example, USS, which correspond to multi-TRPs with an aggregation level (AL) of 2-L, can by aggregating certain pairs {m1, m2} of PDCCH candidates from the first CORESET p1 and the second CORESET p2 with an aggregation level of L being constructed: $$\mathrm{L.}\cdot \left\{\left({\mathrm{<figure-callout\; id="1"\; label="Y\; p"\; filenames="DE102021103592A1\_0036.png,DE102021103592A1\_0039.png"\; state="\{\{state\}\}">Y</figure-callout>}}_{p_{}}+{\mathrm{<figure-callout\; id="1"\; label="j\; p"\; filenames="DE102021103592A1\_0036.png,DE102021103592A1\_0039.png"\; state="\{\{state\}\}">j</figure-callout>}}_{p_{}}^{{}_1,m_1}\right)\text{mod}\frac{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},{\mathrm{<figure-callout\; id="1"\; label="p"\; filenames="DE102021103592A1\_0036.png,DE102021103592A1\_0039.png"\; state="\{\{state\}\}">p</figure-callout>}}_1}}{\mathrm{L.}}\right\}+{\mathrm{<figure-callout\; id="1"\; label="i"\; filenames="DE102021103592A1\_0036.png,DE102021103592A1\_0039.png"\; state="\{\{state\}\}">i</figure-callout>}}_1,\text{if}i=\mathrm{0,}...,\mathrm{L.}-1$$

$$\mathrm{L.}\cdot \left\{\left({\mathrm{<figure-callout\; id="2"\; label="Y\; p"\; filenames="DE102021103592A1\_0042.png,DE102021103592A1\_0043.png"\; state="\{\{state\}\}">Y</figure-callout>}}_{p_{}}+{\mathrm{<figure-callout\; id="2"\; label="j\; p"\; filenames="DE102021103592A1\_0042.png,DE102021103592A1\_0043.png"\; state="\{\{state\}\}">j</figure-callout>}}_{p_{}}^{{}_2,m_2}\right)\text{mod}\frac{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},{\mathrm{<figure-callout\; id="2"\; label="p"\; filenames="DE102021103592A1\_0042.png,DE102021103592A1\_0043.png"\; state="\{\{state\}\}">p</figure-callout>}}_2}}{\mathrm{L.}}\right\}+{\mathrm{<figure-callout\; id="2"\; label="i"\; filenames="DE102021103592A1\_0042.png,DE102021103592A1\_0043.png"\; state="\{\{state\}\}">i</figure-callout>}}_2,\text{if}i=\mathrm{L.},...\mathrm{,\; 2}\cdot \mathrm{L.}-1$$

and i ₁ = i, i ₂ = i, i - L.

In one example, m1 = m2 can be used to determine the pair {m1, m2} of PDCCH candidates of aggregation level 2-L from the first CORESET p_1 and the second CORESET p_2. The total number of PDCCH candidates with aggregation level 2-L can be the minimum between the total number of PDCCH candidates with aggregation level L from CORESET p_1 and the total number of PDCCH candidates with aggregation level L from CORESET p_2

In another example, the PDCCH candidates of aggregation levels 2-L, which correspond to the multi-TRP transmission of PDCCH, are identified in a new USS. The USS configuration should have two or more CORESETs IDs to indicate the CORESETs used for multi-TRP transmission. The USS should also have the configuration of two or more higher-level USS and should be considered valid if the corresponding USS is monitored by the UE in the corresponding slot.

In another example, the PDCCH candidates with an aggregation level of 2-L, which correspond to the multi-TRP transmission, are monitored by the UE if the corresponding PDCCH candidates with an aggregation level of L are monitored by the UE for the higher-level USS will.

In another aspect of the present disclosure, for FR2, the USS corresponding to different CORESETs can be transmitted in different OFDM symbols of the same slot to allow enough time for Rx beam switching at the UE to receive PDDCH received from different ones TRPs are transmitted.

For the one or more embodiments disclosed herein, at least one of the components illustrated in one or more of the preceding figures can be configured to perform one or more operations, techniques, processes and / or methods according to the following example section. For example, as described above in connection with one or more of the preceding figures, the baseband circuit can be set up in such a way that it operates in accordance with one or more of the examples listed below. As a further example, the circuit associated with a UE, a base station, a network element, etc., as described above in accordance with one or more of the preceding figures, can be set up in such a way that it operates in accordance with one or more of the examples listed below in the example section.

Unless otherwise used here, terms, definitions and abbreviations can match the terms, definitions and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06).

Various aspects of the present disclosure are presented below:

FIRST SET OF EXAMPLES

• Einrichten von Gruppen von Steuerungsressourcensätzen (CORESETs) für das Benutzergerät (UE);
• Übertragung desselben physikalischen Downlink-Steuerungskanals (PDCCH) über ein oder mehrere CORESETs innerhalb der eingerichteten CORESET-Gruppe; und
• Dekodierung des PDCCH an dem UE gemäß den eingerichteten Konfigurationen.

Example 1 may include a method of transmitting control channels, the method comprising:

• Establishing groups of control resource sets (CORESETs) for the user equipment (UE);
• Transmission of the same physical downlink control channel (PDCCH) via one or more CORESETs within the established CORESET group; and
• Decoding of the PDCCH at the UE according to the established configurations.

Example 2 may have the method of Example 1 or another example herein, wherein the configuration of the CORESET group comprises a configuration of precoding bundling over REG bundles of the CORESET group.

Example 3 may have the method of Example 2 or any other example herein wherein the precoding is the same in all Physical Resource Blocks (PRBs) corresponding to the same REG bundle.

Example 4 may include the method of Example 3, or another example herein, where the CORESET group is all CORESETs within a slot.

Example 5 may have the method of Example 3, or another example herein, where the CORESET group is all CORESETs within a sub-frame.

Example 6 may have the method of Example 3 or any other example herein wherein the CORESET group is established with the same transmission configuration indicator (TCI).

Example 7 may have the method of Example 1 or another example herein, wherein the REG-to-CCE interleaver (resource element Group-to-control channel element) depends on the OFDM symbol index (orthogonal frequency division multiplexing).

Example 8 may include the method of Example 7 or another example herein wherein the OFDM symbol index is defined within a slot.

Example 9 may include the method of Example 7 or another example herein wherein the OFDM symbol is defined within a sub-frame.

oder ein anderer Höhere-Schicht-Parameter ist.Example 10 may include the method of Example 7 or another example herein, where for the CCE to REG interleaver parameter _shift is defined as n shift = 1 * N _ID , where 1 is the OFDM symbol index of the first CORESET symbol within of a slot or within a sub-frame or within a frame and N _ID = $N_{\text{ID}}^{\text{cell}}$

or another higher layer parameter.

• Empfangen von Konfigurationsinformationen für eine Steuerungsressourcengruppe (CORESET-Gruppe), die eine Mehrzahl von CORESETs aufweist; und
• Dekodieren, basierend auf der Konfigurationsinformation, eines gleichen physikalischen Downlink-Steuerkanals (PDCCH) über ein oder mehrere CORESETs innerhalb der CORESET-Gruppe.

Example 11 may have a method that comprises:

• Receiving configuration information for a control resource group (CORESET group) having a plurality of CORESETs; and
• Decoding, based on the configuration information, of the same physical downlink control channel (PDCCH) via one or more CORESETs within the CORESET group.

Example 12 may include the method of Example 11 or any other example herein, wherein the configuration information includes an indication of precoding bundling via resource element group (REG) bundles of the CORESET group.

Example 13 may include the method of Example 12, or any other example herein, wherein the precoding is the same in all physical resource blocks (PRBs) corresponding to the same REG bundle.

Example 14 may include the method of Examples 11-13 or another example herein wherein the CORESET group includes all CORESETs within a slot.

Example 15 may include the method of Examples 11-13 or another example herein wherein the CORESET group includes all CORESETs within a sub-frame.

Example 16 may include the system and method of Examples 11-15, or another example herein, wherein the configuration information has a same transmission configuration indicator (TCI) state for the plurality of CORESETs in the CORESET group.

Example 17 may include the method of Example 11-16, or another example herein, wherein a REG-to-CCE (Resource-Element-Group-to-Control-Channel-Element) interleaver for the plurality of CORESETs in the CORESET group of an OFCM symbol index (Orthogonal Frequency Division Multiplexing) depends.

Example 18 may include the method of Example 17 or another example herein wherein the OFDM symbol index is defined within a slot.

Example 19 may include the method of Example 17, or another example herein, where the OFDM symbol is defined within a sub-frame.

oder eines anderen konfigurierten Parameters ist.Example 20 may include the method of Example 17 or another example herein, wherein a parameter _shift for the CCE-to-REG interleaver is defined as n shift = 1 * N _ID where 1 is the OFDM symbol index of the first CORESET symbol within a Slots or within a sub-frame or within a frame and N _ID = $N_{\text{ID}}^{\text{cell}}$

or another configured parameter.

Example 21 may comprise the method of Examples 11-20 or another example herein, the method being performed by a user equipment (UE) or a part thereof.

• Kodieren von Konfigurationsinformationen für eine Gruppe von Steuerungsressourcen (CORESET), die eine Mehrzahl von CORESETs aufweist, zur Übertragung an ein Benutzergerät (UE); und
• Kodieren eines gleichen physikalischen Downlink-Steuerkanals (PDCCH) über ein oder mehrere CORESETs innerhalb der CORESET-Gruppe zur Übertragung an das UE auf der Grundlage der Konfigurationsinformationen.

Example 22 may have a method that comprises:

• Coding of configuration information for a group of control resources (CORESET), which has a plurality of CORESETs, for transmission to a user equipment (UE); and
• Coding of the same physical downlink control channel (PDCCH) via one or more CORESETs within the CORESET group for transmission to the UE on the basis of the configuration information.

Example 23 may include the method of Example 22 or any other example herein, wherein the configuration information is an indication of precoding bundling via resource Have element groups (REG) bundles of the CORESET group.

Example 24 may include the method of Example 23, or another example herein, wherein the precoding is the same in all physical resource blocks (PRBs) corresponding to the same REG bundle.

Example 25 may include the method of Examples 22-24, or another example herein, wherein the CORESET group includes all CORESETs within a slot.

Example 26 may include the method of Examples 22-24, or another example herein, wherein the CORESET group includes all CORESETs within a sub-frame.

Example 27 may include the system and method of Examples 22-26, or another example herein, wherein the configuration information has a same transmission configuration indicator (TCI) state for the plurality of CORESETs in the CORESET group.

Example 28 may include the method of Example 22-27, or another example herein, wherein a REG-to-CCE interleaver (resource element group-to-control channel element) for the plurality of CORESETs in the CORESET group of an OFDM symbol index (Orthogonal Frequency Division Multiplexing) depends.

Example 29 may include the method of Example 28, or another example herein, wherein the OFDM symbol index is defined within a slot.

Example 30 may include the method of Example 28, or another example herein, wherein the OFDM symbol is defined within a sub-frame.

oder eines anderen konfigurierten Parameters ist.Example 31 may include the method of Example 28, or another example herein, where a parameter _shift for the CCE-to-REG interleaver is defined as n shift = 1 * N _ID , where 1 is the OFDM symbol index of the first CORESET symbol within of a slot or within a sub-frame or within a frame and N _ID = $N_{\text{ID}}^{\text{cell}}$

or another configured parameter.

Example 32 may include the method of Examples 22-31 or any other example herein, wherein the method is performed by a gNB or a portion thereof.

Example 1A may include an apparatus having means for performing one or more elements of a method described in or related to any of Examples 1-32, or any other method or process described herein.

Example 1B may include one or more non-transitory computer-readable media that contain instructions to cause an electronic device, when the instructions are executed by one or more processors of the electronic device, to perform one or more elements of a method described in one of Examples 1 -32, or any other method or process described herein.

Example 1C may include an apparatus having logic, modules, or circuitry to perform one or more elements of a method described in or related to any of Examples 1-32, or any other method or process described herein.

Example 1D may include a method, technique, or process as described in or related to any of Examples 1-32, or portions or portions thereof.

Example 1E may include an apparatus: one or more processors and one or more computer-readable media that have instructions that, when executed by the one or more processors, cause the one or more processors, the method, technique, or perform the process as described in or associated with any of Examples 1-32, or parts thereof.

Example 1F may have a signal as described in or associated with any of Examples 1-32, or parts thereof.

Example 1G may include a datagram, packet, frame, segment, protocol data unit (PDU), or message, as described in or related to any of Examples 1-32, or portions or portions thereof, or as otherwise herein Revelation described.

Example 1H may have a signal encoded with data as described in or associated with any of Examples 1-32, or portions thereof, or otherwise described in the present disclosure.

Example 1I may have a signal associated with a datagram, packet, frame, a segment, protocol data unit (PDU), or message is encoded as described in or related to any of Examples 1-32, or with portions or portions thereof, or otherwise described in the present disclosure.

Example 1J may include an electromagnetic signal carrying computer readable instructions, the execution of the computer readable instructions by one or more processors serving to cause the one or more processors to use the method, technique, or process, as in any of the examples 1-32 or associated therewith, or to carry out parts thereof.

Example 1K may include a computer program that includes instructions, the execution of the program by a processing element serving to cause the processing element to use the method, technique, or process as described in or associated with any of Examples 1-32, or To carry out parts of it.

Example 1L may have a signal on a wireless network as shown and described herein.

Example 1M may include a method of communicating in a wireless network as illustrated and described herein.

Example 1N may include a system for providing wireless communication as illustrated and described herein.

Example 1N may include an apparatus for providing wireless communication as illustrated and described herein.

SECOND SET OF EXAMPLES

Example 1 may include a method of controlling channel transmission, the method comprising the following
Establishment of control resource sets (CORESETs) with two or more transmission configuration indicators (TCI) or establishment of two or more CORESETs with a TCI state; or
Monitoring the transmission of downlink control information (DCI) on the physical downlink control channel (PDCCH) on control channel elements (CCEs), the CCEs being connected to different TCI states.

Example 2 may include the method of Example 1 or another example herein, wherein, if the CORESET is established with two or more TCI states, the set of CCEs corresponding to a particular aggregation level may be associated with different TCI states.

wobei p ein Index vom CORESET ist, N_CCE,p eine Gesamtanzahl von CCEs ist, N_TCI,p die Anzahl von TCI-Zuständen ist.Example 3 may include the method of Example 2, or another example herein, wherein the i-th CCE is associated with established TCI states according to the following equation $$T\mathrm{C.}{\mathrm{I.}}_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}=\text{mod}\left(\lfloor i\frac{K}{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}}\rfloor ,N_{T\mathrm{C.}\mathrm{I.},p}\right),i=\mathrm{0,}...,N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}-\mathrm{1,}$$

where p is an index of CORESET, N _{CCE, p is} a total number of CCEs, N _{TCI, p is} the number of TCI states.

Example 4 may have the method of Example 3 or another example herein, with the parameter K being predetermined (e.g. set in the specification to e.g. K = 2) or given by higher layers.

Example 5 may have the method of Example 2 or another example herein, using the same precoding across all resource element groups within the set of contiguous resource blocks associated with the same TCI state in CORESET, and that no resource elements in the CORESET overlap with an SSB or LTE cell-specific reference signal according to the higher-layer parameter Ite-CRS-ToMatchAround if the higher-layer parameter precoderGranularity is equal to allContiguousRBs.

Example 6 may include the method of Example 1 or another example herein, wherein if two CORESETs are established with different TCI states, the UE monitors the DCI transmission on CCEs corresponding to different CORESETs.

Example 7 may include the method of Example 1 or another example herein, wherein the UE specific search space is set up to have CCEs from different CORESETs.

Example 8 may include the method of Example 1 or another example herein, wherein the UE-specific search space is set up to have CCEs that correspond to CCEs of aggregation level L of each USS that corresponds to two CORESETs.

Example 9 may include the method of Example 8 or another example herein, with the UE-specific search space defined in the same slot.

Example 10 can include the method from Example 8 or another example herein, wherein UE-specific search spaces are defined in the same slot but on different OFDM symbols for FR2.

Example 11 may include the system and method of Example 8 or another example herein, wherein the total number of PDCCH candidates with an aggregation level of 2-L is the minimum between the total number of PDCCH candidates with an aggregation level of L from CORESET p1 and the Total number of PDCCH candidates with an aggregation level of L from CORESET is p2.

Example 12 may include a method comprising: generating one or more configuration messages containing control resource set (CORESET) configuration information; Transmitting the one or more configuration messages to a user device, the CORESET configuration information being used to set up a CORESET with two or more transmission configuration indicator (TCI) states or to set up two or more CORESETs with a TCI state.

Example 13 may include the method of Example 12, or any other example herein, wherein the CORESET configuration information is used to establish a CORESET with two or more TCI states and a set of CCEs corresponding to different levels of aggregation with different TCI states are connected.

Example 14 may include the method of Example 12 or any other example herein, wherein the CORESET configuration information is used to match CCEs with TCI states for different levels of aggregation according to 2 to link.

Example 15 may include the method of Example 12, or another example herein, where if the CORESET is established with two or more TCI states and sets of CCEs corresponding to a particular aggregation level can be associated with different TCI states.

wobei p ein Index vom CORESET ist, N_CCE,p eine Gesamtanzahl von CCEs ist, N_TCI,p die Anzahl von TCI-Zuständen ist, und K vorbestimmt ist oder von höheren Schichten konfiguriert ist.Example 16 may include the method of Example 15, or another example herein, wherein the i-th CCE is associated with established TCI states according to the following equation: $$T\mathrm{C.}{\mathrm{I.}}_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}=\text{mod}\left(\lfloor i\frac{K}{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}}\rfloor ,N_{T\mathrm{C.}\mathrm{I.},p}\right),i=\mathrm{0,}...,N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}-\mathrm{1,}$$

where p is an index of CORESET, N _{CCE, p is} a total number of CCEs, N _{TCI, p is} the number of TCI states, and K is predetermined or configured by higher layers.

Example 17 may include a method comprising: processing one or more configuration messages to obtain control resource set (CORESET) configuration information; Monitor DCI on PDCCH on CCEs, where CCEs are associated with different TCI states based on CORESET configuration information.

Example 18 may include the method of Example 17, or another example herein, where the CORESET configuration information is used to set up two CORESETs with different TCI states and the monitoring includes monitoring the DCI transmission for CCEs that correspond to different CORESETs.

Example 19 may include the method of Example 17 or another example herein, wherein the CORESET configuration information is configured to set up a UE-specific search space to have CCEs from different CORESETs.

Example 20 may include the method of Example 17, or another example herein, wherein the CORESET configuration information is used to set up a UE-specific search space to include CCEs that correspond to CCEs of aggregation level L of each USS that correspond to two CORESETs .

Example 21 may include the method of example 20 or another example herein, wherein the CORESET configuration information is used to set up a plurality of UE-specific search spaces in a same slot.

Example 22 may include the method of Example 21 or another example herein, wherein the plurality of UE-specific search spaces are set up on different OFDM symbols for FR2.

Example 23 may include the method of Example 20, or any other example herein, wherein the CORESET configuration information is used to identify a total number of PDCCH candidates with an aggregation level of 2-L as a minimum between the total number of PDCCH candidates with an aggregation level of L from CORESET p1 and a total number of PDCCH candidates with an aggregation level of L from CORESET p2.

Example 1A may include an apparatus having means for performing one or more elements of a method described in or relating to any of Examples 1-23, or another method or process described herein.

Example 2A may include one or more non-transitory computer-readable media that contain instructions to cause an electronic device, when the instructions are executed by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1 -23 or is related to it, or any other method or process described herein.

Example 3A may include apparatus that includes logic, modules, or circuitry to perform one or more elements of a method described or related to any of Examples 1-23, or any other method or process described herein.

Example 4A may include a method, technique, or process as described in or related to any of Examples 1-23, or portions or portions thereof.

Example 5A may include an apparatus: one or more processors and one or more computer-readable media that have instructions that, when executed by the one or more processors, cause the one or more processors, the method, technique, or perform the process as described in or associated with any of Examples 1-23, or parts thereof.

Example 6A may have a signal as described in or associated with any of Examples 1-23, or parts thereof.

Example 7A may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of Examples 1-23, or portions thereof, or otherwise described in the present disclosure.

Example 8A may include a signal encoded with data as described or related to any of Examples 1-23, or portions or portions thereof, or otherwise described in the present disclosure.

Example 9A may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of Examples 1-23, or with sections or parts thereof, or otherwise described in the present disclosure.

Example 10A may comprise an electromagnetic signal carrying computer-readable instructions, the execution of the computer-readable instructions by one or more processors serving to cause the one or more processors to use the method, techniques, or process according to any of Examples 1- 23 or parts thereof.

Example 1B may include a computer program that includes instructions, the execution of the program by a processing element serving to cause the processing element to use the method, technique, or process as described in or associated with any of Examples 1-23, or To carry out parts of it.

Example 1C may have a signal on a wireless network as shown and described herein.

Example 1D may include a method of communicating in a wireless network as illustrated and described herein.

Example 1E may include a system for providing wireless communication as illustrated and described herein.

Example 1F may include an apparatus for providing wireless communication as shown and described herein.

Each of the examples described above can be combined with any other example (or any combination of examples), unless expressly stated otherwise. The foregoing description of one or more embodiments is provided for purposes of illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or can be gained from practicing various embodiments.

terminology

As used herein, the term “circuit” refers to hardware components such as an electronic circuit, logic circuit, processor (shared, dedicated, or group) and / or memory (shared, dedicated or group), an application-specific integrated circuit (ASIC), a field-programmable component (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic component (PLD), a complex PLD (CPLD), a PLD with high Capacity (HCPLD), a structured ASIC or a programmable SoC), digital signal processors (DSPs), etc. that are set up to provide the functionality described. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least a portion of the functionality described. The term "circuit" can also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. According to these embodiments, the combination of hardware elements and program code can be referred to as a certain type of circuit.

As used herein, the term “processor circuit” refers to a circuit that is or is capable of sequentially and automatically executing a series of arithmetic or logical operations or recording, storing and / or transmitting digital data Part of it or has one. The processor circuit can have one or more processor cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" can refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core -Processor and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules and / or functional processes. The processing circuit can have further hardware accelerators, which can be microprocessors, programmable processing devices or the like. The one or more hardware accelerators can include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuits” and / or “baseband circuits” can be viewed as synonymous with “processor circuits” and can be designated as such.

As used herein, the term “interface circuit” refers to a circuit that enables the exchange of information between two or more components or devices, is part of them, or has such a circuit. The term “interface circuit” can refer to one or more hardware interfaces, e.g. buses, I / O interfaces, interfaces of peripheral components, network interface cards and / or the like.

As used herein, the term “user device” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources on a communication network. The term "user device" or "UE" can be used as a synonym for client, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio , reconfigurable mobile device, etc., and can be referred to as such. Additionally, the term “user device” or “UE” can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" can be used as a synonym for a networked computer, network hardware, network equipment, network node, router, switch, hub, bridge, wireless network control unit, RAN device, RAN node, gateway, server, virtualized VNF, NFVI and / or the like are considered and / or referred to.

As used herein, the term “computer system” refers to any type of interconnected electronic device, computing device, or component thereof. In addition, the term “computer system” and / or “system” can refer to various components of a computer that are communicatively coupled to one another. In addition, the term “computer system” and / or “system” can refer to a plurality of computer devices and / or a plurality of computer systems that are communicatively coupled to one another and are set up to share computer and / or network resources.

The term “device”, “computer device” or the like, as used here, refers to a computer device or computer system with program code (e.g. software or firmware) that is specifically designed to provide a particular computer resource. A “virtual device” is an image of a virtual machine that is created by a device equipped with a hypervisor is implemented that virtualizes or emulates a computing device or is otherwise intended to provide a particular computing resource.

The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment and / or a physical or virtual component within a specific device, such as computing devices, mechanical devices, storage space, processor / CPU -Time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network jacks, channel / link assignment, throughput, memory usage, storage, network, database and applications, workload units and / or the like. A “hardware resource” can refer to computing, storage and / or network resources provided by one or more physical hardware element (s). A “virtualized resource” can refer to computing, storage, and / or network resources provided by a virtualization infrastructure for an application, device, system, and so on. The term “network resource” or “communication resource” may refer to resources that computing devices / systems can access over a communication network. The term “system resources” can refer to any type of shared device that provides services and can include computer and / or network resources. System resources can be viewed as a set of interrelated functions, network data objects, or services accessible through a server, such system resources residing on a single host or multiple hosts and being uniquely identifiable.

The term “channel” as used here refers to any tangible or intangible transmission medium that is used to transmit data or a data stream. The term "channel" can be synonymous and / or synonymous with "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "connection", "data connection", "carrier", " Radio Frequency Carrier ”and / or any other similar term used to designate a path or medium over which data is transmitted. In addition, as used herein, the term “link” refers to a connection between two devices over a RAT for the purpose of transmitting and receiving information.

The terms "instantiating", "instantiating" and the like, as used here, refer to the creation of an instance. An “instance” also refers to a specific occurrence of an object, e.g. B. can occur during the execution of program code.

The terms “coupled”, “communicatively coupled” and their derivatives are used here. The term “coupled” can mean that two or more elements are in direct physical or electrical contact with one another, can mean that two or more elements are indirectly in contact with one another but still cooperate or interact with one another, and / or can mean that one or more other elements between the elements that are considered to be coupled, coupled or connected to one another. The term “directly coupled” can mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements can be in contact with one another via a communication medium, including via a wire or other connection link, via a wireless communication channel or link, and / or the like.

The term “information element” refers to a structure element that contains one or more fields. The term “field” refers to the individual content of an information element or to a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration that is set up with SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS / PBCH block.

The term "primary cell" refers to the MCG cell operating on the primary frequency on which the UE is either performing the initial connection establishment procedure or initiating the connection establishment procedure.

The term “primary SCG cell” refers to the SCG cell in which the UE carries out random access when it carries out the reconfiguration procedure with sync for DC operation.

The term “secondary cell” refers to a cell that provides additional radio resources in addition to a special cell for a UE established with CA.

The term "secondary cell group" refers to the subset of serving cells that the PSCell and zero or more secondary cells for a UE that is set up to deal with DC.

The term “serving cell” refers to the primary cell for a UE in RRC_CONNECTED that is not set up with CA / DC, there is only one serving cell that has the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells that includes the special cell (s) and all secondary cells for a UE in RRC_CONNECTED that is established with CA / DC.

The term “special cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise the term “special cell” refers to the Pcell.

While the above descriptions and accompanying figures depict electronic device components as separate items, those skilled in the art will appreciate the various possibilities for combining or integrating discrete items into a single item. This can include combining two or more circuits into a single circuit, mounting two or more circuits on a common chip or chassis to form an integrated element, executing discrete software components on a common processor core, and so on Those skilled in the art will recognize the possibility of dividing a single element into two or more discrete elements, such as: B. dividing a single circuit into two or more separate circuits, dividing a chip or chassis into discrete elements originally deployed on it, dividing a software component into two or more sections, and running each section on a separate processor core, etc.

It is believed that the implementations of the methods described herein are demonstrative in nature and are therefore understood to be capable of being implemented in accordance with the apparatus. It is also assumed that implementations of the devices described herein can be implemented as a corresponding method. It is therefore understood that an apparatus that corresponds to a method described herein can have one or more components that are configured to carry out every aspect of the corresponding method.

It is assumed that the implementations of the methods described herein are of a demonstrative nature and are therefore to be understood as being implementable in a corresponding device. It is also assumed that implementations of the devices described herein can be implemented as a corresponding method. It is therefore understood that an apparatus that corresponds to a method described herein can have one or more components that are configured to carry out every aspect of the corresponding method.

All acronyms defined in the above description also apply to all claims herein.

QUOTES INCLUDED IN THE DESCRIPTION

This list of the documents listed by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent literature cited

• US 62/978171 [0001]

Claims (20)

An apparatus for a new radio (NR) user equipment (UE) comprising circuitry that is set up: receive configuration information for a control resource group (CORESET) having a plurality of CORESETs; Receiving a transmission of the same physical downlink control channel (PDCCH) via one or more CORESETs within an established CORESET group; and Decoding of the PDCCH according to the configured configurations. The device according to Claim 1 , the configuration information having an indication of the precoding bundling via resource element groups (REG) of the CORESET group. The device according to Claim 2 , with precoding over physical resource blocks (PRBs) corresponding to the same REG bundle being the same. The device according to one of the Claims 1 until 3 wherein the CORESET group has all CORESETs within a slot or wherein the CORESET group has all CORESETs within a sub-frame. The device according to one of the Claims 1 until 4th , the configuration information having the same TCI status (transmission configuration indicator) for the plurality of CORESETs in the CORESET group. A device of a base station which is set up for operation in a network of the fifth generation (5G), the device having a circuit which is set up configure configuration information for a control resource set group (CORESET) having a plurality of CORESETs for transmission to a user equipment (UE); and to set up the same physical downlink control channel (PDCCH) via one or more CORESETs within the CORESET group for transmission to the UE based on the configuration information. The device according to Claim 6 , the configuration information having an indication of the precoding bundling via resource element groups (REG) bundles of the CORESET group. A device for a base station, comprising a circuit which is arranged to to generate one or more configuration messages that contain configuration information of the control resource unit (CORESET); transmit the one or more configuration messages to a user equipment (UE), wherein the CORESET configuration information is set up to configure a CORESET with two or more transmission configuration indicator states (TCI) or to configure two or more CORESETs with a TCI state. The device according to Claim 8 wherein the CORESET configuration information is used to set up a CORESET with two or more TCI states and a set of control channel elements (control channel elements, CCEs) corresponding to different levels of aggregation associated with different TCI states. The device according to Claim 8 , whereby the CORESET configuration information is used to link CCEs with TCI states for different aggregation levels. The device according to Claim 8 wherein the configuration information is used to set up the CORESET set up with two or more TCI states and sets of CCEs corresponding to a particular level of aggregation associated with different TCI states. The device according to Claim 11 , where the i-th CCE is associated with established TCI states according to the following equation: $$T\mathrm{C.}{\mathrm{I.}}_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}=\text{mod}\left(\lfloor i\frac{K}{N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}}\rfloor ,N_{T\mathrm{C.}\mathrm{I.},p}\right),i=\mathrm{0,}...,N_{\mathrm{C.}\mathrm{C.}\mathrm{E.},p}-\mathrm{1,}$$

where p is the index of CORESET, N _{CCE, p is} the total number of CCEs, N _{TCI, p is} the number of TCI states, and K is a predetermined parameter or is configured by one or more higher layers. A device for a new radio (NR) user equipment (UE) comprising a circuit which is arranged to establish one or more configuration messages to receive control resource set (CORESET) configuration information; Monitor downlink control information (DCI) on a downlink physical control channel (PDCCH) for control channel elements (CCEs), CCEs being associated with various transmission configuration indicator states (TCI) based on CORESET configuration information. The device according to Claim 13 , wherein the CORESET configuration information is used to configure two CORESETs with different TCI states, and the monitoring includes monitoring of the DCI transmission on CCEs which correspond to different CORESETs. The device according to Claim 13 , wherein the CORESET configuration information is set up to set up a user equipment-specific search space (USS) in such a way that it has CCEs from different CORESETs. The device according to Claim 13 wherein the CORESET configuration information is set up to set up a USS so that it has CCEs that correspond to CCEs of aggregation level L of each USS that corresponds to two CORESETs. The device according to Claim 16 , the CORESET configuration information serving to set up a plurality of UE-specific search spaces in the same slot. The device according to one of the Claims 8 - 13th wherein a REG-to-CCE (Resource-Element-Group-to-Control-Channel-Element) interleaver for the plurality of CORESETs in the CORESET group depends on an Orthogonal Frequency Division Multiplexing (OFCM) symbol index. The device according to Claim 18 , wherein the OFDM symbol index is defined within a slot or wherein the OFDM symbol is defined within a sub-frame. The device according to Claim 18 _{, where a parameter shift} for the CCE-to-REG interleaver is defined as n shift = 1 * N _ID , where the OFDM symbol index of the first CORESET symbol is within a slot or within a subframe or within a frame and $N_{\text{ID}}=N_{\text{ID}}^{\text{cell}}$

or another set parameter.

Images