Downlink transmission for high speed scenarios

Abstract

This document describes techniques related to downlink transmission for high-speed scenarios. In one embodiment, a method includes: decoding a Transport Configuration Indicator (TCI) configuration element (IE) associated with a Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first Non-Zero Power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-address (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; determining, based on the TCI configuration IE, that the Tracking Reference Signal (TRS) is associated with the PDSCH or PDCCH; determining parameters based on the TRS; and decoding the PDSCH or PDCCH based on the determined parameters. Other embodiments may be described and claimed.

Description

Technical Field

[0001] The various embodiments described herein generally relate to the field of wireless communication, and more specifically, to downlink transmission for high-speed scenarios. Background Technology

[0002] Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communication platforms. The next-generation wireless communication system, 5G (or New Radio (NR)), will enable a wide range of users and applications to access information and share data anytime, anywhere. NR promises to be a unified network / system designed to meet diverse and sometimes conflicting performance dimensions and services. These different, multi-dimensional requirements are driven by various services and applications. Generally, NR will be based on 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) - Advanced evolution, supplemented by potential new Radio Access Technologies (RATs), thereby enriching people's lives with better, simpler, and seamless wireless connectivity solutions. NR will enable everything to be wirelessly connected, providing fast, rich content and services. Attached Figure Description

[0003] The features and advantages of this disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings. Figure 1 The features of this disclosure are illustrated by way of example; and, wherein:

[0004] Figure 1 This is an illustration of a high-speed train (HST) deployment scenario based on an example.

[0005] Figure 2 This is a graph illustrating the block error rate (BLER) performance under different power offsets.

[0006] Figure 3 This is a diagram illustrating a single-frequency network (SFN) scheme based on a distributed reference signal, as shown in the example.

[0007] Figure 4 An example of two Transmission Configuration Indicator (TCI) status identifiers (IDs) associated with a demodulation reference signal (DM-RS) of a single code division multiplexing (CDM) group is shown according to an embodiment.

[0008] Figure 5 Examples of physical downlink shared channel (PDSCH) and demodulation reference signal (DM-RS) transmission with different numbers of multiple-input multiple-output (MIMO) layer / DM-RS ports are shown according to embodiments.

[0009] Figure 6 An example processing for downlink transmission in a high-speed scenario is shown according to some embodiments.

[0010] Figure 7 Another example of downlink transmission for high-speed scenarios is shown according to some embodiments.

[0011] Figure 8 Another example of downlink transmission for high-speed scenarios is shown according to some embodiments.

[0012] Figure 9 Another example of downlink transmission for high-speed scenarios is shown according to some embodiments.

[0013] Figure 10 Another example of downlink transmission for high-speed scenarios is shown according to some embodiments.

[0014] Figure 11 Networks according to various embodiments are shown.

[0015] Figure 12 A wireless network according to various embodiments is illustrated schematically.

[0016] Figure 13 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments.

[0017] Reference will now be made to the exemplary embodiments shown, and they will be described herein using specific language. However, it should be understood that this is not intended to limit the scope of the technology. Detailed Implementation

[0018] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details such as particular structures, architectures, interfaces, technologies, etc., are set forth for purposes of explanation and not limitation in order to provide a thorough understanding of various aspects of the claimed embodiments. However, it will be apparent to those skilled in the art that various aspects of the claimed embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of embodiments of this disclosure with unnecessary detail.

[0019] Various aspects of the illustrative embodiments will be described using terminology commonly employed by those skilled in the art to convey the essence of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced using only some of the aspects described. Specific figures, materials, and configurations are set forth for illustrative purposes to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced without these specific details. In other instances, well-known features have been omitted or simplified so as not to obscure the illustrative embodiments.

[0020] Furthermore, the various operations will be described sequentially as a plurality of discrete operations in a manner most conducive to understanding the illustrative embodiments. However, the order of description should not be construed as implying that these operations must depend on the order. In particular, these operations do not need to be performed in the order presented.

[0021] The phrases “in various embodiments,” “in some embodiments,” etc., are used repeatedly. This phrase does not usually refer to the same embodiment; however, it may refer to the same embodiment. Unless the context otherwise specifies, the terms “comprising,” “having,” and “including” are synonyms. The phrase “A or B” means (A), (B), or (A and B).

[0022] Example embodiments can be described as processes, depicted as flowcharts, diagrams, data flow diagrams, structural diagrams, or block diagrams. While flowcharts may describe operations as sequential processes, many operations can be executed in parallel, concurrently, or simultaneously. Furthermore, the order of operations can be rearranged. A process may terminate upon completion of its operations, but may also have additional operations not included in the figures. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function and / or the main function.

[0023] As used herein, the term "processor" refers to, or includes, circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations; recording, storing, and / or transferring digital data. The term "processor" can also 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 operating computer-executable instructions (e.g., program code, software modules, and / or function processing). As used herein, the term "interface" refers to, or includes, circuitry providing information exchange between two or more components or devices. The term "interface" can refer to one or more hardware interfaces (e.g., a bus, an input / output (I / O) interface, a peripheral component interface, etc.).

[0024] High-speed train (HST) scenarios can include transmissions from multiple remote radio heads (RRHs) (also known as next-generation node Bs (gNBs), or transmit-receive points (TRPs), or more generally, access nodes (ANs)) to user equipment (UEs) located in a fast-moving train. Figure 1 This is a diagram based on the example HST deployment scheme. (See diagram for example.) Figure 1 As depicted, a UE in a train can simultaneously receive communication from two or more adjacent RRHs placed along the railway. These RRHs can be connected to a central processing unit (CPU) using near-ideal backhaul links; therefore, such a deployment corresponds to a multi-TRP scenario.

