5G NR enhancements for FD-OCC length to support DMRS port configuration

Abstract

A user equipment (UE) configured to: establish a connection with a 5th Generation (5G) new radio (NR) network, where the connection is configured to utilize a cyclic prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM) waveform and a Demodulation Reference Signal (DMRS) Type 1; receiving a DMRS port indication, the DMRS port indication configured to indicate one or more DMRS ports assigned to the UE, where a single symbol DMRS type 1 is configured to support up to 8 DMRS ports, and a dual symbol DMRS type 1 is configured to support up to 16 DMRS ports; and performing a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE.

Description

Background Art

[0001] Fifth generation (5G) New Radio (NR) networks may utilize cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveforms for uplink and / or downlink communications. In 5G NR, under normal circumstances, the network may support up to 8 or 12 demodulation reference signal (DMRS) ports for CP-OFDM, depending on the DMRS configuration type (e.g., DMRS type 1 or DMRS type 2). It has been recognized that there is a need to increase the number of DMRS ports supported by CP-OFDM. Summary of the invention

[0002] Some exemplary embodiments relate to a processor of a user equipment (UE), the processor being configured to: establish a connection with a fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 1; receive a DMRS port indication, the DMRS port indication being configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 1 is configured to support up to 8 DMRS ports and a dual-symbol DMRS type 1 is configured to support up to 16 DMRS ports; and perform a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE.

[0003] Other exemplary embodiments relate to a user equipment (UE) having a transceiver and a processor, the transceiver being configured to communicate with a fifth generation (5G) new radio (NR) network, and the processor being communicatively coupled to the transceiver and configured to: establish a connection with the fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 1; receive a DMRS port indication, the DMRS port indication being configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 1 is configured to support up to 8 DMRS ports and a dual-symbol DMRS type 1 is configured to support up to 16 DMRS ports; and perform a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE.

[0004] Another exemplary embodiment relates to a processor of a user equipment (UE), the processor being configured to: establish a connection with a fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 2; receive a DMRS port indication, the DMRS port indication being configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 2 is configured to support up to 12 DMRS ports and a dual-symbol DMRS type 2 is configured to support up to 24 DMRS ports; and perform a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE.

[0005] Additional exemplary embodiments relate to a user equipment (UE) having a transceiver and a processor, the transceiver being configured to communicate with a fifth generation (5G) new radio (NR) network, and the processor being communicatively coupled to the transceiver and configured to: establish a connection with the fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 2; receive a DMRS port indication, the DMRS port indication being configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 2 is configured to support up to 12 DMRS ports and a dual-symbol DMRS type 2 is configured to support up to 24 DMRS ports; and perform a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0007] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0008] Figure 3 An exemplary base station according to various exemplary embodiments is shown.

[0009] Figures 4a to 4d Examples of code division multiplexing (CDM) groups for different demodulation reference signal (DMRS) configuration types and different DMRS symbol durations are shown.

[0010] Figure 5a to Figure 5b Exemplary frequency domain (FD)-orthogonal cover code (OCC) patterns are shown according to various exemplary embodiments.

[0011] Figure 6Exemplary FD-OCC modes according to various exemplary embodiments are shown.

[0012] Figure 7 Examples of CDM groups configured across PRBs according to various exemplary embodiments are shown.

[0013] Figure 8 A signaling diagram for providing configuration information of CP-OFDM and DMRS ports to a UE according to various exemplary embodiments is shown. DETAILED DESCRIPTION

[0014] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein like elements are provided with like reference numerals.Exemplary embodiments relate to demodulation reference signal (DMRS) ports for cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveforms.

[0015] The exemplary embodiments are described with respect to user equipment (UE). However, reference to UE is provided for illustrative purposes only. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0016] The exemplary embodiments are also described with reference to fifth generation (5G) New Radio (NR) networks. However, reference to 5G NR networks is provided for illustrative purposes only. The exemplary embodiments may be utilized with any network that utilizes CP-OFDM waveforms in the uplink and / or downlink.

[0017] The exemplary embodiments are described with respect to DMRS for CP-OFDM waveforms. Those skilled in the art will appreciate that DMRS is a reference signal that can be used for channel estimation. CP-OFDM can utilize DMRS to implement multi-layer transmission, where each layer corresponds to a different antenna port, for example, a DRMS ​​port. Under normal circumstances, DMRS type 1 can support up to four DMRS ports for single-symbol DMRS and up to eight DMRS ports for dual-symbol DMRS. DMRS type 2 can support up to six DMRS ports for single-symbol DMRS and up to twelve DMRS ports for dual-symbol DMRS. The exemplary embodiments described herein introduce techniques for increasing the number of DMRS ports supported for CP-OFDM.

[0018] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided for illustrative purposes only.

[0019] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 may also communicate with other types of networks (e.g., sixth generation (6G) RAN, 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular network, wireless local area network (WLAN), etc.), and UE 110 may also communicate with the network via a wired connection. Referring to the exemplary embodiment, UE 110 may establish a connection with 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with NR RAN 120.

[0020] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, base stations or access nodes (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to transmit and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0021] Those skilled in the art will appreciate that any relevant process may be performed for the UE 110 to connect to the 5G NR RAN 120. For example, as discussed above, the 5G NR RAN 120 may be associated with a particular cellular provider at which the UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR RAN 120, the UE 110 may transmit corresponding credential information in order to associate with the 5G NR RAN 120. More specifically, the UE 110 may be associated with a particular base station (e.g., gNB 120A).

[0022] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 may refer to an interconnected set of components that manage the operation and traffic of a cellular network. It may include an evolved packet core (EPC) and / or a 5G core (5GC). The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 may generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 may generally be described as a collection of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0023] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. The UE 110 will refer to Figure 1 100. UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, a port for electrically connecting UE 110 to other electronic devices, etc.

[0024] The processor 205 may be configured to execute multiple engines of the UE 110. For example, the engine may include a DMRS port engine 235. The DMRS port engine 235 may perform various operations related to DMRS for CP-OFDM. These operations may include, but are not limited to: receiving configuration information for DMRS; receiving an indication identifying which DMRS ports are allocated to REs assigned to the UE 110; receiving DMRS using the configured DMRS ports; and transmitting DMRS using the configured DMRS ports.

