CSI-RS Sequence Generation and Mapping and DMRS Scrambling ID Configuration

Abstract

In some embodiments, an apparatus of a fifth generation (5G) node B (gNB) includes one or more baseband processors to encode one or more channel state information reference signals (CSI-RS) to be transmitted to a user equipment (UE). The one or more CSI-RS signals include complex sequences mapped to resource elements (REs) such that all CSI-RS ports use the same sequence for one or more of the CSI-RS signals in a symbol. In other embodiments, the gNB includes one or more baseband processors for encoding a scrambling identity (ID) configuration for one or more demodulation reference signals (DMRS), where the scrambling ID configuration indicates one of two scrambling IDs to be signaled to the UE.

Description

Background Art

[0001] In a radio system, a Multiple-Input Multiple-Output (MIMO) system relies on multiple transmit (Tx) antennas and receive (Rx) antennas to provide spatial diversity, multiplexing, and array gain in the downlink channel and the uplink channel. In the downlink, the transmitter can improve performance by using the channel state information (CSI) about the downlink channel observed by the receiver. The CSI can be obtained by the transmitter from the receiver through the estimation of the uplink channel and by using the channel reciprocity of the wireless channel, or from the quantized feedback measured by the receiver.

[0002] Channel State Information Reference Signal (CSI-RS) is a reference signal that supports many functions in NR, including channel measurements for CSI calculation. Demodulation Reference Signal (DMRS) is a user-specific reference signal that can be used for channel estimation for physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) data demodulation. In Release 15 of the New Radio (NR) standard, DMRS is generated using a length-31 Gold sequence similar to the Long-Term Evolution (LTE) standard. The initialization of the Gold sequence involves the configuration of a 16-bit user-specific scrambling identifier ID to randomize interference and reduce the cross-correlation between different DMRS sequences. In the NR standard, each user can configure two such scrambling IDs. Brief Description of the Drawings

[0003] The subject matter claimed is particularly pointed out and distinctly claimed in the concluding portion of this specification. However, such subject matter can be understood when read in conjunction with the following detailed description, where:

[0004] Figure 1 is an illustration of a 5th Generation (5G) New Radio (NR) access network in which Channel State Information Reference Signal (CSI-RS) can be utilized, according to one or more embodiments;

[0005] Figure 2 is an illustration of a process for scrambling ID configuration for Demodulation Reference Signal (DMRS), according to one or more embodiments.

[0006] Figure 3 illustrates the architecture of a system of a network, according to some embodiments.

[0007] Figure 4 illustrates exemplary components of a device, according to some embodiments.

[0008] Figure 5 illustrates an exemplary interface of a baseband circuit, according to some embodiments.

[0009] It should be understood that, for simplicity and / or clarity of illustration, the components illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some components may be exaggerated relative to other components for clarity. Additionally, if deemed appropriate, reference numerals are repeated in the figures to indicate corresponding and / or similar components. Detailed Description

[0010] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will understand that the claimed subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components, and / or circuits have not been described in detail.

[0011] Now referring Figure 1 , an illustration of a fifth generation (5G) new radio (NR) access network in which channel state information reference signals (CSI-RS) may be utilized will be discussed in accordance with one or more embodiments. As Figure 1 shown, a fifth generation (5G) new radio (NR) access network 100 may include a 5G node B (gNB) 112 to communicate with one or more user equipment (UE) devices 110 to receive messages and / or data in a downlink 114 and to send messages and / or data to the gNB 112 in an uplink 116. In one or more embodiments, the UE 110 may receive measurement configuration information such as MeasObjectNR as a radio resource control (RRC) message in the downlink 114 from the gNB 112 to configure the UE 110 to perform reference signal received power (RSRP) or reference signal received quality (RSRQ) measurements on a neighboring or target cell (not shown), e.g., via a channel state information reference signal (CSI-RS) transmitted by the neighboring or target cell 114. The RSRP is the average power of the resource elements (REs) of the cell-specific reference signal (RS) over the entire bandwidth. The RSRP is measured in the symbols carrying the cell-specific reference signal (RS). The UE 110 measures the power of a plurality of resource elements (REs) carrying the reference signal (RS) and then averages the power over the measured REs.

