Upper layer design for release 16 mimo extensions

Abstract

To provide a method and a device for forming a full-power sending mode in user equipment (UE).SOLUTION: In a communication network, a full-power sending mode includes a mode 0 and a mode 3 and these mode are obtained by expanding previous modes disclosed in the 3GPP specification. The UE collects the number of ports, supported modes such as supported coherency schemes, and configuration capabilities, and transfers the configuration capabilities to a network. The network analyzes received information and selects a full-power sending mode supported on the basis of the UE capability. After that, the selection is sent to the UE by a PUSCH-Config message. The UE extracts the selection from the PUSCH-Config message and forms its radio machine accordingly.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] Various embodiments may relate generally to the field of wireless communications. Summary of the Invention

[0002] In one embodiment, a User Equipment (UE) is configured by the network to operate in a full power transmission mode. The network sends a PUSCH-Config message to the UE identifying the full power transmission mode. The network can select any one of four different modes by modifying the contents of the PUSCH-Config message.

[0003] In another embodiment, the UE notifies the network of its capabilities. The UE can specify whether it is capable of full power transmission and the number of ports the UE has that can function at full power transmission. The network sends a PUSCH-Config message to the UE, which configures the UE based on the information received from the UE. In this embodiment, fewer than four modes may be available for configuration, depending on the number of ports for full power transmission that the UE identifies.

[0004] In another embodiment, the network further configures port selection in the UE. When the UE is capable of two-port fully coherent operation, the UE informs the network which modes it supports. When the network attempts to configure two-port uplink operation, the network adjusts the configuration based on the UE's codebook subset and capabilities. Specifically, the network adjusts the configuration based on whether the codebook subset is noncoherent or whether the codebook subset is configured as fullyAndPartialAndNonCoherent.

[0005] In another embodiment, the network can configure port selection in a four-port UE. When the UE is capable of four-port fully coherent operation, the UE informs the network which modes it supports. When the network attempts to configure four-port uplink operation, the network adjusts the configuration based on the UE's codebook subset and capabilities. Specifically, the network adjusts the configuration based on whether the codebook subset is noncoherent or whether the codebook subset is configured as fullyAndPartialAndNonCoherent.

[0006] In another embodiment, a UE includes a memory, a transceiver, and one or more processors. The processor receives at least one full power transmission mode from the memory and causes the transceiver to transmit a capability message to the network including at least one supported full power transmission mode capability. The processor receives a configuration message from the network via the transceiver and extracts a selected full power transmission mode from the configuration message. The processor then configures the transceiver according to the selected full power transmission mode.

[0007] In an embodiment, the configuration message is a PUSCH-Config message.

[0008] In an embodiment, the transceiver includes a plurality of logical ports, and the memory stores the number and coherency capabilities of the plurality of logical ports of the user equipment.

[0009] In an embodiment, the capabilities message includes the number of logical ports and coherency capabilities of the user equipment.

[0010] In an embodiment, the selected full power transmission mode is one of four modes and is selected based on the capabilities of the user equipment.

[0011] In an embodiment, the four modes include Mode 0, in which all power scaling is set to 1, and Mode 3, in which all power scaling is set equal to the ratio of the number of non-zero power ports of the configured TPMI to the maximum number of ports of the user equipment.

[0012] In another embodiment, a method for selecting a communication scheme in a user equipment is disclosed. In the method, the user equipment determines whether it is configured with a first configuration, a second configuration, or both the first and second configurations. Then, in response to determining that the user equipment is configured with only the first configuration or only the second configuration, it analyzes a first set of conditions or a second set of conditions, respectively. Based on the analysis, the UE sets the selected communication scheme to one of the first communication scheme or the second communication scheme.

[0013] In an embodiment, the first configuration is a configuration in which RepSchemeEnabler is configured in the user equipment, and a first set of conditions is analyzed in response to RepSchemeEnabler being configured in the user equipment, and the first set of conditions includes: the user equipment does not expect RepNum16 to be configured in any one entry of the PDSCH-TimeDomainResourceAllocation, or the user equipment ignores RepNum16 configured in any one entry of the PDSCH-TimeDomainResourceAllocation, or the user equipment does not expect Downlink Control Information (DCI) to indicate an entry in the PDSCH-TimeDomainResourceAllocation that includes RepNum16.

[0014] In an embodiment, the user equipment is further configured with two TCI states in the DCI and two DMRS CDM groups in the DCI, and the user equipment is expected to be configured with Scheme 1a, or a Spatial Domain Multiplexing (SDM) scheme, or a Non Coherent Joint Transmission (NCJT) scheme, regardless of other configurations including RepSchemeEnabler or Time Domain Resource Allocation (TDRA) in the DCI.

[0015] In an embodiment, the at least one full power transmit mode capability includes Mode 0 and Mode 3, where Mode 0 sets all power scaling to 1 and Mode 3 sets all power scaling equal to the ratio of the number of non-zero power ports of the configured TPMI to the maximum number of ports of the user equipment.

[0016] In an embodiment, the number of logical ports is two, the coherency capability includes full coherence, and the selected full power transmission mode includes one of mode 0 or mode 2, where mode 2 sets some TPMIs to power scaling 1 and other TPMIs to another power scaling value.