[0025] The engine 235 referenced above is provided as an application (e.g., program) executed by the processor 205 for illustrative purposes only. The functionality associated with the engine 235 may also be represented as a separate combined component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing the signal and other information. The engine may also be embodied as an application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is split between two or more processors (such as a baseband processor and an application processor). The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0026] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables a user to enter input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN (not shown in the figure), traditional RAN (not shown in the figure), WLAN (not shown in the figure), etc. Therefore, the transceiver 225 can operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies).

[0027] Figure 3 An exemplary base station 300 is shown in accordance with various exemplary embodiments. Base station 300 may represent a gNB 120A or any other access node that a UE 110 may use to establish a connection and manage network operations.

[0028] The base station 300 may include a processor 305, a memory arrangement 310, an input / output (I / O) device 315, a transceiver 320, and other components 325. These other components 325 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports for electrically connecting the base station 300 to other electronic devices and / or a power source, and the like.

[0029] The processor 305 may be configured to execute multiple engines of the base station 300. For example, these engines may include a DMRS engine 330. The DMRS port engine 330 may perform various operations related to DMRS for CP-OFDM. These operations may include, but are not limited to, transmitting DMRS configuration information to one or more UEs, allocating DMRS ports to one or more UEs (e.g., single-user multiple input multiple output (SU-MIMO), multi-user MIMO (MU-MIMO), etc.), transmitting to each UE an indication identifying which DMRS ports have been allocated to REs assigned to the UE, transmitting DMRS to one or more UEs, and receiving DMRS from one or more UEs.

[0030] The engine 330 described above as an application (e.g., a program) executed by the processor 305 is merely exemplary. The functionality associated with the engine 330 may also be represented as a separate combined component of the base station 300, or may be a modular component coupled to the base station 300, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuits for receiving signals and processing circuits for processing signals and other information. In addition, in some base stations, the functionality described for the processor 305 is split between multiple processors (e.g., baseband processors, application processors, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0031] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a continuous set of frequencies). Therefore, the transceiver 320 may include one or more components (e.g., radio devices) to enable data exchange with various networks and UEs.

[0032] In various examples described herein, reference is made to 5G NR physical resources arranged in a resource grid, which consists of subcarriers in the frequency domain and OFDM symbols in the time domain. Each element in the resource grid may be referred to as a resource element (RE), and each RE may have a position within the resource grid that may be uniquely identified by coordinates (k, l), where (k) represents a subcarrier position and (l) represents a symbol position.

[0033] A resource block (RB) is referred to as 12 consecutive subcarriers in the frequency domain. An RB can be further characterized as a common resource block (CRB) or a physical resource block (PRB). A CRB can be indexed from 0 upwards in the frequency domain for a specific subcarrier spacing (SCS), and a PRB can be defined within a bandwidth part (BWP) for a specific SCS. There is a defined relationship between CRBs and PRBs such that the location of a BWP and its PRBs can be determined relative to CRB index 0.

[0034] As described above, the exemplary embodiment is described with respect to DMRS type 1 and DMRS type 2. For both DMRS type 1 and DMRS type 2, multiple DMRS ports may be mapped to the same RE. For example, an orthogonal cover code (OCC) of length 2 may be used in the frequency domain (FD-OCC) to enable two DMRS ports to utilize the same RE. When utilizing dual-symbol DMRS, the number of DMRS ports that may be mapped to the same RE may be further increased by using an OCC of length 2 in the time domain (TD-OCC). Throughout this specification, multiple DMRS ports that are configured to use the same RE but separated in the code domain may be referred to as "code division multiplexing (CDM) groups". In order to distinguish between different CDM groups, the exemplary embodiment may refer to CDM group 0, CDM group 1, CDM group 2, etc. Similarly, in order to distinguish between DMRS ports, the exemplary embodiment may refer to port 1, port 2, port 3, port 4, etc. However, the manner in which CDM groups and DMRS ports are numbered throughout this specification is provided for illustrative purposes only and is not intended to limit the exemplary embodiment in any way.

[0035] Figure 4a An example 410 of a DMRS type 1 CDM group for a single symbol DMRS arranged within a PRB is shown according to various exemplary embodiments. Example 410 includes a PRB 412 consisting of 12 subcarriers in the frequency domain and a single symbol in the time domain.

[0036] Example 410 includes CDM group 0 and CDM group 1. Figure 4aIn order to show the mapping of different CDM groups to REs, the REs mapped to CDM group 0 are marked with "0" and the REs mapped to CDM group 1 are marked with "1". For DMRS type 1, each CDM group can be mapped to two REs within a symbol, which are separated from each other by a single subcarrier in the frequency domain. CDM group 0 and CDM group 1 may be interleaved and occupy every other subcarrier within a span of four consecutive subcarriers. For example, CDM group 0 may occupy even-numbered subcarriers (e.g., 0, 2) and CDM group 1 may occupy odd-numbered subcarriers (e.g., 1, 3) (or vice versa). Although not shown in example 410, in some configurations, the CDM group 0 and CDM group 1 pattern may be repeated in the frequency domain using the next entry in the DMRS sequence.

[0037] For DMRS type 1, a single symbol DMRS can support two DMRS ports per CDM group. Example 410 illustrates that two DMRS ports (e.g., port 0, port 1) can belong to CDM group 0 for single symbol DMRS. The DMRS ports of CDM group 0 can utilize the same REs, but they are separated in the code domain using OCCs of length 2 in the frequency domain. Similarly, example 410 illustrates that two DMRS ports (e.g., port 2, port 3) can belong to CDM group 1. The DMRS ports of CDM group 1 can utilize the same REs, but they are separated from each other in the code domain using OCCs of length 2 in the frequency domain. Figure 4a Examples of different orthogonal sequences are illustrated in FIG. 1 using the (+) and (-) signs.

[0038] Figure 4b An example 420 of a DMRS type 1 CDM group for dual-symbol DMRS arranged within a PRB is shown according to various exemplary embodiments. Example 420 includes a PRB 422 consisting of 12 subcarriers in the frequency domain and two symbols in the time domain.