[0025] In Rel-16, the New Radio (NR) defines support for enhanced transport schemes for multi-TRP deployment scenarios, as defined in Section 5.1 of 3GPP TS 38.214 V16.0.0 (December 2019). These transport schemes are designed to improve the reliability of downlink transmissions by using multiple TRPs. More specifically, additional macro diversity can be provided for downlink transmissions of scheduled transport blocks by dividing the allocated frequency or time resources among the TRPs. While the described transport schemes offer performance improvements for relatively low-coding-rate modulation and coding schemes (MCS) (typical for Ultra-Reliable Low-Latency Communication (URLLC), their robustness is insufficient for the general MCS supported by enhanced mobile broadband (eMBB) applications.

[0026] In particular, for scenarios with relatively large differences in reference signal received power (RSRP) between TRPs, the block error rate (BLER) performance will degrade significantly. Figure 2 This is a graph illustrating BLER performance under different power offsets. In comparison, transmission schemes based on single-frequency network (SFN) merging offer more stable performance due to merging gain.

[0027] However, it should be noted that frequency offset tracking becomes difficult in SFN transmission due to Doppler frequency shift. To address the frequency offset tracking problem, the following enhancements to the reference signal transmission are proposed. More specifically, the following candidate transmission schemes based on a distributed reference signal scheme can be considered [Intel, Views on the demodulation requirements for NRHST-SFN scenario, R4-1911003 (October 4, 2019)].

[0028] SFN+ Distributed TRS

[0029] ·SFN+ Distributed TRS and DM-RS

[0030] Figure 3 This is a diagram of an SFN scheme based on a distributed reference signal, as illustrated in the example. Figure 3 The left side illustrates an SFN+ distributed TRS transmission scheme based on an example. In this scheme, different Transmission Configuration Indicator (TCI) states can be assigned to different RRHs for the tracking process. The Physical Downlink Shared Channel (PDSCH), PDSCH Demodulation Reference Signal (DM-RS), and Physical Downlink Control Channel (PDCCH) can be transmitted in SFN mode. In this case, different TCI states can be used to configure different Tracking Reference Signals (TRS) for each RRH. Configuring different TRS resources for different RRHs gives the UE more ability to accurately track time and frequency offsets, especially in the typical case of frequency offset drift.

[0031] Figure 3 The right side illustrates an SFN+ distributed TRS and DM-RS transmission scheme based on an example. In this scheme, different TCI states can be assigned to different RRHs, and different PDSCH DM-RS antenna ports (APs) can be transmitted from different RRHs. PDSCH and PDCCH can be transmitted in SFN mode. In this scenario, since different PDSCH DM-RS APs with corresponding different TRS resources can be assigned to different RRHs, the UE can accurately estimate the propagation channel and channel characteristics for each RRH. Then, the UE can correctly reconstruct the SFN channel conditions and demodulate the data signal by combining the channel estimates from each RRH.

[0032] In this disclosure, signaling for facilitating distributed TRS transmission and distributed DM-RS transmission is proposed.

[0033] Quasi-co-located (QCL) signaling

[0034] 5G NR supports a special type of reference signal called a Tracking Reference Signal (TRS), which can be used to estimate Doppler frequency shift, timing offset, Doppler spread, and delay spread. The TRS can include the transmission of multiple Channel State Information Reference Signals (CSI-RS) resource configurations in different Orthogonal Frequency Division Multiplexing (OFDM) symbols in one or two time slots. Frequency offsets can be estimated by comparing received signals in different OFDM symbols and calculating the relative phase change divided by the time interval between corresponding symbols. Once the corresponding parameters are estimated, they can be passed to other reference signals, such as those used for transmitting PDSCH. More specifically, a connection can be established between a TRS and a scheduled DM-RS / PDSCH transmission using TCI signaling / indication. The TCI configuration can include an identity (ID) for identifying the corresponding TCI state and two QCL information entries (qcl-Type1 and qcl-Type2). Each QCL entry can include information about the serving cell and portion bandwidth (BWP), as well as the source reference signal and the type of QCL (which can be type A, type B, type C, or type D). Depending on the configured QCL type, the corresponding source reference signal can convey different information. For example, for TRS (NZP (Non-Zero Power) CSI-RS) with trs-Info configured, Type A QCL can be used, indicating that the Doppler shift, timing offset, Doppler spread, and delay spread estimated from the source TRS can be used for this TCI state. Generally, in some embodiments, QCL-Type A can indicate Doppler shift, Doppler spread, average delay, and delay spread; QCL-Type B can indicate Doppler shift and Doppler spread; QCL-Type C can indicate Doppler shift and average delay; and QCL-Type D can indicate spatial reception (Rx) parameters. Below is an example of a TCI state information element (IE).

[0035] TCI status information

[0036]

[0037] In some embodiments, to support PDSCH transmission in SFN mode with distributed TRS, the TCI associated with the PDSCH may include a first TRS configuration of qcl-Type1 (with NZP-CSI-RS-ResourceId1) and a second TRS of qcl-Type2 (with NZP-CSI-RS-ResourceId2), wherein the qcl-Type of both QCL-Infos is defined as "typeA". This TCI configuration can be supported for both PDSCH and PDCCH. Given the TRS configuration, the UE can estimate the corresponding parameters (including Doppler shift) provided by type A and apply the corresponding estimate for compensation.

[0038] In other embodiments, to support PDSCH transmission in an SFN mode with distributed TRS, a single code division multiplexing (CDM) group of DM-RS may indicate two TCI states, where, for the same TCI indication field sent in downlink control information (DCI), different TRSs are included in different TCI states. In this case, the high-layer parameter repSchemeEnabler may include the corresponding transmission scheme configuration. Figure 4 An example showing two TCI state IDs associated with a single CDM group of DM-RS is presented. From Figure 4 it can be seen that the resource element (RE) with a slanted pattern is a CDM group. This CDM group may be associated with two TCI states, such as TCI state ID = x and TCI state ID = y, and each state may include a TRS configuration. Therefore, the DM-RS sent in the CDM group may be associated with two TCI states. Those skilled in the art will understand that although in this example a single CDM group is associated with two TCI states, in some embodiments, a single CDM group may be associated with more than two TCI states.

[0039] QCL / TCI for Distributed DM-RS

[0040] To support distributed DM-RS, the association between DM-RS antenna ports and PDSCH antenna ports may be defined as follows.

[0041]

[0042] where υ is the number of multiple input multiple output (MIMO) layers, s , ,

[0044] , ,

[0043] , ,

[0042] ,

[0041] , (x) , , (y) ,

[0040] , (i) is the PDSCH symbol on MIMO layer 'x', p is the number of DM-RS antenna ports, d (y) (i) is the channel on DM-RS antenna port 'y', W(i) is the precoder from DM-RS to PDSCH, and i is the index of the PDSCH resource element. According to the current Rel-16 specification, there is a one-to-one mapping between PDSCH antenna ports and DM-RS antenna ports, that is, υ = p and W(i) = I.

[0043] In some embodiments, for distributed DM-RS, the number of DM-RS antenna ports may be greater than (or equal to) the number of MIMO layers, e.g., υ < p (or υ <= p). The precoder W(i) may change in a predetermined manner in the frequency domain and time domain. The actual value of W(i) may be determined according to the type I codebook of the NR specification corresponding to the sizes of υ and p.

[0044] For example, for a p=2 and υ=1 MIMO layer corresponding to two TRP / RRHs, the precoder can be derived from the codebook below containing four vectors (e.g., N=4).

[0045]

[0046] In the example, the precoding matrix W(i) can be fixed, or it can be a predetermined sequence that depends on the precoding resource block group (PRG) index and / or slot index with PDSCH transmission. For example, the index i′ of the precoder from the codebook can be derived as follows:

[0047] i′=mod(j+l,N)

[0048] Where j is, for example, the PRG index of the scheduled PDSCH, starting from reference point 0; l is the slot index of the scheduled PDSCH; and N is the number of precoders in the codebook used for precoder cycles.

[0049] In another example, the precoder index may depend only on the PRG index or only on the slot index. In yet another example, the precoder may be fixed at [1,…,1]. T .

[0050] Based on the measurements of the DM-RS antenna port and the precoding matrix W(i), the UE can derive the channel on the PDSCH antenna port using the formula above. Figure 5 An example of this embodiment is shown, in which two DM-RS ports and a PDSCH MIMO layer are used. Figure 5 As shown, two CDM groups can be configured on a subcarrier: a first CDM group and a second CDM group. The first CDM group can be associated with a first TCI state ID (e.g., y), and the second CDM group can be associated with a second TCI ID (e.g., x). That is, each DM-RS antenna port in different CDM groups has a TCI state ID associated with a single TRS.

[0051] Figure 6 An example processing 600 for downlink transmission in a high-speed scenario is illustrated according to some embodiments. Processing 600 can be performed by a user equipment (UE) or a portion thereof.

[0052] like Figure 6As shown, process 600 may begin at block 602: decoding a Transmission Configuration Indicator (TCI) configuration element (IE) associated with the Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A. In some embodiments, the TCI configuration IE may include an ID for identifying the TCI state, and type A may indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for that TCI state. This TCI configuration may be designed, for example, to facilitate an SFN+ distributed TRS scheme in a high-speed train (HST) scenario.

[0053] Process 600 may continue at block 604: determining the Tracking Reference Signal (TRS) associated with the PDSCH or PDCCH based on the TCI configuration IE. Process 600 may further include: at block 606, determining parameters based on the TRS. In some embodiments, the parameters may include one or more of Doppler frequency shift, timing offset, Doppler spread, or delay spread. In some embodiments, determining the parameters may include: estimating the frequency offset. Process 600 may further include: at block 608, decoding the PDSCH or PDCCH based on the determined parameters. In some embodiments, decoding the PDSCH or PDCCH may include: compensating for the frequency offset of the PDSCH or PDCCH based on the estimated frequency offset.

[0054] Figure 7 Another example of processing 700 for downlink transmission in high-speed scenarios is illustrated according to some embodiments. Processing 700 can be performed by a user equipment (UE) or a portion thereof.

[0055] like Figure 7 As shown, process 700 can begin at block 702: decoding configuration information used to associate multiple Transmission Configuration Indicator (TCI) states with a single Code Division Multiplexing (CDM) group of Demodulation Reference Signals (DM-RS), wherein, for the same TCI indication field transmitted in Downlink Control Information (DCI), multiple Tracking Reference Signals (TRS) are included in the corresponding multiple TCI states. This TCI configuration can be designed, for example, to facilitate an SFN+ distributed TRS scheme in a High-Speed ​​Train (HST) scenario.

[0056] Process 700 may continue at block 704: determining the association between the Tracking Reference Signal (TRS) and the Physical Downlink Shared Channel (PDSCH) based on configuration information. Process 700 may further include: at block 706, determining parameters based on the TRS. In some embodiments, the parameters may include one or more of Doppler frequency shift, timing offset, Doppler spread, or delay spread. In some embodiments, determining the parameters may include: estimating the frequency offset. Process 700 may further include: at block 708, decoding the PDSCH based on the determined parameters. In some embodiments, decoding the PDSCH may include: compensating for the frequency offset of the PDSCH based on the estimated frequency offset.

[0057] Figure 8 An example processing 800 for downlink transmission in a high-speed scenario is illustrated according to some embodiments. Processing 800 can be performed by a next-generation node B (gNB) or a portion thereof.

[0058] like Figure 8 As shown, process 800 may begin at block 802: generating a Transmission Configuration Indicator (TCI) configuration element (IE) associated with the Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH). The TCI configuration IE includes a first Tracking Reference Signal (TRS) configuration having a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A. In some embodiments, the TCI configuration IE may include an ID for identifying the TCI state, and type A may indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for that TCI state. This TCI configuration can be designed, for example, to facilitate an SFN+ distributed TRS scheme in a high-speed train (HST) scenario.