[0012] According to one or more embodiments, CSI-RS sequence generation and its mapping to physical resource elements for NR are provided. The design used by the access network 100 may support more than one complex symbol per physical resource block orthogonal frequency division multiplexing (OFDM) symbol while using the same sequence for all CSI-RS ports in the symbol. The CSI-RS resources are described in the 3GPP new radio version 15 in the 3GPP technical specification (TS) 38.211 V1.3.0 (2017-12) as follows.

[0013] 1. CSI-RS Resources

[0014] The CSI-RS resources for X = {1, 2, 4, 8, 12, 16, 24, 32} ports are composed of a combination of one or more CSI-RS components. The CSI-RS resource components in a PRB consist of adjacent Y resource elements in frequency and Z adjacent resource elements in time domain. The possible value pairs of (Y, Z) = {(2, 1), (4, 1), (2, 2)}. The possible combinations of the CSI-RS resource components that make up the X-port CSI-RS resources are described in Table 1. The time domain positions l0 and l1 are defined relative to the starting position of the CSI-RS resources within the time slot configured by a higher layer parameter The frequency domain position k of the CSI-RS resource component i is given by a bitmap provided by a higher layer parameter. The value k in Table 1 i corresponds to the i-th set bit starting from b0 in the bitmap, where the bitmap and the value k i are given by the following formula

[0015] - For the first row of Table 1, [b3…b0], k i = f(i)

[0016] - For the second row of Table 1, [b 11 …b0], k i = f(i)

[0017] - For the fourth row of Table 1, [b2…b0], k i = 4 f(i)

[0018] - For all other cases, [b5…b0], k i = 2 f(i)

[0019] where f(i) is the bit number of the i-th set bit in the bitmap

[0020] 2. Sequence Generation

[0021] The UE shall assume that the reference signal sequence r(m) is defined by the following formula

[0022]

[0023] where in the case where the pseudo-random sequence c(i) is defined in Clause 5.2.1[1], the pseudo-random sequence generator shall be initialized using the following formula

[0024] c init = (2 10 ·(14n s，f + l + 1)(2n ID + 1)+ n ID ) mod 231

[0025] At the start of each OFDM symbol, where n s,f is the slot number within a radio frame, l is the OFDM symbol number within a slot, and n ID equals the higher layer parameter ScramblingID.

[0026] In addition to the above CSI-RS details reviewed from NR Rel-15, we agree that 3GPP RAN1 conforms to #91[2], for one OFDM symbol, the CSI-RS sequence is the same for all ports, and each symbol supports more than one complex symbol per PRB. Considering these constraints, we propose the subsequent RE mapping of the CSI-RS sequence.

[0027] For X = 1, port CSI-RS resources,

[0028]

[0029]

[0030]

[0031] For X > 1, port CSI-RS resources,

[0032]

[0033]

[0034]

[0035] where m' is an integer corresponding to the occupied PRB. For non-zero power CSI-RS, the UE shall assume β CSIRS > 0, where β CSIRS is selected such that the power offset specified by the higher layer parameter (if provided) is satisfied. The quantities k′, l′, w f (k′) and w t (l′) are given in Tables 1 to 5 below.

[0036]

[0037] Table 1: CSI-RS positions within a slot.

[0038] Index <![CDATA[w f (k′)]]> <![CDATA[w t (l′)]]> 0 1 1

[0039] Table 2: Sequences w f (k′) and w t (l′) equal "no CDM"

[0040] Index <![CDATA[w f (k′)]]> <![CDATA[w t (l′)]]> 0 [+1 +1] 1 1 [+1 -1] 1

[0041] Table 3: Sequence w of CDM type f (k′) and w t (l′) is equal to "FD-CDM2"

[0042] Index <![CDATA[w f (k′)]]> <![CDATA[w t (l′)]]> 0 [+1 +1] [+1 +1] 1 [+1 -1] [+1 +1] 2 [+1 +1] [+1 -1] 3 [+1 -1] [+1 -1]

[0043] Table 4: Sequence w of CDM type f (k′) and w t (l′) is equal to "CDM4"

[0044] Index <![CDATA[w f (k′)]]> <![CDATA[w t (l′)]]> 0 [+1 +1] [+1 +1 +1 +1] 1 [+1 -1] [+1 +1 +1 +1] 2 [+1 +1] [+1 -1 +1 -1] 3 [+1 -1] [+1 -1 +1 -1] 4 [+1 +1] [+1 +1 -1 -1] 5 [+1 -1] [+1 +1 -1 -1] 6 [+1 +1] [+1 -1 -1 +1] 7 [+1 -1] [+1 -1 -1 +1]