[0039] Example 420 includes CDM group 0 and CDM group 1. Figure 4bIn order to show the mapping of different CDM groups to REs, the REs mapped to CDM group 0 are marked with "0" and the REs mapped to CDM group 1 are marked with "1". For DMRS type 1, each CDM group can be mapped to a total of four REs. Two adjacent REs of the first set in the time domain are separated from two adjacent REs of the second set in the time domain by a single subcarrier in the frequency domain. CDM group 0 and CDM group 1 may be interleaved and occupy every other subcarrier within a span of four consecutive subcarriers. For example, CDM group 0 may occupy even-numbered subcarriers (e.g., 0, 2) and CDM group 1 may occupy odd-numbered subcarriers (e.g., 1, 3), or vice versa. Although not shown in example 420, in some configurations, the pattern of CDM group 0 and CDM group 1 may be repeated in the frequency domain using the next entry in the DMRS sequence.

[0040] For DMRS type 1, dual-symbol DMRS can support four DMRS ports per CDM group. Example 420 illustrates that for dual-symbol DMRS, four DMRS ports (e.g., port 0, port 1, port 4, port 5) can belong to CDM group 0. The DMRS ports of CDM group 0 can utilize the same REs, but they are separated in the code domain using an OCC of 2 in the frequency domain and an OCC of length 2 in the time domain. Similarly, Example 420 illustrates that four DMRS ports (e.g., port 2, port 3, port 6, port 7) belong to CDM group 1. The DMRS ports of CDM group 1 can utilize the same REs, but they are separated from each other in the code domain using an OCC of 2 in the frequency domain and an OCC of length 2 in the time domain. Figure 4b Examples of different orthogonal sequences are illustrated in FIG. 1 using the (+) and (-) signs.

[0041] DMRS type 2 can utilize three CDM groups. For single-symbol DMRS, each DMRS type 2 CDM group can support two DMRS ports. For dual-symbol DMRS, each DMRS type 2 CDM group can support four DMRS ports. Therefore, compared with DMRS type 1, DMRS type 2 can support a larger number of DMRS ports, but has a lower DMRS density per DMRS port.

[0042] Figure 4c An example 430 of a DMRS type 2 CDM group for a single symbol DMRS arranged within a PRB is shown according to various exemplary embodiments. Example 430 includes a PRB 432 consisting of 12 subcarriers in the frequency domain and a single symbol in the time domain.

[0043] Example 430 includes CDM group 0, CDM group 1, and CDM group 2. Figure 4cIn order to show the mapping of different CDM groups to REs, the REs mapped to CDM group 0 are marked with "0", the REs mapped to CDM group 1 are marked with "1", and the REs mapped to CDM group 2 are marked with "2". For DMRS type 2, each CDM group can be mapped to a total of two REs. CDM group 0 can be mapped to two adjacent REs in the frequency domain, CDM group 1 can be mapped to two adjacent REs in the frequency domain, and CDM group 2 can also be mapped to two adjacent REs in the frequency domain. CDM groups 0 to 2 are arranged to occupy six consecutive subcarriers. Although not shown in example 430, in some configurations, CDM group 0, CDM group 1, and CDM group 2 can be repeated in the frequency domain using the next entry of the DMRS sequence.

[0044] For DMRS type 2, a single symbol DMRS can support two DMRS ports per CDM group. Example 430 illustrates that for a single symbol DMRS, two DMRS ports (e.g., port 0, port 1) can belong to CDM group 0. The DMRS ports of CDM group 0 can utilize the same RE, but they are separated in the code domain using an OCC of length 2 in the frequency domain. Example 430 also illustrates that two DMRS ports (e.g., port 2, port 3) can belong to CDM group 1. The DMRS ports of CDM 1 group can utilize the same RE, but they are separated from each other in the code domain using an OCC of length 2 in the frequency domain. Example 430 also illustrates that two DMRS ports (e.g., port 4, port 5) can belong to CDM group 2. The DMRS ports of CDM 2 group can utilize the same RE, but they are separated from each other in the code domain using an OCC of length 2 in the frequency domain. Figure 4c Examples of different orthogonal sequences are illustrated in FIG. 1 using the (+) and (-) signs.

[0045] Figure 4d An example 440 of a DMRS type 2 CDM group for dual-symbol DMRS arranged within a PRB is shown according to various exemplary embodiments. Example 440 includes a PRB 442 consisting of 12 subcarriers in the frequency domain and two symbols in the time domain.

[0046] Example 440 includes CDM group 0, CDM group 1, and CDM group 2. Figure 4dIn order to show the mapping of different CDM groups to REs, the REs mapped to CDM group 0 are marked with "0", the REs mapped to CDM group 1 are marked with "1", and the REs mapped to CDM group 2 are marked with "2". For DMRS type 2, each CDM group can be mapped to a total of four REs. CDM group 0 can be mapped to two adjacent REs in the frequency domain for each DMRS symbol, CDM group 1 can be mapped to two adjacent REs in the frequency domain for each DMRS symbol, and CDM group 2 can also be mapped to two adjacent REs in the frequency domain for each DMRS symbol. CDM groups 0 to 2 are arranged to occupy six consecutive subcarriers. Although not shown in example 440, in some configurations, the pattern of CDM group 0, CDM group 1, and CDM group 2 can be repeated in the frequency domain using the next entry of the DMRS sequence.

[0047] For DMRS type 2, a single symbol DMRS can support four DMRS ports per CDM group. Example 440 illustrates that for dual symbol DMRS, four DMRS ports (e.g., port 0, port 1, port 6, port 7) can belong to CDM group 0. The DMRS ports of CDM group 0 can utilize the same RE, but they are separated in the code domain using an OCC of 2 in the frequency domain and an OCC of length 2 in the time domain. Similarly, Example 440 illustrates that four DMRS ports (e.g., port 2, port 3, port 8, port 9) can belong to CDM group 1. The DMRS ports of CDM group 1 can utilize the same RE, but they are separated from each other in the code domain using an OCC of 2 in the frequency domain and an OCC of 2 in the time domain. Example 440 also illustrates that four DMRS ports (e.g., port 4, port 5, port 10, port 11) can belong to CDM group 2. The DMRS ports of CDM group 2 may utilize the same REs, but they are separated from each other in the code domain using an OCC of 2 in the frequency domain and an OCC of 2 in the time domain. Figure 4d Examples of different orthogonal sequences are shown in FIG. 1 using the (+) and (-) signs.