[0059] Processing 800 can continue at box 804: Encode the TCI configuration IE for transmission to the User Equipment (UE).

[0060] Figure 9 Another example of processing 900 for downlink transmission in high-speed scenarios is illustrated according to some embodiments. Processing 900 can be performed by a next-generation node B (gNB) or a portion thereof.

[0061] like Figure 9As shown, process 900 can begin at box 902: generating configuration information for associating multiple Transmission Configuration Indicator (TCI) states with a single Code Division Multiplexing (CDM) group of Demodulation Reference Signals (DM-RS), wherein, for the same TCI indication field transmitted in Downlink Control Information (DCI), multiple Tracking Reference Signals (TRS) are included in the corresponding multiple TCI states. This TCI configuration can be designed, for example, to facilitate an SFN+ distributed TRS scheme in a High-Speed ​​Train (HST) scenario.

[0062] Processing 900 can continue to box 904: Encoding the configuration information for transmission to the user equipment (UE).

[0063] Figure 10 Another example of a downlink transmission process 1000 for high-speed scenarios is illustrated according to some embodiments. Process 1000 can be performed by a next-generation node B (gNB) or a portion thereof.

[0064] like Figure 10 As shown, process 1000 may begin at block 1002: generating a demodulation reference signal (DM-RS). Process 1000 may further include: at block 1004, encoding the DM-RS for transmission using one or more antenna ports, wherein the number of antenna ports for the DM-RS is greater than the number of multiple-input multiple-output (MIMO) layers used for transmitting Physical Downlink Shared Channel (PDSCH) transmissions. In some embodiments, the number of antenna ports for the DM-RS may be greater than or equal to the number of MIMO layers used for PDCSH transmissions.

[0065] Figure 11-12 Various systems, devices, and components are shown that can implement aspects of the disclosed embodiments.

[0066] Figure 11 A network 1100 according to various embodiments is illustrated. Network 1100 can operate in a manner consistent with 3GPP technical specifications for LTE (Long Term Evolution) or 5G / NR (New Radio) systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0067] Network 1100 may include UE (User Equipment) 1102, which may include any mobile or non-mobile computing device designed to communicate with RAN (Radio Access Node) 1104 via an over-the-air connection. UE 1102 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment systems, in-vehicle entertainment devices, dashboards, head-up displays, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked devices, machine-type communication devices, M2M (machine-to-machine) or D2D (device-to-device) devices, IoT (Internet of Things) devices, etc.

[0068] In some embodiments, network 1100 may include multiple UEs directly coupled to each other via sidelink ports. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, including but not limited to PSBCH (Physical Sidelink Broadcast Channel), PSDCH (Physical Sidelink Discovery Channel), PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), etc.

[0069] In some embodiments, UE 1102 can also communicate with AP (Access Point) 1106 via an over-the-air connection. AP 1106 can manage WLAN connections and can be used to offload some / all network services from RAN 1104. The connection between UE 1102 and AP 1106 can comply with any IEEE 802.11 protocol, where AP 1106 can be Wireless Fibre Channel. Router. In some embodiments, UE 1102, RAN 1104, and AP 1106 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve RAN 1104 configuring UE 1102 to utilize both cellular radio resources and WLAN resources.

[0070] RAN 1104 may include one or more access nodes (ANs), such as AN 1108. AN 1108 can terminate the air interface protocol used by UE 1102 by providing access layer protocols including RRC (Radio Resource Control), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Media Access Control), and L1 (Layer 1) protocols. In this way, AN 1108 can establish a data / voice connection between CN (Core Network) 1120 and UE 1102. In some embodiments, AN 1108 can be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network, which may be referred to as CRAN (Cloud RAN) or a virtual baseband unit pool. AN 1108 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 1108 can be a macro cell base station, or a low-power base station used to provide a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macro cell.

[0071] In embodiments where RAN 1104 includes multiple ANs, they can be coupled to each other via an X2 interface (if RAN 1104 is an LTE RAN) or an Xn interface (if RAN 1104 is a 5G RAN). The X2 / Xn interfaces (which in some embodiments can be divided into a control plane interface and a user plane interface) allow ANs to pass information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0072] Each AN of RAN 1104 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 1102. UE 1102 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 1104. For example, UE 1102 and RAN 1104 can use carrier aggregation to allow UE 1102 to connect to multiple component carriers, each corresponding to a Pcell (primary cell) or Scell ​​(secondary cell). In a dual-connectivity scenario, the first AN can be the primary node providing the MCG (primary cell group), while the second AN can be the secondary node providing the SCG (secondary cell group). The first / secondary AN can be any combination of eNB, gNB, ng-eNB, etc.

[0073] RAN 1104 can provide an air interface on licensed or unlicensed spectrum. For operation in unlicensed spectrum, these nodes can use LAA, eLAA, and / or feLAA mechanisms based on CA (carrier aggregation) technology with PCell / Scell. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-Before-Speak (LBT) protocol.

[0074] In V2X scenarios, UE 1102 or AN 1108 can be or act as an RSU (Roadside Unit), which can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE can be called a "UE-type RSU," an RSU implemented in or by an eNB can be called an "eNB-type RSU," an RSU implemented in or by a gNB can be called a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UEs. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. An RSU can provide very low-latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, an RSU can provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0075] In some embodiments, RAN 1104 may be an LTE RAN 1110 with an eNB (e.g., eNB 1112). LTE RAN 1110 may provide an LTE air interface with the following characteristics: 15 kHz SCS (subcarrier spacing); CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; Turbo coding for data and TBCC for control; etc. At the UE, the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH DM-RS for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection. The LTE air interface may operate in the sub-6 GHz band.

