Method and system for enhancing codebook-based uplink or physical uplink shared channel transmission

Abstract

A user equipment (UE) includes a transceiver associated with a set of antenna ports; and a processor configured to transmit, via the transceiver, a UE capability corresponding to a coherence mode of a codebook-based physical uplink shared channel (PUSCH) operation to a network device. The processor is configured to: transmit, via the transceiver, an indication of an antenna architecture of the UE to the network device according to the UE capability corresponding to the coherence mode of the codebook-based PUSCH operation, the antenna architecture based at least in part on the set of antenna ports; and receiving, via the transceiver, an uplink (UL) transmit precoding matrix indicator (TPMI) codebook for the codebook-based PUSCH operation from the network device according to the antenna architecture of the UE indicated to the network device.

Description

[0001] Cross - reference to related applications

[0002] This Patent Cooperation Treaty patent application claims priority to U.S. Provisional Patent Application No. 63 / 422,281, filed on November 3, 2022, entitled "Methods and Systems for Enhancement of Codebook Based Uplink or Physical Uplink Shared Channel Transmission", the entire content of which is incorporated herein by reference. Technical Field

[0003] This application generally relates to wireless communication systems, including methods and systems for enhancing codebook-based coherent uplink (UL) or physical uplink shared channel (PUSCH) transmission using a set of antenna ports. Background Art

[0004] Wireless mobile communication technologies use various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLAN) (commonly referred to within the industry organization as ).

[0005] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between a base station of the RAN (which may sometimes also be referred to as a RAN node, a network node, or simply a node) and a wireless communication device called a user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0006] Each RAN can use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (which is sometimes simply referred to as LTE), and NG-RAN implements NR RAT (which is sometimes referred to as 5G RAT, 5G NR RAT, or simply NR in this document). In some deployments, E-UTRAN can also implement NR RAT. In some deployments, NG-RAN can also implement LTE RAT.

[0007] The base station used by the RAN can correspond to that RAN. An example of an E-UTRAN base station is an evolved universal terrestrial radio access network (E-UTRAN) Node B (which is usually also denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a next-generation Node B (which is sometimes also referred to as g Node B or gNB).

[0008] The RAN, together with external entities through its connection to the core network (CN), provides communication services. For example, E-UTRAN can utilize the evolved packet core (EPC), while NG-RAN can utilize the 5G core network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS

[0009] To easily identify the discussion of any particular element or action, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0010] Figure 1 An example wireless communication system according to the embodiments described herein is shown.

[0011] Figure 2 Various examples of antenna architectures according to the embodiments described herein are shown.

[0012] Figure 3 An example method of wireless communication performed by a user equipment (UE) according to the embodiments described herein is shown.

[0013] Figure 4 An example method of wireless communication performed by a network device according to the embodiments described herein is shown.

[0014] Figure 5 An example architecture of a wireless communication system according to the embodiments disclosed herein is illustrated.

[0015] Figure 6 A system for performing signaling between a wireless device and a network device according to the embodiments disclosed herein is illustrated. Detailed implementation manners

[0016] Describes various embodiments related to enhanced codebook-based uplink (UL) or physical uplink shared channel (PUSCH) transmission for implementing PUSCH transmission that supports four (4) or more layers per user equipment (UE) simultaneously using eight (8) transmitters (Tx), and specifically, enhancements related to transmit precoding matrix indicator (TPMI) for codebook PUSCH transmission.

[0017] In some embodiments, for 5G or 5G new radio (5G NR), UL (or PUSCH) transmission via a multiple-input multiple-output (MIMO) antenna architecture supports two different modes - codebook-based PUSCH operation and non-codebook-based PUSCH operation. For codebook-based PUSCH operation, the transmit precoding matrix indicator (TPMI) and the number of layers corresponding to the PUSCH operation can be indicated in the "Precoding information and number of layers" field of the downlink control information (DCI) used to schedule the PUSCH operation. As an example, the possible values of the TPMI can be hard-coded or can be fixed values, as specified in the 3rd Generation Partnership Project (3GPP) technical specification (TS) 38.211. For non-codebook-based PUSCH operation, the sounding reference signal (SRS) resource indicator (SRI) field of the downlink control information (DCI) used to schedule the PUSCH operation can be used to indicate the TPMI and the number of layers corresponding to the PUSCH operation.

