Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04B—TRANSMISSION
  • H04B7/00—Radio transmission systems, i.e. using radiation field
  • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
  • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
  • H04B7/0413—MIMO systems
  • H04B7/0452—Multi-user MIMO systems
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/0001—Arrangements for dividing the transmission path
  • H04L5/0014—Three-dimensional division
  • H04L5/0023—Time-frequency-space
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
  • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal

Definitions

• This application relates generally to wireless communication systems, including methods for supporting an increased number of demodulation reference signal (DMRS) ports for transmission of a DMRS.
• DMRS demodulation reference signal
• support is provided for an increased number of DMRS ports using a frequency domain orthogonal cover code (FD-OCC) length of 4.
• FD-OCC frequency domain orthogonal cover code
• RANs radio access networks
• a network device e.g., a base station, a network access point, or a relay
• RAN wireless communication device
• UE user equipment
• 3GPP RANs can include, for example, global system for mobile communications (GSM), enhanced data rates 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).
• GSM global system for mobile communications
• EDGE enhanced data rates for GSM evolution
• GERAN Universal Terrestrial Radio Access Network
• E-UTRAN Evolved Universal Terrestrial Radio Access Network
• NG-RAN Next- Generation Radio Access Network
• a network device used by a RAN may correspond to that RAN.
• the network device may be an E-UTRAN base station, which is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB).
• E-UTRAN Evolved Universal Terrestrial Radio Access Network
• eNodeB enhanced Node B
• eNB evolved Node B
• NG-RAN base station which is a next generation Node B (also sometimes referred to as a gNode B or gNB).
• a RAN provides its communication services with external entities through its connection to a core network (CN).
• CN core network
• E-UTRAN may utilize an Evolved Packet Core (EPC)
• NG-RAN may utilize a 5G Core Network (5GC).
• EPC Evolved Packet Core
• 5GC 5G Core Network
• FIG. 1 shows a communication system including a user equipment (UE) in communication with a network device.
• UE user equipment
• FIG. 2 shows an example method of wireless communication as performed by a network device, in accordance with some embodiments.
• FIG. 3 shows another example method of wireless communication as performed by a network device, in accordance with some embodiments.
• FIG. 4 shows an example method of wireless communication as performed by a UE, in accordance with some embodiments.
• FIG. 5 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
• FIG. 6 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.
• a network device and/or a user equipment (UE).
• UE user equipment
• the example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with a network. Therefore, the UE as described herein is used to represent any appropriate electronic device.
• a network device which may be a network access point, a base station, and/or a relay deployed in a terrestrial network (TN), a satellite, and/or a high-altitude platform system (HAPS) including manned or unmanned aerial vehicles, and so on.
• TN terrestrial network
• HAPS high-altitude platform system
• the number of antenna ports than can be supported by a network device such as a base station, a network access point, and/or a relay has increased.
• the network device may serve more UEs within the same timefrequency resource using spatial beamforming techniques. Accordingly, the number of antenna ports used to transmit a DMRS to a UE may be increased, and/or additional patterns of DMRS ports may be indicated in downlink control information (DCI).
• DCI downlink control information
• the DCI is transmitted to a UE and from a network device to schedule a physical downlink shared channel (PDSCH), which supports a maximum of eight layers.
• PDSCH physical downlink shared channel
• Various patterns of one or more DMRS ports are specified in 3GPP specification TS 38.212. However, various embodiments, as described herein, disclose additional patterns of one or more DMRS ports that can be indicated by a network device in DCI, and thereby enhance a network device’s capability to serve UEs.
• FIG. 1 shows a communication system 100 including a UE 104 in communication with a network device 102.
• the network device 102 may be a base station, a network access point, or a relay that is deployed in a terrestrial network (TN) or a non-terrestrial network (NTN).
• the network device 102 may transmit DCI to the UE 104 in a physical downlink control channel (PDCCH).
• the UE 104 may decode the PDCCH, and use the DCI to schedule uplink (UL) transmission 104b and downlink (DL) transmission 104a with the network device 102, in accordance with DMRS ports specified in the DCI.
• DL downlink
• additional patterns of one or more DMRS ports may use frequency domain orthogonal cover code (FD-OCC) of a predetermined length 4, for a DMRS of DMRS configuration type 1 that uses a maximum of 1 or 2 DMRS symbols.
• FD-OCC frequency domain orthogonal cover code
• the FD-OCC may have a length of 4.
• a value of a DMRS port that can be included in DCI for communicating a pattern of one or more DMRS ports corresponds with a DMRS configuration type, a type of code divisional multiplexing (CDM) group without data, and whether a DMRS includes 1 symbol or 2 symbols.
• a DMRS of 1 symbol may include DMRS ports 0 and 1, or DMRS ports 8 and 9, for CDM group 0(, and a DMRS of 2 symbols may include DMRS ports 4 and 5, or DMRS ports 12 and 13, for the CDM group 0.
• the DMRS ports with a value of 0, 1, 2, 3, 4, 5, 6, or 7 may be referred in this disclosure as an unsealed DMRS port, and a DMRS port of a value above 7 may be referred in this disclosure as a scaled-up DMRS port.
• Various patterns of DMRS ports may be selected by a network device in accordance with a set of subcarriers used for DMRS, and/or a CDM group.
• the following patterns of one or more additional DMRS ports, and in particular, scaled-up DMRS ports may be supported.
• various patterns of one or more DMRS ports as specified in Table 7.3.1.2.2-1 of 3GPP TS 38.212 may be updated by adding a value of 8 to the specified DMRS port value.
• a pattern of one or more DMRS ports as specified in the table above may also be used for DMRS configuration type 1 and for a DMRS of a maximum 2 symbols when a number of front-loaded symbols is 1.
• a network device may facilitate multi-user M1M0 (MU-
• the MU-MIMO scheduling may be used for coscheduling among a plurality of UEs.
• the plurality of UEs may include a legacy UE and an enhanced UE.
• the legacy UE as referenced herein may be a UE which may not support scaled-up DMRS ports and only supports unsealed DMRS ports, and the enhanced UE may support both scaled-up DMRS ports and unsealed DMRS ports.
• a network device may facilitate multi-user MIMO (MU- MIMO) scheduling by a pattern of five DMRS ports that includes both scaled-up and unsealed DMRS ports, as shown in the below table.
• the MU-MIMO scheduling may be used for coscheduling among a plurality of UEs.
• the plurality of UEs in some embodiments, and by way of a non- limiting example, may include a legacy UE and an enhanced UE.
• the pattern of five DMRS ports as specified in the below table may be used for a PDSCH of more than 4 layers.
• a network device may transmit an activation command, which maps a codepoint of DCI field transmission configuration indication (TCI) to two TCI states, the UE may need to select DMRS ports as specified in Table 7.3.1.2.2.-1A of 3GPP TS 38.212 specification, which is an alternate or a fallback of Table 7.3.1.2.2-1 of 3GPP TS 38.212 mentioned above. Additional patterns of one or more DMRS ports may be added to the Table 7.3.1.2.2.-1 A, as shown below. Additional patterns of one or more DMRS ports shown in the below table may include scaled-up DMRS ports and/or unsealed DMRS ports.
• TCI DCI field transmission configuration indication
• a DMRS of DMRS configuration type 1 and having a maximum of 2 symbols for a DMRS following patterns of one or more additional DMRS ports, and in particular, scaled-up DMRS ports, may be supported. Additionally, or alternatively, various patterns of one or more DMRS ports as specified in Table 7.3.1.2.2-2 of 3GPP TS 38.212 specification, which corresponds with DMRS configuration type 1 and having a maximum of 2 symbols for a DMRS, may be updated by adding a value of 8 to a specified DMRS port value.
• Table 7.3.1.2.2-2 of 3GPP TS 38.212 specification may be further enhanced using a mix of one or more scaled-up DMRS ports and one or more unsealed DMRS ports, as specified in the below table, to support PDSCH of up to 4 layers.
• the Table 7.3. 1.2.2-2 of 3GPP TS 38.212 specification may be enhanced by using a pattern of DMRS ports, as specified in the below table.
• Various patterns of DMRS ports in the below table may include one or more scaled-up DMRS ports and one or more unsealed DMRS ports.
• the Table 7.3.1.2.2-2 of 3GPP TS 38.212 specification may be enhanced by using a pattern of DMRS ports, as specified in the below table.
• Various patterns of DMRS ports in the below table may include one or more scaled-up DMRS ports and one or more unsealed DMRS ports.
• a value of 8 may be added to a DMRS port value specified in the Table 7.3.1.2.2-2 of 3GPP TS 38.212 specification for an additional pattern of one or more DMRS ports.
• the Table 7.3.1.2.2-2 of 3GPP TS 38.212 specification may be enhanced by using a pattern of DMRS ports, as specified in the below table.
• Various patterns of DMRS ports in the below table may include one or more scaled-up DMRS ports and one or more unsealed DMRS ports.
• 3GPP TS 38.212 specification may be enhanced by using a pattern of DMRS ports, as specified in the below table.
• Various patterns of DMRS ports in the below table may include one or more scaled-up DMRS ports and one or more unsealed DMRS ports.
• a network device transmits an activation command which maps a codepoint of DCI field transmission configuration indication (TCI) to two TCI states
• the UE may need to use DMRS ports as specified in Table 7.3.1.2.2.-2A of 3GPP TS 38.212 specification, which is an alternate or a fallback of Table 7.3.1.2.2-2 of 3GPP TS 38.212 mentioned above. Additional patterns of one or more DMRS ports may be added to the Table 7.3.1.2.2.-2A, as shown below. Additional patterns of one or more DMRS ports shown in the below table may include one or more scaled-up DMRS ports and/or one or more unsealed DMRS ports.
• FIG. 2 shows an example method of wireless communication as performed by a network device, in accordance with some embodiments.
• a network device may determine DMRS configuration type and a count of DMRS ports.
• the DMRS configuration type may be DMRS configuration type 1 or DMRS configuration type 2.
• the count of DMRS ports may correspond with antenna ports of the network device.
• the DMRS ports, or the antenna ports referenced herein, may also be referenced as PDSCH antenna ports for the reason that the DMRS ports or the antenna ports information is transmitted to a UE in DCI to schedule PDSCH, and to transmit the DMRS with the PDSCH.
• the network device may identify a count of DMRS CDM groups without data. As described herein, in accordance with various embodiments, different patterns of one or more DMRS ports may be selected by a network device. Accordingly, at 206, in accordance with the determined count of DMRS CDM groups without data, the DMRS configuration type, and the count of DMRS ports, the network device may determine a count of scaled-up DMRS ports and a respective value of each scaled -up DMRS port of a pattern of DMRS ports.
• the network device may transmit, to the UE, a PDCCH including DCI, which DCI indicates scaled- up DMRS ports according to the count of scaled-up DMRS ports determined at 206, and the respective value of each scaled-up DMRS port determined at 206.
• the network device may transmit, to the UE, PDSCH scheduled by the DCI along with transmission of DMRS on the indicated scaled-up DMRS ports.
• the DMRS may include a maximum of 1 symbol, and the DMRS configuration type may be DMRS configuration type 1.
• the DCI may also include unsealed DMRS ports in addition to the scaled-up DMRS ports, as described herein, to facilitate MU-MIMO scheduling.
• FIG. 3 shows another example method of wireless communication as performed by a network device, in accordance with some embodiments.
• a network device may determine DMRS configuration type and a count of DMRS ports.
• the DMRS configuration type may be DMRS configuration type 1 or DMRS configuration type 2.
• the count of DMRS ports may correspond with antenna ports of the network device.
• the network device may identify a count of DMRS CDM groups without data. As described herein, in accordance with various embodiments, different patterns of one or more DMRS ports may be selected by a network device.
• the network device may determine a total count of DMRS ports.
• the total count of DMRS ports may include a count of scaled-up DMRS ports and a count of unsealed DMRS ports. Further, a respective value of each DMRS port may also be determined.
• the network device may transmit, to the UE, a PDCCH including DCI, which DCI indicates a respective value for each DMRS port of the DMRS ports determined at 306.
• the network device may transmit, to the UE, PDSCH scheduled by the DCI along with transmission of DMRS on the indicated DMRS ports.
• the DMRS may include a maximum of 2 symbols, and the DMRS configuration type may be DMRS configuration type 1.
• the count of unsealed DMRS ports may be determined to be 0, and hence the DMRS ports specified in the DCI may include one or more scaled-up DMRS ports only.
• the count of an unsealed DMRS port may be at least 1
• the count of a scaled-up DMRS port may be at least 1
• the total count of DMRS may not be greater than 4.
• FIG. 4 shows an example method of wireless communication as performed by a UE, in accordance with some embodiments.
• a UE may receive from a network device, downlink control information (DCI) including a pattern of DMRS ports, which indicates a particular count of scaled-up DMRS ports and a particular count of unsealed DMRS ports.
• the DCI may be received in PDCCH.
• the pattern of DMRS ports identifies a respective value of each DMRS port of DMRS ports.
• the UE may receive a DMRS on the DMRS ports as specified in the DCI received at 402.
• the DMRS may be received in PDSCH transmission.
• Embodiments contemplated herein include an apparatus having means to perform one or more elements of the method 200, 300, or 400.
• the apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE, as described herein).
• the apparatus may be, for example, an apparatus of a network device (such as a network device 620 that is a network access point or a base station, as described herein).
• Embodiments contemplated herein include one or more non-transitory computer- readable media storing instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 200, 300, or 400.
• the non-transitory computer- readable media may be, for example, a memory of a UE (such as a memory 606 of a wireless device 602 that is a UE, as described herein).
• the non- transitory computer-readable media may be, for example, a memory of a network device (such as a memory 624 of a network device 620 that is a network access point or a base station, as described herein).
• Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the method 200, 300, or 400.
• the apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE, as described herein).
• the apparatus may be, for example, an apparatus of a network device (such as a network device 620 that is a network access point or a base station, as described herein).
• Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 200, 300, or 400.
• the apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE, as described herein).
• the apparatus may be, for example, an apparatus of a network device (such as a network device 620 that is a network access point or a base station, as described herein).
• Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the method 200, 300, or 400.
• the processor may be a processor of a UE (such as a processor(s) 604 of a wireless device 602 that is a UE, as described herein), and the instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 606 of a wireless device 602 that is a UE, as described herein).
• the processor may be a processor of a network device (such as a processor(s) 622 of a network device 620 that is a network access point or a base station, as described herein), and the instructions may be, for example, located in the processor and/or on a memory of the network device (such as a memory 624 of a network device 620 that is a network access point or a base station, as described herein).
• FIG. 5 illustrates an example architecture of a wireless communication system 500, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 500 that operates in conjunction with the LTE system standards and/or 5G or NR system standards as provided by 3GPP technical specifications.
• the wireless communication system 500 includes UE 502 and UE 504 (although any number of UEs may be used).
• the UE 502 and the UE 504 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.
• the UE 502 and UE 504 may be configured to communicatively couple with a RAN 506.
• the RAN 506 may be NG-RAN, E-UTRAN, etc.
• the UE 502 and UE 504 utilize connections (or channels) (shown as connection 508 and connection 510, respectively) with the RAN 506, each of which comprises a physical communications interface.
• the RAN 506 can include one or more base stations, such as base station 512 and base station 514, that enable the connection 508 and connection 510.
• the RAN 506 may include one or more relays.
• connection 508 and connection 510 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 506, such as, for example, an LTE and/or NR.
• the UE 502 and UE 504 may also directly exchange communication data via a sidelink interface 516.
• the UE 504 is shown to be configured to access an access point (shown as AP 518) via connection 520.
• the connection 520 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 518 may comprise a Wi-Fi® router.
• the AP 518 may be connected to another network (for example, the Internet) without going through a CN 524.
• the UE 502 and UE 504 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 512 and/or the base station 514 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
• OFDM signals can comprise a plurality of orthogonal subcarriers.
• the base station 512 or base station 514 may be implemented as one or more software entities running on server computers as part of a virtual network.
• the base station 512 or base station 514 may be configured to communicate with one another via interface 522.
• the 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 and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC.
• the interface 522 may be an Xn interface.
• the Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 512 (e.g., a gNB) connecting to 5GC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN 524).
• the RAN 506 is shown to be communicatively coupled to the CN 524.
• the CN 524 may comprise one or more network elements 526, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 502 and UE 504) who are connected to the CN 524 via the RAN 506.
• the components of the CN 524 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non- transitory machine-readable storage medium).
• the CN 524 may be an EPC, and the RAN 506 may be connected with the CN 524 via an S I interface 528.
• the SI interface 528 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 512 or base station 514 and a serving gateway (S-GW), and the Sl-MME interface, which is a signaling interface between the base station 512 or base station 514 and mobility management entities (MMEs).
• SI-U SI user plane
• S-GW serving gateway
• MMEs mobility management entities
• the CN 524 may be a 5GC, and the RAN 506 may be connected with the CN 524 via an NG interface 528.
• the NG interface 528 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 512 or base station 514 and a user plane function (UPF), and the SI control plane (NG-C) interface, which is a signaling interface between the base station 512 or base station 514 and access and mobility management functions (AMFs).
• NG-U NG user plane
• UPF user plane function
• SI control plane NG-C interface
• an application server 530 may be an element offering applications that use internet protocol (TP) bearer resources with the CN 524 (e.g., packet switched data services).
• TP internet protocol
• the application server 530 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 502 and UE 504 via the CN 524.
• the application server 530 may communicate with the CN 524 through an IP communications interface 532.
• FIG. 6 illustrates a system 600 for performing signaling 638 between a wireless device 602 and a network device 620, according to embodiments disclosed herein.
• the system 600 may be a portion of a wireless communication system as herein described.
• 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., an eNB or a gNB), or a relay of a wireless communication system.
• the wireless device 602 may include one or more processor(s) 604.
• the processor(s) 604 may execute instructions such that various operations of the wireless device 602 are performed, as described herein.
• the processor(s) 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.
• CPU central processing unit
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• the wireless device 602 may include a memory 606.
• the memory 606 may be a non- transitory computer-readable storage medium that stores instructions 608 (which may include, for example, the instructions being executed by the processor(s) 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, and results computed by, the processor(s) 604.
• the wireless device 602 may include one or more transceiver(s) 610 that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna(s) 612 of the wireless device 602 to facilitate signaling (e.g., the signaling 640) to and/or from the wireless device 602 with other devices (e.g., the network device 620) according to corresponding RATs.
• RF radio frequency
• the wireless device 602 may include one or more antenna(s) 612 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 612, the wireless device 602 may leverage the spatial diversity of such multiple antenna(s) 612 to send and/or receive multiple different data streams on the same time and 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 a transmitting device and a receiving device that enable this aspect).
• MIMO multiple input multiple output
• MIMO transmissions by the wireless device 602 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 602 that multiplexes the data streams across the antenna(s) 612 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that 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 multiuser MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).
• SU-MIMO single user MIMO
• MU-MIMO multiuser MIMO
• the wireless device 602 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 612 are relatively adjusted such that the (joint) transmission of the antenna(s) 612 can be directed (this is sometimes referred to as beam steering).
• the wireless device 602 may include one or more interface(s) 614.
• the interface(s) 614 may be used to provide input to or output from the wireless device 602.
• a wireless device 602 that is a UE may include interface(s) 614 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE.
• Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 610/antenna(s) 612 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).
• known protocols e.g., Wi-Fi®, Bluetooth®, and the like.
• the wireless device 602 may include one or more DMRS enhancement module(s) 616.
• the DMRS enhancement module(s) 616 may be implemented via hardware, software, or combinations thereof.
• the DMRS enhancement module(s) 616 may be implemented as a processor, circuit, and/or instructions 608 stored in the memory 606 and executed by the processor(s) 604.
• the DMRS enhancement module(s) 616 may be integrated within the processor(s) 604 and/or the transceiver(s) 610.
• the DMRS enhancement module(s) 616 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 604 or the transceiver(s) 610.
• the DMRS enhancement module(s) 616 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-4, from a UE perspective.
• the network device 620 may include one or more processor(s) 622.
• the processor(s) 622 may execute instructions such that various operations of the network device 620 are performed, as described herein.
• the processor(s) 604 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASTC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
• the network device 620 may include a memory 624.
• the memory 624 may be a non- transitory computer-readable storage medium that stores instructions 626 (which may include, for example, the instructions being executed by the processor(s) 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, and results computed by, the processor(s) 622.
• the network device 620 may include one or more transceiver(s) 628 that may include RF transmitter and/or receiver circuitry that use the antenna(s) 630 of the network device 620 to facilitate signaling (e.g., the signaling 638) to and/or from the network device 620 with other devices (e.g., the wireless device 602) according to corresponding RATs.
• transceiver(s) 628 may include RF transmitter and/or receiver circuitry that use the antenna(s) 630 of the network device 620 to facilitate signaling (e.g., the signaling 638) to and/or from the network device 620 with other devices (e.g., the wireless device 602) according to corresponding RATs.
• the network device 620 may include one or more antenna(s) 630 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 630, the network device 620 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
• the network device 620 may include one or more interface(s) 632.
• the interface(s) 632 may be used to provide input to or output from the network device 620.
• a network device 620 that is a base station may include interface(s) 632 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 628/antenna(s) 630 already described) that enables the base station to communicate with other equipment in a core network, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operation, administration, and maintenance of the base station or other equipment operably connected thereto.
• circuitry e.g., other than the transceiver(s) 628/antenna(s) 630 already described
• the network device 620 may include one or more DMRS enhancement module(s) 634.
• the DMRS enhancement module(s)) 634 may be implemented via hardware, software, or combinations thereof.
• the DMRS enhancement module(s) 634 may be implemented as a processor, circuit, and/or instructions 626 stored in the memory 624 and executed by the processor(s) 622.
• the DMRS enhancement module(s) 634 may be integrated within the processor(s) 622 and/or the transceiver(s) 628.
• the DMRS enhancement module(s) 634 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 622 or the transceiver(s) 628. [0070] The DMRS enhancement module(s) 634 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1 -4, from a network device perspective.
• At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein.
• a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
• circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
• Embodiments and 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.
• a 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 for performing the operations or may include a combination of hardware, software, and/or firmware.
• personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
• personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

• Engineering & Computer Science (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=90123499

Family Applications (1)

Country Status (4)

• 2024
  • 2024-01-23 EP EP24708921.2A patent/EP4649599A1/de active Pending
  • 2024-01-23 JP JP2025546225A patent/JP2026509127A/ja active Pending
  • 2024-01-23 WO PCT/US2024/012575 patent/WO2024173000A1/en not_active Ceased
  • 2024-01-23 CN CN202480012002.4A patent/CN120677647A/zh active Pending

Also Published As

Similar Documents

Legal Events