[0076] In some embodiments, RAN 1104 may be an NG-RAN 1114 with a gNB (e.g., gNB 1116) or an ng-eNB (e.g., ng-eNB 1118). gNB 1116 can connect to a 5G-enabled UE using a 5G NR interface. gNB 1116 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 1118 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 1116 and ng-eNB 1118 can connect to each other via an Xn interface.

[0077] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface, which carries service data between the node of NG-RAN 1114 and UPF (User Plane Function) 1148 (e.g., N3 interface); and the NG control plane (NG-C) interface, which is the signaling interface between the node of NG-RAN 1114 and AMF (Access Management Function) 1144 (e.g., N2 interface).

[0078] NG-RAN 1114 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar codes, repetition codes, simplex codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface can rely on CSI-RS, PDSCH / PDCCH DM-RS. The 5G-NR air interface may not use CRS, but can use PBCH DM-RS for PBCH demodulation; PTRS for PDSCH phase tracking; and a tracking reference signal for time tracking. The 5G-NR air interface can operate in the FR1 band, including the sub-6GHz band, or in the FR2 band, including the band from 24.25GHz to 52.6GHz. The 5G-NR air interface may include an SSB (Synchronization Signal Block), which is an area in the downlink resource grid that includes the PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal), and PBCH (Physical Broadcast Channel).

[0079] In some embodiments, the 5G-NR air interface can utilize BWPs (Partial Bandwidth Packages) for various purposes. For example, BWPs can be used for dynamic adaptation of SCS (Self-Signal Classes). For instance, UE 1102 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 1102 for a change, the transmitted SCS is also changed. Another example of a BWP use case relates to power saving. Specifically, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 1102 to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs can be used for data transmission with low traffic loads while allowing power saving at UE 1102 (and in some cases at gNB 1116). A BWP containing more PRBs can be used for scenarios with high traffic loads.

[0080] RAN 1104 is communicatively coupled to CN (core network) 1120, which includes network elements for providing various functions to support data and telecommunications services to customers / subscribers (e.g., users of UE 1102). Components of CN 1120 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV (Network Functions Virtualization) may be used to virtualize any or all of the functions provided by the network elements of CN 1120 onto physical computing / storage resources such as servers, switches, etc. Logical instantiation of CN 1120 may be referred to as a network slice, and logical instantiation of a portion of CN 1120 may be referred to as a network subslice.

[0081] In some embodiments, CN 1120 may be LTE CN 1122, which may also be referred to as EPC (Evolved Packet Core). LTE CN 1122 may include MME (Mobility Management Entity) 1124, SGW (Serving Gateway) 1126, SGSN (Serving GPRS Support Node) 1128, HSS (Home Subscriber Server) 1130, PGW (PDN Gateway) 1132, and PCRF (Policy Control and Charging Rules Function) 1134, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the components of LTE CN 1122 can be briefly described below.

[0082] MME 1124 enables mobility management functions to track the current location of UE 1102 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0083] The SGW 1126 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN 1122. The SGW 1126 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include statutory interception, charging, and certain policy enforcement.

[0084] SGSN 1128 can track the location of UE 1102 and perform security functions and access control. Additionally, SGSN 1128 can perform: inter-EPC signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1124; MME selection for handover; etc. The S3 reference point between MME 1124 and SGSN 1128 enables the exchange of user and bearer information for mobility between 3GPP access networks in both idle and active states.

[0085] The HSS 1130 may include a database for network users, containing subscription-related information to support network entities in handling communication sessions. The HSS 1130 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependencies, etc. The S6a reference point between the HSS 1130 and the MME 1124 enables the transmission of subscription and authentication data for authenticating / authorizing user access to the LTE CN 1120.

[0086] The PGW 1132 may terminate its SGi interface toward a data network (DN) 1136, which may include an application / content server 1138. The PGW 1132 may route data packets between the LTE CN 1122 and the data network 1136. The PGW 1132 may be coupled to the SGW 1126 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1132 may also include nodes for policy enforcement and charging data collection (e.g., a PCEF (Policy and Charging Enforcement Function)). Additionally, the SGi reference point between the PGW 1132 and the data network 1136 may be, for example, an external public network, a private PDN, or an internal packet data network (PDN) for providing IMS services. The PGW 1132 may be coupled to the PCRF 1134 via a Gx reference point.

[0087] PCRF 1134 is the policy and charging control element of LTE CN 1122. PCRF 1134 can be communicatively coupled to app / content server 1138 to determine appropriate QoS and charging parameters for service flows. PCRF 1132 can assign associated rules to PCEF (via Gx reference point) through appropriate TFT and QCI.

[0088] In some embodiments, CN 1120 may be 5GC (5G Core Network) 1140. 5GC 1140 may include AUSF (Authentication Server Function) 1142, AMF (Access and Mobility Management Function) 1144, SMF (Session Management Function) 1146, UPF (User Plane Function) 1148, NSSF (Network Slice Selection Function) 1150, NEF (Network Open Function) 1152, NRF (NF Repository Function) 1154, PCF (Policy Control Function) 1156, UDM (Unified Data Management) 1158, and AF (Application Function) 1160, which are coupled to each other via interfaces (or "reference points") as shown. The functions of the components of 5GC 1140 are briefly described below.

[0089] The AUSF 1142 can store data used for authenticating the UE 1102 and handle authentication-related functions. The AUSF 1142 facilitates a common authentication framework for various access types. As shown in the figure, in addition to communicating with other components of the 5GC 1140 via a reference point, the AUSF 1142 can also demonstrate an interface based on Nausf services.

[0090] AMF 1144 allows other functions of 5GC 1140 to communicate with UE 1102 and RAN 1104 and subscribe to notifications of mobility events related to UE 1102. AMF 1144 can handle registration management (e.g., registering UE 1102), connection management, reachability management, mobility management, statutory interception of AMF-related events, and access authentication and authorization. AMF 1144 can provide the transmission of SM (Session Management) messages between UE 1102 and SMF 1146 and acts as a transparent broker for routing SM messages. AMF 1144 can also provide the transmission of SMS messages between UE 1102 and SMSF. AMF 1144 can interact with AUSF 1142 and UE 1102 to perform various security anchoring and context management functions. Furthermore, AMF 1144 can be the termination point of the RAN CP (control plane) interface, which may include or may be the N2 reference point between RAN1104 and AMF 1144; AMF 1144 can be the termination point of NAS (Non-Access Stratum) (N1) signaling and perform NAS encryption and integrity protection. AMF 1144 can also support NAS signaling with UE 1102 through the N3 IWF interface.