[0018] In some embodiments, codebook-based UL (or PUSCH) operation via a MIMO antenna architecture can support three different coherence modes - non-coherent, partially coherent, and fully coherent. The codebook subset that supports the partially coherent mode is "partialAndNonCoherent", and the codebook subset that supports the fully coherent mode is "fullyAndPartialAndNonCoherent". Currently, codebook-based UL (or PUSCH) operation via a MIMO antenna architecture supports PUSCH operation with up to four Tx and up to four layers.

[0019] In the present disclosure, various embodiments enable codebook-based UL (or PUSCH) operation via a MIMO antenna architecture to support PUSCH operation with at least 8 Tx (or antenna ports) and four (4) or more layers per UE. As described above, various embodiments describe the TPMI for codebook-based coherent PUSCH operation using at least 8 antenna ports. Currently, the TPMI for codebook-based coherent PUSCH operation only supports up to four antenna ports.

[0020] In some embodiments, the TPMI for at least 8Tx codebook-based coherent PUSCH operation may be based on the UE's antenna architecture and may be sent by the UE as UE capabilities. Additionally or alternatively, the TPMI for at least 8Tx codebook-based coherent PUSCH operation may be based on a type I downlink (DL) codebook. Thus, the UE may apply the phase or amplitude coefficients specified by the network device (located in the radio access network (RAN) or core network (CN)) for each layer of the PUSCH to each of at least 8 antenna ports for codebook-based coherent PUSCH operation. Further enhancements corresponding to reducing the overhead associated with the indication of the UL TPMI codebook are also described in the present disclosure. The present disclosure describes embodiments using 8 antenna ports, but the embodiments described herein may also be applied to UEs having more than 8 antenna ports or fewer than 8 antenna ports (but more than the four antenna ports currently supported in 5G or 5G NR).

[0021] Reference will now be made specifically to representative embodiments / aspects shown in the accompanying drawings. The following description is not intended to limit the embodiments to one preferred embodiment. Instead, it is intended to cover alternative forms, combinations, modifications, and equivalents that may be included within the spirit and scope of the described embodiments as defined by the appended claims.

[0022] Figure 1 An example wireless communication system according to the embodiments described herein is shown. As Figure 1 shown, the wireless communication system 100 may include a network device 102 and a user equipment (UE) 104. The UE 104 may be communicatively coupled to the network device 102 to send data in the uplink (UL) direction. For example, the UE may perform PUSCH transmissions (shown as PUSCH 1 108a and PUSCH 2 108b) via the first antenna panel 106a and the second antenna panel 106b of the UE 104. The UE 104 may also receive data in the downlink (DL) direction using the first antenna panel 106a and the second antenna panel 106b.

[0023] In some embodiments, the network device 102 can be an eNodeB (eNB), gNodeB (gNB), or access point (AP) in a radio access network (RAN), and can support one or more radio access technologies such as 4G, 5G New Radio (5G NR (or 5G)), 6G, etc. The UE 104 can be a phone, smartphone, tablet, smartwatch, Internet of Things (IoT), vehicle, etc. References to user equipment (UE) in this disclosure are provided for illustrative purposes only. Example embodiments can be used with any electronic component that can establish a connection with the network and is configured with hardware, software, and / or firmware for information and data exchange with the network. Thus, the UE described herein is used to represent any suitable electronic device.

