Upper layer design for release 16 mimo enhancements
By configuring the PUSCH-Config message and UE capability information in the 3GPP specification, the configuration problem of full-power transmission mode in version 16 MIMO enhancement was solved, achieving more efficient wireless communication.
Patent Information
- Application Number
- CN202080099464.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-04-08
- Publication Date
- 2025-11-18
- Estimated Expiration
- 2040-04-08
AI Technical Summary
The existing 3GPP specifications do not define how to configure full-power transmission in the MIMO enhancement of version 16, which makes the operation of the UE in full-power transmission mode unclear.
By transmitting PUSCH-Config messages between the UE and the network, the network selects and configures one of the four full-power transmission modes. Combined with the UE's capability information and port selection mechanism, the full-power transmission mode configuration is achieved.
It enables full-power transmission configuration of UE in 3GPP environment, improves the efficiency and reliability of wireless communication, and meets the MIMO enhancement requirements of version 16.
Smart Images

Figure CN115362732B_ABST
Abstract
Description
Technical Field
[0001] Various implementation schemes can typically involve the field of wireless communications. Summary of the Invention
[0002] In one implementation, the user equipment (UE) is configured to operate in full-power transmission mode over the network. The network transmits a PUSCH-Config message to the UE that identifies the full-power transmission mode. The network can select any of four different modes by changing the content of the PUSCH-Config message.
[0003] In another implementation, the UE informs the network about its capabilities. The UE may specify whether it is capable of full-power transmission and the number of ports it has that can operate in full-power transmission. The network transmits a PUSCH-Config message to the UE, which configures the UE based on information received from the UE. In this implementation, fewer than all four modes are available for configuration, depending on the number of ports the UE identifies for full-power transmission.
[0004] In another implementation, the network further configures port selection in the UE. When the UE is capable of 2-port fully coherent operation, the UE notifies the network which mode it supports. When the network attempts to configure 2-port uplink operation, it adjusts the configuration based on the UE's codebookSubset and capabilities. Specifically, the network adjusts the configuration based on whether the codebookSubset is noncoherent or configured as fullyAndPartialAndNonCoherent.
[0005] In another implementation, the network can configure port selection in a 4-port UE. When the UE is capable of 4-port fully coherent operation, the UE notifies the network which mode it supports. When the network attempts to configure 4-port uplink operation, it adjusts the configuration based on the UE's codebookSubset and capabilities. Specifically, the network adjusts the configuration based on whether the codebookSubset is noncoherent or configured as fullyAndPartialAndNonCoherent.
[0006] In another embodiment, a UE includes a memory, a transceiver, and one or more processors. These processors receive at least one full-power transmission mode from the memory and cause the transceiver to transmit capability messages to the network, these capability messages including at least one capability supporting the full-power transmission mode. The processors receive configuration messages from the network via the transceiver and extract a selected full-power transmission mode from the configuration messages. The processors then configure the transceiver according to the selected full-power transmission mode.
[0007] In the implementation scheme, this configuration message is the PUSCH-Config message.
[0008] In the implementation, the transceiver includes multiple logical ports, and the memory stores the number of the multiple logical ports and the coherence capability of the user equipment.
[0009] In the implementation scheme, these capability messages include the number of the plurality of logical ports and the coherent capabilities of the user equipment.
[0010] In the implementation plan, the selected full-power transmission mode is one of four modes, and the selection is based on these capabilities of the user equipment.
[0011] In the implementation scheme, the four modes include mode 0 and mode 3, in which all power scaling ratios are set to 1, and in mode 3, all power scaling ratios are set to a ratio equal to the ratio between the number of multiple non-zero power ports of the configured TPMI and 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 this 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 or the second configuration, the user equipment analyzes a first set of conditions or a second set of conditions, respectively. Based on these analyses, the UE sets the selected communication scheme to one of the first or the second communication scheme.
[0013] In the implementation scheme, the first configuration is that the user equipment is configured with RepSchemeEnabler, and the first set of conditions is analyzed in response to the user equipment being configured with RepSchemeEnabler. The first set of conditions includes that the user equipment does not expect to configure RepNum16 in any entry of PDSCH-TimeDomainResourceAllocation, or that the user equipment ignores RepNum16 configured in any entry of PDSCH-TimeDomainResourceAllocation, or that the user equipment does not expect the downlink control information (DCI) to indicate an entry containing RepNum16 in PDSCH-TimeDomainResourceAllocation.
[0014] In the implementation scheme, the user equipment is further configured with two TCI states and two DMRSCDM groups in the DCI, and the user equipment is expected to be configured with scheme 1a, or spatial domain multiplexing (SDM) scheme, or noncoherent joint launch (NCJT) scheme, regardless of other configurations, including RepSchemeEnabler or time domain resource allocation (TDRA) in the DCI.
[0015] In the implementation, the at least one full-power transmission mode capability includes mode 0 and mode 3, wherein mode 0 sets all power scaling to 1, and mode 3 sets all power scaling to a ratio equal to the ratio between the number of non-zero power ports of the configured TPMI and the maximum number of ports of the user equipment.
[0016] In the implementation, the number of multiple logical ports is 2, and the coherence capability includes full coherence. The selected full-power transmission mode includes either mode 0 or mode 2, where mode 2 sets some TPMIs to a power scaling ratio of 1 and other TPMIs to different power scaling values.
[0017] In the implementation, the number of multiple logical ports is 4 and the coherence capability includes full coherence, and the selected full-power transmission mode includes either mode 0 or mode 2, where mode 2 sets some of the 4 TPMIs to have a power scaling ratio of 1 and sets the other TPMIs to different power scaling values.
[0018] In the implementation plan, it is further determined that the user equipment is served by multiple cells. In response, a choice is made regarding whether to set the BDFactorR complexity value at the per-cell level or the per-cell-group level. Then, in response to selecting the per-cell level, the BDFactorR is set individually for each of the multiple cells, or in response to selecting the per-cell-group level, the BDFactorR is set to the same value for all cells in the cell group.
[0019] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users. Attached Figure Description
[0020] Figure 1 An exemplary wireless communication environment according to one implementation scheme is shown;
[0021] Figure 2 A block diagram of an exemplary user equipment according to one embodiment is shown;
[0022] Figure 3 A functional block diagram of an exemplary wireless communication environment according to one embodiment is shown;
[0023] Figure 4 A flowchart is shown for a method of setting the full-power transmission mode in a UE;
[0024] Figure 5 A flowchart is shown for the method of configuring PDCCH complexity;
[0025] Figure 6 A flowchart illustrating an exemplary method for configuring a communication scheme for a UE is shown;
[0026] Figure 7 A flowchart illustrating an exemplary method for selecting a communication scheme according to an embodiment of the present disclosure is shown;
[0027] Figure 8 Exemplary systems for implementing measurement signal conflict resolution according to some embodiments of this disclosure are shown; and
[0028] Figure 9 A block diagram of an exemplary general-purpose computer system capable of implementing certain aspects of this disclosure is shown. Detailed Implementation
[0029] Release 16 of the 3GPP specification describes certain MIMO enhancements to previously implemented specifications. For example, Release 16 describes multi-beam enhancements to reduce overhead and latency. Beam quality measurement and reporting are also available on L1-SINR. Furthermore, beam fault recovery is available on second cells. However, due to 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 achieve full-power transmission.
[0030] Full-power transmission for uplink transmission allows the UE to transmit at full power. However, the current 3GPP specification does not define MAC-level and RRC-level configurations to support MIMO enhancements in version 16.
[0031] During implementation, the access point (such as the eNodeB) sends information to the UE regarding which precoding matrix is used as part of the downlink control information. This precoding matrix is called the Transmit Precoder Matrix Indicator (TPMI). Version 16 of the 3GPP specification currently supports two full-power transmission modes. In Mode 1, a new coherent transmit precoder matrix indicator (TPMI) is added to a subset of the partial and / or incoherent codebook to support full-power transmission. Additionally, power scaling follows Version 15 behavior, as the power scaling ratio for each TPMI is set to the ratio between the number of non-zero ports and the maximum number of ports. In Mode 2, the UE can indicate to the network a list of TPMIs that the UE can support for full-power transmission. The power scaling ratio for those TPMIs is given as 1. The power scaling ratio for the remaining TPMIs is given as the ratio between the number of non-zero ports and the actual number of ports (those configured by the network). The following disclosure describes various methods and / or configurations by which networks can configure full-power modes according to various implementations.
[0032] Figure 1 An exemplary wireless communication environment 100 according to an embodiment is illustrated. Environment 100 includes base stations 110 and 120, each having a corresponding coverage area 110a and 120a. In one embodiment, base stations 110 and 120 are access points for a gNodeB, eNodeB, or another network connection. Base stations 110 and 120 are connected to a network backend and provide cellular connectivity to devices within their respective coverage areas.
[0033] Access point 130 may also be located within environment 100 and includes its own coverage area 130a. The access point can be any other type of transmit and receive point (TRP), such as a macro cell, small cell, pico cell, femtocell, remote radio head, relay node, etc. Base stations 110 and 120, together with access point 130, provide a network for cellular connectivity to a UE in environment 100. A UE 140 of this type is shown within the coverage areas 110a of base station 110 and 120a of base station 120. In operation, the serving base stations 110 / 120 and / or access point 130 will communicate with UE 140 to configure full-power transmission.
[0034] Figure 2 A block diagram of an exemplary wireless system 200 implementing measurement signal conflict resolution of an electronic device according to some embodiments of the present disclosure is shown. System 200 may be any electronic device of environment 100 (e.g., AP 1010, STA 1020), including UE 140. System 200 includes processor 210, transceiver 220, buffers 230a and 230b, communication infrastructure 240, memory 250, operating system 252, application 254, and antenna 260. The illustrated system is provided as an exemplary part of wireless system 200, and system 200 may include other circuitry and subsystems. Furthermore, although the wireless system 200 is shown as separate components, embodiments of the present disclosure may include any combination of these components, fewer components, or more components.
[0035] 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, hard disk drives and / or removable storage devices / cells. According to some examples, operating system 252 may be stored in memory 250. Operating system 252 can manage data transfer from memory 250 and / or one or more applications 254 to processor 210 and / or transceiver 220. In some examples, operating system 252 holds one or more network protocol stacks (e.g., Internet Protocol stack, cellular protocol stack, etc.) that may include multiple logical layers. At the corresponding layer of the protocol stack, operating system 252 includes control mechanisms and data structures to perform functions associated with that layer.
[0036] According to some examples, application 254 may be stored in memory 250. Application 254 may include applications used by the wireless system 200 and / or users of the wireless system 200 (e.g., user applications). Applications in application 254 may include, but are not limited to, applications such as, Siri. TM FaceTimeTM Radio current, video streaming, remote control, measurement conflict resolution, and / or other user applications.
[0037] As an alternative to or supplement to the operating system, system 200 may include communication infrastructure 240. Communication infrastructure 240 provides communication, for example, between processor 210, transceiver 220, and memory 250. In some implementations, communication infrastructure 240 may be a bus. Processor 210, together with instructions stored in memory 250, executes to enable the wireless system 200 of system 1000 to perform the measurement conflict resolution operations as described herein. Alternatively or additionally, transceiver 220 performs operations that enable the wireless system 200 of system 1000 to perform the measurement conflict resolution operations as described herein.
[0038] According to some embodiments, transceiver 220 transmits and receives communication signals supporting measurement collision resolution and may be coupled to antenna 260. Antenna 260 may include one or more antennas, which may be the same or different types. Transceiver 220 allows system 200 to communicate with other devices, which may be wired and / or wireless. Transceiver 220 may include a processor, controller, radio components, socket, plug, buffer, and similar circuitry / devices for connecting to and communicating on a network. According to some examples, transceiver 220 may include one or more circuitry for connecting to and communicating on a wired and / or wireless network. Transceiver 220 may include a cellular subsystem, a WLAN subsystem, and / or Bluetooth. TM Subsystems, each comprising its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some specific implementations, transceiver 220 may include more or fewer systems for communicating with other devices.
[0039] The cellular subsystem (not shown) may include one or more circuits (including cellular transceivers) for connecting to and communicating on a cellular network. The cellular network may include, but is not limited to, 3G / 4G / 5G networks, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), etc. Bluetooth TM Subsystems (not shown) may include those for implementing, for example, Bluetooth-based... TM Protocol, Bluetooth TM Low power protocol or Bluetooth TM One or more circuits for low-power remote protocol connectivity and communication (including Bluetooth) TMTransceiver). The WLAN subsystem (not shown) may include one or more circuits (including a WLAN transceiver) to enable connectivity and communication via a WLAN network, such as, but not limited to, networks based on standards described in IEEE 802.11 (such as, but not limited to, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11bc, IEEE 802.11bd, IEEE 802.11be, etc.).
[0040] According to some implementations, processor 210 performs full-power transmission configuration alone or in combination with memory 250 and / or transceiver 220. For example, system 200 is configured to generate device capabilities and transmit them to the network, and to receive and implement transmission power configurations from the network, as will be discussed in further detail below.
[0041] According to some implementations, processor 210 can transmit UE capabilities alone or in combination with transceiver 220 and / or memory 205. Processor 210 can receive and implement power transmission configurations alone or in combination with transceiver 220 and / or memory 205.
[0042] Full power transmission configuration
[0043] In one implementation, two additional full-power transmission modes supplement the existing Mode 1 and Mode 2 defined in the current 3GPP specification. 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 at the UE via a PUSCH-Config message. Specifically, because there are four available power transmission modes that can be set 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 sets the full-power transmission mode according to the received PUSCH-Config message.
[0044] As discussed above, Modes 1 and 2 exist in the current 3GPP specifications. In Mode 1, power scaling follows the power scaling behavior specified in Release 15 of the 3GPP specifications. That is, the number of non-zero ports is divided by the maximum number of ports that the UE can support. The UE then applies the resulting value as a power scaling factor to each TPMI in the UE's TPMI. Additionally, in Mode 1, new coherent TPMIs are added to a subset of the codebook that is part of the incoherent codebook subset.
[0045] In Mode 2, the UE operates partly in full-power transmission mode and partly outside of full-power transmission mode. Specifically, for all TPMIs for which the UE has been identified as being able to operate in full-power transmission mode, the power scaling factor is set to 1. For all other TPMIs, the power scaling ratio is set to the ratio between the number of non-zero power ports and the number of ports in the SRS resources indicated by the scheduling DCI.
[0046] In the first new mode (Mode 0), all TPMIs are set to have a power scaling ratio of 1. In the second new mode (Mode 3), the UE operates under the same power scaling ratio defined by Version 15. In other words, the power scaling ratio of all TPMIs is set to the ratio of all non-zero ports to the maximum number of ports.
[0047] Another implementation supports a UE with four uplink ports / layers. In this implementation, the UE indicates to the network that it supports four uplink ports and that it supports uplink full-power transmission. In this case, the network can configure the UE to operate in full-power transmission mode 2 and configure the UE to have an SRS resource set including up to four SRS resources. In this case, at least one SRS resource will have four ports, and at least one SRS resource will have two ports. Additionally, the network will configure a subset of the UE's codebook and the full-power transmission mode.
[0048] For example, the network will configure a subset of the codebook used for 2-port SRS as fullyAndPartialAndNonCoherent or nonCoherent. In one implementation, the codebook subset type can be hardcoded into the specification, so that the configuration does not need to be transmitted from the network to the UE. When configuring full-power operation mode for 2-port SRS, mode 1 is no longer available. Therefore, the network selects from mode 0, mode 2, and mode 3. As discussed above, the network sets the relevant bits in the PUSCH-Config message based on the selected full-power transmission mode and transmits the message to the UE for configuration. In one implementation, the full-power transmission mode can be hardcoded into the specification as an alternative, so that the UE can execute the correct mode without the network specifically instructing the UE about the correct mode.
[0049] In another implementation, the network receives an indication from the UE that the UE is configured for 2-port fully coherent operation. In one implementation, the UE also informs the network whether it can support mode 0, mode 1, or mode 2. Because the UE is fully coherent, there is always a TPMI using all ports. Therefore, there is always a TPMI supporting full-power transmission, even if other TPMIs that do not support full-power transmission may exist.
[0050] Based on the received UE information, the network will select to support one of Mode 0, Mode 1, or Mode 2. It is important to note that the network only selects the mode supported by the UE. In one implementation, this selection further depends on the UE's codebookSubset. Specifically, when the codebookSubset is configured as nonCoherent, the network can only configure the UE to operate in Mode 0, Mode 1, or Mode 2 if the UE indicates that it can support the selected mode. Otherwise, the network will configure the UE to operate in Mode 3.
[0051] On the other hand, when 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 Mode 2 if the UE supports it. If neither is supported, the network must configure the UE to operate in Mode 3. In this implementation, the network can configure SRS resources in the SRS resource set with a different number of ports, which is prohibited when Mode 2 is selected. This is because in Mode 2, it is not necessary to configure SRS resources with a different number of ports.
[0052] In another implementation, a 4-port UE can also be configured. In addition to operating in fully coherent and non-coherent configurations, a 4-port UE can also operate in a partially coherent configuration. When configuring the UE, the network considers this additional capability. Specifically, as in previous implementations, the UE indicates to the network whether it can operate in mode 0, mode 1, or mode 2. The network then determines the UE's codebook subset. When the codebook subset is noncoherent or partialAndNonCoherent, the network configures the UE to operate in mode 0, mode 1, or mode 2 based on the capability indicated by the UE. If the UE has indicated that it cannot operate in any of mode 0, mode 1, or mode 2, the network configures the UE to operate in mode 3.
[0053] Alternatively, when the codebookSubset is configured as fullyAndPartialAndNonCoherent, Mode 1 is no longer available. Therefore, depending on the UE's reporting capabilities, the network configures the UE to operate in either Mode 0 or Mode 2. If the UE has indicated that it cannot operate in either Mode 0 or Mode 2, the network configures the UE to operate in Mode 3. Again, even though the network can typically configure SRS resources in the SRS resource set with a different number of ports, this is prohibited when Mode 2 is selected. This is because in Mode 2, it is not necessary to configure SRS resources with a different number of ports.
[0054] Figure 3 A functional block diagram of an exemplary wireless communication environment 300 according to one embodiment is shown. The environment includes a plurality of access points 320 providing wireless connectivity from a network backend 310 to a UE 350. In one embodiment, the access point 320 corresponds to either a base station 110 or 120, and the UE 350 corresponds to... Figure 1 UE 140. For illustrative purposes, only the relevant function blocks for network 310 and UE 350 are shown.
[0055] like Figure 3 As shown, UE 350 includes a transceiver 352 connected to antenna 355. The transceiver includes multiple logic ports 352. Processor 354 is connected to transceiver 352 and performs most of the processing in UE 350. The processor is also connected to memory 356. Mode configuration 358 sets the mode specified by the network.
[0056] like Figure 3 As shown, network 310 includes a transceiver 312 that sends and receives information with access points 320a and 320b. Although only two connected access points are shown, it should be understood that network 310 can 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 can be implemented individually or integrated with each other in any combination.
[0057] According to the above implementation, the processor 354 of UE 350 accesses memory 356 to access the UE's capabilities. The processor encapsulates the UE's capabilities and causes transceiver 352 to transmit the capabilities to network 310 via antenna 355. The message is received by one or more of the access points 320 and forwarded to network 310. The network receives the capabilities via transceiver 312. The processor 314 decodes the received information to identify the UE's capabilities. According to the above implementation, configuration selection 318 then selects an appropriate full-power transmission mode based on the UE's capabilities. The selected mode is then encapsulated by processor 314. The processor then causes transceiver 312 to forward the encapsulated selection in the PUSCH-Config message to access point 320, which forwards the message to UE 350.
[0058] The transceiver 352 of UE 350 receives a PUSCH-Config message via its antenna 355 and forwards it to the processor 354. The processor 354 extracts the relevant full-power transmission mode selection from the PUSCH-Config message and stores it in memory 356. Mode configuration 358 accesses the mode selection stored in memory 356 and configures TPMI, port 353, and / or other aspects of the transceiver or transceiver logic accordingly, as described with respect to the above embodiments.
[0059] Figure 4 A flowchart of a method 400 for setting a full-power transmission mode in a UE is shown. Figure 4 As shown, the network receives UE capabilities from the UE (410). These capabilities may include multiple supported ports, supported coherence, and supported full-power transmission modes. Therefore, based on the received UE capabilities, the network determines the number of ports of the UE (420). This value is typically 2 or 4. Next, the network determines the coherence of the UE (430). For a 2-port UE, this will be either coherent or incoherent. For a 4-port UE, this may also include partial coherence.
[0060] The network then determines, based on its received capabilities, whether the UE has identified any supported full-power transmission modes (440). Based on port, coherence, and mode information received from the UE, the network selects a mode (450). As described above, four available full-power transmission modes exist in embodiments of this disclosure. Once a mode is selected, the network configures the bits of the PUSCH-Config signal (460). The resulting signal is then transmitted to the UE (470).
[0061] Although the method has been described with reference to a specific implementation, it should be understood that many of these steps may be performed in a different order or omitted depending on the specific application.
[0062] BDFactor Instructions
[0063] Downlink Control Information (DCI) is transmitted via the Physical Downlink Control Channel (PDCCH) and is a signal that includes information about: Downlink Shared Channel (DL-SCH) resource allocation (e.g., the set of resource blocks containing the DL-SCH), transmission format, and information related to Hybrid Automatic Repeat Request (HARQ) for the DL-SCH. To form the PDCCH payload, the DCI undergoes channel coding (e.g., adding a CRC appendix, followed by convolutional coding and rate matching according to the PDCCH format capacity). Similarly, the DCI is decoded upon reception.
[0064] In addition, it is common for a single PDCCH transmission to carry DCI information for multiple UEs. Because the UEs are not explicitly informed of the detailed control channel structure, they must blindly attempt to decode the control area. This is known as "blind detection" or "blind decoding".
[0065] In a multi-TRP (Multiple Transmit and Receive Points) configuration, the UE connects to multiple serving cells. In this configuration, the UE can receive a single DCI specifying communication with all serving cells, or it can receive multiple DCIs. In the case of multiple DCIs, a different DCI is provided for each serving TRP. In the latter case, the UE must determine how to correctly decode the DCI information for each serving cell. The UE's ability to correctly decode this information depends on the amount of channel complexity the UE can handle. Based on the UE's capabilities, the network can set a value BDFactorR that controls the PDCCH decoding complexity according to the number of blind detection and non-overlapping control channel elements (CCEs) present in the transmission.
[0066] In one implementation, BDFactorR can be configured at the per-cell level. In this implementation, for cell i, if the cell is configured to operate in multi-DCI mode, the BDFactor for cell i is used to determine the maximum number of blind detections and non-overlapping CCEs. On the other hand, if cell i is not configured to operate in multi-DCI mode, BDFactorR is assumed to be 1, and this value is used to determine the maximum number of blind detections and non-overlapping CCEs.
[0067] In another implementation, BDFactorR can be configured at the per cell group level as an alternative. In this implementation, the same BDFactorR is used for all cells in the cell group.
[0068] refer to Figure 3According to the above embodiment, the processor 354 of UE 350 accesses memory 356 to access the UE's capabilities. The processor encapsulates the UE's capabilities and causes transceiver 352 to transmit the capabilities to network 310 via antenna 355. The message is received by one or more of the access points 320 and forwarded to network 310. The network receives the capabilities via transceiver 312. The processor 314 decodes the received information to identify the UE's capabilities. According to the above embodiment, configuration selection 318 then selects an appropriate BDFactorR based on the UE's capabilities. The selected BDFactorR is then referenced by the processor 314 when generating the DCI signal for transmission to the UE, or adopted by the access point for the same reason.
[0069] Figure 5 A flowchart of method 500 for configuring PDCCH complexity is shown. Figure 5 As shown, the network identifies the UE operating in multiple DCIs and multiple TRPs (510). The network receives information about the UE's capabilities at a complexity level relative to blind detection handling (520). Based on this information, the network then configures the cells with appropriate complexity. Specifically, for multiple TRPs, the network can choose to configure each cell independently (per cell) or configure all cells within a cell group together (per cell group) (525).
[0070] When a per-cell configuration (525 per cell) is selected, the network then determines whether a given cell i is operating in multiple DCIs. If yes (535-Y), the network sets the complexity of cell i to be equal to the BDFactorR of that cell. On the other hand, if cell i is not operating in multiple DCIs (535-N), the network sets the complexity to 1.
[0071] At the same time, if the network selects a cell in the configuration group (525 per cell group), the network will configure all cells in the group to have the same BDFactorR (560).
[0072] Multiple TRP Configurations for FDM / TDM Solutions
[0073] As discussed above, in a multi-TRP, the UE is served by multiple cells. Therefore, there are transmission schemes between each TRP serving the UE. For example, there are multiple frequency-domain multiplexing (FDM) schemes (FDMScheme A and FDMScheme B) and multiple time-domain multiplexing (TDM) schemes (TDMScheme A and TDMScheme B) available for communication between the UE and the corresponding serving cell. It is important to note that these communication schemes are not mutually exclusive.
[0074] Current 3GPP specifications disclose dynamic handover between different communication schemes. In this configuration, the network tracks several variables present in the communication system. These variables may include, for example, the number of indicated beams (e.g., Transmit Configuration Indication (TCI)), the number of Coded Domain Multiplexing (CDM) groups, the Time Domain Resource Allocation (TDRA) indicated in the DCI, and the Radio Resource Control (RRC) configuration. Based on the values of these variables, the network adjusts the UE's behavior. In one implementation, the UE behavior may be hard-coded into the specification, allowing the UE to adjust its behavior without receiving explicit instructions from the network.
[0075] Table 1 below lists the relevant variable values and their corresponding UE behaviors.
[0076]
[0077] As shown in the table above, the UE's communication scheme can be dynamically adjusted based on the variable values. 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 the TDRA does not contain the value RepNum16. In this case, the UE follows version 15 behavior. The remainder of Table 1 can be read similarly. For example, in the fourth configuration (row), there are 2 TCI states, 1 CDM group, the TDRA contains RepNum16, and this RepNum16 is configured in at least one entry in PDSCH-TimeDomainResourceAllocation. When the variable values satisfy those in this row, the UE adopts TDMScheme B (e.g., scheme 3 or inter-slot TDM scheme).
[0078] According to one embodiment of this disclosure, an additional configuration is disclosed. In this embodiment, the UE can be configured to operate in Spatial Domain Multiplexing (SDM) (also known as Non-Coherent Joint Transport (NCJT)) when two conditions are met. Specifically, assuming the UE is indicated to have two TCI states in the DCI and two DMRS CDM groups in the DCI, SDM can be assumed regardless of other configurations. In other embodiments, scheme 1a can be assumed.
[0079] In another implementation, TDMSchemeA may be prioritized when there is a conflict between two or more schemes. In this implementation, the UE is configured with a RepSchemeEnabler. Then, the occurrence of any of three conditions can trigger the prioritization 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 the DCI to indicate an entry in PDSCH-TimeDomainResourceAllocation containing RepNum16. When any of these conditions occur, the UE prioritizes TDMSchemeA regardless of the other configurations.
[0080] In another implementation, TDMSchemeB may be given priority. This implementation occurs when the UE is configured with RepNum16 in at least one entry of PDSCH-TimeDomainResourceAllocation. In this implementation, TDMSchemeB is given priority when the UE does not expect to configure RepSchemeEnabler. Specifically, under this condition, the user equipment does not expect to configure RepSchemeEnabler, or if it is configured, the user equipment ignores RepSchemeEnabler. The user equipment is expected to operate in TDMSchemeB, Mode 4, or inter-slot TDM schemes.
[0081] In another implementation, error resolution is provided. Specifically, the UE may be configured with RepNum16 in the DCI TDRA field and with a RepSchemeEnabler configured to be one of FDMSchemeA, FDMSchemeB, or TDMSchemeA. However, this is an invalid state, which causes an error. Therefore, when two of these conditions are met, the UE operates in the scheme indicated by the RepSchemeEnabler according to the first implementation. Alternatively, in another implementation, when these conditions are met, the UE operates in an inter-slot TDM scheme such as Scheme 4 or TDMSchemeB.
[0082] Figure 6 A flowchart of an exemplary method 600 for configuring a communication scheme for a UE is shown. Figure 6As shown, the network receives information about UE operation (610), such as the number of TCI states in the DCI and the number of DMRS CDM groups in the DCI. Based on this information, the network determines whether the UE is indicated to have two TCI states in the DCI. If yes (615-Y), the network determines whether the UE has two DMRS CDM groups (625). If yes, the network sets the UE to operate in SDM (630).
[0083] On the other hand, if the network determines that the UE is not identified as having two TCI states in the DCI (615-N), or that the UE is not identified as having two DMRS CDM groups (625-N), the network configures the UE to operate according to the dynamic configuration defined in version 16 (640). Although the above method is described as being performed by the network, it should be understood that the method can also be implemented by the UE.
[0084] Figure 7 A flowchart of an exemplary method 700 for selecting a communication scheme according to an embodiment of the present disclosure is shown. Figure 7 As shown, the UE identifies whether it has RepSchemeEnabler configured or RepNum16 in at least one entry in PDSCH-TimeDomainResourceAllocation. If the UE only has RepSchemeEnabler configured (705-RSE), the UE checks whether certain conditions 710 are met. For example, the UE determines whether it does not expect to configure RepNum16 in any entry in PDSCH-TimeDomainResourceAllocation, whether the UE ignores RepNum16 configured in any entry in PDSCH-TimeDomainResourceAllocation, or whether a third condition occurs when the UE does not expect the DCI to indicate an entry in PDSCH-TimeDomainResourceAllocation containing RepNum16. When any of these conditions occurs (720), the UE prioritizes TDMSchemeA regardless of other configurations.
[0085] On the other hand, if the UE identifies that it has RepNum16 (705-RN16) in at least one entry of PDSCH-TimeDomainResourceAllocation, then the UE analyzes another set of conditions (730). In this case, the UE determines whether it expects to configure RepSchemeEnabler. If not, the UE prioritizes TDMSchemeB.
[0086] Finally, if the UE recognizes that it is configured with both RepNum16 and RepSchemeEnabler (705 - both), the UE recognizes this condition as an error (750). Therefore, the UE chooses whether to operate in the scheme indicated by RepSchemeEnabler or in TDMSchemeB. Although the above method has been described as occurring at the UE, it should be understood that method 700 can be performed by the network, which will need to receive configuration information from the UE and additional steps to notify the UE of the selected configuration.
[0087] Figure 8 An exemplary system 800 for implementing measurement signal conflict resolution according to some embodiments of this disclosure is shown. The exemplary system 800 is provided for illustrative purposes only and is not intended to limit the disclosed embodiments. System 800 may include, but is not limited to, an access point (AP) 810, a station (STA) 820, and a network 830. Stations 820a-820c may include, but are not limited to, wireless local area network (WLAN) stations, such as wireless communication devices, smartphones, laptops, desktop computers, tablets, personal assistants, monitors, televisions, wearable devices, etc. Access point (AP) 810 may include, but is not limited to, WLAN electronic devices, such as wireless routers, wearable devices (e.g., smartwatches), wireless communication devices (e.g., smartphones), or combinations thereof. Network 830 may be the Internet and / or WLAN. Communication at station 820 is shown as wireless communication 840. Communication between AP 810 and STA 820 may be performed using wireless communication 840a-840c. Wireless communication 840a-840c may be based on various wireless communication technologies. These technologies may include, but are 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.).
[0088] One or more computer systems (such as...) can be used, for example. Figure 9 The computer system 900 shown herein is used to implement various implementation schemes. The computer system 900 can be any well-known computer capable of performing the functions described herein, such as... Figure 9 Equipment 910, 920, or Figure 2The computer system 900 includes one or more processors (also referred to as a central processing unit or CPU), such as processor 904. Processor 904 is connected to communication infrastructure 906 (e.g., a bus). The computer system 900 also includes user input / output devices 903, such as a monitor, keyboard, pointing device, etc., that communicate with the communication infrastructure 906 via user input / output interface 902. The computer system 900 also includes main memory or primary memory 908, such as random access memory (RAM). Main memory 908 may include one or more levels of cache. Main memory 908 stores control logic components (e.g., computer software) and / or data.
[0089] The computer system 900 may also include one or more auxiliary storage devices or memories 910. Auxiliary memory 910 may include, for example, a hard disk drive 912 and / or a removable storage device or drive 914. The removable storage drive 914 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and / or any other storage device / drive.
[0090] Removable storage drive 914 can interact with removable storage unit 918. Removable storage unit 918 includes a computer-usable or readable storage device on which computer software (control logic components) and / or data are stored. Removable storage unit 918 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disk, and / or any other computer data storage device. Removable storage drive 914 reads from and / or writes to removable storage unit 918 in a well-known manner.
[0091] According to some embodiments, auxiliary storage 910 may include other means, tools, or other methods for allowing computer system 900 to access computer programs and / or other instructions and / or data. Such means, tools, or other methods may include, for example, removable storage unit 922 and interface 920. Examples of removable storage unit 922 and interface 920 may include a program box and box interface (such as those found in video game devices), a removable memory chip (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards and associated memory card slots, and / or any other removable storage unit and associated interface.
[0092] Computer system 900 may also include a communication or network interface 924. Communication 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, communication interface 924 may allow computer system 900 to communicate with remote device 928 via communication path 926, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic components and / or data may be transmitted to and from computer system 900 via communication path 926.
[0093] The operations described in the foregoing embodiments can be implemented with a wide variety of configurations and architectures. Therefore, some or all of the operations described in the foregoing embodiments can be performed in hardware, software, or both. In some embodiments, tangible, non-transitory means or articles of art include tangible, non-transitory computer-usable or readable media on which control logic components (software) are stored, also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 900, main memory 908, secondary memory 910, and removable storage units 918 and 922, and tangible articles embodying any combination thereof. When executed by one or more data processing devices (such as computer system 900), such control logic components cause such data processing devices to operate as described herein.
[0094] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 9 The embodiments of this disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown herein. Specifically, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.
[0095] It should be understood that the Detailed Description section, rather than the Summary and Abstract section, is intended to interpret the claims. The Summary and Abstract section may set forth one or more, but not all, exemplary embodiments of this disclosure as contemplated by the inventors, and therefore is not intended to limit this disclosure and the appended claims in any way.
[0096] This disclosure has been described above using functional building blocks, which illustrate the implementation of specified functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined provided that the specified functions and their relationships are properly performed.
[0097] The above description of specific embodiments fully demonstrates the general nature of this disclosure, enabling others to easily modify and / or adapt various applications of such specific embodiments using knowledge within the scope of the art without requiring excessive experimentation, without departing from the general conception of this disclosure. Therefore, based on the teachings and guidance presented herein, such modifications and alterations are intended to fall within the meaning and scope of equivalents of the embodiments disclosed herein. It should be understood that the wording or terminology used herein is for illustrative purposes and not for limitation, and therefore the terminology or terminology of this specification should be interpreted by those skilled in the art in accordance with the teachings and guidance presented.
[0098] The breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.
Claims
1. A user equipment (UE), comprising: A memory that stores at least one full-power transmission mode capability of the user equipment; A transceiver configured to transmit and receive information with a communication network; as well as One or more processors, said one or more processors being configured to: This causes the transceiver to transmit a capability message to the communication network, the capability message indicating whether the UE supports each of the four different full-power transmission modes; Receive configuration messages from the communication network via the transceiver; The selected full-power transmission mode is determined based on the configuration message; as well as Configure the transceiver according to the selected full-power transmission mode from the four different full-power transmission modes. The four different full-power transmission modes include mode 0, mode 1, mode 2, and mode 3, and The four different full-power transmission modes include a mode in which the power scaling ratio is set to be equal to the ratio between the number of non-zero power ports of the configured transmit precoder matrix indicator TPMI and the maximum number of ports of the user equipment.
2. The user equipment according to claim 1, wherein the configuration message is a PUSCH-Config message.
3. The user equipment according to claim 1, wherein the transceiver includes a plurality of logical ports, and The memory further stores the number of the plurality of logical ports and the coherence capability of the user equipment.
4. The user equipment according to claim 3, wherein the capability message includes the number of the plurality of logical ports and the coherent capability of the user equipment.
5. The user equipment of claim 3, wherein the number of the plurality of logical ports is 2, and the coherence capability includes full coherence, and The mode 2 wherein some transmit precoder matrix indicators (TPMIs) are set to a power scaling ratio of 1 and other TPMIs are set to different power scaling values.
6. The user equipment of claim 3, wherein the number of the plurality of logical ports is 4, and the coherence capability includes full coherence, and The mode 2 described therein sets some transmit precoder matrix indicators (TPMIs) to have a power scaling ratio of 1 and sets other TPMIs to different power scaling values.
7. The user equipment of claim 1, wherein mode 0 sets all power scaling ratios to 1.
8. A method for setting a full-power transmission mode in a user equipment (UE), comprising: Capable of receiving at least one full-power transmission mode; Transmit a capability message to the communication network, the capability message indicating whether the UE supports each of the four different full-power transmission modes; Receive configuration messages from the communication network; The selected full-power transmission mode is determined based on the configuration message; as well as Configure the transceiver according to the selected full-power transmission mode from the four different full-power transmission modes. The four different full-power transmission modes include mode 0, mode 1, mode 2, and mode 3, and The four different full-power transmission modes include a mode in which the power scaling ratio is set to be equal to the ratio between the number of non-zero power ports of the configured transmit precoder matrix indicator TPMI and the maximum number of ports of the user equipment.
9. The method according to claim 8, wherein the configuration message is a PUSCH-Config message.
10. The method of claim 8, further comprising: The number of logical ports supported by the transceiver of the user equipment and the coherence capability of the user equipment are received.
11. The method of claim 10, wherein the capability message includes the number of logical ports supported by the transceiver and the coherent capabilities of the user equipment.
12. The method of claim 10, wherein the selected full-power transmission mode is one of the four different full-power transmission modes, and is selected based on the capabilities of the user equipment.
13. The method of claim 12, wherein in mode 0, all power scaling ratios are set to 1.
14. A method for operating a base station in a wireless network, comprising: Receive capability messages from the user equipment (UE), the capability messages indicating whether the UE supports each of four different full-power transmission modes; Based on the received capability message, select the selected full-power transmission mode from the four different full-power transmission modes; A configuration message is generated based on the selected full-power transmission mode; as well as The configuration message is transmitted to the user equipment. The four different full-power transmission modes include mode 0, mode 1, mode 2, and mode 3, and The four different full-power transmission modes include a mode in which the power scaling ratio is set to be equal to the ratio between the number of non-zero power ports of the configured transmit precoder matrix indicator TPMI and the maximum number of ports of the user equipment.
15. The method of claim 14, wherein the configuration message is a PUSCH-Config message.
16. The method of claim 15, wherein the selected full-power transmission mode is encoded in at least two bits of the PUSCH-Config message.
17. The method of claim 14, wherein the capability message further includes the number of logical ports supported by the transceiver of the UE and the coherence capability of the UE, and The selected full-power transmission mode is based on at least one of the number of logical ports or the coherence capability.
18. The method of claim 17, wherein in mode 0, the scaling ratio is set to 1.
19. The method of claim 14, further comprising: It is determined that the UE is served by multiple cells; Choose whether to set the BDFactorR complexity value at the per-cell level or at the per-cell group level; as well as In response to selecting the per-cell level, BDFactorR can be set individually for each of the plurality of cells, or in response to selecting the per-cell group level, the BDFactorR can be set to the same for all cells in the cell group.
Citation Information
Patent Citations
Uplink power control for advanced wireless communication systems
US20190327693A1