[0045] Table 5: Sequence w of CDM type f (k′) and w t (l′) is equal to "CDM8"

[0046] Now refer to Figure 2 , a flowchart of a process for scrambling ID configuration for demodulation reference signal (DMRS) according to one or more embodiments will be discussed. As Figure 2 shown, the flowchart illustrates signaling to a user the selection of a configured scrambling identifier (ID) using two options below. In the first option, the selection of the scrambling ID is configured by transmitting a scrambling ID configuration 310 from gNB 112 to UE 110 using a transmission configuration indication (TCI) state as part of a synchronization signal block (SSB) or as part of a channel state information reference signal (CSI-RS) configuration. In the second option, the selection of the scrambling ID is configured by transmitting a scrambling ID configuration 310 from gNB 112 to UE 110 using explicit downlink control information (DCI) signaling to select one of the scrambling IDs. The selected scrambling ID can then be used to transmit DMRS signals in a physical downlink shared channel (PDSCH) 314 and a physical uplink shared channel (PUSCH) 316, for example for data demodulation.

[0047] DMRS Generation

[0048] For the new radio (NR) Release 15 demodulation reference signal (DMRS) design, it was agreed in RAN1#91 that DMRS will be generated using a pseudo-random sequence of length 31. The pseudo-random sequence is defined by a Gold sequence of length 31. The output sequence c(n) of length M PN , where n = 0, 1,......, M PN is defined by the following formula

[0049] c(n) = (x1(n + N C ) + x2(n + N C )) mod 2

[0050] x1(n + 31) = (x1(n + 3) + x1(n)) mod 2

[0051] x2(n + 31) = (x2(n + 3) + x2(n + 2) + x2(n + 1) + x2(n)) mod 2

[0052] where N c = 1600, and the first m-sequence is initialized with x 1(0) = 1, x 1(n) = 0, n = 1, 2,......30. The initialization of the second m-sequence is represented by the C init value given as follows:

[0053]

[0054] where n s is the time slot index in the radio frame, l is the OFDM symbol index, and is a 16-bit scrambling ID given by the higher layer parameters UL-DMRS-Scrambling-ID or DL-DMRS-Scrambling-ID for uplink and downlink respectively. The scrambling code is indexed by a 1-bit value n SCID ∈ {0, 1}, which will be signaled to the user to determine the configured scrambling ID.

[0055] Signaling scrambling ID

[0056] In one embodiment, n SCID can be configured in the CSI-RS configuration. In another embodiment, n SCID can be configured in the SS-block. In both of these embodiments, if the higher layer parameter TCI-PresentInDCI is "enabled", the actual value of n SCID can be signaled using the transmission configuration information (TCI) state. In this case, 3 bits in the DCI of the ControlResourceSet (CORESET) that schedules the PDSCH / PUSCH are used to signal the TCI state. The value of n SCID can be associated with the TCI state that is associated with the CSI-RS or SS-block configuration.

[0057] In another embodiment, when the higher layer parameter TCI-PresentInDCI is "disabled", there are no TCI bits associated with the DCI. In this case, n SCIDThe default value is set to 0. In yet another embodiment, a single bit in the DCI associated with the CORESET that schedules PDSCH / PUSCH for the user may be used to signal the user the value of n SCID ∈ {0, 1}.

[0058] Section 7.4.1.1.1 of 3GPP TS 38.211 V15.2.0 (2018-06) shows an example of the sequence generation of the DMRS signal of PDSCH, as described below.

[0059] 7.4.1.1.1 Sequence generation

[0060] The UE shall assume that the sequence r(n) is defined by

[0061]

[0062] where the pseudo-random sequence c(i) is defined in Clause 5.2.1. The pseudo-random sequence generator shall be initialized using

[0063]

[0064] where l is the OFDM symbol number within the slot, is the slot number within the frame, and

[0065] - If provided, are given by the higher layer parameters scramblingID0 and scramblingID1 in the DMRS-DownlinkConfig IE, respectively, and the PDSCH is scheduled by the PDCCH using DCI format 1_1 with a CRC scrambled by C-RNTI or CS-RNTI;

[0066] - If provided, is given by the higher layer parameter scramblingID0 in the DMRS-DownlinkConfig IE, and the PDSCH is scheduled by the PDCCH using DCI format 1_0 with a CRC scrambled by C-RNTI or CS-RNTI;

