Extension to support an increase in the number of DMRS ports for DMRS transmissions.

Abstract

A network device including a transceiver and a processor is disclosed. The processor is configured to determine a demodulation reference signal (DMRS) configuration type, a count of DMRS ports, and a count of DMRS code division multiplexing (CDM) groups without data. The processor is configured to determine a count of scaled-up DMRS ports and a distinct value for each scaled-up DMRS port, according to the determined count of DMRS CDM groups without data, the DMRS configuration type, and the count of DMRS ports. The transceiver is configured to transmit a physical downlink shared channel (PDSCH) scheduled by downlink control information (DCI) to the user equipment (UE). The DCI indicates a count of scaled-up DMRS ports and a distinct value for each scaled-up DMRS port. The distinct value for each scaled-up DMRS port is greater than 7, and DMRS contains one symbol.

Description

Technical Field

[0001] (Cross - reference to Related Applications) This PCT (Patent Cooperation Treaty) patent application claims priority to U.S. Patent Application No. 63 / 445,626, entitled "Enhancements to Support Increased Number of DMRS Ports for Transmission of a DMRS", filed on February 14, 2023, the content of which is hereby incorporated by reference in its entirety.

[0002] This application generally relates to a wireless communication system, including methods for supporting an increase in the number of demodulation reference signal (DMRS) ports for transmission of DMRS. Specifically, support for an increase in the number of DMRS ports using a frequency domain orthogonal cover code (FD - OCC) length of 4 is provided.

Background Art

[0003] Wireless mobile communication technologies use various standards and protocols to transmit data between network devices (e.g., base stations, network access points, or relays) and wireless communication devices (e.g., user equipment (UE)). Wireless communication system standards and protocols can include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known as Wi - Fi (registered trademark) in the industry.

[0004] As intended by 3GPP, different radio communication system standards and protocols may use various RANs to communicate between network devices (e.g., base stations, network access points, or relays) of a radio access network (RAN) (sometimes commonly referred to as RAN nodes, network nodes, or simply nodes) and radio communication devices known as user equipment (UEs). 3GPP RANs may include, for example, the Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolutionary (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Advanced Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0005] Each RAN may use one or more radio access technologies (RATs) to perform communication between network devices and UEs. For example, GERAN implements GSM and / or EDGE RATs, UTRAN implements Universal Mobile Telecommunication System (UMTS) RATs or other 3GPP RATs, E-UTRAN implements LTE RATs (sometimes simply referred to as LTE), and NG-RAN implements NR RATs (sometimes referred to herein as 5G RATs, 5G NR RATs, or simply NR). In certain deployments, E-UTRAN may also implement NR RATs. In certain deployments, NG-RAN may also implement LTE RATs.

[0006] Network devices used by a RAN (e.g., base stations, network access points, or relays) can be compatible with that RAN. An example of a network device might be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (commonly also called Evolved Node B, Extended Node B, eNode B, or eNB), which could be an E-UTRAN base station. Another example of a network device might be a Next Generation Node B (sometimes called gNode B or gNB), which could be an NG-RAN base station.

[0007] RANs provide communication services with external entities via connections to the core network (CN). For example, E-UTRANs can utilize the Advanced Packet Core (EPC), and NG-RANs can utilize the 5G Core Network (5GC).

[0008] To facilitate the identification of any particular element or action, the most significant digit(s) of the reference number refers to the number of the figure in which that element was first introduced. [Brief explanation of the drawing]

[0009] [Figure 1] This refers to a communication system that includes user equipment (UE) that communicates with network devices.

[0010] [Figure 2] This document illustrates exemplary methods of wireless communication, such as those performed by network devices, according to several embodiments.

[0011] [Figure 3] This document presents another exemplary method of wireless communication, such as that performed by a network device, according to several embodiments.

[0012] [Figure 4]This document illustrates exemplary methods of wireless communication, such as those performed by a UE, according to several embodiments.

[0013] [Figure 5] This specification shows an exemplary architecture of a wireless communication system according to embodiments disclosed herein.

[0014] [Figure 6] This specification discloses a system for performing signaling between a wireless device and a network device, according to embodiments of this specification. [Modes for carrying out the invention]

[0015] Various embodiments are described with respect to network devices and / or user equipment (UEs). However, references to UEs are provided for illustrative purposes only. Exemplary embodiments may be used with any electronic component, which consists of hardware, software, and / or firmware capable of establishing connectivity to a network and exchanging information and data with the network. Thus, UEs described herein are used to represent any suitable electronic device. Similarly, various embodiments are described with respect to network devices, which may include network access points, base stations, and / or relays deployed in a terrestrial network (TN), satellites, and / or high-altitude platform systems (HAPS) including manned or unmanned aerial vehicles.