[0048] For DMRS type 1 and DMRS type 2, multiple PRBs may occupy the same symbol or symbols and be indexed 0 to (N) in the frequency domain. In some configurations, each of the PRBs indexed 0 to N may contain REs mapped to the same CDM group.

[0049] According to some aspects, exemplary embodiments include techniques for implementing larger FD-OCC length modes to support a larger number of DRMS ​​ports. In a first approach, for CP-OFDM, a FD-OCC of length four is used to increase the number of supported DMRS ports. Figure 5a to Figure 5bIn the second method, for CP-OFDM, a FD-OCC of length six is ​​used to increase the number of supported DMRS ports. Figure 6 Let's describe such an example in more detail.

[0050] Figure 5a to Figure 5b Exemplary FD-OCC modes according to various exemplary embodiments are shown. Figure 5a to Figure 5b Each of the FD-OCC patterns in is configured with an FD-OCC of length four.

[0051] Figure 5a FD-OCC patterns 505-515 are shown. FD-OCC pattern 505 shows a dual-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to 16 DMRS ports can be supported. REs occupied by CDM group 0 are marked with "0", and REs occupied by CDM group 1 are marked with "1".

[0052] In FD-OCC pattern 505, for a span of 8 consecutive subcarriers in the frequency domain, CDM group 0 and CDM group 1 occupy every other subcarrier. This is an example of concatenating two opportunities for a conventional CDM group arrangement for DMRS type 1. Although not shown in FIG. 5, FD-OCC pattern 505 is used for one symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to eight DMRS ports can be supported.

[0053] FD-OCC mode 510 shows a dual-symbol DMRS type 2 including CDM group 0, CDM group 1, and CDM group 2 within a PRB, and can support up to 24 DMRS ports. REs occupied by CDM group 0 are marked with "0", REs occupied by CDM group 1 are marked with "1", and REs occupied by CDM group 2 are marked with "2".

[0054] In FD-OCC pattern 510, CDM group 0 occupies a first set of contiguous subcarriers, CDM group 1 occupies a second set of contiguous subcarriers, and CDM group 2 occupies a third set of contiguous subcarriers. This pattern repeats in the second half of the PRB. Thus, CDM group 0 occupies two sets of contiguous subcarriers within the PRB, the two sets of contiguous subcarriers being separated from each other by a set of contiguous subcarriers occupied by CDM group 1 and a set of contiguous subcarriers occupied by CDM group 2. CDM group 1 occupies two sets of contiguous subcarriers within the PRB, the two sets of contiguous subcarriers being separated from each other by a set of contiguous subcarriers occupied by CDM group 2 and a set of contiguous subcarriers occupied by CDM group 0. CDM group 2 occupies two sets of contiguous subcarriers within the PRB, the two sets of contiguous subcarriers being separated from each other by a set of contiguous subcarriers occupied by CDM group 0 and a set of contiguous subcarriers occupied by CDM group 1. This is an example of two opportunities for cascading a conventional CDM group arrangement for DMRS type 2. Although not shown in FIG. 5 , the FD-OCC mode 510 is used for one symbol DMRS type 2 including CDM group 0, CDM group 1, and CDM group 2 within a PRB, and up to 12 DMRS ports may be supported.

[0055] As noted above, FD-OCC pattern 505 and FD-OCC pattern 510 are examples of two opportunities to concatenate conventional CDM group arrangements for DMRS type 1 and DMRS type 2, respectively. This approach may allow for better co-scheduling compatibility with conventional approaches.

[0056] FD-OCC pattern 515 shows a dual-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and can support up to 16 DMRS ports. REs occupied by CDM group 0 are marked with "0", and REs occupied by CDM group 1 are marked with "1".

[0057] In the FD-OCC pattern 515, CDM group 0 occupies a first set of contiguous subcarriers and CDM group 1 occupies a second set of contiguous subcarriers. This pattern is repeated in the PRB. Thus, CDM group 0 occupies two sets of contiguous subcarriers within the PRB, the two sets of contiguous subcarriers being separated from each other by a set of contiguous subcarriers occupied by CDM group 1, and CDM group 1 occupies two sets of contiguous subcarriers within the PRB, the two sets of contiguous subcarriers being separated from each other by a set of contiguous subcarriers occupied by CDM group 0. Although not shown in FIG. 5 , the FD-OCC pattern 515 is used for one symbol DMRS type 1 including CDM group 0 and CDM group 1 within the PRB, and up to eight DMRS ports may be supported.

[0058] Figure 5bFD-OCC patterns 520 to 525 are shown. FD-OCC pattern 520 shows a two-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to 16 DMRS ports can be supported. In FD-OCC pattern 520, each CDM group includes four consecutive subcarriers. REs occupied by CDM group 0 are marked with "0", and REs occupied by CDM group 1 are marked with "1". Although not shown in Figure 5, FD-OCC pattern 520 is used for one-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to eight DMRS ports can be supported.

[0059] FD-OCC pattern 525 shows a dual-symbol DMRS type 2 including CDM group 0, CDM group 1, and CDM group 2 within a PRB, and up to 24 DMRS ports can be supported. In FD-OCC pattern 525, each CDM group includes four consecutive subcarriers. REs occupied by CDM group 0 are marked with "0", REs occupied by CDM group 1 are marked with "1", and REs occupied by CDM group 2 are marked with "2". Although not shown in Figure 5, FD-OCC pattern 525 is used for one-symbol DMRS type 2 including CDM group 0, CDM group 1, and CDM group 0 within a PRB, and up to 12 DMRS ports can be supported.

[0060] FD-OCC patterns 515 to 525 are more robust to frequency selective fading than FD-OCC patterns 505-510. FD-OCC pattern 520 and FD-OCC pattern 525 may be considered the most robust options with respect to frequency selective fading (eg, channels with large delay spread).