[0017] In an embodiment, the number of logical ports is four, the coherency capability includes full coherence, and the selected full power transmission mode includes one of mode 0 or mode 2, where mode 2 sets some of the four TPMIs to power scaling 1 and sets other TPMIs to another power scaling value.

[0018] In an embodiment, it is further determined that the user equipment is served by multiple cells. In response, a selection is made to set the BDFactorR complexity value at a per-cell level or a per-cell group level. Then, in response to the per-cell level selection, the BDFactorR for each cell of the multiple cells is set separately, or in response to the per-cell group level selection, the same BDFactorR is set for all cells in a cell group.

[0019] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed 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 uses should be clearly indicated to users. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 1 illustrates an exemplary wireless communication environment, according to one embodiment. [Figure 2] FIG. 2 is a block diagram of an exemplary user equipment according to one embodiment. [Figure 3] FIG. 1 is a functional block diagram of an exemplary wireless communication environment according to one embodiment. [Figure 4] 1 is a flowchart of a method for configuring a full power transmission mode in a UE. [Figure 5] FIG. 10 is a flowchart diagram of a method for configuring PDCCH complexity. [Figure 6] 1 is a flowchart of an example method for configuring a communication scheme on a UE. [Figure 7] FIG. 1 is a flowchart diagram of an exemplary method for selecting a communication scheme according to an embodiment of the present disclosure. [Figure 8]FIG. 1 illustrates an example system for implementing measurement signal collision resolution according to some embodiments of the present disclosure. [Figure 9] FIG. 1 is a block diagram of an exemplary general computer system in which certain aspects of the present disclosure may be implemented. DETAILED DESCRIPTION OF THE INVENTION

[0021] Release 16 of the 3GPP specifications describes certain MIMO enhancements over previous implementations. For example, Release 16 describes multi-beam enhancements that reduce overhead and latency. Beam quality measurement and reporting is also available in L1-SINR. Additionally, beam failure recovery is available in the second cell. However, as a result of these advantages, Release 16 does not specify how a UE in a 3GPP environment can perform full power transmission. This disclosure provides various mechanisms for configuring a UE in a 3GPP environment to perform full power transmission.

[0022] Full power transmission for uplink transmission allows the UE to transmit at full power, however, current 3GPP specifications do not define MAC-level and RRC-level configurations to support the MIMO enhancements of Release 16.

[0023] In practice, an access point (e.g., eNodeB) transmits information about the precoding matrix to be used as part of downlink control information to the UE. This precoding matrix is ​​called the Transmission Precoder Matrix Indicator (TPMI). Release 16 of the 3GPP specifications currently supports two full power transmission modes. In Mode 1, a new coherently transmitted Precoder Matrix Indicator (TPMI) is added to the partially coherent and / or non-coherent codebook subset to support full power transmission. Furthermore, power scaling follows the behavior of Release 15 in that the power scaling of each TPMI is set to the ratio of the number of non-zero ports to the maximum number of ports. In Mode 2, the UE can indicate to the network a list of TPMIs for which the UE can support full power transmission. These TPMIs are given a power scaling of 1. The remaining TPMIs are given a power scaling equal to the ratio of the number of non-zero ports to the actual number of ports (configured by the network). The following disclosure describes various methods and / or configurations by which the network can configure full power mode, according to various embodiments.

[0024] 1 illustrates an exemplary wireless communication environment 100, according to one embodiment. Environment 100 includes base stations 110 and 120, each having a respective coverage area 110a and 120a. In one embodiment, base stations 110 and 120 are gNodeBs, eNodeBs, or access points connected to another network. Base stations 110 and 120 are connected to a network backend and provide cellular connectivity to devices within their respective coverage areas.

[0025] An access point 130 is also located in the environment 100 and may include its own coverage area 130a. The access point may be any other type of transmission and reception point (TRP), such as a macrocell, small cell, picocell, femtocell, remote radio head, relay node, etc. The base stations 110, 120 and the access point 130 together provide a network of cellular connectivity to UEs in the environment 100. One such UE 140 is shown as being within the coverage area 110a of the base station 110 and the coverage area 120a of the base station 120. During operation, the serving base station 110 / 120 and / or the access point 130 communicate with the UE 140 to configure full power transmission.

[0026] 2 illustrates a block diagram of an exemplary wireless system 200 of electronic devices implementing measurement signal collision resolution, according to some embodiments of the present disclosure. System 200 may be any of the electronic devices (e.g., AP 1010, STA 1020) of environment 100, including UE 140. System 200 includes a processor 210, a transceiver 220, buffer(s) 230a and 230b, a communication infrastructure 240, a memory 250, an operating system 252, an application 254, and an antenna 260. The illustrated system is provided as an exemplary portion of wireless system 200, which may include other circuit(s) and subsystem(s). Additionally, while the systems of wireless system 200 are shown as separate components, embodiments of the present disclosure may include any combination of these components, fewer components, or more components.

[0027] Memory 250 may include random access memory (RAM) and / or cache and may include control logic (e.g., computer software) and / or data. Memory 250 may include other storage devices or memories, such as, but not limited to, a hard disk drive and / or a removable storage device / unit. According to some examples, operating system 252 may be stored in memory 250. Operating system 252 may manage the transfer of data from memory 250 and / or one or more applications 254 to processor 210 and / or transceiver 220. In some examples, operating system 252 maintains one or more network protocol stacks (e.g., Internet protocol stack, cellular protocol stack, etc.), which may include multiple logic layers. At a corresponding layer of the protocol stack, operating system 252 includes control mechanisms and data structures for performing functions associated with that layer.