[0016] With the advancement of multiple-input and multiple-output (MIMO) wireless communication systems, the number of antenna ports that can be supported by network devices such as base stations, network access points, and / or relays is increasing. As the number of antenna ports increases, network devices can serve more UEs within the same time-frequency resources using spatial beamforming techniques. Therefore, the number of antenna ports used to transmit DMRS to UEs can be increased, and / or additional patterns of DMRS ports can be indicated in downlink control information (DCI). DCI is transmitted to and from UEs to schedule physical downlink shared channels (PDSCHs) supporting up to eight layers. Various patterns of one or more DMRS ports are specified in the 3GPP specification TS 38.212. However, the various embodiments described herein disclose additional patterns of one or more DMRS ports that can be indicated by network devices in DCI, thereby enhancing the network device's ability to serve UEs.

[0017] Figure 1 shows a communication system 100 including a UE 104 that communicates with a network device 102. The network device 102 may be a base station, network access point, or relay deployed in a terrestrial network (TN) or a non-terrestrial network (NTN). The network device 102 can transmit a DCI to the UE 104 in a physical downlink control channel (PDCCH). The UE 104 can decode the PDCCH and use the DCI to schedule uplink (UL) transmissions 104b and downlink (DL) transmissions 104a with the network device 102 according to the DMRS ports specified in the DCI. As described herein, according to some embodiments, an additional pattern of one or more DMRS ports may be used for a DMRS of DMRS configuration type 1 using up to one or two DMRS symbols, by using a frequency domain orthogonal cover code (FD-OCC) of a predetermined length 4. In some embodiments, as a non-limiting embodiment, the FD-OCC may have a length of 4.

[0018] As shown in the table below, in some embodiments, the DMRS port values ​​that may be included in the DCI for communicating patterns of one or more DMRS ports correspond to the DMRS configuration type, the type of code divisional multiplexing (CDM) group without data, and whether the DMRS contains one symbol or two symbols. [Table 1]

[0019] As shown in the above table, in the case of DMRS configuration type 1, the DMRS of one symbol can include DMRS ports 0 and 1 for CDM group 0, or DMRS ports 8 and 9, and the DMRS of two symbols can include DMRS ports 4 and 5 for CDM group 0, or DMRS ports 12 and 13. DMRS ports having values of 0, 1, 2, 3, 4, 5, 6, or 7 may be referred to in this disclosure as unscaled DMRS ports, and DMRS ports having values greater than 7 may be referred to in this disclosure as scaled-up DMRS ports.

[0020] The various patterns of DMRS ports described in this disclosure can be selected by a network device according to the set of subcarriers used for DMRS and / or the CDM group.

[0021] In some embodiments, for a DMRS of DMRS configuration type 1 having at most one symbol for DMRS, the following patterns of one or more additional DMRS ports, particularly scaled-up DMRS ports, can be supported. Additionally or alternatively, the various patterns of one or more DMRS ports as defined in Table 7.3.1.2.2-1 of 3GPP TS 38.212 can be updated by adding a value of 8 to the defined DMRS port values.

Table 2