[0067] - Otherwise

[0068] If DCI format 1_1 in [4, TS 38.212] is used, the quantity n SCID ∈ {0, 1} is given by the DM-RS sequence initialization field in the DCI associated with the PDSCH transmission, otherwise n SCID = 0.

[0069] Figure 3Shows the architecture of a system of a network according to some embodiments. System 300 is shown as including user equipment (UE) 301 and UE 302. UE 301 and UE 302 are shown as smart phones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but these UEs can also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless handheld terminal, or any computing device including a wireless communication interface.

[0070] In some embodiments, either of UE 301 and UE 302 can include an Internet of Things (IoT) UE, which can include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity services (ProSe), or device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange can be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which can include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connections to the IoT network.

[0071] UE 301 and UE 302 can be configured to connect (e.g., communicatively couple) to a radio access network (RAN) 310, which can be, for example, an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next-generation RAN (NG RAN), or some other type of RAN. UE 301 and UE 302 respectively utilize connections 303 and 304, where each connection includes a physical communication interface or layer (discussed further below); in this example, connections 303 and 304 are shown as air interfaces to enable communicative coupling and can be consistent with cellular communication protocols, such as the global system for mobile communications (GSM) protocol, code division multiple access (CDMA) network protocol, push-to-talk (PTT) protocol, cellular PTT (POC) protocol, universal mobile telecommunications system (UMTS) protocol, 3GPP long-term evolution (LTE) protocol, fifth-generation (5G) protocol, new radio (NR) protocol, etc.

[0072] In this embodiment, UE 301 and UE 302 may also directly exchange communication data via ProSe interface 305. ProSe interface 305 may alternatively be referred to as a sidelink interface including one or more logical channels, the one or more logical channels including but not limited to Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0073] The illustrated UE 302 is configured to access access point (AP) 306 via connection 307. Connection 307 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, where AP 306 will include a Wi-Fi router. In this example, the illustrated AP 306 is connected to the Internet without being connected to the core network of the wireless system (described in further detail below).

[0074] RAN 310 may include one or more access nodes enabling connections 303 and 304. These access nodes (ANs) may be referred to as base stations (BSs), Node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and may include terrestrial stations (e.g., land access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). RAN 310 may include one or more RAN nodes (e.g., macro RAN node 311) for providing macro cells, and one or more RAN nodes (e.g., low-power (LP) RAN node 312) for providing femtocells or picocells (e.g., cells having a smaller coverage area, smaller user capacity, or higher bandwidth compared to macro cells).

[0075] Either of RAN node 311 and RAN node 312 may terminate the air interface protocol and may be the first point of contact for UE 301 and UE 302. In some embodiments, either of RAN nodes 311 and 312 may fulfill various logical functions of RAN 310, including but not limited to the functions of a Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0076] According to some embodiments, UE 301 and UE 302 may be configured to communicate with each other or with any one of RAN node 311 and RAN node 312 via a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the embodiments is not limited in this regard. The OFDM signal may include a plurality of orthogonal sub-carriers.

[0077] In some embodiments, a downlink resource grid may be used for downlink transmission from any one of RAN node 311 and RAN node 312 to UE 301 and UE 302, and uplink transmission may utilize a similar technique. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resources in the downlink in each time slot. For an OFDM system, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid correspond to an OFDM symbol and an OFDM sub-carrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the smallest amount of resources that can be currently allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0078] The physical downlink shared channel (PDSCH) may deliver user data and higher layer signaling to UE 301 and UE 302. The physical downlink control channel (PDCCH) may carry information about the transmission format and resource allocation related to the PDSCH channel, etc. It may also notify UE 301 and UE 302 of the transmission format, resource allocation, and H-ARQ (hybrid automatic repeat request) information related to the uplink shared channel. Generally, downlink scheduling (allocating control and shared channel resource blocks to UE 102 within a cell) may be performed at any one of RAN node 311 and RAN node 312 based on the channel quality information fed back from any one of UE 301 and UE 302. The downlink resource allocation information may be sent on the PDCCH for each of UE 301 and UE 302 (e.g., allocated to).

[0079] The PDCCH can use control channel elements (CCEs) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruples, and then a sub-block interleaver can be used to permute them for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, called resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8).