[0091] SMF 1146 can be responsible for SM (e.g., session establishment, tunnel management between UPF 1148 and AN 1108); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of service bootstrapping at UPF 1148 to route services to the correct destination; termination of the interface toward policy control functions; control of policy enforcement, accounting, and QoS as part of the process; statutory interception (for SM events and interfaces to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information, which is sent to AN 1108 via AMF 1144 through N2; and determining the SSC mode of the session. SM can refer to the management of the PDU session, and a PDU session or “session” can refer to the PDU connection service that provides or enables the exchange of PDUs between UE 1102 and data network 1136.

[0092] UPF 1148 can serve as an anchor point for mobility within and between RATs, an external PDU session point for interconnection to data network 1136, and a branch point supporting multi-homed PDU sessions. UPF 1148 can also perform packet routing and forwarding, perform packet inspection, enforce policy rules in the user plane portion, perform lawful packet interception (UP collection), perform service usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink service authentication (e.g., SDF-to-QoS flow mapping), perform transport layer packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1148 may include an uplink classifier to support routing service flows to the data network.

[0093] NSSF 1150 can select a set of network slice instances to serve UE 1102. If needed, NSSF 1150 can also determine the allowed NSSAI (Network Slice Selection Auxiliary Information) and the mapping to subscribed S-NSSAI (Individual NSSAI). NSSF 1150 can also determine the AMF set or candidate AMF list to be used to serve UE 1102 based on appropriate configuration and, possibly, by querying NRF 1154. The selection of a set of network slice instances for UE 1102 can be triggered by AMF 1144 registered to UE 1102 through interaction with NSSF 1150, which may result in a change of AMF. NSSF 1150 can interact with AMF 1144 via reference point N22; and can communicate with another NSSF in the visited network via reference point N31 (not shown). Additionally, NSSF 1150 can demonstrate the NNSSF service-based interface.

[0094] The NEF 1152 can securely expose the services and capabilities provided by 3GPP network functions to third parties, internal open / reopened AFs (e.g., AF 1160), edge computing, or fog computing systems. In these embodiments, the NEF 1152 can authenticate, authorize, or restrict AFs. The NEF 1152 can also translate information exchanged with the AF 1160 and information exchanged with internal network functions. For example, the NEF 1152 can translate between AF service identifiers and internal 5GC information. The NEF 1152 can also receive information from other NFs based on their open capabilities. This information can be stored as structured data at the NEF 1152 or stored in a data storage NF using a standardized interface. The NEF 1152 can then reopen the stored information to other NFs and AFs or use it for other purposes, such as analysis. Furthermore, the NEF 1152 can expose the Nnef's service-based interface.

[0095] NRF 1154 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 1154 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" can refer to the creation of an instance, while "instance" can refer to the actual occurrence of an object, which may happen, for example, during the execution of program code. Furthermore, NRF 1154 can demonstrate NRF service-based interfaces.

[0096] The PCF 1156 can provide policy rules to control plane functions for enforcement and also supports a unified policy framework for managing network behavior. The PCF 1156 can also implement a front-end for accessing subscription information related to policy decisions in the UDR (Unified Data Repository) of the UDM 1158. In addition to communicating with functions via reference points as shown in the figure, the PCF 1156 can also present an NPCF service-based interface.

[0097] UDM 1158 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 1102. For example, subscription data can be transferred between UDM 1158 and AMF1144 via the N8 reference point. UDM 1158 may include two parts: an application front-end and a UDR. The UDR can store subscription and policy data for UDM 1158 and PCF1156, and / or structured data (including PFDs (Packet Flow Descriptions) for application detection and application request information for multiple UEs 1102) for open and application data for NEF 1152. UDR 221 can expose a service-based interface to the Nudr to allow UDM 1158, PCF 1156, and NEF 1152 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. UDM may include a UDM-FE (front-end) responsible for handling credentials, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown in the figure, the UDM 1158 can also demonstrate a Nudm service-based interface.

[0098] The AF 1160 can provide application impact on service routing, provide access to NEF, and interact with the policy framework for policy control.

[0099] In some embodiments, 5GC 1140 can implement edge computing by selecting a point on the network to which UE 1102 is attached, where the operator / third-party service is geographically close. This can reduce latency and load on the network. To provide edge computing implementation, 5GC 1140 can select a UPF 1148 close to UE 1102 and perform service control from UPF 1148 to data network 1136 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1160. In this way, AF 1160 can influence UPF (re)selection and service routing. Based on operator deployment, when AF 1160 is considered a trusted entity, the network operator can allow AF 1160 to interact directly with the relevant NF. Furthermore, AF 1160 can expose a service-based interface of Naf.

[0100] Data network 1136 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers (including, for example, application / content server 1138).

[0101] Figure 12 A wireless network 1200 according to various embodiments is illustrated schematically. The wireless network 1200 may include a UE 1202 that communicates wirelessly with an AN 1204. The UE 1202 and the AN 1204 may be similar to components with similar names described elsewhere herein and are substantially interchangeable.

[0102] UE 1202 can be communicatively coupled to AN 1204 via connection 1206. Connection 1206 is shown as the air interface for implementing the communication coupling and can follow cellular communication protocols (e.g., LTE protocols) or operate on 5G NR at mmWave or sub-6GHz frequencies.

[0103] UE 1202 may include a host platform 1208 coupled to modem platform 1210. Host platform 1208 may include application processing circuitry 1212, which may be coupled to protocol processing circuitry 1214 of modem platform 1210. Application processing circuitry 1212 may run various applications for UE 1202 to source / sink application data. Application processing circuitry 1212 may also implement one or more layer operations for sending / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) operations and Internet (e.g., IP) operations.

[0104] Protocol processing circuitry 1214 can implement one or more layer operations to facilitate the transmission or reception of data through connection 1206. Layer operations implemented by protocol processing circuitry 1214 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0105] The modem platform 1210 may also include digital baseband circuitry 1216, which can implement one or more layer operations that are "lower" layer operations performed by protocol processing circuitry 1214 in the network protocol stack. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time coding, space-frequency coding, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0106] The modem platform 1210 may also include transmitting circuitry 1218, receiving circuitry 1220, RF circuitry 1222, and an RF front-end (RFFE) 1224, which may include or be connected to one or more antenna panels 1226. In short, transmitting circuitry 1218 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 1220 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 1222 may include a low-noise amplifier, power amplifier, power point tracking component, etc.; and RFFE (RF front-end) 1224 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components of transmitting circuitry 1218, receiving circuitry 1220, RF circuitry 1222, RFFE 1224, and antenna panels 1226 (collectively referred to as the "transmit / receive assembly") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at millimeter wave or sub-6 GHz frequencies, etc. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, or in the same or different chips / modules, etc.

[0107] In some embodiments, the protocol processing circuitry 1214 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting / receiving components.

[0108] UE reception can be established via and through antenna panel 1226, RFFE 1224, RF circuit 1222, receiving circuit 1220, digital baseband circuit 1216, and protocol processing circuit 1214. In some embodiments, antenna panel 1226 can receive transmissions from AN 1204 through receive beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 175.

[0109] UE transmission can be established via and through protocol processing circuitry 1214, digital baseband circuitry 1216, transmission circuitry 1218, RF circuitry 1222, RFFE 1224, and antenna panel 1226. In some embodiments, the transmission component of UE 1204 may apply spatial filtering to the data to be transmitted to form a transmission beam transmitted by the antenna elements of antenna panel 1226.

[0110] Similar to UE 1202, AN 1204 may include a host platform 1228 coupled to a modem platform 1230. Host platform 1228 may include application processing circuitry 1232 coupled to protocol processing circuitry 1234 of modem platform 1230. The modem platform may also include digital baseband circuitry 1236, transmit circuitry 1238, receive circuitry 1240, RF circuitry 1242, RFFE circuitry 1244, and antenna panel 1246. Components of AN 1204 may be similar to components with similar names in UE 1202 and are substantially interchangeable. In addition to performing data transmission / reception as described above, components of AN 1208 may also perform various logical functions, including, for example, RNC (Radio Network Control) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and packet scheduling.

[0111] Figure 13 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 13 The illustration shows a representation of hardware resource 1300, which includes one or more processors (or processor cores) 1310, one or more memory / storage devices 1320, and one or more communication resources 1330, each of which can be communicatively coupled via bus 1340 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1302 can be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 1300.