[0024] As described herein, in some embodiments, codebook-based coherent PUSCH operations are performed via a set of antenna ports. The set of antenna ports can include more than 4 antenna ports (e.g., 8 antenna ports). The antenna architecture that describes the set of antenna ports can be represented as a tuple (N g , N 1 , N 2 ). The first parameter N g can correspond to the number of antenna port groups, the second parameter N 1 can correspond to the number of antenna positions in the vertical direction, and the third parameter N 2 can correspond to the number of antenna positions in the horizontal direction. Each antenna port can have a one-to-one or one-to-N mapping with a physical antenna element, where N is greater than 1. In some embodiments, and as a non-limiting example, the value of N can be 2 because each antenna port can include a vertically polarized antenna element and a horizontally polarized antenna element.

[0025] As a non-limiting example, each antenna port group or one or more antenna groups in the number of antenna port groups represented by N g can have the same uniform linear antenna (ULA) structure. Additionally, the distance between two adjacent antenna port groups can be the same or different. The nature of the distance between two adjacent antenna port groups can be arbitrarily selected. For example, each antenna position represented by N 1 and / or N 2 can include cross-polarized antenna elements. The cross-polarization of the antenna elements can be achieved through vertical polarization and / or horizontal polarization. Furthermore, each antenna position represented by N 1 (if N 1 ≥ 2) can be vertically separated from another adjacent antenna position by an equal vertical distance, e.g., distance d1, and each antenna position represented by N 2 (if N 2Each antenna position represented by ≥2) can be horizontally separated from an adjacent antenna position by an equal horizontal distance, such as distance d2. As a non-limiting example, distance d1 can be the same as distance d2, or distance d1 can be different from distance d2.

[0026] Figure 2 illustrates various examples of antenna architectures that can be represented using the tuple (N g , N 1 , N 2 ). In FIG. 200, four different antenna architectures are illustrated, which can correspond to the antenna architectures that need to be supported in some embodiments, while other antenna architectures are also possible. The first antenna architecture 202 includes four antenna positions 202a, 202b, 202c, and 202d in a single antenna panel. The first antenna architecture 202 can be represented using N g = 1, N 1 = 4, and N 2 = 1, such as (1, 4, 1). The second antenna architecture 204 includes four antenna positions 204a, 204b, 204c, and 204d in a single antenna panel. However, the four antenna positions 204a, 204b, 204c, and 204d are arranged in two rows and two columns, and accordingly the second antenna architecture 204 can be represented using N g = 1, N 1 = 2, and N 2 = 2, such as (1, 2, 2).

[0027] The third antenna architecture 206 includes two antenna panels 208 and 210, and each antenna panel includes two antenna positions. For example, antenna panel 208 includes two antenna positions 208a and 208b arranged horizontally, and antenna panel 210 includes two antenna positions 210a and 210b arranged horizontally. Thus, the third antenna architecture 206 can be represented using N g = 2, N 1 = 2, and N 2 = 1, such as (2, 2, 1).

[0028] Correspondingly, in other words, the antenna panel corresponds to the antenna port group. Thus, each of the antenna architecture 202 and the antenna architecture 204 is a single-panel (SP) antenna architecture, and the antenna architecture 206 is a multi-panel (MP) antenna architecture.

[0029] The fourth antenna architecture 212 includes four antenna panels 214, 216, 218, and 220, and each antenna panel includes a single antenna position 214a, 216a, 218a, and 220a, respectively. The fourth antenna architecture 212 can be represented using N g = 4, N1 = 1 and N 2 = 1 such as (4, 1, 1) to represent. Since the value of N for the fourth antenna architecture is 4 (or greater than 1), the fourth antenna architecture is also an MP antenna architecture as described herein. g The value of N for the fourth antenna architecture is 4 (or greater than 1), so the fourth antenna architecture is also an MP antenna architecture as described herein.