[0080] Some embodiments can use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments can utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) can be used to transmit the EPDCCH. Similar to the above, each ECCE can correspond to four sets of nine physical resource elements, called enhanced resource element groups (EREGs). In some cases, an ECCE can have a different number of EREGs.

[0081] RAN 310 is shown as communicatively coupled to a core network (CN) 320 via an S1 interface 313. In various embodiments, the CN 320 can be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this embodiment, the S1 interface 313 is divided into two parts: an S1-U interface 314 that carries traffic data between the RAN nodes 311 and 312 and a serving gateway (S-GW) 322; and an S1-mobility management entity (MME) interface 315 that is a signaling interface between the RAN nodes 311 and 312 and the MME 321.

[0082] In this embodiment, CN 320 includes a Mobility Management Entity (MME) 321, a Serving Gateway (S-GW) 322, a Packet Data Network (PDN) Gateway (P-GW) 323, and a Home Subscriber Server (HSS) 324. The MME 321 may be functionally similar to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 321 may manage aspects of mobility in access, such as gateway selection and tracking area list management. The HSS 324 may include a database for network users, which includes subscription-related information for supporting network entities in processing communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN 320 may include one or more HSSs 324. For example, the HSS 324 may provide support for routing / roaming, authentication, authorization, name / address resolution, location dependencies, etc.

[0083] The S-GW 322 may terminate the S1 interface 313 towards the RAN 310 and route data packets between the RAN 310 and the CN 320. Additionally, the S-GW 322 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies.

[0084] The P-GW 323 may terminate the SGi interface towards the PDN. The P-GW 323 may route data packets between the EPC network 323 and an external network, such as a network including an Application Server 330 (alternatively referred to as an Application Function (AF)), via an Internet Protocol (IP) interface 325. Generally, the Application Server 330 may be an element that provides an application that uses IP bearer resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 323 is shown communicatively coupled to the Application Server 330 via the IP communication interface 325. The Application Server 330 may also be configured to support one or more communication services for the UEs 301 and 302 via the CN 320 (e.g., Internet Protocol Voice (VoIP) sessions, Push-to-Talk (PTT) sessions, group communication sessions, social network services, etc.).

[0085] The P-GW 323 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 326 is the policy and charging control element of the CN 320. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the Internet Protocol Connectivity Access Network (IP-CAN) session of the UE. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of the UE: the Home PCRF (H-PCRF) within the HPLMN and the Visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). The PCRF 326 may be communicatively coupled to the application server 330 via the P-GW 323. The application server 330 may signal the PCRF 326 to indicate a new service flow and select appropriate Quality of Service (QoS) and charging parameters. The PCRF 326 may configure the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with an appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which begins the QoS and charging specified by the application server 330.

[0086] Figure 4 Exemplary components of a device are shown in accordance with some embodiments. In some embodiments, the device 400 may include an application circuit 402, a baseband circuit 404, a Radio Frequency (RF) circuit 406, a Front End Module (FEM) circuit 408, one or more antennas 410, and a Power Management Circuit (PMC) 412 (coupled together as shown at least). The illustrated components of the device 400 may be included in a UE or a RAN node. In some embodiments, the device 400 may include fewer elements (e.g., a RAN node may not utilize the application circuit 402 but includes a processor / controller to process the IP data received from the EPC). In some embodiments, the device 400 may include additional elements such as a memory / storage device, a display, a camera, a sensor, or an Input / Output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuits may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

[0087] The application circuit 402 may include one or more application processors. For example, the application circuit 402 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage, and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 400. In some embodiments, the processors of the application circuit 402 may process IP data packets received from the EPC.