[0112] Processor 1310 may include, for example, processor 1312 and processor 1314. Processor 1310 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP (e.g., a baseband processor), an ASIC (Application-Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), a radio frequency integrated circuit (RFIC), another processor (including the processors discussed herein), or any suitable combination thereof.

[0113] The memory / storage device 1320 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1320 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0114] Communication resource 1330 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1304 or one or more databases 1306 via network 1308. For example, communication resource 1330 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, etc. (or low power consumption) ) components, Components and other communication components.

[0115] Instructions 1350 may include software, programs, applications, applets, or other executable code for causing at least any processor 1310 to perform any one or more of the methods discussed herein. Instructions 1350 may reside wholly or partially within at least one of the processor 1310 (e.g., within the processor's cache memory), memory / storage device 1320, or any suitable combination thereof. Furthermore, any portion of instructions 1350 may be transferred from any combination of peripheral device 1304 or database 1306 to hardware resource 1300. Therefore, the memory of processor 1310, memory / storage device 1320, peripheral device 1304, and database 1306 are examples of computer-readable and machine-readable media.

[0116] The following examples are further embodiments.

[0117] Example 1 is an apparatus for a user equipment (UE) comprising: one or more processors configured to: decode a Transport Configuration Indicator (TCI) configuration element (IE) received from a next-generation node B (gNB) and associated with a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first Non-Zero Power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; determine, based on the TCI configuration IE, that the Tracking Reference Signal (TRS) is associated with the PDSCH or the PDCCH; determine parameters based on the TRS; and decode the PDSCH or the PDCCH based on the determined parameters; and a memory configured to: store the first TRS configuration and the second TRS configuration.

[0118] Example 2 may include the subject of Example 1 or any other example in this document, wherein the TCI configuration IE includes an ID for identifying the TCI state, and wherein the type A is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

[0119] Example 3 may include the subject of Example 2 or any other example in this document, wherein the parameters include one or more of Doppler frequency shift, timing offset, Doppler spread, or delay spread.

[0120] Example 4 may include the subject of Example 1 or any other example in this document, wherein the TCI configuration IE is used to support PDSCH and PDCCH transmissions in a single-frequency network (SFN) mode with distributed TRS.

[0121] Example 5 may include the subject of Example 1 or any other example herein, wherein determining the parameters includes estimating the frequency offset, and wherein decoding the PDSCH or the PDCCH includes compensating for the frequency offset of the PDSCH or the PDCCH based on the estimation of the frequency offset.

[0122] Example 6 is an apparatus for a user equipment (UE) comprising: one or more processors configured to: decode configuration information received from a next-generation node B (gNB) for associating multiple Transport Configuration Indicator (TCI) states with a single code division multiplexing (CDM) group of demodulation reference signals (DM-RS), wherein multiple tracking reference signals (TRS) are included in corresponding multiple TCI states for the same TCI indication field transmitted in downlink control information (DCI); determine, based on the configuration information, that the tracking reference signals (TRS) are associated with a physical downlink shared channel (PDSCH); determine parameters based on the TRS; and decode the PDSCH based on the determined parameters; and a memory configured to: store the configuration information.

[0123] Example 7 may include the subject matter described in Example 6 or any other example herein, wherein a single CDM group of the DM-RS is associated with two TCI state IDs used to identify the TCI state.

[0124] Example 8 may include the subject of Example 7 or any other example in this document, wherein the TCI configuration IE is used to support PDSCH transmission in a single-frequency network (SFN) mode with two TRSs.

[0125] Example 9 may include the subject of Example 6 or any other example herein, wherein determining the parameters includes estimating the frequency offset, and wherein decoding the PDSCH includes compensating for the frequency offset of the PDSCH based on the estimation of the frequency offset.

[0126] Example 10 is an apparatus for a next-generation node B (gNB) comprising: a radio frequency (RF) interface; and one or more processors configured to: generate a Transport Configuration Indicator (TCI) configuration element (IE) associated with a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; and encode the TCI configuration IE for transmission to a user equipment (UE) via the RF interface.

[0127] Example 11 may include the subject of Example 10 or any other example herein, wherein the TCI configuration IE includes an ID for identifying the TCI state, and wherein the typeA is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

[0128] Example 12 may include the subject of Example 10 or any other example herein, wherein the TCI configuration IE is used to support PDSCH and PDCCH transmissions in a single-frequency network (SFN) mode with distributed TRS.

[0129] Example 13 is an apparatus for a next-generation node B (gNB) comprising: a radio frequency (RF) interface; and one or more processors configured to: generate configuration information that associates multiple Transmission Configuration Indicator (TCI) states with a single code division multiplexing (CDM) group of demodulation reference signals (DM-RS), wherein multiple tracking reference signals (TRS) are included in corresponding multiple TCI states for the same TCI indication field transmitted in downlink control information (DCI); and encode the configuration information for transmission to a user equipment (UE) via the RF interface.

[0130] Example 14 may include the subject of Example 13 or any other example herein, wherein a single CDM group of the DM-RS is associated with two TCI state IDs used to identify the TCI state.

[0131] Example 15 may include the subject of Example 14 or any other example in this document, wherein the TCI configuration IE is used to support PDSCH transmission in a single-frequency network (SFN) mode with two TRS.

[0132] Example 16 is a next-generation node B (gNB) apparatus comprising: a radio frequency (RF) interface; and one or more processors configured to: generate a demodulation reference signal (DM-RS); and encode the DM-RS for transmission via the RF interface using one or more antenna ports, wherein the number of antenna ports for the DM-RS is greater than the number of multiple-input multiple-output (MIMO) layers for transmitting physical downlink shared channel (PDSCH) transmissions.

[0133] Example 17 may include the subject of Example 16 or any other example herein, wherein the number of antenna ports for the DM-RS is greater than or equal to the number of MIMO layers for the PDCSH transmission.

[0134] Example 18 may include the subject of Example 16 or any other example herein, wherein the antenna port used for the DM-RS is associated with the antenna port used for the PDSCH transmission using the following formula:

[0135]

[0136] Where υ is the number of Multiple-Input Multiple-Output (MIMO) layers, s (x) (i) represents the PDSCH symbol on the MIMO layer 'x', p is the number of DM-RS antenna ports, and d (y) (i) is the channel on antenna port 'y' used for DM-RS, W(i) is the DM-RS to PDSCH precoder, and i is the index of the PDSCH resource element.

[0137] Example 19 may include the subject of Example 18 or any other example in this document, wherein W(i) is a precoder of type I codebook.

[0138] Example 20 may include the subject of Example 18 or any other example in this document, wherein W(i) is fixed.

[0139] Example 21 may include the topic of Example 20 or any other example in this document, wherein W(i) is fixed as [1,…,1]. T .

[0140] Example 22 may include the subject of Example 18 or any other example herein, wherein W(i) is a predetermined sequence based on the precoded resource block group PRG index and slot index with PDSCH transmission.

[0141] Example 23 may include the subject of Example 22 or any other example in this paper, wherein the precoder index i′ from the codebook for W(i) is derived as follows: i′ = mod(j+l,N), where j is the PRG index of the scheduled PDSCH, l is the slot index of the scheduled PDSCH, and N is the number of precoders in the codebook used for the precoder cycle.

[0142] Example 24 may include the subject of Example 18, wherein the W(i) is a predetermined sequence based on a precoded resource block group (PRG) index or a slot index with PDSCH transmission.

[0143] Example 25 may include the subject of Example 16 or any other example herein, wherein the gNB operates using distributed DM-RS transport.

[0144] Example 26 is a method to be performed at a user equipment (UE), the method comprising: decoding a Transport Configuration Indicator (TCI) configuration element (IE) received from a next-generation node B (gNB) and associated with a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first Non-Zero Power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; determining, based on the TCI configuration IE, that the Tracking Reference Signal (TRS) is associated with the PDSCH or the PDCCH; determining parameters based on the TRS; and decoding the PDSCH or the PDCCH based on the determined parameters.

[0145] Example 27 may include the subject of Example 26 or any other example herein, wherein the TCI configuration IE includes an ID for identifying the TCI state, and wherein the typeA is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

[0146] Example 28 may include the subject of Example 27 or any other example in this document, wherein the parameters include one or more of Doppler frequency shift, timing offset, Doppler spread, or delay spread.

[0147] Example 29 may include the subject of Example 26 or any other example herein, wherein the TCI configuration IE is used to support PDSCH and PDCCH transmissions in a single-frequency network (SFN) mode with distributed TRS.

[0148] Example 30 may include the subject of Example 26 or any other example herein, wherein determining parameters includes estimating the frequency offset, and wherein decoding the PDSCH or the PDCCH includes compensating for the frequency offset of the PDSCH or the PDCCH based on the estimation of the frequency offset.

[0149] Example 31 is a method to be performed at a user equipment (UE), the method comprising: decoding configuration information received from a next-generation node B (gNB) for associating multiple Transport Configuration Indicator (TCI) states with a single code division multiplexing (CDM) group of demodulation reference signals (DM-RS), wherein multiple tracking reference signals (TRS) are included in corresponding multiple TCI states for the same TCI indication field transmitted in downlink control information (DCI); determining, based on the configuration information, that the tracking reference signals (TRS) are associated with a physical downlink shared channel (PDSCH); determining parameters based on the TRS; and decoding the PDSCH based on the determined parameters.

[0150] Example 32 may include the subject matter described in Example 31 or any other example herein, wherein a single CDM group of the DM-RS is associated with two TCI state IDs used to identify the TCI state.

[0151] Example 33 may include the subject of Example 32 or any other example herein, wherein the TCI configuration IE is used to support PDSCH transmission in a single-frequency network (SFN) mode with two TRSs.

[0152] Example 34 may include the subject of Example 31 or any other example herein, wherein determining the parameters includes estimating the frequency offset, and wherein decoding the PDSCH includes compensating for the frequency offset of the PDSCH based on the estimation of the frequency offset.

[0153] Example 35 is a method to be performed at a next-generation node B (gNB), the method comprising: generating a Transport Configuration Indicator (TCI) configuration element (IE) associated with a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first Non-Zero Power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; and encoding the TCI configuration IE for transmission to a User Equipment (UE).

[0154] Example 36 may include the subject of Example 35 or any other example herein, wherein the TCI configuration IE includes an ID for identifying the TCI state, and wherein the typeA is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

[0155] Example 37 may include the subject of Example 35 or any other example herein, wherein the TCI configuration IE is used to support PDSCH and PDCCH transmissions in a single-frequency network (SFN) mode with distributed TRS.

[0156] Example 38 is a method to be performed at a next-generation node B (gNB), the method comprising: generating configuration information that associates multiple Transport Configuration Indicator (TCI) states with a single code division multiplexing (CDM) group of demodulation reference signals (DM-RS), wherein multiple tracking reference signals (TRS) are included in corresponding multiple TCI states for the same TCI indication field transmitted in downlink control information (DCI); and encoding the configuration information for transmission to a user equipment (UE).

[0157] Example 39 may include the subject of Example 38 or any other example herein, wherein a single CDM group of the DM-RS is associated with two TCI state IDs used to identify the TCI state.

[0158] Example 40 may include the subject of Example 39 or any other example herein, wherein the TCI configuration IE is used to support PDSCH transmission in a single-frequency network (SFN) mode with two TRSs.

[0159] Example 41 is a method to be performed at a next-generation node B (gNB), the method comprising: generating a demodulation reference signal (DM-RS); and encoding the DM-RS for transmission using one or more antenna ports, wherein the number of antenna ports for the DM-RS is greater than the number of multiple-input multiple-output (MIMO) layers for transmitting physical downlink shared channel (PDSCH) transmissions.

[0160] Example 42 may include the subject of Example 41 or any other example herein, wherein the number of antenna ports for the DM-RS is greater than or equal to the number of MIMO layers for the PDCSH transmission.

[0161] Example 43 may include the subject matter of Example 41 or any other example herein, wherein the antenna port used for the DM-RS is associated with the antenna port used for the PDSCH transmission using the following formula:

[0162]

[0163] Where υ is the number of Multiple-Input Multiple-Output (MIMO) layers, s (x) (i) represents the PDSCH symbol on the MIMO layer 'x', p is the number of DM-RS antenna ports, and d (y)(i) is the channel on antenna port 'y' used for DM-RS, W(i) is the DM-RS to PDSCH precoder, and i is the index of the PDSCH resource element.

[0164] Example 44 may include the subject of Example 43 or any other example in this document, wherein W(i) is a precoder of type I codebook.

[0165] Example 45 may include the subject of Example 43 or any other example in this document, wherein W(i) is fixed.

[0166] Example 46 may include the topic of Example 45 or any other example in this document, wherein W(i) is fixed as [1,…,1]. T .

[0167] Example 47 may include the subject of Example 43 or any other example herein, wherein W(i) is a predetermined sequence based on the precoded resource block group PRG index and slot index with PDSCH transmission.

[0168] Example 48 may include the subject of Example 47 or any other example in this paper, wherein the precoder index i′ from the codebook for W(i) is derived as follows: i′ = mod(j+l,N), where j is the PRG index of the scheduled PDSCH, l is the slot index of the scheduled PDSCH, and N is the number of precoders in the codebook used for the precoder cycle.

[0169] Example 49 may include the subject of Example 43, wherein the W(i) is a predetermined sequence based on a precoded resource block group (PRG) index or a slot index with PDSCH transmission.

[0170] Example 50 may include the subject of Example 41 or any other example herein, wherein the gNB operates using distributed DM-RS transport.

[0171] Example 51 is a machine-readable medium storing instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: decode a Transport Configuration Indicator (TCI) configuration element (IE) received from a next-generation node B (gNB) and associated with a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; determine, based on the TCI configuration IE, that the Tracking Reference Signal (TRS) is associated with the PDSCH or the PDCCH; determine parameters based on the TRS; and decode the PDSCH or the PDCCH based on the determined parameters.

[0172] Example 52 may include the subject of Example 51 or any other example herein, wherein the TCI configuration IE includes an ID for identifying the TCI state, and wherein the typeA is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

[0173] Example 53 may include the subject of Example 52 or any other example herein, wherein the parameters include one or more of Doppler frequency shift, timing offset, Doppler spread, or delay spread.

[0174] Example 54 may include the subject of Example 51 or any other example herein, wherein the TCI configuration IE is used to support PDSCH and PDCCH transmissions in a single-frequency network (SFN) mode with distributed TRS.

[0175] Example 55 may include the subject of Example 51 or any other example herein, wherein determining the parameters includes estimating the frequency offset, and wherein decoding the PDSCH or the PDCCH includes compensating for the frequency offset of the PDSCH or the PDCCH based on the estimation of the frequency offset.

[0176] Example 56 is a machine-readable medium storing instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: decode configuration information received from a next-generation node B (gNB) for associating multiple Transport Configuration Indicator (TCI) states with a single code division multiplexing (CDM) group of demodulation reference signals (DM-RS), wherein multiple tracking reference signals (TRS) are included in corresponding multiple TCI states for the same TCI indication field transmitted in downlink control information (DCI); determine, based on the configuration information, that the tracking reference signals (TRS) are associated with a physical downlink shared channel (PDSCH); determine parameters based on the TRS; and decode the PDSCH based on the determined parameters.

[0177] Example 57 may include the subject matter described in Example 56 or any other example herein, wherein a single CDM group of the DM-RS is associated with two TCI state IDs used to identify the TCI state.

[0178] Example 58 may include the subject of Example 57 or any other example in this document, wherein the TCI configuration IE is used to support PDSCH transmission in a single-frequency network (SFN) mode with two TRSs.

[0179] Example 59 may include the subject of Example 56 or any other example herein, wherein determining the parameters includes estimating the frequency offset, and wherein decoding the PDSCH includes compensating for the frequency offset of the PDSCH based on the estimation of the frequency offset.

[0180] Example 60 is a machine-readable medium storing instructions that, when executed by one or more processors of a next-generation node B (gNB), cause the gNB to: generate a Transport Configuration Indicator (TCI) configuration element (IE) associated with a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH), the TCI configuration IE including a first Tracking Reference Signal (TRS) configuration having a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A; and encode the TCI configuration IE for transmission to a user equipment (UE).