[0028] According to some examples, applications 254 may be stored in memory 250. Applications 254 may include applications (e.g., user applications) used by wireless system 200 and / or a user of wireless system 200. Applications in applications 254 may include, but are not limited to, applications such as Siri™, FaceTime™, radio streaming, video streaming, remote control, measurement conflict resolution, and / or other user applications.

[0029] Alternatively or in addition to an operating system, system 200 may include a communications infrastructure 240. Communications infrastructure 240 provides communications between, for example, processor 210, transceiver 220, and memory 250. In some implementations, communications infrastructure 240 may be a bus. Processor 210, in conjunction with instructions stored in memory 250, performs operations that enable wireless system 200 of system 1000 to perform measurement collision resolution as described herein. Additionally or alternatively, transceiver 220 performs operations that enable wireless system 200 of system 1000 to perform measurement collision resolution as described herein.

[0030] According to some embodiments, transceiver 220 can transmit and receive communication signals supporting measurement collision resolution and can be coupled to antenna 260. Antenna 260 can include one or more antennas, which can be of the same or different types. Transceiver 220 enables system 200 to communicate with other devices, which can be wired and / or wireless. Transceiver 220 can include a processor, controller, radio, sockets, plugs, buffers, and circuits / devices used to connect to and communicate with a network. According to some examples, transceiver 220 includes one or more circuits for connecting to and communicating with a wired network and / or a wireless network. Based on the discussion of this disclosure, one skilled in the art will understand that transceiver 220 can include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth™ subsystem, each with its own radio transceiver and protocol(s). In some implementations, transceiver 220 can include more or fewer systems for communicating with other devices.

[0031] The cellular subsystem (not shown) may include one or more circuits (including a cellular transceiver) for connecting to and communicating with a cellular network. The cellular network may include, but is not limited to, 3G / 4G / 5G networks such as Universal Mobile Telecommunications System (UMTS) and Long Term Evolution (LTE). The Bluetooth™ subsystem (not shown) may include one or more circuits (including a Bluetooth™ transceiver) for enabling connection(s) and communication based on, for example, the Bluetooth™ protocol, the Bluetooth™ Low Energy protocol, or the Bluetooth™ Low Energy Long Range protocol. The WLAN subsystem (not shown) may include one or more circuits (including a WLAN transceiver) for enabling connection(s) and communication over networks, including, but not limited to, WLAN networks based on standards set forth in IEEE 802.11 (including, but not limited to, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11bc, IEEE 802.11bd, IEEE 802.11be, etc.).

[0032] According to some embodiments, processor 210, alone or in combination with memory 250 and / or transceiver 220, executes the full power transmit configuration. For example, system 200 is configured to generate and transmit device capabilities to the network, and to receive and execute transmit power configurations from the network, as described in further detail below.

[0033] According to some embodiments, the processor 210, alone or in combination with the transceiver 220 and / or memory 205, can transmit the UE capabilities. The processor 210, alone or in combination with the transceiver 220 and / or memory 205, can receive and execute the power transmission configuration. Full Power Transmit Configuration

[0034] In one embodiment, two additional full power transmission modes supplement the existing Mode 1 and Mode 2 defined in the current 3GPP specifications. The UE informs the network which of these four modes it supports. Based on the received UE capabilities, the network selects one of the four modes. The network then configures the full power transmission mode in the UE via a PUSCH-Config message. Specifically, because there are four available power transmission modes that can be configured by the network, the network sets two or more bits in the PUSCH-Config message to identify the desired power transmission mode. Upon receipt at the UE, the UE configures the full power transmission mode according to the received PUSCH-Config message.

[0035] As mentioned above, Mode 1 and Mode 2 exist in the current 3GPP specification. In Mode 1, power scaling follows the power scaling behavior specified in Release 15 of the 3GPP specification. That is, the number of non-zero ports is divided by the maximum number of ports the UE can support. The UE then applies the resulting value as a power scaling factor to each of its TPMIs. Additionally, in Mode 1, a new coherent TPMI is added to the partially coherent and non-coherent codebook subsets.

[0036] In mode 2, the UE operates partially in full power transmission mode and partially in modes other than full power transmission mode. Specifically, for all TPMIs identified as those for which the UE is capable of operating in full power transmission mode, the power scaling factor is set to 1. For all other TPMIs, the power scaling is set to the ratio of the number of non-zero power ports divided by the number of ports in the SRS resource indicated by the scheduling DCI.

[0037] In the first new mode (mode 0), all TPMIs are configured to have a power scaling of 1. In the second new mode (mode 3), the UE operates according to Release 15 with the same power scaling as defined by Release 15. In other words, the power scaling of all TPMIs is set to the ratio of all non-zero ports to the maximum number of ports.

[0038] Another embodiment supports a UE with four uplink ports / layers. In this embodiment, the UE indicates to the network that it supports four uplink ports and that it supports uplink full power transmission. In this example, the network can configure the UE to operate in full power transmission mode 2 and can configure the UE with an SRS resource set having up to four SRS resources. In such a case, at least one SRS resource has four ports and at least one SRS resource has two ports. In addition, the network also configures the codebook subset and full power transmission mode for the UE.