[0088] The baseband circuit 404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 404 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 406 and to generate baseband signals for the transmit signal path of the RF circuit 406. The baseband processing circuit 404 may interact with the application circuit 402 to generate and process baseband signals and to control the operation of the RF circuit 406. For example, in some embodiments, the baseband circuit 404 may include a third-generation (3G) baseband processor 404A, a fourth-generation (4G) baseband processor 404B, a fifth-generation (5G) baseband processor 404C, or other baseband processors 404D of other existing generations, generations under development, or generations to be developed in the future (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuit 404 (e.g., one or more of the baseband processors 404A-404D) may process various radio control functions that enable communication with one or more radio networks via the RF circuit 406. In other embodiments, some or all of the functions of the baseband processors 404A-404D may be included in modules stored in the memory 404G and executed via a central processing unit (CPU) 404E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 404 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 404 may include convolutional, tail-biting convolutional, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

[0089] In some embodiments, baseband circuitry 404 may include one or more audio digital signal processors (DSPs) 404F. The audio DSP 404F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, the components of the baseband circuitry may be appropriately combined on a single chip, in a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuitry 404 and the application circuitry 402 may be implemented together, such as on a system on a chip (SOC).

[0090] In some embodiments, baseband circuitry 404 may provide communication compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 404 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuitry 404 is configured to support radio communication for more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0091] The RF circuitry 406 may communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 406 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuitry 406 may include a receive signal path that may include circuitry for down-converting an RF signal received from the FEM circuitry 408 and providing a baseband signal to the baseband circuitry 404. The RF circuitry 406 may also include a transmit signal path that may include circuitry for up-converting a baseband signal provided by the baseband circuitry 404 and providing an RF output signal for transmission to the FEM circuitry 408.

[0092] In some embodiments, the receive signal path of RF circuit 406 may include mixer circuit 406a, amplifier circuit 406b, and filter circuit 406c. In some embodiments, the transmit signal path of RF circuit 406 may include filter circuit 406c and mixer circuit 406a. RF circuit 406 may also include synthesizer circuit 406d, which is used to synthesize the frequencies used by mixer circuit 406a of the receive signal path and the transmit signal path. In some embodiments, mixer circuit 406a of the receive signal path may be configured to down-convert the RF signal received from FEM circuit 408 based on the synthesized frequency provided by synthesizer circuit 406d. Amplifier circuit 406b may be configured to amplify the down-converted signal, and filter circuit 406c may be a low-pass filter (LPF) or a band-pass filter (BPF), which is configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 404 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, mixer circuit 406a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0093] In some embodiments, mixer circuit 406a of the transmit signal path may be configured to up-convert the input baseband signal based on the synthesized frequency provided by synthesizer circuit 406d to generate an RF output signal for FEM circuit 408. The baseband signal may be provided by baseband circuit 404 and may be filtered by filter circuit 406c.

[0094] In some embodiments, mixer circuit 406a of the receive signal path and mixer circuit 406a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, mixer circuit 406a of the receive signal path and mixer circuit 406a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, mixer circuit 406a of the receive signal path and mixer circuit 406a may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, mixer circuit 406a of the receive signal path and mixer circuit 406a of the transmit signal path may be configured for superheterodyne operation.

[0095] In some embodiments, the output baseband signal and the input baseband signal can be analog baseband signals, although the scope of the embodiments is not limited in this regard. In some alternative embodiments, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative embodiments, the RF circuit 406 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 404 can include a digital baseband interface to communicate with the RF circuit 406. In some dual-mode embodiments, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the embodiments is not limited in this regard.

[0096] In some embodiments, the synthesizer circuit 406d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard since other types of frequency synthesizers can also be suitable. For example, the synthesizer circuit 406d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0097] The synthesizer circuit 406d can be configured to synthesize an output frequency based on a frequency input and a frequency divider control input for use by the mixer circuit 406a of the RF circuit 406. In some embodiments, the synthesizer circuit 406d can be a fractional-N / N+1 synthesizer.

[0098] In some embodiments, the frequency input can be provided by a voltage-controlled oscillator (VCO), but this is not required. The frequency divider control input can be provided by the baseband circuit 404 or the application processor 402 based on the desired output frequency. In some embodiments, the frequency divider control input (e.g., N) can be determined from a look-up table based on the channel indicated by the application processor 402.

[0099] The synthesizer circuit 406d of the RF circuit 406 can include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider can be a dual-modulus divider (DMD), and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide an input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL can include cascaded, tunable, delay elements, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements can be configured to divide the VCO period into Nd equal phase bins, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0100] In some embodiments, the synthesizer circuit 406d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with the quadrature generator and divider circuits to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 406 may include an IQ / polarity converter.

[0101] The FEM circuit 408 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 410, amplify the received signals, and provide an amplified version of the received signals to the RF circuit 406 for further processing. The FEM circuit 408 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuit 406 for transmission via one or more of the one or more antennas 410. In various embodiments, amplification through the transmit or receive signal paths may be accomplished only in the RF circuit 406, only in the FEM 408, or in both the RF circuit 406 and the FEM 408.