[0181] Example 61 may include the subject of Example 60 or any other example herein, wherein the TCI configuration IE includes an ID for identifying the TCI state, and wherein the type A is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

[0182] Example 62 may include the subject of Example 60 or any other example herein, wherein the TCI configuration IE is used to support PDSCH and PDCCH transmissions in a single-frequency network (SFN) mode with distributed TRS.

[0183] Example 63 is a machine-readable medium storing instructions that, when executed by one or more processors of a next-generation node B (gNB), cause the gNB to: generate configuration information that associates multiple Transport Configuration Indicator (TCI) states with a single code division multiplexing (CDM) group of demodulation reference signals (DM-RS), wherein, for the same TCI indication field transmitted in downlink control information (DCI), multiple tracking reference signals (TRS) are included in the corresponding multiple TCI states; and encode the configuration information for transmission to a user equipment (UE).

[0184] Example 64 may include the subject of Example 63 or any other example herein, wherein a single CDM group of the DM-RS is associated with two TCI state IDs used to identify the TCI state.

[0185] Example 65 may include the subject of Example 64 or any other example herein, wherein the TCI configuration IE is used to support PDSCH transmission in a single-frequency network (SFN) mode with two TRSs.

[0186] Example 66 is a machine-readable medium storing instructions that, when executed by one or more processors of a next-generation node B (gNB), cause the gNB to: generate a demodulation reference signal (DM-RS); and encode the DM-RS for transmission using one or more antenna ports, wherein the number of antenna ports for the DM-RS is greater than the number of multiple-input multiple-output (MIMO) layers used for transmitting physical downlink shared channel (PDSCH) transmissions.