[0039] For example, the network configures the codebook subset for the two-port SRS to be either fullyAndPartialAndNonCoherent or nonCoherent. In one embodiment, the codebook subset type may be hard-coded in the specification so that the configuration does not need to be sent from the network to the UE. When configuring the full power mode of operation for the two-port SRS, mode 1 is no longer available. Therefore, the network selects between modes 0, 2, and 3. As described above, the network sets the relevant bit in a PUSCH-Config message based on the selected full power transmission mode and sends a message to the UE to configure it. Alternatively, in one embodiment, the full power transmission mode may be hard-coded in the specification so that the UE can execute the appropriate mode without requiring specific instructions from the network about the appropriate mode.

[0040] In another embodiment, the network receives an indication from the UE that the UE is in a two-port fully coherent configuration. In one embodiment, the UE also informs the network whether the UE can support modes 0, 1, or 2. Because the UE is fully coherent, there is always a TPMI that uses all ports. Therefore, there is always a TPMI that supports full power transmission, even if there are other TPMIs that do not support full power transmission.

[0041] Based on the received UE information, the network selects one of the supported modes 0, 1, or 2. Note that the network selects only modes that the UE supports. In one embodiment, this selection further depends on the UE's codebook subset. Specifically, if the codebook subset is configured as nonCoherent, the network can configure the UE to operate in mode 0, 1, or 2 only if the UE indicates that it can support the selected mode. Otherwise, the network configures the UE to operate in mode 3.

[0042] On the other hand, if the codebookSubset is configured as fullyAndPartialAndNonCoherent (e.g., fully coherent), Mode 1 is no longer available. Therefore, the network can only configure the UE to operate in Mode 0 or 2 if Mode 0 or 2 is supported by the UE. If neither is supported, the network must configure the UE to operate in Mode 3. In this embodiment, the network may configure SRS resources with different port numbers in the SRS resource set, but is prohibited from doing so when Mode 2 is selected. This is because there is no need to configure SRS resources with different port numbers in Mode 2.

[0043] In another embodiment, a four-port UE can also be configured. In addition to being able to operate in fully coherent and noncoherent configurations, a four-port UE can also operate in a partially coherent configuration. The network assumes this additional capability when configuring the UE. Specifically, as in the previous embodiment, the UE indicates to the network whether it can operate in mode 0, 1, or 2. The network then determines the UE's codebook subset. If the codebook subset is nonCoherent or partialAndNonCoherent, the network configures the UE to operate in mode 0, 1, or 2, depending on the UE's indicated capabilities. If the UE indicates that it cannot operate in any of modes 0, 1, or 2, the network configures the UE to operate in mode 3.

[0044] Alternatively, when codebookSubset is configured as fullyAndPartialAndNonCoherent, Mode 1 is no longer available. Therefore, the network configures the UE to operate in Mode 0 or 2, depending on the UE's reported capabilities. If the UE indicates that it cannot operate in either Mode 0 or 2, the network configures the UE to operate in Mode 3. Again, although the network may normally configure SRS resources with different port numbers in the SRS resource set, it is prohibited from doing so when Mode 2 is selected. This is because there is no need to configure SRS resources with different port numbers in Mode 2.

[0045] 3 illustrates a functional block diagram of an exemplary wireless communication environment 300 according to one embodiment. The environment includes multiple access points 320 that provide wireless connectivity from a network backend 310 to a UE 350. In one embodiment, the access points 320 correspond to either of the base stations 110 or 120 of FIG. 1, and the UE 350 corresponds to the UE 140 of FIG. 1. For ease of explanation, only the relevant functional blocks of the network 310 and the UE 350 are shown.

[0046] 3, the UE 350 includes a transceiver 352 connected to an antenna 355. The transceiver includes multiple logical ports 352. A processor 354 is connected to the transceiver 352 and performs most of the processing in the UE 350. The processor is also connected to a memory 356. A mode configuration 358 sets the mode specified by the network.

[0047] 3, network 310 includes a transceiver 312 that transmits and receives information using access points 320a and 320b. While only two connected access points are shown, it should be understood that network 310 may be connected to any number of access points 320. Network backend 310 includes a processor 314 connected to transceiver 312. Memory 316 and configuration selection block 318 are connected to processor 314. Although shown as separate components, it should be understood that the functional blocks may be implemented separately or integrated with each other in any combination.

[0048] According to the above embodiment, the processor 354 of the UE 350 accesses the memory 356 to access the UE's capabilities. The processor packages the UE capabilities and causes the transceiver 352 to transmit the capabilities to the network 310 via the antenna(s) 355. The message is received by one or more of the access points 320 and forwarded to the network 310. The network receives the capabilities via the transceiver 312. The processor 314 decodes the received information to identify the UE's capabilities. The configuration selection 318 then selects an appropriate full power transmission mode based on the UE capabilities, according to the above embodiment. The selected mode is then packaged by the processor 314. The processor then causes the transceiver 312 to forward the packaged selection in a PUSCH-Config message to the access point(s) 320, which forwards the message to the UE 350.