[0061] Figure 6 Exemplary FD-OCC modes according to various exemplary embodiments are shown. Figure 6 Each FD-OCC pattern in is configured with an FD-OCC of length six.

[0062] FD-OCC pattern 605 shows a dual-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to 16 DMRS ports can be supported. REs occupied by CDM group 0 are marked with "0", and REs occupied by CDM group 1 are marked with "1". In FD-OCC pattern 605, CDM group 0 and CDM group 1 occupy every other subcarrier of the PRB. This is an example of concatenating three opportunities for the traditional CDM group arrangement for DMRS type 1. Although in Figure 6Not shown, but the FD-OCC mode 565 is used for one symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to twelve DMRS ports can be supported.

[0063] As noted above, FD-OCC pattern 605 is an example of concatenating three opportunities for a conventional CDM group arrangement for DMRS Type 1. This approach may allow for better co-scheduling compatibility with conventional approaches.

[0064] FD-OCC pattern 610 shows a dual-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to 24 DMRS ports can be supported. REs occupied by CDM group 0 are marked with "0" and REs occupied by CDM group 1 are marked with "1". In FD-OCC pattern 610, CDM group 0 occupies a first set of three consecutive subcarriers and CDM group 1 occupies a second set of three consecutive subcarriers. This pattern is repeated in the PRB. Therefore, CDM group 0 occupies two sets of three consecutive subcarriers within the PRB, and the two sets of three consecutive subcarriers are separated from each other by the set of three consecutive subcarriers occupied by CDM group 1, and CDM group 1 occupies two sets of three consecutive subcarriers within the PRB, and the two sets of three consecutive subcarriers are separated from each other by the set of three consecutive subcarriers occupied by CDM group 0. Although in Figure 6 Not shown, but the FD-OCC mode 610 is used for one symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to twelve DMRS ports can be supported.

[0065] FD-OCC pattern 615 shows a dual-symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and can support up to 24 DMRS ports. REs occupied by CDM group 0 are marked with "0", and REs occupied by CDM group 1 are marked with "1". In FD-OCC pattern 615, each CDM group includes six consecutive subcarriers. Although in Figure 6 Not shown, but the FD-OCC mode 615 is used for one symbol DMRS type 1 including CDM group 0 and CDM group 1 within a PRB, and up to twelve DMRS ports can be supported.

[0066] FD-OCC patterns 610-615 are more robust to frequency selective fading than FD-OCC pattern 605. FD-OCC pattern 615 may be considered the most robust option with respect to frequency selective fading (eg, channels with large delay spread).

[0067] The network may support a variety of different FD-OCC modes to handle different situations, and use one or more radio resource control (RRC) messages to configure different FD-OCC modes for UE 110. For example, the network may indicate the FD-OCC mode for downlink communication in the DMRS-DownlinkConfig information element (IE), and indicate the FD-OCC mode for uplink communication in the DMRS-UplinkConfig IE. In some embodiments, the network may configure UE 110 with a variety of different modes, and semi-statically or dynamically change the FD-OCC mode to be used. For example, the network may configure UE 110 with a variety of different FD-OCC modes for uplink communication and / or downlink communication. The network may then transmit a medium access control (MAC) control element (CE) or downlink control information (DCI) to semi-statically or dynamically change the FD-OCC mode to be used.

[0068] For DMRS type 1, when using FD-OCC of length 4, there may be a situation where a CDM group may span two PRBs or PRGs. Those skilled in the art will understand that a PRG refers to a physical resource block group configured for a physical downlink shared channel (PDSCH). Each PRG contains multiple PRBs (e.g., 2 PRBs, 4 PRBs, wideband). Figure 7 Let's describe such an example in more detail.

[0069] It has been discovered that when increasing the FD-OCC to length four for DMRS Type 1 to support additional DMRS ports, enhancements and techniques are needed that take into account the possibility of CDM groups crossing PRB and / or PRG boundaries.

[0070] Figure 7 Examples of CDM groups configured across PRBs according to various exemplary embodiments are shown.

[0071] Example 705 shows a dual-symbol DMRS type 1, which includes CDM group 0 and CDM group 1 occupying symbols spanning the first PRB and the second PRB. REs mapped to CDM group 0 are marked with "0", and REs mapped to CDM group 1 are marked with "1".

[0072] In this example, consecutive PRBs are indexed, where even-indexed PRBs 710 are shown adjacent to odd-indexed PRBs 711. Furthermore, even-indexed PRBs 710 are shown as part of a first PRG(n), and odd-indexed PRBs 711 are shown as part of a second PRG(n+1). In example 705, the FD-OCC mode is identical to Figure 6The FD-OCC pattern 605 is the same as the FD-OCC pattern shown in FIG.

[0073] Example 715 shows a dual-symbol DMRS type 1, which includes CDM group 0 and CDM group 1 occupying symbols spanning the first PRB and the second PRB. REs mapped to CDM group 0 are marked with "0", and REs mapped to CDM group 1 are marked with "1".

[0074] In this example, consecutive PRBs are indexed, where even-indexed PRBs 720 are shown adjacent to odd-indexed PRBs 721. In addition, even-indexed PRBs 720 are shown as part of a first PRB (n), and odd-indexed PRBs 721 are shown as part of a second PRB (n+1). In example 715, the FD-OCC mode is similar to Figure 6 The FD-OCC pattern 615 is the same as the FD-OCC pattern shown in FIG.