[0030] In some embodiments, the UE may report or indicate to a network device (e.g., in the RAN or CN) via Radio Resource Control (RRC) signaling and / or MAC Control Element (MACCE) that the UE supports codebook - based coherent PUSCH operation using 8 antenna ports, and also the antenna architecture that supports codebook - based coherent PUSCH operation using 8 antenna ports. The antenna architecture for 8 antenna ports can be represented by (N g , N 1 , N 2 ) including but not limited to (1, 4, 1), (1, 2, 2), (2, 2, 1), or (4, 1, 1). As a non - limiting example, the UE may report the antenna architecture that supports codebook - based coherent PUSCH operation using 8 antenna ports. For example, when the UE supports partial - coherent PUSCH operation mapped to a partially - coherent coherence mode, and / or when the UE supports coherent PUSCH operation mapped to a fully - coherent coherence mode, as described herein, the UE may report to the network device the antenna architecture supported by the UE. In some embodiments, when the UE indicates that the UE supports coherent PUSCH operation mapped to a partially - coherent and / or fully - coherent coherence mode, the network device may configure the UL TPMI codebook for codebook - based PUSCH operation for at least one of the following: two antenna ports or four antenna ports of the UE's antenna architecture. It is expected that the UE supports and complies with the configured TPMI codebook for coherent PUSCH operation.

[0031] In some embodiments, when the network device configures the UE for codebook - based coherent PUSCH operation using, for example, 8 antenna ports, the network device may or may not configure the UE for the UE's antenna architecture, which may imply different TPMI codebooks for codebook - based PUSCH operation. The TPMI codebook for codebook - based PUSCH operation is determined based on the antenna architecture reported by the UE. Codebook - based coherent PUSCH operation may refer to a partially - coherent and / or fully - coherent coherence mode, as described herein.

[0032] In some embodiments, the codebook for UL TPMI may be based on a Type I downlink (DL) codebook, and the UL TPMI may be based on a Type I SP codebook and / or a Type I MP codebook. When the UL TPMI can be based on both a Type I SP codebook and a Type I MP codebook, the UE may explicitly and / or independently report or send to the network device whether the UE supports the Type I SP codebook or the Type I MP codebook for UL TPMI. In some embodiments, whether the UE supports the Type I SP codebook or the Type I MP codebook for UL TPMI may be implicitly determined by the network device, for example, based on the antenna architecture of the UE indicated by the UE as UE capabilities to the network device. Accordingly, when the network device receives in the UE capabilities that the UE supports the first antenna architecture or the second antenna architecture described herein Figure 2 the network device may determine that the UE supports the Type I SP codebook for UL TPMI, and when the network device receives in the UE capabilities that the UE supports the third antenna architecture or the fourth antenna architecture described herein Figure 2 the network device may determine that the UE supports the Type I MP codebook for UL TPMI. In some embodiments, the UE may report the Type I SP codebook or the Type I MP codebook, but not both. In some embodiments, the UE may support at least the Type I SP codebook for UL TPMI. The network device may configure the UL TPMI codebook for the UE using RRC signaling, MAC CE, and the UL TPMI codebook may be a Type I SP codebook or a Type I MP codebook. As an example, the network device may dynamically update the UL TPMI codebook, for example, using DCI. The Type I SP codebook and / or the Type I MP codebook described herein may be a sub-band Type I codebook or a wide-band Type I codebook.

[0033] In some embodiments, when the Type I SP codebook and / or the Type I MP codebook is used for the UL TPMI codebook, and the UL TPMI codebook is not indicated as a Type 1 SP codebook or a Type 1 MP codebook in the DCI, the size of the "precoding information and number of layers" field in the DCI for scheduling PUSCH may be where L max corresponds to the maximum number of ranks configured by RRC, Nl corresponds to the number of different precoding matrices supported by the UL TPMI codebook (or Type I codebook) of Type I, and l may correspond to the values 1, 2... 8 of the antenna architecture with 8 antenna ports.

[0034] In some embodiments, the following table may be used to map the "precoding information and number of layers" field to a specific TPMI.

[0035] Value of the "Precoding information and number of layers" field in DCI Mapped TPMI 0 to N1 - 1 Type - I codebook for rank 1 with 8 ports N1 to N1 + N2 - 1 Type - I codebook for rank 2 with 8 ports … … N1 + N2+…+N7 to N1 + N2+…+N8 - 1 Type - I codebook for rank 8 with 8 ports