[0049] The transceiver 352 of the UE 350 receives the PUSCH-Config message via its antenna(s) 355 and forwards it to the processor 354. The processor 354 extracts the associated full power transmission mode selection from the PUSCH-Config message and stores it in memory 356. The mode configuration 358 accesses the mode selection stored in memory 356 and configures the TPMI, the port 353, and / or other aspects of the transceiver or transceiver logic as described with respect to the above embodiments.

[0050] FIG. 4 shows a flowchart of a method 400 for configuring a full power transmission mode in a UE. As shown in FIG. 4, the network receives UE capabilities from the UE (410). These capabilities may include the number of supported ports, the supported coherency, and the supported full power transmission mode. Thus, from the received UE capabilities, the network determines the number of ports of the UE (420). This value is typically either 2 or 4. The network then determines the coherency of the UE (430). For a two-port UE, this is either coherent or non-coherent. For a four-port UE, this may include partial coherency.

[0051] The network then identifies (440) from the received capabilities whether the UE has identified any supported full power transmission modes. Based on the port, coherency, and mode information received from the UE, the network selects (450) a mode. As noted above, in an embodiment of the present disclosure, there are four available full power transmission modes. Once a mode is selected, the network configures (460) the bits of a PUSCH-Config signal. The resulting signal is then transmitted (470) to the UE.

[0052] Although the method has been described according to one implementation, it should be understood that many of the steps may be performed in a different order or omitted according to the particular circumstances of the application. BDFactor instructions

[0053] Downlink Control Information (DCI) is a signal transmitted over the Physical Downlink Control Channel (PDCCH) and contains information about Downlink Shared Channel (DL-SCH) resource allocation (e.g., the set of resource blocks comprising the DL-SCH), the transport format, and information related to DL-SCH Hybrid Automatic Repeat Request (HARQ). To form the PDCCH payload, the DCI undergoes channel coding (e.g., adding a CRC attachment followed by convolutional coding and rate matching according to the PDCCH format capacity). Similarly, decoding of the DCI is performed upon reception.

[0054] Moreover, it is common for a single PDCCH transmission to carry DCI information for multiple UEs. Because the UE is not explicitly informed of the detailed control channel structure, it must blindly attempt to decode the control region. This is called "blind detection" or "blind decoding."

[0055] In a multi-TRP (multiple transmission / reception point) configuration, the UE is connected to multiple serving cells. In this configuration, the UE can receive a single DCI that directs transmission to all serving cells, or it can receive multiple DCIs, where a different DCI is provided for each serving TRP. In the latter scenario, the UE must determine how to correctly decode the DCI information for each of the serving cells. The UE's ability to correctly decode this information depends on the degree of channel complexity the UE can handle. Based on the UE's capabilities, the network can configure a value, BDFactorR, that controls the PDCCH decoding complexity in terms of the number of blind detection and non-overlapping control channel elements (CCEs) present in the transmission.

[0056] In one embodiment, BDFactorR may be configured at a per-cell level. In this embodiment, for cell i, if the cell is configured to operate in multi-DCI mode, then BDFactor of cell i is used to determine the blind detection and the maximum number of non-overlapping CCEs. On the other hand, if cell i is not configured to operate in multi-DCI mode, then BDFactorR is assumed to be 1, and this value is used to determine the blind detection and the maximum number of non-overlapping CCEs.

[0057] In another embodiment, BDFactorR may alternatively be configured at a per-cell-group level, in which the same BDFactorR is used for all cells within a cell group.

[0058] 3 , according to the above embodiment, the processor 354 of the UE 350 accesses the memory 356 to access the UE's capabilities. The processor packages the UE capabilities and causes the transceiver 352 to transmit the capabilities to the network 310 via the antenna(s) 355. The message is received by one or more of the access points 320 and forwarded to the network 310. The network receives the capabilities via the transceiver 312. The processor 314 decodes the received information to identify the UE's capabilities. The configuration selection 318 then selects an appropriate BDFactorR based on the UE capabilities, according to the above embodiment. The selected BDFactorR is then referenced by the processor 314 when generating DCI signals for transmission to the UE, or used by the access point at the same time.

[0059] Figure 5 shows a flowchart of a method 500 for configuring PDCCH complexity. As shown in Figure 5, the network identifies 510 that the UE is operating with multiple DCIs and multiple TRPs. The network receives 520 the UE's capabilities regarding the level of complexity the UE can handle for blind detection. Based on this information, the network configures the appropriate complexity for the cells. Specifically, for multiple TRPs, the network can choose 525 whether to configure each cell independently (cell-by-cell) or all cells in a cell group together (cell-group-by-cell).

[0060] Once the per cell configuration is selected (525 per cell), the network determines whether a given cell i is operating in multi-DCI. If so (535-Y), the network sets the complexity of cell i equal to the BDFactorR of that cell. On the other hand, if cell i is not operating in multi-DCI (535-N), the network sets the complexity to 1.

[0061] On the other hand, if the network chooses to configure cells per group (525 per cell group), the network configures all cells in that group to have the same BDFactorR (560). Multi-TRP configuration for FDM / TDM schemes

[0062] As mentioned above, in a multi-TRP, a UE is served by multiple cells. Therefore, there are transmission schemes between each of the serving TRPs. For example, there are multiple Frequency Domain Multiplexing (FDM) schemes (FDMSchemeA and FDMSchemeB) and multiple Time Domain Multiplexing (TDM) schemes (TDMSchemeA and TDMSchemeB) available for communication between the UE and each serving cell. Note that these communication schemes are not mutually exclusive.