[0075] The exemplary embodiments provided below take into account the possibility that a CDM group crosses a PRB and / or PRG boundary (non-limiting examples of which are Figure 7 These exemplary embodiments may be used to support implementations of DMRS Type 1 with an OCC of length four for uplink communications and / or downlink communications.

[0076] In a first approach, when a FD-OCC of length four is used for DMRS Type 1 to support an increased number of DMRS ports (e.g., 8, 16, etc.), UE 110 may not wish to have any CDM groups that cross PRG boundaries. Thus, for downlink communications, the network may not transmit and UE 110 may not receive a CDM group that includes REs that occupy a first PRG and REs that occupy a second different PRG with a single CDM group (e.g., Figure 7 For uplink communications, the network may not receive and UE 110 may not transmit a signal including REs of a first PRG and a second different PRG occupied by a single CDM group (e.g., Figure 7 The signals of the CDM group are arranged in the manner of PRG(n) and PRG(n+1)).

[0077] In a second method, when a FD-OCC of length four is used for DMRS type 1 to support an increased number of DMRS ports (e.g., 8, 16, etc.), UE 110 may not want to have any CDM groups that cross PRB boundaries. Therefore, for downlink communications, the network may not transmit and UE 110 may not receive REs that occupy a first PRB and a second different PRB with a single CDM group (e.g., Figure 7For uplink communication, the network may not receive and UE 110 may not transmit a signal including REs of a first PRG and REs of a second different PRG occupied by a single CDM group (e.g., Figure 7 The signals of the CDM group are arranged in the manner of PRG(n) and PRG(n+1)).

[0078] In another approach, the use of FD-OCC length four may be limited to wideband PRGs only for DMRS Type 1. Thus, the network may configure the use of FD-OCC length four only for DMRS Type 1 when wideband PRGs are also configured.

[0079] In another approach, when DMRS type 1 is configured with a FD-OCC of length four and a CDM group is configured to cross a PRG boundary (e.g., occupying REs of a first PRG and REs of a second, different PRG), the UE 110 may assume that the precoding used in the two adjacent PRGs is the same. For downlink communications, the UE 110 may make this implicit determination and decode the contents of the REs of the CDM group across the PRG boundary using the assumption that the precoding of the two PRGs is the same. For uplink communications, the UE 110 may only map the contents of the CDM group to cross the PRG boundary if the precoding of the two PRGs is the same.

[0080] Furthermore, the exemplary embodiments introduce techniques to prevent CDM groups from being configured to perform PDSCH frequency domain resource allocation across PRG boundaries. Figure 8 A signaling diagram 800 is shown for providing configuration information of CP-OFDM and DMRS ports to UE 110 according to various exemplary embodiments. Signaling diagram 800 includes UE 110 and gNB 120A.

[0081] In 805, UE 110 receives configuration information. The configuration information may be received in a radio resource control (RRC) message, a medium access control (MAC) control element (CE), downlink control information (DCI), or any other suitable type of information.

[0082] The configuration information may include DMRS port configuration information, such as, but not limited to, a maximum number of supported DMRS ports and a maximum number of supported CDM groups.

[0083] In addition, the network may also provide other configuration information to UE 110. For example, in 5G NR, the PRG configuration for frequency selective precoding may be configured to include two PRBs, four PRBs, or in a wideband configuration. Those skilled in the art will appreciate that the PRG is configured with reference to point A (e.g., common resource block 0).

[0084] For downlink frequency domain resource allocation (FDRA), 5G NR supports FDRA type 0 and FDRA type 1. Those skilled in the art will appreciate that for FDRA type 0, a bitmap can be used where each bit represents a corresponding resource block group (RBG). The RGB size selection is hard-coded in the 3GPP specification for different bandwidth part (BWP) sizes. The RBGs can be counted with reference to point A (e.g., common resource block 0).

[0085] As will be described in more detail below, the exemplary embodiment introduces conditions to prevent CDM groups from being configured across PRG boundaries. These conditions may be present in the configuration information of 805.

[0086] In 810, UE 110 receives a DMRS port indication from gNB 120A. When the network schedules PDSCH or PUSCH, the network may indicate which DMRS ports are assigned to UE 110. The DMRS port indication may indicate which DMRS ports are to be used for DMRS transmission. In addition, the DMRS port indication may facilitate MU-MIMO operation and / or DMRS power boost.

[0087] DMRS ports may be applicable to uplink and / or downlink. Thus, in 815a, if the scheduling DCI is used for PUSCH or any other appropriate type of uplink communication, the UE 110 may use the indicated DMRS port to perform uplink transmission. Alternatively, in 815b, if the scheduling DCI is used for PDSCH or any other appropriate type of downlink communication, the UE 110 may use the indicated DMRS port to perform downlink reception.

[0088] As described above, according to some aspects, the exemplary implementation introduces the following conditions to avoid CDM groups being configured to perform PDSCH FDRA type 0 across PRG boundaries. The exemplary conditions may be present in the configuration information provided to UE 110 (e.g., 805 of signaling diagram 800), or hard-coded in the 3GPP specification and used in combination with each other or independently of each other.

[0089] In one example, a CDM group configuration may be applied for each RBG. The starting point of the CDM group arrangement may be point A (e.g., common resource block 0). In another example, the first and last indicated RBGs in the bitmap may contain an even number of PRBs. Other RBGs in the bitmap are guaranteed to have an even number of PRBs.

[0090] In another example, if the first indicated RBG in the bitmap contains an odd number of PRBs, the first PRB is assumed to have no DMRS or the DMRS is ignored. If the last indicated RBG in the bitmap contains an odd number of PRBs, the last PRB is assumed to have no DMRS or the DMRS is ignored.

[0091] For FDRA Type 1, the frequency resource allocation may be a set of contiguously allocated PRBs and a plurality of contiguously allocated PRBs indicated by a starting PRB relative to the beginning of a BWP.

[0092] According to some aspects, the exemplary embodiments introduce the following conditions to avoid CDM groups being configured for PDSCH FDRA Type 1 across PRG boundaries. The exemplary conditions may be present in configuration information provided to UE 110 (e.g., 805 of signaling diagram 800), or hard-coded in 3GPP specifications and used in combination with each other or independently of each other.

[0093] In the following examples, it is assumed that the CDM group is applied starting from point A. In one example, for FDRA type 1 indicated / configured for PDSCH, the starting PRB has an even number of PRBs starting from point A. In another example, for FDRA type 1 indicated / configured for PDSCH, an even number of PRBs (e.g., an even number of PRBs in length) is scheduled. In another example, for FDRA type 1 indicated / configured for PDSCH, if the starting PRB has an odd number of PRBs starting from point A, it is assumed that the first PRB has no DMRS or ignores DMRS. In another example, for FDRA type 1 indicated / configured for PDSCH, if the last scheduled PRB has an odd number of PRBs starting from point A, it is assumed that the last scheduled PRB has no DMRS or ignores DMRS.

[0094] In another method, in order to avoid the CDM group being configured for PDSCH FDRA type 1 across PRG boundaries, one or more of the following conditions may be implemented. The exemplary conditions may be present in the configuration information provided to the UE 110 (e.g., 805 of the signaling diagram 800), or may be hard-coded in the 3GPP specification and used in combination with each other or independently of each other. In the following examples, it is assumed that the CDM group is applied starting from the first scheduled PRB. In one example, an even number of PRBs (e.g., an even length) is scheduled. In another example, for the FDRA type 1 indicated / configured for the PDSCH, if an odd number of PRBs are scheduled, it is assumed that the last scheduled PRB has no DMRS or the DMRS is ignored.

[0095] Example

[0096] In a first embodiment, a processor of a user equipment (UE) is configured to: establish a connection with a fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 1; receive a DMRS port indication, wherein the DMRS port indication is configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 1 is configured to support up to 8 DMRS ports and a dual-symbol DMRS type 1 is configured to support up to 16 DMRS ports; and perform a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE.

[0097] In a second embodiment, the processor according to the first embodiment, wherein the connection further comprises a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 0 configuration.

[0098] In a third embodiment, the processor according to the second embodiment, wherein each resource block group (RBG) is configured with a code division multiplexing (CDM) group.

[0099] In a fourth embodiment, the processor according to the second embodiment, wherein code division multiplexing (CDM) groups are applied starting from point A common resource blocks.

[0100] In a fifth embodiment, the processor according to the second embodiment, wherein the bitmap indicates a resource block group (RBG) configuration, wherein a first and a last indicated RBG in the bitmap contain an even number of physical resource blocks (PRBs).

[0101] In a sixth embodiment, the processor according to the second embodiment, wherein a bitmap indicates a resource block group (RBG) configuration, wherein a first indicated RBG in the bitmap contains an odd-even number of physical resource blocks (PRBs), and wherein the first indicated PRB does not contain a DMRS or the first indicated PRB contains a DMRS and the DMRS is ignored.

[0102] In a seventh embodiment, the processor according to the second embodiment, wherein the bitmap indicates a resource block group (RBG) configuration, wherein the last indicated RBG in the bitmap contains an odd number of physical resource blocks (PRBs), and wherein the last indicated PRB does not contain a DMRS or the last indicated PRB contains a DMRS and the DMRS is ignored.

[0103] In an eighth embodiment, the processor according to the first embodiment, wherein the connection further comprises a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 1 configuration.

[0104] In a ninth embodiment, the processor according to the eighth embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A, wherein a starting physical resource block (PRB) has an even number of PRBs starting from point A.

[0105] In a tenth embodiment, the processor according to the eighth embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A and an even number of physical resource blocks (PRBs) are scheduled.

[0106] In an eleventh embodiment, the processor according to the eighth embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A, wherein a starting physical resource block (PRB) has an odd number of PRBs starting from point A, and wherein the first PRB does not contain a DMRS or the first PRB contains an ignored DMRS.

[0107] In a twelfth embodiment, the processor according to the eighth embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A, wherein the last physical resource block (PRB) has an odd number of PRBs starting from point A, and wherein the last PRB does not contain a DMRS or the last PRB contains an ignored DMRS.

[0108] In a thirteenth embodiment, the processor according to the eighth embodiment, wherein a code division multiplexing (CDM) group is applied starting from a first scheduled physical resource block (PRB), wherein an even number of PRBs are scheduled.

[0109] In a fourteenth embodiment, the processor according to the eighth embodiment, wherein a code division multiplexing (CDM) group is applied starting from a first scheduled physical resource block (PRB), wherein an odd number of PRBs are scheduled, and wherein the last PRB does not contain a DMRS or the last PRB contains an ignored DMRS.

[0110] In a fifteenth embodiment, a user equipment (UE) includes a transceiver configured to communicate with a fifth generation (5G) new radio (NR) network and a processor according to any one of the first to fourteenth embodiments communicatively coupled to the transceiver.

[0111] In a sixteenth embodiment, a processor of a user equipment (UE) is configured to: establish a connection with a fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 2; receive a DMRS port indication, wherein the DMRS port indication is configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 2 is configured to support up to 12 DMRS ports and a dual-symbol DMRS type 2 is configured to support up to 24 DMRS ports; and perform a transmission operation or a reception operation using the one or more DMRS ports assigned to the UE.

[0112] In a seventeenth embodiment, the processor of the sixteenth embodiment, wherein the connection further comprises a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 0 configuration.

[0113] In an eighteenth embodiment, the processor according to the seventeenth embodiment, wherein each resource block group (RBG) configures a code division multiplexing (CDM) group.

[0114] In a nineteenth embodiment, the processor of the seventeenth embodiment, wherein the bitmap indicates a resource block group (RBG) configuration, wherein the first and last indicated RBGs in the bitmap contain an even number of physical resource blocks (PRBs).

[0115] In a twentieth embodiment, a processor according to the seventeenth embodiment, wherein a bitmap indicates a resource block group (RBG) configuration, wherein a first indicated RBG in the bitmap contains an even number of physical resource blocks (PRBs), and wherein the last indicated PRB does not contain a DMRS or the first indicated PRB contains a DMRS and the DMRS is ignored.

[0116] In a twenty-first embodiment, a processor according to the seventeenth embodiment, wherein a bitmap indicates a resource block group (RBG) configuration, wherein a last indicated RBG in the bitmap contains an odd-even number of physical resource blocks (PRBs), and wherein the last indicated PRB does not contain a DMRS or the first indicated PRB contains a DMRS and the DMRS is ignored.

[0117] In a twenty-second embodiment, the processor of embodiment sixteen, wherein the connection further comprises a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 1 configuration.

[0118] In a twenty-third embodiment, the processor of the twenty-second embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A, wherein a starting physical resource block (PRB) has an even number of PRBs starting from point A.

[0119] In a twenty-fourth embodiment, the processor of the twenty-second embodiment, wherein code division multiplexing (CDM) groups are applied starting from point A and an even number of physical resource blocks (PRBs) are scheduled.

[0120] In a twenty-fifth embodiment, a processor according to the twenty-second embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A, wherein a starting physical resource block (PRB) has an odd number of PRBs starting from point A, and wherein the first PRB does not contain a DMRS or the first PRB contains an ignored DMRS.

[0121] In a twenty-sixth embodiment, the processor according to the twenty-second embodiment, wherein a code division multiplexing (CDM) group is applied starting from point A, wherein the last physical resource block (PRB) has an odd number of PRBs starting from point A, and wherein the last PRB does not contain a DMRS or the last PRB contains an ignored DMRS.

[0122] In a twenty-seventh example, the processor according to the twenty-second embodiment, wherein a code division multiplexing (CDM) group is applied starting from a first scheduled physical resource block (PRB), wherein an even number of PRBs are scheduled.

[0123] In a twenty-eighth embodiment, a processor according to the twenty-second embodiment, wherein a code division multiplexing (CDM) group is applied starting from a first scheduled physical resource block (PRB), wherein an odd number of PRBs are scheduled, and wherein the last PRB does not contain a DMRS or the last PRB contains an ignored DMRS.

[0124] In a twenty-ninth embodiment, a user equipment (UE) includes a transceiver configured to communicate with a fifth generation (5G) new radio (NR) network and a processor according to any one of the sixteenth to twenty-eighth embodiments communicatively coupled to the transceiver.

[0125] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0126] Although this application describes various embodiments, each having different features in various combinations, those skilled in the art will understand that any feature of one embodiment may be combined with features of other embodiments in any manner that is not expressly negated or that is not functionally or logically inconsistent with the operation of the device or the prescribed function of the disclosed embodiment.

[0127] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0128] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, it is intended that the present disclosure covers modifications and variations of the present disclosure as long as they fall within the scope of the appended claims and their equivalents.

Claims

1. A processor of a user equipment (UE), the processor being configured to: establishing a connection with a fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 1; receiving a DMRS port indication configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 1 is configured to support up to 8 DMRS ports and a dual-symbol DMRS type 1 is configured to support up to 16 DMRS ports; as well as A transmission operation or a reception operation is performed using the one or more DMRS ports assigned to the UE.

2. The processor of claim 1, wherein the connection is further configured with a frequency domain (FD)-orthogonal cover code (OCC) of length 4.

3. The processor of claim 2, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group occupying every other subcarrier across a span of 8 consecutive subcarriers of the PRB.

4. The processor of claim 2, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, wherein the first CDM group occupies two sets of two consecutive subcarriers of the PRB, and The second CDM group occupies two sets of two consecutive subcarriers of the PRB.

5. The processor of claim 2, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, The first CDM group occupies a set of 4 consecutive subcarriers of the PRB, and The second CDM group occupies a set of 4 consecutive subcarriers of the PRB.

6. The processor of claim 2, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, Neither the first CDM group nor the second CDM group is configured to cross a PRB boundary.

7. The processor of claim 2, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, Wherein neither the first CDM group nor the second CDM group is configured to cross a physical resource block group (PRG) boundary.

8. The processor of claim 2, wherein the FD-OCC of length 4 is configured only for wideband physical resource block group (PRG) configuration.

9. The processor of claim 2, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, wherein the first CDM group and the second CDM group are configured to cross a PRG boundary between adjacent first physical resource block groups (PRGs) and second PRGs, and Wherein precoding is used in both the first PRG and the second PRG.

10. The processor of claim 1, wherein the connection is further configured with a frequency domain (FD)-orthogonal cover code (OCC) of length 6.

11. The processor of claim 10, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group occupying every other subcarrier of the PRB.

12. The processor of claim 10, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, wherein the first CDM group occupies two sets of 3 consecutive subcarriers of the PRB, and The second CDM group occupies two sets of 3 consecutive subcarriers of the PRB.

13. The processor of claim 10, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group and a second CDM group, wherein the first CDM group occupies a set of 6 consecutive subcarriers of the PRB, and The second CDM group occupies a set of 6 consecutive subcarriers of the PRB.

14. The processor of claim 1, wherein the UE is configured with multiple frequency domain (FD)-orthogonal cover code (OCC) patterns using radio resource control (RRC) signaling.

15. The processor of claim 14, further configured to: Downlink control information (DCI) is received, the DCI being configured to change a configured FD-OCC mode from a first FD-OCC mode to a second different FD-OCC mode.

16. The processor of claim 14, further configured to: A medium access control (MAC) control element (CE) is received, the DCI being configured to change a configured FD-OCC mode from a first FD-OCC mode to a second different FD-OCC mode.

17. A processor of a user equipment (UE), the processor being configured to: establishing a connection with a fifth generation (5G) new radio (NR) network, wherein the connection is configured to utilize a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and a demodulation reference signal (DMRS) type 2; receiving a DMRS port indication configured to indicate one or more DMRS ports assigned to the UE, wherein a single-symbol DMRS type 2 is configured to support up to 12 DMRS ports and a dual-symbol DMRS type 2 is configured to support up to 24 DMRS ports; as well as A transmission operation or a reception operation is performed using the one or more DMRS ports assigned to the UE.

18. The processor of claim 17, wherein the connection is further configured with a frequency domain (FD)-orthogonal cover code (OCC) of length 4.

19. The processor of claim 18, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group, a second CDM group, and a third CDM group, wherein the first CDM group occupies two sets of two consecutive subcarriers of the PRB, wherein the second CDM group occupies two sets of two consecutive subcarriers of the PRB, and The third CDM group occupies two sets of two consecutive subcarriers of the PRB.

20. The processor of claim 18, wherein a physical resource block (PRB) comprises at least a first code division multiplexing (CDM) group, a second CDM group, and a third CDM group, The first CDM group occupies a set of 4 consecutive subcarriers of the PRB, wherein the second CDM group occupies a set of 4 consecutive subcarriers of the PRB, and The third CDM group occupies a set of 4 consecutive subcarriers of the PRB.

21. The processor of claim 20, wherein code division multiplexing (CDM) is applied starting from point A common resource blocks.

Images