[0022] [[ID=​​​In some embodiments, a network device can facilitate multi-user MIMO (MU-MIMO) scheduling by a pattern of DMRS ports that includes both scaled-up and unscaled DMRS ports, as shown in the table below. MU-MIMO scheduling can be used for cooperative scheduling among multiple UEs. In some embodiments, the multiple UEs may include legacy UEs and extended UEs as non-limiting examples. A legacy UE as referred herein may not support scaled-up DMRS ports and may only support unscaled DMRS ports, while an extended UE may support both scaled-up and unscaled DMRS ports. [Table 3]

[0024] In some embodiments, a network device can facilitate multi-user MIMO (MU-MIMO) scheduling by a pattern of five DMRS ports, including both scaled-up and unscaled DMRS ports, as shown in the table below. MU-MIMO scheduling can be used for cooperative scheduling among multiple UEs. In some embodiments, the multiple UEs may include legacy UEs and extended UEs, in non-limiting examples. Furthermore, a pattern of five DMRS ports, as specified in the table below, can be used for PDSCHs with more than four layers. [Table 4]

[0025] In some embodiments, a network device may send an activation command mapping a DCI field transmission configuration indication (TCI) code point to two TCI states, and the UE may need to select a DMRS port as specified in Table 7.3.1.2.2-1A of the 3GPP TS 38.212 specification, which is an alternative or fallback to Table 7.3.1.2.2-1 of 3GPP TS 38.212 described above. Additional patterns of one or more DMRS ports may be added to Table 7.3.1.2.2-1A, as shown below. The additional patterns of one or more DMRS ports shown in the table below may include scaled-up DMRS ports and / or unscaled DMRS ports. [Table 5]

[0026] In some embodiments, for a DMRS of DMRS configuration type 1 and having up to two symbols for the DMRS, the following patterns of one or more additional DMRS ports, in particular scaled-up DMRS ports, can be supported. As an addition or alternative, various patterns of one or more DMRS ports corresponding to DMRS configuration type 1 and having up to two symbols for the DMRS, as defined in Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification, can be updated by adding a value of 8 to the defined DMRS port value. [Table 6]

[0027] The various patterns of one or more DMRS ports specified in the table above are additions to Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification, but Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification can be further extended using a mix of one or more scaled-up DMRS ports and one or more unscaled DMRS ports, as specified in the table below, to support up to four layers of PDSCH. [Table 7]

[0028] In some embodiments, to support more than four layers of PDSCH, Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification can be extended by using DMRS port patterns as specified in the following table. The various DMRS port patterns in the following table may include one or more scaled-up DMRS ports and one or more unscaled DMRS ports. [Table 8]

[0029] In some embodiments, to support more than four layers of PDSCH, Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification can be extended by using DMRS port patterns as specified in the following table. The various DMRS port patterns in the following table may include one or more scaled-up DMRS ports and one or more unscaled DMRS ports. As an addition or alternative, for one or more additional patterns of DMRS ports, a value of 8 may be added to the DMRS port values ​​specified in Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification. [Table 9]

[0030] In some embodiments, to support co-scheduling of more than four layers and multiple UEs in the PDSCH, Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification can be extended by using patterns of DMRS ports as specified in the following table. The various patterns of DMRS ports in the following table may include one or more scaled-up DMRS ports and one or more unscaled DMRS ports. [Table 10]

[0031] In some embodiments, to support three or four layers of PDSCH, Table 7.3.1.2.2-2 of the 3GPP TS 38.212 specification can be extended by using DMRS port patterns as specified in the following table. The various DMRS port patterns in the following table may include one or more scaled-up DMRS ports and one or more unscaled DMRS ports. [Table 11]

[0032] In some embodiments, when a network device sends an activation command that maps a DCI Field Transmitted Configuration Instruction (TCI) code point to two TCI states, the UE may need to use a DMRS port as specified in Table 7.3.1.2.2-2A of the 3GPP TS 38.212 specification, which is an alternative or fallback to Table 7.3.1.2.2-2 of 3GPP TS 38.212 described above. Additional patterns of one or more DMRS ports can be added to Table 7.3.1.2.2-2A, as shown below. The additional patterns of one or more DMRS ports shown in the table below may include one or more scaled-up DMRS ports and / or one or more unscaled DMRS ports. [Table 12]

[0033] Figure 2 illustrates exemplary methods of wireless communication, such as those performed by a network device, according to several embodiments. As shown in flowchart 200, in 202, the network device can determine the DMRS configuration type and the count of DMRS ports. The DMRS configuration type may be DMRS configuration type 1 or DMRS configuration type 2. The count of DMRS ports may correspond to the antenna ports of the network device. DMRS ports, or antenna ports as referred to herein, are sometimes called PDSCH antenna ports because the DMRS port or antenna port information is transmitted to the UE in DCI for scheduling the PDSCH and for transmitting DMRS on the PDSCH.

[0034] In 204, the network device can identify a count of DMRS CDM groups without data. As described herein, according to various embodiments, a different pattern of one or more DMRS ports can be selected by the network device. Thus, in 206, according to the determined count of DMRS CDM groups without data, the DMRS configuration type, and the count of DMRS ports, the network device can determine the count of scaled-up DMRS ports and the individual values ​​for each scaled-up DMRS port in the DMRS port pattern. In 208, the network device can send a PDCCH including a DCI to the UE, where the DCI indicates the scaled-up DMRS ports according to the count of scaled-up DMRS ports determined in 206 and the individual values ​​for each scaled-up DMRS port determined in 206. In 210, the network device can send a PDSCH scheduled by the DCI to the UE along with the transmission of DMRS on the indicated scaled-up DMRS ports. A DMRS may include up to one symbol, and the DMRS configuration type may be DMRS configuration type 1. In some embodiments, DCI may also include unscaled DMRS ports in addition to scaled-up DMRS ports, as described herein, to facilitate MU-MIMO scheduling.

[0035] Figure 3 illustrates another exemplary method of wireless communication performed by a network device, according to several embodiments. As shown in flowchart 300, in 302, the network device can determine the DMRS configuration type and the count of DMRS ports. The DMRS configuration type may be DMRS configuration type 1 or DMRS configuration type 2. The count of DMRS ports may correspond to the antenna ports of the network device. In 304, the network device can identify the count of DMRS CDM groups without data. According to various embodiments, as described herein, one or more different patterns of DMRS ports can be selected by the network device. Thus, in 306, according to the determined count of DMRS CDM groups without data, the DMRS configuration type, and the count of DMRS ports, the network device can determine the total count of DMRS ports. The total count of DMRS ports may include the count of scaled-up DMRS ports and the count of unscaled DMRS ports. Furthermore, individual values ​​for each DMRS port can also be determined. In 308, the network device may send a PDCCH to the UE that includes a DCI, where the DCI represents a separate value for each DMRS port determined in 306. In 310, the network device may send a PDSCH scheduled by the DCI to the UE along with the transmission of DMRS on the indicated DMRS ports. A DMRS may include up to two symbols, and the DMRS configuration type may be DMRS configuration type 1.

[0036] In some embodiments, the count of unscaled DMRS ports can be determined to be 0, and therefore, a DMRS port specified in DCI may include only one or more scaled-up DMRS ports. In some embodiments, the count of unscaled DMRS ports may be at least 1, the count of scaled-up DMRS ports may be at least 1, and the total count of DMRS may not be greater than 4.

[0037] Figure 4 illustrates exemplary methods of wireless communication performed by a UE, according to several embodiments. As shown in flowchart 400, in 402, the UE may receive downlink control information (DCI) from a network device, which includes a pattern of DMRS ports indicating a specific count of scaled-up DMRS ports and a specific count of unscaled DMRS ports. The DCI may be received in a PDCCH. The pattern of DMRS ports identifies a distinct value for each DMRS port. In 404, the UE may receive DMRS on the DMRS ports as specified in the DCI received in 402. The DMRS may be received in a PDSCH transmission.

[0038] Embodiments contemplated herein include apparatus having means for performing one or more elements of Method 200, 300, or 400. In the context of Method 400, the apparatus may be, for example, an apparatus of a UE (such as a wireless device 602, which is a UE as described herein). In the context of Method 200 or 300, the apparatus may be an apparatus of a network device (such as a network device 620, which is a network access point or base station as described herein).

[0039] Embodiments contemplated herein include one or more non-temporary computer-readable media for storing instructions, which, when an instruction is executed by one or more processors of the electronic device, cause the electronic device to execute one or more elements of Method 200, 300, or 400. In the context of Method 400, the non-temporary computer-readable media may be, for example, the memory of the UE (such as memory 606 of wireless device 602, which is a UE as described herein). In the context of Method 200 or 300, the non-temporary computer-readable media may be the memory of a network device (such as memory 624 of network device 620, which is a network access point or base station as described herein).

[0040] Embodiments contemplated herein include devices having logic, modules, or circuits that perform one or more elements of Method 200, 300, or 400. In the context of Method 400, the device may be, for example, a device of a UE (such as a wireless device 602, which is a UE as described herein). In the context of Method 200 or 300, the device may be a device of a network device (such as a network device 620, which is a network access point or base station as described herein).

[0041] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that, when executed by the one or more processors, uses or stores instructions causing the one or more processors to execute one or more elements of Method 200, 300, or 400. In the context of Method 400, the apparatus may be an apparatus of a UE (such as a wireless device 602, which is a UE as described herein). In the context of Method 200 or 300, the apparatus may be an apparatus of a network device (such as a network device 620, which is a network access point or base station as described herein).

[0042] Embodiments contemplated herein include signals described in or related to one or more elements of Method 200, 300, or 400.

[0043] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein the execution of the program by a processor causes the processor to execute one or more elements of Method 200, 300, or 400. In the context of Method 400, the processor may be a processor of a UE (such as a processor(s) 604 of a wireless device 602 which is a UE as described herein), and the instructions may be located, for example, within the processor and / or on the memory of the UE (such as memory(s) 606 of a wireless device 602 which is a UE as described herein). In the context of Method 200 or 300, the processor may be a processor of a network device (such as a processor(s) 622 of a network device 620 which is a network access point or base station as described herein), and the instructions may be located, for example, within the processor and / or on the memory of the network device (such as memory(s) 624 of a network device 620 which is a network access point or base station as described herein).

[0044] Figure 5 shows an exemplary architecture of the wireless communication system 500 according to embodiments disclosed herein. The following description is provided for an exemplary wireless communication system 500 that operates in conjunction with LTE system standards and / or 5G or NR system standards, as provided by 3GPP technical specifications.

[0045] As shown in Figure 5, the wireless communication system 500 includes UE502 and UE504 (however, any number of UEs can be used). In this embodiment, UE502 and UE504 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but they can also include any mobile or non-mobile computing device configured for wireless communication.

[0046] UE502 and UE504 can be configured to communicate with RAN506. In some embodiments, RAN506 may be an NG-RAN, E-UTRAN, or the like. UE502 and UE504 utilize connections (or channels) with RAN506 (referred to as connections 508 and 510, respectively), each of which has a physical communication interface. RAN506 may include one or more base stations, such as base stations 512 and 514, which enable connections 508 and 510. In some embodiments, RAN506 may include one or more relays.

[0047] In this embodiment, connections 508 and 510 are air interfaces for enabling such communication coupling and may correspond to RAT(s) used by RAN506, such as LTE and / or NR.

[0048] In some embodiments, UE502 and UE504 can also directly exchange communication data via the sidelink interface 516. UE504 is shown configured to access an access point (shown as AP518) via connection 520. For example, connection 520 may include a local radio connection such as a connection matching any IEEE 802.11 protocol, and AP518 may include a Wi-Fi® router. In this embodiment, AP518 may be connected to another network (e.g., the Internet) without going through CN524.

[0049] In this embodiment, UE502 and UE504 can be configured to communicate with each other or with base stations 512 and / or 514 using orthogonal frequency division multiplexing (OFDM) communication signals via a multi-carrier communication channel according to various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (for example, for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (for example, for uplink and ProSe or sidelink communication), and the scope of the embodiment is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0050] In some embodiments, all or part of base stations 512 or base stations 514 can be implemented as one or more software entities running on a server computer as part of a virtual network. In addition, or in other embodiments, base stations 512 or base stations 514 can be configured to communicate with each other via interface 522. In embodiments where the wireless communication system 500 is an LTE system (e.g., CN524 is an EPC), interface 522 may be an X2 interface. The X2 interface may be defined between two or more base stations connected to the EPC (e.g., two or more eNBs, etc.) and / or between two eNBs connected to the EPC. In embodiments where the wireless communication system 500 is an NR system (e.g., CN524 is a 5GC), interface 522 may be an Xn interface. The Xn interface may be defined between two or more base stations connected to the 5GC (e.g., two or more gNBs, etc.), between base station 512 (e.g., a gNB) and an eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN524).

[0051] RAN506 is shown to be communicatively coupled to CN524. CN524 may comprise one or more network elements 526 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE502 and UE504) connected to CN524 via RAN506. Components of CN524 may be implemented in one or separate physical devices, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-temporary machine-readable storage media).