[0063] Current 3GPP specifications disclose dynamic switching between different communication schemes. In that configuration, the network tracks several variables present in the communication system. These variables may include, for example, the number of indicated beams (e.g., Transmission Configuration Indication (TCI)), the number of Code Domain Multiplexing (CDM) groups, the Time Domain Resource Assignment (TDRA) indicated in the DCI, and the Radio Resource Control (RRC) configuration. The network adjusts the UE behavior depending on the values ​​of these variables. In one embodiment, the UE behavior may be hard-coded in the specification so that the UE can adjust its behavior without receiving explicit instructions from the network.

[0064] Table 1 below lists the values ​​of the relevant variables and the corresponding UE behavior. [Table 1]

[0065] As shown in the table above, the values ​​of the variables allow the UE to dynamically adjust its communication scheme. For example, as shown in the first row, the number of TCI states is 1, the number of CDM groups is less than or equal to 1, and TDRA does not contain the value RepNum16. In this scenario, the UE follows Release 15 behavior. The rest of Table 1 can be read similarly. For example, in the fourth configuration (row), there are two TCI states, one CDM group, TDRA contains RepNum16, and RepNum16 is configured in at least one entry of PDSCH-TimeDomainResourceAllocation. If the variable values ​​satisfy those in this row, the UE uses TDMSchemeB (e.g., scheme 3 or inter-slot TDM scheme).

[0066] According to one embodiment of the present disclosure, an additional configuration is disclosed. In this embodiment, a UE can be configured to operate in Spatial Domain Multiplexing (SDM), also known as Non-Coherent Joint Transmission (NCJT), when two conditions are met. Specifically, SDM can be assumed regardless of other configurations, provided that the UE is instructed that there are two TCI states in the DCI and two DMRS CDM groups in the DCI. In another embodiment, Scheme 1a can be assumed.

[0067] In another embodiment, if there is a conflict between two or more schemes, TDMSchemeA may be prioritized. In this embodiment, the UE is configured with RepSchemeEnabler. The occurrence of any one of three conditions can then trigger the priority of TDMSchemeA. The first condition occurs when the UE does not expect RepNum16 to be configured in any entry of PDSCH-TimeDomainResourceAllocation. The second condition occurs when the UE ignores RepNum16 configured in any entry of PDSCH-TimeDomainResourceAllocation. The third condition occurs when the UE does not expect DCI to indicate an entry in PDSCH-TimeDomainResourceAllocation that includes RepNum16. When any of these conditions occurs, the UE prioritizes TDMSchemeA regardless of other configurations.

[0068] In another embodiment, TDMSchemeB may be preferred. This embodiment may occur when the UE is configured with RepNum16 in at least one entry of PDSCH-TimeDomainResourceAllocation. In this embodiment, the preference for TDMSchemeB occurs when the UE does not expect RepSchemeEnabler to be configured. Specifically, under this condition, the UE is not expected to configure RepSchemeEnabler, or if configured, the UE ignores RepSchemeEnabler. The UE is expected to operate with TDMSchemeB, Mode 4, or an inter-slot TDM scheme.

[0069] In another embodiment, an error resolution is provided. Specifically, it is possible for a UE to be configured with RepNum16 in the DCI TDRA field and with RepSchemeEnabler set to one of FDMSchemeA, FDMSchemeB, or TDMSchemeA. However, this is an invalid state and will cause an error. As a result, when both of these conditions are met, the UE operates in the scheme indicated by RepSchemeEnabler, according to the first embodiment. Alternatively, in another embodiment, when these conditions are met, the UE operates in an inter-slot TDM scheme, such as Scheme 4 or TDMSchemeB.

[0070] 6 shows a flowchart of an example method 600 for configuring a communication scheme for a UE. As shown in FIG. 6, the network receives information regarding UE operation, such as the number of TCI states in a DCI and the number of DMRS CDM groups in the DCI (610). Based on this information, the network determines whether the UE is instructed to have two TCI states in the DCI. If so (615-Y), then the network determines whether the UE has two DMRS CDM groups (625). If so, the network configures the UE to operate in SDM (630).

[0071] On the other hand, if the network determines that the UE has not been identified as having two TCI states in the DCI (615-N) or that the UE has not been identified as having two DMRS CDM groups (625-N), then the network configures the UE (640) to operate in accordance with dynamic configuration as defined in Release 16. While the above method has been described as being performed by the network, it should be understood that the method may equally be performed by the UE.

[0072] 7 illustrates a flowchart of an example method 700 for selecting a communication scheme, according to an embodiment of the present disclosure. As shown in FIG. 7, the UE identifies whether it is configured with RepSchemeEnabler or whether RepNum16 is configured in at least one entry of the PDSCH-TimeDomainResourceAllocation. If the UE is configured with only RepSchemeEnabler (705-RSE), the UE checks whether certain conditions are met (710). For example, the UE determines whether it does not expect RepNum16 to be configured in any entry of the PDSCH-TimeDomainResourceAllocation, whether the UE ignores RepNum16 configured in any entry of the PDSCH-TimeDomainResourceAllocation, or whether a third condition occurs when the UE does not expect the DCI to indicate an entry in the PDSCH-TimeDomainResourceAllocation that includes RepNum16. If any one of these conditions occurs (720), the UE will prioritize TDMSchemeA regardless of other configurations.