[0102] In some embodiments, the FEM circuit 408 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 406). The transmit signal path of the FEM circuit 408 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 406); and one or more filters for generating an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 410).

[0103] In some embodiments, the PMC 412 may manage the power provided to the baseband circuit 404. Specifically, the PMC 412 may control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 400 is capable of being powered by a battery, e.g., when the device is included in a UE, the PMC 412 is typically included. The PMC 412 may improve power conversion efficiency while providing the desired form factor and thermal characteristics.

[0104] While Figure 4PMC 412 is shown coupled only to the baseband circuitry 404. However, in other embodiments, PMC 412 may be additionally or alternatively coupled to other components such as, but not limited to, the application circuitry 402, the RF circuitry 406, or the FEM 408, and perform similar power management operations.

[0105] In some embodiments, PMC 412 may control or otherwise be part of various power saving mechanisms of the device 400. For example, if the device 400 is in the RRC_Connected state and is still connected to a RAN node in this state because the device expects to receive communication soon, then the device may enter a state called discontinuous reception mode (DRX) after being inactive for a period of time. During this state, the device 400 may power off for short intervals, thus saving power.

[0106] If there is no data traffic activity for an extended period of time, the device 400 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 400 enters a very low power state and performs paging, in which the device wakes up periodically again to listen for the network and then powers off again. The device 400 may not be able to receive data in this state and, to receive data, it must transition back to the RRC_Connected state.

[0107] Additional power saving modes may cause the device to be unable to use the network for a time period longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and may be completely powered off. Any data sent during this period will incur a significant delay and it is assumed that the delay is acceptable.

[0108] The processors of the application circuitry 402 and the baseband circuitry 404 may be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 404 may be used, either alone or in combination, to execute layer 3, layer 2, or layer 1 functions, while the processor of the application circuitry 404 may utilize the data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., the transport control protocol (TCP) and the user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include the radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include the media access control (MAC) layer, the radio link control (RLC) layer, and the packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0109] Figure 5An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 4 the baseband circuit 404 of Figure 4 may include processors 404A - 404E and a memory 404G utilized by the processors. Each of the processors 404A - 404E may respectively include a memory interface 504A - 504E for sending / receiving data to / from the memory 404G.

[0110] The baseband circuit 404 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as the memory interface 512 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 404), the application circuit interface 514 (e.g., an interface for sending / receiving data to / from Figure 4 the application circuit 402 of Figure 4 ), the RF circuit interface 516 (e.g., an interface for sending / receiving data to / from Figure 4 the RF circuit 406 of Figure 4 ), the wireless hardware connection interface 518 (e.g., an interface for sending / receiving data to / from a near - field communication (NFC) component, a component (e.g., low - power), a component, and other communication components), and the power management interface 520 (e.g., an interface for sending / receiving power or control signals to / from the PMC 412).

[0111] In the specification and / or claims of this document, the terms "coupled" and "connected" and their derivatives may be used. In a particular embodiment, "connected" may be used to indicate that two or more elements are in direct physical and / or electrical contact with each other. "Coupled" may mean that two or more elements are in direct physical contact and / or electrical contact. However, "coupled" may also mean that two or more elements may not be in direct contact with each other, but may still cooperate and / or interact with each other. For example, "coupled" may mean that two or more elements are not in contact with each other, but are indirectly joined together via another element or intermediate element. Finally, the terms "on", "overlying", and "above" may be used in the following specification and claims. "On", "overlying", and "above" may be used to indicate that two or more elements are in direct physical contact with each other. However, it should be noted that "above" may also mean that two or more elements are not in direct contact with each other. For example, "above" may mean that one element is higher than another element but not in contact with each other, and there may be another element or more elements between the two elements. In addition, the term "and / or" may mean "and", it may mean "or", it may mean "exclusive or", it may mean "one", it may mean "some but not all", it may mean "none", and / or it may mean "both", but does not limit the scope of the subject matter protected by the claims in this regard. In the specification and / or claims of this document, the terms "comprising" and "including" and their derivatives may be used and are intended to be used as synonyms of each other.