[0052] In the embodiment, CN524 may be an EPC, and RAN506 may be connected to CN524 via S1 interface 528. In the embodiment, S1 interface 528 may be divided into two parts: an S1 user plane (S1-U) interface that carries traffic data between base station 512 or base station 514 and a serving gateway (S-GW), and an S1-MME interface which is a signaling interface between base station 512 or base station 514 and mobility management entities (MME).

[0053] In this embodiment, CN524 may be a 5GC, and RAN506 may be connected to CN524 via NG interface 528. In this embodiment, NG interface 528 may be divided into two parts: an NG user plane (NG-U) interface that carries traffic data between base station 512 or base station 514 and user plane functions (UPF), and an S1 control plane (NG-C) interface that is a signaling interface between base station 512 or base station 514 and access and mobility management functions (AMF).

[0054] Generally, the application server 530 may be an element that provides applications using Internet Protocol (IP) bearer resources (e.g., packet-switched data services) with the CN524. The application server 530 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE502 and UE504 via the CN524. The application server 530 may communicate with the CN524 via the IP communication interface 532.

[0055] Figure 6 shows a system 600 for performing signaling 638 between a wireless device 602 and a network device 620 according to an embodiment disclosed herein. System 600 may be part of a wireless communication system as described herein. The wireless device 602 may be, for example, a UE of the wireless communication system. The network device 620 may be, for example, a base station (e.g., eNB or gNB) or relay of the wireless communication system.