[0073] On the other hand, if the UE determines that at least one entry in the PDSCH-TimeDomainResourceAllocation is configured with RepNum16 (705-RN16), the UE analyzes another set of conditions (730). In this example, the UE determines whether it expects RepSchemeEnabler to be configured. If not, the UE prioritizes TDMSchemeB.

[0074] Finally, if the UE identifies that both RepNum16 and RepSchemeEnabler are configured for the UE (705-BOTH), the UE identifies this condition as an error (750). As a result, the UE selects whether to operate with the scheme indicated by RepSchemeEnabler or with TDMSchemeB. While the above method has been described as being performed by the UE, it should be understood that method 700 can also be performed by the network. If performed by the network, it requires the additional steps of receiving configuration information from the UE and informing the UE of the selected configuration.

[0075] FIG. 8 illustrates an exemplary system 800 for implementing measurement signal collision resolution according to some embodiments of the present disclosure. The exemplary system 800 is merely illustrative and does not limit the disclosed embodiments. The system 800 may include, but is not limited to, an access point (AP) 810, stations (STAs) 820, and a network 830. The stations 820a-820c may include, but are not limited to, Wireless Local Area Network (WLAN) stations such as wireless communication devices, smartphones, laptops, desktops, tablets, personal assistants, monitors, televisions, wearable devices, etc. The access point (AP) 810 may include, but is not limited to, WLAN electronic devices such as wireless routers, wearable devices (e.g., smart watches), wireless communication devices (e.g., smartphones), or combinations thereof. The network 830 may be the Internet and / or a WLAN. Communication for the stations 820 is illustrated as wireless communication 840. Communication between the AP 810 and the STAs 820 may occur using wireless communication 840a-840c. The wireless communications 840a-840c may be based on a wide variety of wireless communication technologies, including but not limited to technologies based on IEEE 802.11 (such as, but not limited to, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11bc, IEEE 802.11bd, IEEE 802.11be, IEEE 802.11v, etc.).

[0076] Various embodiments can be implemented using one or more computer systems, such as, for example, computer system 900 shown in FIG. 9 . Computer system 900 can be any known computer capable of performing the functions described herein, such as devices 910, 920 of FIG. 9 or device 200 of FIG. 2 . Computer system 900 includes one or more processors (also referred to as central processing units, or CPUs), such as processor 904. Processor 904 is connected to a communications infrastructure 906 (e.g., a bus). Computer system 900 also includes user input / output device(s) 903, such as a monitor, keyboard, pointing device, etc., that communicate with communications infrastructure 906 via user input / output interface(s) 902. Computer system 900 also includes main or primary memory 908, such as random access memory (RAM). Main memory 908 can include one or more levels of cache. Main memory 908 stores control logic (e.g., computer software) and / or data.

[0077] Computer system 900 may also include one or more secondary storage devices or secondary memories 910. Secondary memories 910 may include, for example, a hard disk drive 912 and / or a removable storage device or drive 914. Removable storage drive 914 may be a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0078] The removable storage drive 914 can interact with a removable storage unit 918. The removable storage unit 918 includes a computer-usable or computer-readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 918 may be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and / or any other computer data storage device. The removable storage drive 914 reads from and / or writes to the removable storage unit 918 in well-known fashion.

[0079] According to some embodiments, secondary memory 910 may include other means, intermediaries, or other techniques that allow computer programs and / or other instructions and / or data to be accessed by computer system 900. Such means, intermediaries, or other techniques may include, for example, removable storage unit 922 and interface 920. Examples of removable storage unit 922 and interface 920 may include a program cartridge and cartridge interface (such as those found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0080] Computer system 900 may further include a communications interface or network interface 924. Communications interface 924 enables computer system 900 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 928). For example, communications interface 924 may enable computer system 900 to communicate with remote devices 928 over communications path 926, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic and / or data may be transmitted to and / or received from computer system 900 via communications path 926.

[0081] The operations of the aforementioned embodiments can be implemented in a wide variety of configurations and architectures. Thus, some or all of the operations of the aforementioned embodiments may be performed in hardware, software, or both. In some embodiments, a tangible, non-transitory device or article of manufacture including a tangible, non-transitory computer-usable or computer-readable medium having control logic (software) stored thereon is also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 900, main memory 908, secondary memory 910, removable storage units 918 and 922, and tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (e.g., computer system 900), causes such data processing devices to operate as described herein.

[0082] Based on the teachings contained herein, it will be apparent to one skilled in the art how to make and use embodiments of the present disclosure using data processing devices, computer systems and / or computer architectures other than those shown in Figure 9. In particular, embodiments may operate using software, hardware, and / or operating system implementations other than those described herein.

[0083] It should be understood that it is the "Detailed Description" section, and not the "Summary" and "Abstract" sections, that are intended to be used to interpret the claims. The "Summary" and "Abstract" sections present only one or a few exemplary embodiments of the invention, rather than every exemplary embodiment of the invention contemplated by the inventor(s), and are therefore not intended to limit the scope of the present disclosure and the appended claims in any way.

[0084] The present disclosure has been described using functional building blocks that illustrate the implementation of specific functions and their relationships. For the convenience of explanation, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships are appropriately performed.