[0036] In some embodiments, when a type ISP codebook and / or a type IMP codebook are used for the UL TPMI codebook, and it is indicated in the DCI whether the UL TPMI codebook is a type 1SP codebook or a type 1MP codebook, the type I SP codebook and the type I MP codebook can be cascaded in the "precoding information and number of layers" field in the DCI for scheduling PUSCH operations. Accordingly, the size of the "precoding information and number of layers" field in the DCI can be In some embodiments, and by way of non-limiting example, additional bits in the "precoding information and number of layers" field in the DCI can be used to indicate whether the UL TPMI is a type ISP codebook or a type IMP codebook. Accordingly, the size of the "precoding information and number of layers" field in the DCI can be

[0037] In some embodiments, and by way of non-limiting example, to reduce the overhead of TPMI indication (e.g., the possible number of TPMIs), the rotation factor (or oversampling factor) in one or both of the vertical polarization and the horizontal polarization of the cross-polarized antenna elements of the UE's antenna architecture can be reduced from 4 to 2, or from 4 to 1. Additionally or alternatively, the overhead of TPMI indication can be reduced by reducing the quantization bits for the co-phase of the polarization of the antenna elements of the UE's antenna architecture, and / or by reducing the selection for orthogonal layers (other than the first layer) on a spatial basis.

[0038] Figure 3 An example method of wireless communication performed by a user equipment (UE) according to embodiments described herein is shown. As shown in the flowchart 300, at 302, the UE can send UE capabilities corresponding to the coherence mode of the codebook-based PUSCH operation to a network device. The coherence mode can be one of a non-coherent mode, a fully coherent mode, and a partially coherent mode, and can be sent to the network device as UE capabilities using RRC and / or MAC CE. At 304, the UE can send an indication of the antenna architecture supported by the UE to the network device. The antenna architecture can be at least partially based on a plurality of antenna ports and their corresponding arrangements, as Figure 2 shown. Additionally, as described herein, the UE can send an indication of the antenna architecture supported by the UE based on the UE capabilities corresponding to the coherence mode supported by the UE. At 306, the UE can receive an uplink (UL) transmission precoding matrix indicator (TPMI) codebook for codebook-based PUSCH operations from the network device. As described herein, the TPMI codebook is determined by the network device based on the antenna architecture of the UE indicated to the network device by the UE.

[0039] Figure 4Illustrates an example method of wireless communication performed by a network device according to an embodiment described herein. The network device may be a network device, such as a base station in a RAN, a server in a CN, etc. As shown in the flowchart 400, at 402, the network device may receive UE capabilities corresponding to the coherence mode of PUSCH operation and / or the antenna architecture of the UE. The UE capabilities corresponding to the coherence mode of PUSCH operation and / or the antenna architecture of the UE may be received via RRC signaling or MAC CE. At 404, the network device may configure or update the UE with a TPMI codebook for PUSCH operation. The TPMI codebook may be configured or updated using RRC signaling, MAC CE, and / or DCI. Since various antenna architectures, coherence modes, and details of selecting the TPMI codebook based on the coherence mode and / or antenna architecture have been described in detail, those details are not repeated here for the sake of brevity.

[0040] Embodiments contemplated herein include an apparatus having logic components, modules, or circuits for performing one or more elements of method 300 or 400. In the context of method 300, the apparatus may be an apparatus such as a UE (such as the wireless device 602 as a UE, as described herein). In the context of method 400, the apparatus may be a network device such as a network device 620 that may be a base station, as described herein.

[0041] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 300 or 400. In the context of method 300, the apparatus may be an apparatus such as a UE (such as the wireless device 602 as a UE, as described herein). In the context of method 400, the apparatus may be a network device such as a network device 620 that may be a base station, as described herein.

[0042] Embodiments contemplated herein include a signal as described in or related to one or more elements of method 300 or 400.