[0112] Although the subject matter protected by the claims has been described to a certain degree of specificity, it should be recognized that those skilled in the art may change the elements of the subject matter protected by the claims without departing from the essence and / or scope of the subject matter protected by the claims. It is believed that the subject matter related to CSI-RS sequence generation and mapping and DMRS scrambling ID configuration and many of its attendant utilities will be understood from the foregoing description, and it will be apparent that various changes may be made to the form, construction, and / or arrangement of its components without departing from the scope and / or essence of the subject matter protected by the claims, or without sacrificing all of its material advantages. The forms described above are merely illustrative embodiments of such components, and / or further do not provide a substantial change thereto. The purpose of the claims is to cover and / or include such changes.

Claims

1. An apparatus for a base station, the apparatus comprising: One or more baseband processors that encode a scrambling identity ID configuration for one or more demodulation reference signals DMRS, where the scrambling ID configuration indicates one of two scrambling IDs to be signaled to a user equipment UE, and where the value of the scrambling ID is configured in a channel state information reference signal CSI-RS configuration or a signal synchronization block SSB configuration associated with a transmission configuration indication TCI state; and A transmitter that transmits the scrambling ID configuration to the UE, where the scrambling ID configuration is transmitted to the UE using the TCI state.

2. The apparatus according to claim 1, wherein one of the two scrambling ID selections is used to transmit the one or more DMRSs in a Physical Downlink Shared Channel (PDSCH).

3. The apparatus according to claim 1, wherein one of the two scrambling ID selections is used to transmit the one or more DMRSs in a Physical Uplink Shared Channel (PUSCH).

4. The apparatus according to claim 1, wherein the transmitter transmits Downlink Control Information (DCI) to the UE, the DCI indicating that the scrambling ID will be signaled using the TCI state.

5. The apparatus according to claim 1, wherein the TCI state is part of a Signal Synchronization Block (SSB).

6. The apparatus according to claim 1, wherein the TCI state is part of a Channel State Information Reference Signal (CSI-RS).

7. One or more non-transitory storage media having instructions stored thereon that, when executed by a base station, cause the base station to perform operations including: Encoding a scrambling identification (ID) configuration for one or more Demodulation Reference Signals (DMRSs), wherein the scrambling ID configuration indicates one of two scrambling IDs to be signaled to a User Equipment (UE), and wherein the value of the scrambling ID is configured in a Channel State Information Reference Signal (CSI-RS) configuration or a Signal Synchronization Block (SSB) configuration associated with a Transmission Configuration Indicator (TCI) state; and Transmitting the scrambling ID configuration to the UE, wherein the scrambling ID configuration is transmitted to the UE using the TCI state.

8. The one or more non-transitory storage media according to claim 7, wherein one of the two scrambling IDs is used to transmit the one or more DMRSs in a Physical Downlink Shared Channel (PDSCH).

9. The one or more non-transitory storage media according to claim 7, wherein one of the two scrambling IDs is used to transmit the one or more DMRSs in a Physical Uplink Shared Channel (PUSCH).

10. The one or more non-transitory storage media according to claim 7, wherein a transmitter transmits Downlink Control Information (DCI) to the UE, the DCI indicating that the scrambling ID will be signaled using the TCI state.

11. The one or more non-transitory storage media according to claim 7, wherein the TCI state is part of a signal synchronization block SSB.

12. The one or more non-transitory storage media according to claim 7, wherein the TCI state is part of a channel state information reference signal CSI-RS.

13. An apparatus for a user equipment UE, the apparatus comprising: A receiver that receives a scrambling identity ID configuration from a fifth generation (5G) node B (gNB), where the scrambling ID configuration is for one or more demodulation reference signals DMRS, where the scrambling ID configuration indicates one of two scrambling IDs to be signaled to the user equipment UE, where the value of the scrambling ID is configured in a channel state information reference signal CSI-RS configuration or a signal synchronization block SSB configuration associated with a transmission configuration indication TCI state, and where the scrambling ID configuration is transmitted to the UE using the TCI state.

14. The apparatus according to claim 13, wherein a selected one of the two scrambling IDs is used to transmit the one or more DMRS in a physical downlink shared channel PDSCH.

15. The apparatus according to claim 13, wherein a selected one of the two scrambling IDs is used to transmit the one or more DMRS in a physical uplink shared channel PUSCH.

16. The apparatus according to claim 13, wherein the receiver receives downlink control information DCI, the DCI indicating that the scrambling ID will be signaled using the TCI state.

17. The apparatus according to claim 13, wherein the TCI state is part of a signal synchronization block SSB.

18. The apparatus according to claim 13, wherein the TCI state is part of a channel state information reference signal CSI-RS.

Images