[0085] The foregoing description of specific embodiments will sufficiently clarify the general nature of the present disclosure so that others, by applying knowledge of the art, can readily modify and / or adapt these specific embodiments for various applications without undue experimentation and without departing from the general concepts of the present disclosure. Such adaptations and modifications are therefore intended to be within the spirit and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for purposes of description and not of limitation, and as such should be interpreted by those of skill in the art in light of the teachings and descriptions.

[0086] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. a transceiver configured to transmit and receive information with a user equipment (UE); one or more processors, receiving, via the transceiver, a capability message from the UE indicating whether the UE supports each of four different full power transmission modes; determining one full power transmission mode from among the four full power transmission modes based on the received capability message; causing the transceiver to transmit a configuration message to the UE via the transceiver, causing the UE to configure itself according to the determined full power transmission mode; one or more processors; 11. The apparatus, wherein the four different full power transmission modes include a mode in which power scaling is set equal to a ratio of a number of non-zero power ports of a configured transmitted precoder matrix indicator (TPMI) to a maximum number of ports of the UE.

2. The apparatus of claim 1 , wherein the configuration message is a PUSCH-Config message.

3. The apparatus of claim 1 , wherein the capability message includes the number of logical ports of the UE's transceiver.

4. The apparatus of claim 3 , wherein the capability message further includes coherency capabilities of the UE.

5. the number of logical ports is two, the coherency capability includes full coherency, 5. The apparatus of claim 4, wherein the four different full power transmission modes include at least one of Mode 0 or Mode 2, wherein Mode 2 sets some transmitted precoder matrix indicators (TPMIs) to a power scaling value of 1 and other TPMIs to another power scaling value.

6. the number of logical ports is four, the coherency capability includes full coherency, 5. The apparatus of claim 4, wherein the four different full power transmission modes include at least one of Mode 0 or Mode 2, wherein Mode 2 sets some transmitted precoder matrix indicators (TPMIs) to have power scaling 1 and sets other TPMIs to another power scaling value.

7. 2. The apparatus of claim 1, wherein the four different full power transmission mode capabilities further include a mode 0, which sets all power scaling to one.

8. receiving a capability message from a user equipment (UE) indicating whether the UE supports each of four different full power transmission modes; determining one full power transmission mode from among the four full power transmission modes based on the received capability message; sending a configuration message to the UE to configure itself according to the detected full power transmission mode; The method, wherein the four different full power transmission modes include a mode in which power scaling is set equal to a ratio of a number of non-zero power ports of a configured transmitted precoder matrix indicator (TPMI) to a maximum number of ports of the UE.

9. The method of claim 8, wherein the configuration message is a PUSCH-Config message.

10. The method of claim 8 , wherein the capability message includes the number of logical ports of the UE's transceiver.

11. The method of claim 10 , wherein the capability message further includes coherency capabilities of the UE.

12. the number of logical ports is two, the coherency capability includes full coherency, 12. The method of claim 11, wherein the four different full power transmission modes include at least one of Mode 0 or Mode 2, and Mode 2 sets some transmitted precoder matrix indicators (TPMIs) to a power scaling value of 1 and other TPMIs to another power scaling value.

13. the number of logical ports is four, the coherency capability includes full coherency, 12. The method of claim 11 , wherein the four different full power transmission modes include at least one of Mode 0 or Mode 2, and Mode 2 sets some transmitted precoder matrix indicators (TPMIs) to have power scaling 1 and sets other TPMIs to another power scaling value.

14. 9. The method of claim 8, wherein the four different full power transmission mode capabilities further include a mode 0, which sets all power scaling to one.

15. 1. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a computing device, cause the computing device to: receiving a capability message from a user equipment (UE) indicating whether the UE supports each of four different full power transmission modes; determining one full power transmission mode from among the four full power transmission modes based on the received capability message; transmitting a configuration message to the UE causing the UE to configure itself according to the determined full power transmission mode; 12. A non-transitory computer-readable storage medium, wherein the four different full power transmission modes include a mode in which power scaling is set equal to a ratio of a number of non-zero power ports of a configured transmitted precoder matrix indicator (TPMI) to a maximum number of ports of the UE.

16. 16. The non-transitory computer-readable medium of claim 15, wherein the configuration message is a PUSCH-Config message.

17. 16. The non-transitory computer-readable medium of claim 15, wherein the capabilities message includes a number of logical ports and coherency capabilities of a transceiver of the UE.

18. the number of logical ports is two, the coherency capability includes full coherency, 18. The non-transitory computer-readable medium of claim 17, wherein the four different full power transmission modes include at least one of Mode 0 or Mode 2, wherein Mode 2 sets some transmitted precoder matrix indicators (TPMIs) to a power scaling of 1 and sets other TPMIs to another power scaling value.

19. the number of logical ports is four, the coherency capability includes full coherency, 18. The non-transitory computer-readable medium of claim 17, wherein the four different full power transmission modes include at least one of Mode 0 or Mode 2, wherein Mode 2 sets some transmitted precoder matrix indicators (TPMIs) to have a power scaling of 1 and sets other TPMIs to another power scaling value.

20. 16. The non-transitory computer-readable medium of claim 15, wherein the four different full power transmission mode capabilities further include Mode 0, which sets all power scaling to 1.

Images