[0043] The embodiments contemplated herein include a computer program or computer program product having instructions, where execution of the program by a processor causes the processor to perform one or more elements of method 300 or 400. In the context of method 300, the processor can be a processor of the UE (such as processor 604 of wireless device 602 that is the UE, as described herein), and the instructions can be located, for example, in the processor and / or on the memory of the UE (such as memory 606 of wireless device 602 that is the UE, as described herein). In the context of method 600, the processor can be a processor of the base station (such as processor 622 of network device 620 that is the base station, as described herein), and the instructions can be located, for example, in the processor and / or on the memory of the base station (such as memory 624 of network device 620 that is the base station, as described herein).

[0044] Figure 5 An example architecture of a wireless communication system 500 in accordance with embodiments disclosed herein is illustrated. The description provided below is directed to an exemplary wireless communication system 500 operating in conjunction with the LTE system standard and / or 5G or NR system standards provided in 3GPP technical specifications.

[0045] As Figure 5 shown, wireless communication system 500 includes UEs 502 and 504 (however, any number of UEs can be used). In this example, UEs 502 and 504 are illustrated as smart phones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but can also include any mobile or non-mobile computing device configured for wireless communication.

[0046] UEs 502 and 504 can be configured to be communicatively coupled to RAN 506. In an embodiment, RAN 506 can be an NG-RAN, an E-UTRAN, etc. UEs 502 and 504 utilize connections (or channels) to RAN 506 (shown as connections 508 and 510, respectively), where each includes a physical communication interface. RAN 506 can include one or more base stations that enable connections 508 and 510, such as base stations 512 and 514.

[0047] In this example, connections 508 and 510 are air interfaces for enabling such communicative coupling and can conform to the RAT used by RAN 506, such as, for example, LTE and / or NR.

[0048] In some embodiments, UE 502 and UE 504 may also directly exchange communication data via sidelink interface 516. UE 504 is illustrated as being configured to access an access point (shown as AP 518) via connection 520. As an example, connection 520 may include a local wireless connection, such as any connection compliant with the IEEE 802.11 protocol, where AP 518 may include a router. In this example, AP 518 may be connected to another network (e.g., the Internet) without passing through CN 524.

[0049] In embodiments, UE 502 and UE 504 may be configured to communicate with each other or with base stations 512 and / or base stations 514 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this regard. The OFDM signal may include a plurality of orthogonal sub-carriers.

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

[0051] RAN 506 is illustrated as communicatively coupled to CN 524. CN 524 may include one or more network elements 526, which are configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 502 and UE 504) connected to CN 524 via RAN 506. The components of CN 524 may be implemented in one physical device or in respective independent physical devices including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

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

[0053] In an embodiment, CN 524 may be a 5GC, and RAN 506 may be connected to CN 524 via the NG interface 528. In an embodiment, the NG interface 528 may be divided into two parts: the NG user plane (NG-U) interface, which carries traffic data between the base station 512 or base station 514 and the user plane function (UPF); and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 512 or base station 514 and the access and mobility management function (AMF).

[0054] Generally, the application server 530 may be an element that provides an application using Internet protocol (IP) bearer resources together with CN 524 (e.g., packet-switched data services). The application server 530 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 502 and UE 504 via CN 524. The application server 530 may communicate with CN 524 through the IP communication interface 532.

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

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

[0057] The wireless device 602 may include a memory 606. The memory 606 may be a non-transitory computer-readable storage medium storing instructions 608 (which may include, for example, instructions executed by the processor 604). The instructions 608 may also be referred to as program code or a computer program. The memory 606 may also store data used by the processor 604 and results computed by the processor.

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

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

[0060] In some embodiments with multiple antennas, the wireless device 602 may implement analog beamforming techniques, whereby the phases of the signals transmitted by the antennas 612 are adjusted relative to each other such that the (joint) transmission of the antennas 612 can be directed (which is sometimes referred to as beam steering).