[0056] The wireless device 602 may include one or more processors 604. The processors 604 can execute instructions to perform various operations of the wireless device 602, as described herein. The processors 604 may include, for example, one or more baseband processors implemented using a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0057] The wireless device 602 may include a memory 606. The memory 606 may be a non-temporary computer-readable storage medium that stores instructions 608 (for example, instructions being executed by a processor(s) 604). Instructions 608 may also be called program code or computer programs. The memory 606 may also store data used by the processor(s) 604 and the results calculated by the processor(s) 604.

[0058] The wireless device 602 may include one or more transceivers 610 that can include radio frequency (RF) transmitter and / or receiver circuits that use the antenna(s) 612 of the wireless device 602 to facilitate signaling to and from the wireless device 602 with other devices (e.g., network device 620) according to the corresponding RAT (Random Attack).

[0059] The wireless device 602 may include one or more antennas 612 (e.g., one, two, four, or more). In embodiments having multiple antennas 612, the wireless device 602 can leverage the spatial diversity of such multiple antennas 612 to transmit and / or receive multiple different data streams on the same time and frequency resources. This behavior is sometimes referred to as multiple-input multiple-output (MIMO) behavior (referring to the multiple antennas used in each of the transmitting and receiving devices that enable this embodiment). MIMO transmission by the wireless device 602 can be achieved according to precoding (or digital beamforming) applied in the wireless device 602, which multiplexes the data streams across the antennas 612 according to known or assumed channel characteristics, so that each data stream is received at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream) with appropriate signal strength relative to the other streams. Certain embodiments may employ a single-user MIMO (SU-MIMO) method (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) method (where individual data streams may be directed to individual (different) receivers at different locations in the spatial domain).