[0187] Example 67 may include the subject of Example 66 or any other example herein, wherein the number of antenna ports for the DM-RS is greater than or equal to the number of MIMO layers for the PDCSH transmission.

[0188] Example 68 may include the subject of Example 66 or any other example herein, wherein the antenna port used for the DM-RS is associated with the antenna port used for the PDSCH transmission using the following formula:

[0189]

[0190] Where υ is the number of Multiple-Input Multiple-Output (MIMO) layers, s (x) (i) represents the PDSCH symbol on the MIMO layer 'x', p is the number of DM-RS antenna ports, and d (y) (i) is the channel on antenna port 'y' used for DM-RS, W(i) is the DM-RS to PDSCH precoder, and i is the index of the PDSCH resource element.

[0191] Example 69 may include the subject of Example 68 or any other example in this document, wherein W(i) is a precoder of type I codebook.

[0192] Example 70 may include the subject of Example 68 or any other example in this document, wherein W(i) is fixed.

[0193] Example 71 may include the topic of Example 70 or any other example in this document, wherein W(i) is fixed as [1,…,1]. T .

[0194] Example 72 may include the subject of Example 68 or any other example herein, wherein W(i) is a predetermined sequence based on the precoded resource block group PRG index and slot index with PDSCH transmission.

[0195] Example 73 may include the subject of Example 72 or any other example in this paper, wherein the precoder index i′ from the codebook for W(i) is derived as follows: i′ = mod(j + l, N), where j is the PRG index of the scheduled PDSCH, l is the slot index of the scheduled PDSCH, and N is the number of precoders in the codebook used for the precoder cycle.

[0196] Example 74 may include the subject of Example 68, wherein the W(i) is a predetermined sequence based on a precoded resource block group (PRG) index or a slot index with PDSCH transmission.

[0197] Example 75 may include the subject of Example 66 or any other example herein, wherein the gNB operates using distributed DM-RS transport.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising: One or more processors are configured as follows: The Transmission Configuration Indicator (TCI) configuration cells (IEs) received from the next-generation node B (gNB) and associated with the Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH) are decoded. The TCI configuration IE includes a first Tracking Reference Signal (TRS) configuration with a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-location (QCL) type value set to type A, and a second TRS configuration with a second NZP-CSI-RS resource ID and a QCL type value set to type A. Based on the TCI configuration IE, determine that the first TRS and the second TRS are associated with the PDSCH or the PDCCH; Parameters are determined based on the first TRS and the second TRS; as well as Based on the determined parameters, the PDSCH or the PDCCH is decoded; and The memory is configured to store the first TRS configuration and the second TRS configuration. The parameters include one or more of Doppler frequency shift, timing offset, Doppler spread, or delay spread. The parameters to be determined include: the estimated frequency shift, and Decoding the PDSCH or PDCCH includes: compensating for the frequency offset of the PDSCH or PDCCH based on an estimate of the frequency offset; The one or more processors are further configured to: Receive a first code division multiplexing (CDM) group of demodulation reference signal (DM-RS) on the PDSCH from a first transmit-receive point (TRP), and a second CDM group of the DM-RS on the PDSCH from a second TRP, wherein the first CDM group is associated with the first TRS and the second CDM group is associated with the second TRS. The DM-RS transmitted in the first CDM group and the second CDM group demodulates the data signal carried by the PDSCH.

2. The apparatus according to claim 1, wherein, The TCI configuration IE includes an ID for identifying the TCI state, wherein the typeA is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

3. The apparatus according to claim 1, wherein, The TCI configuration IE is used to support PDSCH and PDCCH transmission in Single Frequency Network (SFN) mode with distributed TRS.

4. An apparatus for a next-generation node B (gNB), the apparatus comprising: Radio frequency (RF) interface; and One or more processors are configured as follows: Generate a Transmission Configuration Indicator (TCI) configuration element (IE) associated with the Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH). The TCI configuration IE includes a first Tracking Reference Signal (TRS) configuration having a first non-zero power Channel State Information Reference Signal (NZP-CSI-RS) resource identity (ID) and a Quasi-Co-address (QCL) type value set to type A, and a second TRS configuration having a second NZP-CSI-RS resource ID and a QCL type value set to type A. as well as The TCI configuration IE is encoded for transmission to the user equipment (UE) via the RF interface. The one or more processors are further configured to: A first code division multiplexing (CDM) group for generating a demodulation reference signal (DM-RS) and a second CDM group for the DM-RS, wherein the first CDM group is associated with the first TRS and the second CDM group is associated with the second TRS; The first CDM group is transmitted on the PDSCH from the first Transmitting and Receiving Point (TRP), and the second CDM group is transmitted on the PDSCH from the second TRP.

5. The apparatus according to claim 4, wherein, The TCI configuration IE includes an ID for identifying the TCI state, wherein the typeA is used to indicate that Doppler frequency shift, timing offset, Doppler spread, or delay spread can be used for the TCI state.

6. The apparatus according to claim 4, wherein, The TCI configuration IE is used to support PDSCH and PDCCH transmission in Single Frequency Network (SFN) mode with distributed TRS.

Images