[0061] The wireless device 602 may include one or more interfaces 614. The interfaces 614 may be used to provide input to or output from the wireless device 602. For example, the wireless device 602 as a UE may include interfaces 614 such as a microphone, a speaker, a touch screen, buttons, etc. to allow a user of the UE to provide input to and / or output from the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry (e.g., other than the transceiver 610 / antenna 612 already described), which allow the UE to communicate with other devices and may operate according to known protocols (e.g., etc.).

[0062] The wireless device 602 may include one or more modules for physical uplink shared channel transmission, which are shown as PUSCH modules 616. The PUSCH modules 616 may be implemented via hardware, software, or a combination thereof. For example, the PUSCH modules 616 may be implemented as a processor, circuitry, and / or instructions 608 stored in the memory 606 and executed by the processor 604. In some examples, the PUSCH modules 616 may be integrated within the processor 604 and / or the transceiver 610. For example, the CSI measurement and reporting module 616 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the processor 604 or the transceiver 610.

[0063] The PUSCH modules 616 may be used for various aspects of the present disclosure, for example, Figures 1 to 4 aspects of. The PUSCH modules 616 may be configured to, for example, configure CSI measurement and reporting and send one or more CSI reports to another device (e.g., to the network device 620).

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

[0065] The network device 620 may include a memory 624. The memory 624 may be a non-transitory computer-readable storage medium storing instructions 626 (which may include, for example, instructions executed by the processor 622). The instructions 626 may also be referred to as program code or a computer program. The memory 624 may also store data used by the processor 622 and results calculated by the processor.

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

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

[0068] The network device 620 may include one or more interfaces 632. The interface 632 may be used to provide input to or output from the network device 620. For example, the network device 620 acting as a base station may include an interface 632 composed of a transmitter, a receiver, and other circuitry (e.g., in addition to the transceivers 628 / antennas 630 already described), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers, databases, etc., for the purpose of performing operations, managing, and maintaining the base station or other equipment operably connected to the base station.