[0060] In certain embodiments having multiple antennas, the wireless device 602 may implement analog beamforming techniques so that the phase of the signals transmitted by antenna(s) 612 is relatively adjusted so that the (joint) transmission of antenna(s) 612 can be directed (this is sometimes called beam steering).

[0061] The wireless device 602 may include one or more interfaces 614. Interfaces 614 can be used to provide inputs to or outputs from the wireless device 602. For example, the wireless device 602, which is a UE, may include interfaces 614 such as microphones, speakers, touchscreens, and buttons to enable inputs and / or outputs to the UE by a user of the UE. Other interfaces of such a UE may consist of transmitters, receivers, and other circuits (other than, for example, the transceivers 610 / antennas 612 already described) that enable communication between the UE and other devices and can operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, etc.).

[0062] The wireless device 602 may include one or more DMRS extension modules 616. The DMRS extension modules 616 can be implemented via hardware, software, or a combination thereof. For example, the DMRS extension module 616 can be implemented as an instruction 608 stored in a processor, circuitry, and / or memory 606 and executed by a processor 604. In some embodiments, the DMRS extension module 616 can be integrated within a processor 604 and / or a transceiver 610. For example, the DMRS extension module 616 can be implemented by a combination of software components (executed by a DSP or general-purpose processor, e.g., a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within a processor 604 or a transceiver 610.

[0063] The DMRS extension module(s) 616 can be used from a UE perspective for various aspects of the present disclosure, for example, the aspects shown in Figures 1 to 4.

[0064] The network device 620 may include one or more processors 622. The processors 622 can execute instructions to perform various operations of the network device 620, as described herein. The processors 604 may include one or more baseband processors implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0065] The network device 620 may include memory 624. Memory 624 may be a non-temporary computer-readable storage medium that stores instructions 626 (for example, instructions being executed by processor(s) 622). Instructions 626 are also sometimes called program code or computer programs. Memory 624 may also store data used by processor(s) 622 and results calculated by processor(s) 622.

[0066] The network device 620 may include one or more transceivers 628 that can include RF transmitter and / or receiver circuits that use the antenna(s) 630 of the network device 620 to facilitate signaling to and from the network device 620 (e.g., signaling 638) with other devices (e.g., wireless device 602) according to the corresponding RAT.

[0067] The network device 620 may include one or more antennas 630 (e.g., one, two, four, or more). In embodiments having multiple antennas 630, the network device 620 can perform MIMO, digital beamforming, analog beamforming, beam steering, and the like, as described.

[0068] The network device 620 may include one or more interfaces 632. Interfaces 632 can be used to provide inputs to or outputs from the network device 620. For example, a network device 620 that is a base station may include interfaces 632 consisting of transmitters, receivers, and other circuits (other than the transceivers 628 / antennas 630 described above) that enable the base station to communicate with other equipment in the core network and / or enable the base station to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining the base station or other equipment operably connected thereto.

[0069] The network device 620 may include one or more DMRS extension modules 634. The DMRS extension modules 634 can be implemented via hardware, software, or a combination thereof. For example, the DMRS extension module 634 can be implemented as an instruction 626 stored in a processor, circuitry, and / or memory 624 and executed by a processor 622. In some embodiments, the DMRS extension module 634 can be integrated within a processor 622 and / or a transceiver 628. For example, the DMRS extension module 634 can be implemented by a combination of software components (executed by a DSP or general-purpose processor, for example) and hardware components (for example, logic gates and circuits) within a processor 622 or a transceiver 628.

[0070] The DMRS extension module(s) 634 can be used for various embodiments of the present disclosure, for example, the embodiments shown in Figures 1 to 4, from the perspective of a network device.

[0071] In one or more embodiments, at least one of the components described in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes and / or methods as described herein. For example, the baseband processor described above in relation to one or more of the figures herein may be configured to operate according to one or more of the examples described herein. In another embodiment, a circuit associated with a UE, base station, network element, etc., as described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described herein.

[0072] Any of the embodiments described above can be combined with any other embodiment (or combination of embodiments) unless otherwise specified. The above descriptions of one or more implementations are illustrative and illustrative, but are not intended to be exhaustive or to limit the scope of the embodiments to the exact forms disclosed. Modifications and variations are possible based on the above teachings or can be learned from the practice of various embodiments.

[0073] The embodiments and implementations of the systems and methods described herein may include a variety of operations that can be embodied by machine-executable instructions performed by a computer system. The computer system may include one or more general-purpose computers or dedicated computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing operations, or it may include a combination of hardware, software, and / or firmware.

[0074] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, divided into multiple systems, or otherwise divided or combined. In addition, parameters, attributes, aspects, etc. of one embodiment are intended to be used in another embodiment. Parameters, attributes, aspects are described in one or more embodiments for clarity only, and it should be recognized that parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, etc. of another embodiment unless specifically abandoned herein.

[0075] It should be fully understood that the use of personally identifiable information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0076] While the foregoing has been described in some detail for clarity, it will be clear that certain changes and modifications can be made without departing from the principles. It should be noted that many alternative methods exist for implementing both the processes and apparatus described herein. Therefore, these embodiments should be considered illustrative and not limiting, and the description is not limited to the details given herein and may be modified within the appended claims and equivalents.

Claims

1. A network device, Transmitter and receiver, It is a processor, Determine the demodulation reference signal (DMRS) configuration type and the DMRS port count. Determine the count of DMRS code partitioning multiplexing (CDM) groups without data. The number of scaled-up DMRS ports and the individual values ​​for each scaled-up DMRS port are determined according to the determined count of the DMRS CDM group without data, the DMRS configuration type, and the count of the DMRS ports. A processor configured as follows, Equipped with, The aforementioned transceiver, The system is configured to transmit a physical downlink shared channel (PDSCH) scheduled by downlink control information (DCI) to a user device (UE), wherein the DCI indicates the count of scaled-up DMRS ports and the individual values ​​for each scaled-up DMRS port. The individual values ​​for each scaled-up DMRS port exceed 7. DMRS includes one symbol, Network device.

2. The determined count for the DMRS CDM group without data is 1. The count of the scaled-up DMRS port is 1. The individual values ​​for each scaled-up DMRS port are 8 or 9. The network device according to claim 1.

3. The determined count for the DMRS CDM group without data is 1. The count of the scaled-up DMRS port is 2, The individual value of the first scaled-up DMRS port is 8. The individual value of the second scaled-up DMRS port is 9. The network device according to claim 1.

4. The determined count for the DMRS CDM group without data is 2. The count of the scaled-up DMRS port is 2, The individual value of the first scaled-up DMRS port is 8. The individual value of the second scaled-up DMRS port is 10. The network device according to claim 1.