[0069] The network device 620 may include one or more modules for physical uplink shared channel transmission, and the one or more modules are shown as PUSCH modules 634. The PUSCH module 634 may be implemented via hardware, software, or a combination thereof. For example, the PUSCH module 634 may be implemented as a processor, circuitry, and / or instructions 626 stored in the memory 624 and executed by the processor 622. In some examples, the PUSCH module 634 may be integrated within the processor 622 and / or the transceiver 628. For example, the PUSCH module 634 may be implemented by a combination of software components (e.g., software components executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the processor 622 or the transceiver 628.

[0070] From the perspective of the network device, the PUSCH module 634 may be used in various aspects of the present disclosure, for example, Figures 1 to 4 in various aspects of.

[0071] For one or more embodiments, at least one of the components recited in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples recited herein. As another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples recited herein.

[0072] Unless otherwise explicitly stated, any one of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from practice of various embodiments.

[0073] Embodiments and specific implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic components for performing operations; or may include a combination of hardware, software, and / or firmware.

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

[0075] It is well known that the use of personally identifiable information should follow privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly explained to the user.

[0076] Although the foregoing has been described in considerable detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and apparatus described herein. Accordingly, the embodiments of the invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein but may be modified within the scope and equivalents of the appended claims.

Claims

1. A user equipment (UE), comprising: a transceiver associated with a set of antenna ports; and a processor configured to: send, via the transceiver, UE capabilities corresponding to a coherence mode of codebook-based physical uplink shared channel (PUSCH) operation to a network device; send, via the transceiver, an indication of the antenna architecture of the UE to the network device, the antenna architecture being at least partially based on the set of antenna ports; and receive, via the transceiver, an uplink (UL) transmit precoding matrix indicator (TPMI) codebook for the codebook-based PUSCH operation from the network device according to the coherence mode and the antenna architecture of the UE indicated to the network device.

2. The UE according to claim 1, wherein the set of antenna ports comprises at least eight antenna ports.

3. The UE according to claim 1, wherein the coherence mode is one of the following: non-coherent mode, full-coherent mode, and partial-coherent mode.

4. The UE according to claim 3, wherein the indication of the antenna architecture of the UE is sent for the coherence mode in the full-coherent mode or the partial-coherent mode.

5. The UE according to claim 1, wherein: the antenna architecture parameters of the UE are parameterized using at least the following: a first parameter corresponding to the number of antenna port groups; a second parameter corresponding to the number of antenna positions in the vertical direction; and a third parameter corresponding to the number of antenna positions in the horizontal direction.

6. The UE according to claim 5, wherein the first parameter has a value indicating that the antenna architecture of the UE is a single panel (SP) antenna architecture.

7. The UE according to claim 5, wherein the first parameter has a value indicating that the antenna architecture of the UE is a multi-panel (MP) antenna architecture.

8. The UE according to claim 5, wherein: the value of the first parameter is at least any one of the following: 1, 2, and 4; the value of the second parameter is at least any one of the following: 1, 2, and 4; and the value of the third parameter is at least any one of the following: 1 and 2.

9. The UE according to claim 8, wherein the value of the second parameter is 4 and the value of the third parameter is 1.

10. The UE according to claim 8, wherein the value of the second parameter is 2 and the value of the third parameter is 2.

11. The UE according to claim 5, wherein the UL TPMI codebook for the codebook-based PUSCH operation is received at the UE via radio resource control (RRC) signaling from the network device.

12. The UE according to claim 11, wherein the processor is further configured to receive, via the transceiver, the UL TPMI for the codebook-based PUSCH operation for four antenna ports of the antenna architecture of the UE from the network device.

13. The UE according to claim 12, wherein the processor is further configured to receive, via the transceiver, a configuration of the antenna architecture of the UE from the network device.

14. The UE according to claim 12, wherein: the UL TPMI codebook for the codebook-based PUSCH operation is based on a downlink (DL) codebook; the DL codebook is a type 1 DL codebook; and the UL TPMI codebook is a type 1 single panel (SP) codebook corresponding to a single panel (SP) antenna architecture.

15. A method for performing physical uplink shared channel (PUSCH) operations using a plurality of transmitters including at least eight transmitters, comprising: determining, by a user equipment (UE), a coherence mode of the PUSCH operation; sending, from the UE to a network device, UE capabilities corresponding to the coherence mode of the PUSCH operation; sending, from the UE to the network device, an indication corresponding to the antenna architecture of the UE; determining, according to the coherence mode and the UE capabilities corresponding to the antenna architecture of the UE, an uplink (UL) transmit precoding matrix indicator (TPMI) codebook for the PUSCH operation; and sending, from the UE to the network device, an indication corresponding to the determined UL TPMI codebook according to the determination of the UL TPMI codebook.

16. The method according to claim 15, wherein the set of antenna ports includes at least eight antenna ports.

17. The method according to claim 15, wherein the coherence mode is one of the following: non-coherent mode, full coherence mode, and partial coherence mode.

18. The method according to claim 15, wherein: parameterizing the antenna architecture of the UE using at least the following: a first parameter corresponding to the number of antenna port groups; a second parameter corresponding to the number of antenna positions in the vertical direction; and a third parameter corresponding to the number of antenna positions in the horizontal direction.

19. The UE according to claim 8, wherein: the value of the second parameter is 4, and the value of the third parameter is 1; or the value of the second parameter is 2, and the value of the third parameter is 2.

20. A network device, comprising: a transceiver; and a processor configured to: receive, via the transceiver, from a user equipment (UE): UE capabilities corresponding to a coherence mode of a codebook-based physical uplink shared channel (PUSCH) operation using a plurality of transmitters of the UE and a single panel or multi-panel antenna architecture; and the antenna architecture of the UE according to the UE capabilities corresponding to the PUSCH operation and the coherence mode of the codebook-based PUSCH operation; and configure or update, according to the UE capabilities corresponding to the antenna architecture, an uplink (UL) transmit precoding matrix indicator (TPMI) codebook for the PUSCH operation using radio resource control (RRC) signaling.

Images