5. The determined count for the DMRS CDM group without data is 2. The count of the scaled-up DMRS port is 3. The individual value of the first scaled-up DMRS port is 8. The individual values ​​of the second scaled-up DMRS port are 9, 10, or 11. The individual values ​​of the third scaled-up DMRS port are 10 or 11. The individual values ​​of the second scaled-up DMRS port are different from the individual values ​​of the third scaled-up DMRS port. The network device according to claim 1.

6. The determined count for the DMRS CDM group without data is 2. The count of the scaled-up DMRS port is 4. The individual value of the first scaled-up DMRS port is 8. The individual value of the second scaled-up DMRS port is 9. The individual value of the third scaled-up DMRS port is 10. The individual value of the fourth scaled-up DMRS port is 11. The network device according to claim 1.

7. The network device according to claim 1, wherein the processor is further configured to facilitate multi-user multi-input multi-output (MU-MIMO) scheduling by including two scaled-up DMRS ports with values ​​8 and 9, and a third DMRS port with value 0 or 1.

8. The network device according to claim 7, wherein the determined count of the DMRS CDM group without data is 1 or 2.

9. The processor is further configured to facilitate multi-user multi-input multi-output (MU-MIMO) scheduling by including one scaled-up DMRS port with a value of 8 and a second DMRS port with a value of 0 or 1. The determined count for the DMRS CDM group without data is 1. The network device according to claim 1.

10. The processor is further configured to facilitate multi-user multi-input multi-output (MU-MIMO) scheduling by including one scaled-up DMRS port with value 10, a second DMRS port with value 2, and a third DMRS port with value 3. The determined count for the DMRS CDM group without data is 2. The network device according to claim 1.

11. The processor is further configured to facilitate multi-user multi-input multiple-output (MU-MIMO) scheduling by including two scaled-up DMRS ports with values ​​10 and 11, and a third DMRS port with value 2. The determined count for the DMRS CDM group without data is 2. The network device according to claim 1.

12. The processor is further configured to facilitate multi-user multi-input multi-output (MU-MIMO) scheduling by including two scaled-up DMRS ports with values ​​10 and 11, a third DMRS port with value 2, and a fourth DMRS port with value 3. The determined count for the DMRS CDM group without data is 2. The network device according to claim 1.

13. The processor is further configured to facilitate multi-user multi-input multi-output (MU-MIMO) scheduling by indicating five DMRS ports in the DCI, wherein the five DMRS ports include at least two scaled-up DMRS ports. The determined count for the DMRS CDM group without data is 2. The DCI schedules the PDSCH using more than a certain number of layers. The network device according to claim 1.

14. The network device according to claim 13, wherein the specific number of layers is greater than four.

15. A network device, Transmitter and receiver, It is a processor, Determine the demodulation reference signal (DMRS) configuration type and the DMRS port count. Determine the count of DMRS code partitioning multiplexing (CDM) groups without data. The total count of DMRS ports, according to the determined count of the DMRS CDM group without data, the DMRS configuration type, and the count of the DMRS ports, The count of scaled-up DMRS ports, The count of unscaled DMRS ports, The individual values ​​for each DMRS port, This determines the total count of DMRS ports, including A processor configured as follows, Equipped with, The aforementioned transceiver, The user equipment is configured to transmit a physical downlink shared channel (PDSCH) scheduled by downlink control information (DCI), and the DCI indicates the individual values ​​for each DMRS port of the DMRS port. The individual values ​​for each scaled-up DMRS port exceed 7. The DMRS includes two symbols, Network device.

16. The network device according to claim 15, wherein the count of unscaled DMRS ports is 0.

17. The count of the unscaled DMRS ports is at least 1, The count of the scaled-up DMRS port is at least 1, The total count of the DMRS port is 4 or less. The network device according to claim 15.

18. The network device according to claim 17, wherein the PDSCH has four or fewer layers.

19. The network device according to claim 15, wherein the PDSCH has more than four layers.

20. User equipment, Transmitter and receiver, It is a processor, The system receives downlink control information (DCI) from a network device via the transceiver, which includes a pattern of demodulated reference signals (DMRS) ports, which includes a specific count of scaled-up DMRS ports and a specific count of unscaled DMRS ports, and which includes a pattern of DMRS ports corresponding to the individual values ​​of each DMRS port. Receiving DMRS on the DMRS port, which includes the scaled-up DMRS port or the unscaled DMRS port, according to the specific count of the scaled-up DMRS port and the specific count of the unscaled DMRS port as shown in the DCI, A processor configured as follows, Equipped with, The individual values ​​of the scaled-up DMRS ports exceed 7. The DMRS includes one or two symbols, User equipment.

Images