Enhanced Demodulation Reference Signal (DMRS) for Uplink Transmission

Abstract

Systems, apparatus, methods, and computer-readable media are provided for enhanced demodulation reference signals (DMRS) for uplink transmissions (e.g., uplink single-user (SU) multiple-input multiple-output (MIMO) transmissions) using up to eight layers. Additionally, embodiments relate to antenna port indication for DMRS transmissions. Other embodiments may be described and claimed.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to International Patent Application No. PCT / CN2022 / 080877, filed March 15, 2022, and International Patent Application No. PCT / CN2022 / 090356, filed April 29, 2022.

[0002] Field Various embodiments may relate generally to the field of wireless communications, For example, some embodiments may relate to an enhanced demodulation reference signal (DMRS) for uplink transmissions (e.g., using up to eight layers) and / or antenna port indication for the DMRS. [Background technology]

[0003] The New Radio (NR) Release (Rel)-15 / Rel-16 specifications define two types of demodulation reference signals (DMRSs) for physical uplink shared channel (PUSCH) transmissions: Type 1 and Type 2. For cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveforms, the DMRS sequences are based on Gold sequences. For discrete Fourier transform (DFT)-spread (s)-OFDM waveforms, the DMRS sequences are based on Zadoff-Chu (ZC) sequences.

[0004] Type-1 DMRS is based on the Comb-2 structure. For one particular port, the DMRS occupies six resource elements (REs) in one physical resource block (PRB), and the six REs are distributed in the PRB. For one-symbol DMRS, an orthogonal cover code (OCC) of length 2 may be applied in the frequency domain. Thus, for one-symbol Type-1 DMRS, four orthogonal ports may be generated. For two-symbol DMRS, OCC may also be applied in the time domain, and thus, for two-symbol Type-1 DMRS, eight orthogonal ports may be generated.

[0005] For Type-2 DMRS, the DMRS for one specific port occupies four REs in one PRB, and the four REs are divided into two pairs of two consecutive REs, and the two pairs of REs are distributed in the PRB. For 1-symbol DMRS, OCC of length 2 may be applied in the frequency domain. Thus, for 1-symbol Type-2 DMRS, six orthogonal ports may be generated. For 2-symbol DMRS, OCC may also be applied in the time domain, and thus, for 2-symbol Type-2 DMRS, twelve orthogonal ports may be generated. [Brief description of the drawings]

[0006] [Figure 1] A one-symbol demodulation reference signal (DMRS) and a two-symbol DMRS for type 1 DMRS are shown. [Diagram 2] 1-symbol DMRS and 2-symbol DMRS for Type 2 DMRS are shown. [Diagram 3] 1 illustrates an example of a Type 1 DMRS in accordance with various embodiments. [Figure 4] 1 illustrates an example of a Type 2 DMRS in accordance with various embodiments. [Diagram 5] 1 illustrates an example of a new DMRS type according to various embodiments. [Figure 6]1 illustrates an example of antenna port mapping for single-symbol Type-1 DMRS (Rank-1) in accordance with various embodiments. [Figure 7] 1 illustrates an example of antenna port mapping for single-symbol Type-1 DMRS (Rank-2) in accordance with various embodiments. [Figure 8] 1 illustrates an example of antenna port mapping for single-symbol Type-1 DMRS (Rank-3) in accordance with various embodiments. [Figure 9] 1 illustrates an example of antenna port mapping for single-symbol Type-1 DMRS (Rank-4) in accordance with various embodiments. [Figure 10] 1 illustrates a network in accordance with various embodiments. [Figure 11] 1 illustrates a schematic diagram of a wireless network according to various embodiments; [Figure 12] FIG. 1 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods described herein, according to some example embodiments. [Figure 13] 1 illustrates an exemplary procedure for carrying out various embodiments of the present disclosure. [Figure 14] 1 illustrates an exemplary procedure for carrying out various embodiments of the present disclosure. [Figure 15] 1 illustrates an exemplary procedure for carrying out various embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be implemented in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this specification, the phrase "A or B" means (A), (B), or (A and B).

[0008] As mentioned above, Type 1 and Type 2 DMRS were defined for PUSCH transmission in 3GPP Rel-15 / Rel-16. Figure 1 shows 1-symbol DMRS and 2-symbol DMRS for Type 1 DMRS. Figure 2 shows 1-symbol DMRS and 2-symbol DMRS for Type 2 DMRS.

[0009] In 3GPP Rel-18, up to 8 layers of uplink transmission are supported for SU-MIMO. It can be seen that for some existing DMRS configurations, the number of orthogonal ports is less than 8. Therefore, an enhancement is required for DMRS to support up to 8 layers of uplink transmission for Single User (SU)-Multiple Input Multiple Output (MIMO) transmission.

[0010] Various embodiments herein provide techniques for a DMRS to support up to eight layer uplink transmissions (e.g., SU-MIMO transmissions). Additionally, embodiments provide techniques for antenna port indication for the DMRS.

[0011] Enhanced DMRS for CP-OFDM In an embodiment, for a CP-OFDM waveform, a larger comb size, e.g., Comb-4 and / or Comb-8, may be introduced for Type-1 DMRS to support uplink SU-MIMO transmission with up to eight layers.

[0012] In another example, for a Type-1 DMRS, when the PUSCH transmission is more than four layers, only a two-symbol DMRS (with Comb-2) may be configured.

[0013] In another embodiment, for a CP-OFDM waveform and Type-1 DMRS, the DMRS is still based on the Comb-2 structure. The sequence is generated according to a sequence length based on Comb-2. Over one comb offset, the DMRS sequence is further applied with OCC to generate two ports. Or, over one comb offset, the DMRS sequence is further split into two parts without OCC, one part corresponding to one port. In this way, the new DMRS sequence can be multiplexed with legacy UEs.

[0014] Figure 3 shows an example. i ' and port p i+4 The DMRS sequence of port p i The sequence is based on, but with different OCCs (i=0,1,2,3).

[0015] Alternatively, port p i The DMRS sequence of is split into two parts without any additional OCC, and one part is sent to port p i ' and another part corresponds to port p i+4 For example, ports p on ports RE #0, #2, #4, #6, #8, #10... 0 The sequence for RE #0, #4, #8, ... is divided into two parts. The sequence above is 0 ', and the sequence of RE #2, #6, #10, ... is port p 4' to build.

[0016] In another example, for a CP-OFDM waveform and a Type-1 DMRS, the DMRS is still based on a Comb-2 structure, with a length-4 OCC applied in the frequency domain to generate eight ports.

[0017] In another embodiment, for a Type 2 DMRS, when the PUSCH transmission is more than 6 layers, only a 2-symbol DMRS may be configured.

[0018] In another embodiment, for a CP-OFDM waveform and Type-2 DMRS, the DMRS sequence length is still based on the legacy Type-2 DMRS structure. On one pair of REs, the DMRS sequence is further applied with an OCC to generate two ports. Or, on one pair of REs, the DMRS sequence is further split into two parts without an OCC, one part corresponding to one port. In this way, the new DMRS sequence can be multiplexed with legacy UEs.

[0019] Figure 4 shows an example. i ' and port p i+6 The DMRS sequence of port p i , but with different OCCs (i=0,1,…,5).

[0020] Alternatively, port p i The DMRS sequence of is split into two parts without any additional OCC, one part is sent to port p i ' and another part corresponds to port p i+6 For example, ports p on RE #0, #1, #6, #7, #12, #13, ... 0 The sequence for is divided into two parts. RE #0, #1, #12, #13, ... The above sequence is 0 ', RE #6, #7, #18, #19... the sequence above is port p 6 ' to build.

[0021] In another example, for a CP-OFDM waveform and a Type-1 DMRS, the DMRS is still based on the legacy Type-2 DMRS structure, with a length-4 OCC applied in the frequency domain to generate eight ports.

[0022] In another embodiment, a new type of DMRS can be defined to support uplink SU-MIMO transmission with up to 8 layers, e.g., as shown in Figure 5. The DMRS occupies 4 consecutive REs, and an OCC of length 4 can be applied in the frequency domain. Thus, with one symbol DMRS, 12 orthogonal symbols can be generated for SU-MIMO.

[0023] Enhanced DMRS for DFT-s-OFDM In an embodiment, for a DFT-s-OFDM waveform, an additional cyclic shift may be introduced to support uplink SU-MIMO transmission with up to 4 layers and / or up to 8 layers, which may be applied to both Type-1 DMRS (including 1-symbol DMRS and 2-symbol DMRS) and Type-2 DMRS (including 1-symbol DMRS and 2-symbol DMRS). The additional cyclic shift may be predefined or configured by higher layers.

[0024] For example, for DMRS type 1 with one symbol, DMRS ports 0 to 3 are cyclically shifted by α 0 DMRS ports 4 to 7 are mapped to the cyclic shift α 1 is mapped to.

[0025] In another example, the cyclic shift used for DMRS is α i =2π(n CS,i / n CS,max ), where n CS,max =6 and n CS,i ∈{0,1,…,5} is configured by RRC.

[0026] In an embodiment, for a DFT-s-OFDM waveform, a larger comb size, e.g., Comb-4 and / or Comb-8, may be introduced for Type-1 DMRS to support uplink SU-MIMO transmissions with up to eight layers.

[0027] In another embodiment, for a DFT-s-OFDM waveform, a new type of DMRS may be defined to support uplink SU-MIMO transmission with up to eight layers, as shown in FIG.

[0028] Antenna Port Indication for DMRS As mentioned above, in 3GPP Rel-15 / Rel-16, Type 1 and Type 2 DMRS were defined for PUSCH transmission. For Type 1 DMRS, four orthogonal ports may be generated for single symbol DMRS. For two symbol DMRS, eight orthogonal ports may be generated. For Type 2 DMRS, six orthogonal ports may be generated for single symbol DMRS. For two symbol DMRS, twelve orthogonal ports may be generated. In DCI scheduling PUSCH, e.g., DCI format 0_1 / 0_2, there is an antenna port field indicating the port(s) used for DMRS. Figures 6, 7, 8, and 9 show examples of antenna port field mapping with DMRS ports (rank-1 to rank-4).

[0029] In Rel-18, up to 8 layers of uplink transmission are supported for SU-MIMO. Correspondingly, 8-port DMRS is required. Therefore, the DCI fields of the antenna ports should be enhanced to support 8-port DMRS operation. The embodiments of the present disclosure address these and other issues by enhancing the DCI fields of the antenna ports for uplink transmission with 8Tx.

[0030] Enhanced Antenna Port Indication for DMRS with CP-OFDM In one embodiment, for a CP-OFDM waveform, a DMRS with eight ports is required to support 8Tx uplink transmissions, and correspondingly, the antenna port field in the DCI scheduling the PUSCH should be enhanced to support the 8-port DMRS.

[0031] An 8-port DMRS can be achieved by introducing more ports into one CDM group, e.g., two CDM groups, each containing four ports, or an 8-port DMRS can be achieved by introducing more CDM groups, e.g., four CDM groups, each containing two ports.

[0032] In the DCI scheduling the PUSCH, a mapping between the antenna port field code points and the indicated DMRS ports should be defined.

[0033] In one embodiment, a mapping between antenna port field code points and indicated DMRS ports should be defined for each rank value R, where R={1,2,3,...8}. The antenna port field length should be the same for each rank value, i.e., the field length is determined by the maximum bit width between each rank.

[0034] Tables 1 to 8 show examples of mapping between antenna port field code points and indicated DMRS ports for rank 1 to rank 8, where the DMRS is type 1 and single symbol. The number of CDM groups is 2, and the number of ports in one CDM group is 4.

[0035] In another example, to maintain backward compatibility, the 8 ports for a single symbol Type 1 DMRS may be numbered as #0 to #3 and #8 to #11. In such a case, DMRS port #X (X≧4) in Tables 1 to 8 should be replaced with #X+4.

[0036] [Table 1]

[0037] [Table 2]

[0038] [Table 3]

[0039] [Table 4]

[0040] [Table 5]

[0041] [Table 6]

[0042] [Table 7]

[0043] [Table 8]

[0044] In another embodiment, the mapping between the antenna port field code points and the indicated DMRS ports may be jointly coded for all rank values ​​R, where R={1, 2, 3, ... 8}.

[0045] Table 9 shows an example of mapping between antenna port field code points and indicated DMRS ports for rank 1 to rank 8, where the DMRS is type 1 and single symbol. The number of CDM groups is 2, and the number of ports in one CDM group is 4.

[0046] In another example, to maintain backward compatibility, the 8 ports for a single-symbol Type 1 DMRS may be numbered as #0 to #3 and #8 to #11. In such a case, DMRS port #X (X≧4) in Table 9 should be replaced with #X+4.

[0047] [Table 9]

[0048] In another embodiment, to reduce DCI overhead, for an 8-port DMRS, if rank value R≦4, then only the first four ports are used for the DMRS. If rank value R>4, then the first four ports and some remaining ports are used (e.g., ports #0-#3 and one or more of #4-#7 are used).

[0049] In another embodiment, the antenna port field length may depend on the value of maxRank or maxMIMO-Layers. The table of mapping between antenna port field code points and indicated DMRS ports should contain rank values ​​less than or equal to maxRank or maxMIMO-Layers.

[0050] In another embodiment, for uplink transmission with 8Tx, multiple codewords or multiple port groups can be used, e.g., two codewords / port groups are used, each codeword / port group corresponding to four DMRS ports.

[0051] In one example, when the rank value is greater than 4, both codewords / port groups are used. When the rank value is less than or equal to 4, either codeword / port group may be used.

[0052] In another example, when the rank value is greater than 4, both codewords / port groups are used. When the rank value is less than or equal to 4, only the first codeword / port group is used.

[0053] If two codeword / port groups are configured, the field length of the antenna port field shall be the same when only one codeword is enabled as when both codewords are enabled.

[0054] Table 10 shows an example of mapping between antenna port field code points and DMRS ports indicated for multiple codeword / port groups, where the DMRS is type 1 and single symbol. The number of CDM groups is 2, and the number of ports in a CDM group is 4. In another example, to maintain backward compatibility, the 8 ports for a single symbol Type 1 DMRS may be numbered as #0 to #3 and #8 to #11. In such a case, DMRS port #X (X≧4) in Table 10 should be replaced with #X+4. [Table 10]

[0055] In another embodiment, for uplink transmission with 8Tx, multiple codewords or multiple port groups can be used, e.g., two codewords / port groups are used, each codeword / port group corresponding to four DMRS ports.

[0056] Correspondingly, multiple antenna port fields, for example two antenna port fields, may be included in the DCI, with one antenna port field corresponding to one codeword / port group.

[0057] Improved Antenna Port Designation for DMRS with DFT-s-OFDM In one embodiment, for a DFT-s-OFDM waveform with rank-1 transmission, a DMRS with 8 ports is required to support 8Tx uplink transmissions. Correspondingly, the antenna port field in the DCI scheduling the PUSCH should be enhanced to support the 8-port DMRS.

[0058] Table 11 shows an example of mapping between antenna port field code points and indicated DMRS ports for rank 1 to rank 8, where the DMRS is type 1 and single symbol. The number of CDM groups is 2, and the number of ports in one CDM group is 4. In another example, to maintain backward compatibility, the 8 ports for a single symbol Type 1 DMRS may be numbered as #0 to #3 and #8 to #11. In such a case, DMRS port #X (X≧4) in Table 11 should be replaced with #X+4. [Table 11]

[0059] System and Implementation 10-12 illustrate various systems, devices and components that may implement aspects of the disclosed embodiments.

[0060] 10 illustrates a network 1000 according to various embodiments. The network 1000 may operate in a manner compliant with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this respect and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems.

[0061] The network 1000 may include a UE 1002, which may include any mobile or non-mobile computing device designed to communicate with the RAN 1004 over a wireless connection. The UE 1002 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0062] In some embodiments, the network 1000 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

[0063] In some embodiments, the UE 1002 may further communicate with the AP 1006 via a wireless connection. The AP 1006 may manage a WLAN connection, which may serve to offload some / all network traffic from the RAN 1004. The connection between the UE 1002 and the AP 1006 may be consistent with any IEEE 802.11 protocol, and the AP 1006 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 1002, RAN 1004, and AP 1006 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 1002 being configured by the RAN 1004 to utilize both cellular radio resources and WLAN resources.

[0064] The RAN 1004 may include one or more access nodes, e.g., the AN 1008. The AN 1008 may terminate air interface protocols for the UE 1002 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 1008 may enable data / voice connectivity between the CN 1020 and the UE 1002. In some embodiments, the AN 1008 may be implemented as one or more software entities running on a server computer, in a discrete device, or as part of a virtual network, e.g., which may be referred to as a CRAN or a virtual baseband unit pool. The AN 1008 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1008 may be a macrocell base station, or a low-power base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0065] In embodiments where the RAN 1004 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 1004 is an LTE RAN) or an Xn interface (if the RAN 1004 is a 5G RAN). The X2 / Xn interface, which in some embodiments may be separated into a control / user plane interface, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0066] Each of the ANs of the RAN 1004 may manage one or more cells, cell groups, component carriers, etc., to provide the UE 1002 with an air interface for network access. The UE 1002 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 1004. For example, the UE 1002 and the RAN 1004 may use carrier aggregation that allows the UE 1002 to connect with multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0067] The RAN 1004 may provide an air interface through a licensed or unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on Carrier Aggregation (CA) techniques using PCell / SCell. Prior to accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a listen-before-talk (LBT) protocol.

[0068] In a V2X scenario, the UE 1002 or AN 1008 may be or act as an RSU, which may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by an appropriate AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU", in the case of an eNB it may be referred to as an "eNB-type RSU", in the case of a gNB it may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled to a radio frequency circuit located at the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications necessary for high speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0069] In some embodiments, the RAN 1004 may be an LTE RAN 1010 having an eNB, e.g., an eNB 1012. The LTE RAN 1010 may provide an LTE air interface with the following characteristics: 15 kHz SCS; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI collection and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search and initial collection, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0070] In some embodiments, the RAN 1004 may be an NG-RAN 1014 having a gNB, e.g., gNB 1016, or an ng-eNB, e.g., ng-eNB 1018. The gNB 1016 may connect to a 5G-capable UE using a 5G NR interface. The gNB 1016 may connect to a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1018 may also connect to a 5G core through an NG interface, but may also connect to a UE through an LTE air interface. The gNB 1016 and the ng-eNB 1018 may connect to each other through an Xn interface.

[0071] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface, which carries traffic data between nodes of the NG-RAN 1014 and the UPF 1048 (e.g., the N3 interface), and an NG Control Plane (NG-C) interface, which is a signaling interface between nodes of the NG-RAN 1014 and the AMF 1044 (e.g., the N2 interface).

[0072] The NG-RAN 1014 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarity, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0073] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs may be used for dynamic adaptation of the SCS. For example, the UE 1002 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 1002, the SCS of the transmission is also changed. Another example use case of BWPs relates to power conservation. In particular, multiple BWPs may be configured for the UE 1002 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP that includes a smaller number of PRBs may be used for data transmissions with a small traffic load while enabling power savings at the UE 1002 and possibly at the gNB 1016. A BWP that includes a larger number of PRBs may be used for scenarios with a higher traffic load.

[0074] The RAN 1004 is communicatively coupled to the CN 1020, which includes network elements for providing various functions to customers / subscribers (e.g., users of UEs 1002) for supporting data and telecommunication services. The components of the CN 1020 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1020 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 1020 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1020 may be referred to as a network sub-slice.

[0075] In some embodiments, the CN 1020 may be an LTE CN 1022, sometimes referred to as an EPC. The LTE CN 1022 may include an MME 1024, an SGW 1026, an SGSN 1028, an HSS 1030, a PGW 1032, and a PCRF 1034 coupled together through interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 1022 may be briefly introduced as follows.

[0076] The MME 1024 may implement mobility management functionality to track the current location of the UE 1002 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0077] The SGW 1026 terminates the S1 interface towards the RAN and can route data packets between the RAN and the LTE CN 1022. The SGW 1026 may be a local mobility anchor point for inter-RAN node handover and may provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and some policy enforcement.

[0078] The SGSN 1028 may track the location of the UE 1002 and perform security functions and access control. Additionally, the SGSN 1028 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 1024; MME selection for handover, etc. The S3 reference point between the MME 1024 and the SGSN 1028 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states.

[0079] The HSS 1030 may include a database for network users, including subscription-related information to support processing of communication sessions by network entities. The HSS 1030 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 1030 and the MME 1024 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 1020.

[0080] The PGW 1032 may terminate an SGi interface towards a data network (DN) 1036, which may include an application / content server 1038. The PGW 1032 may route data packets between the LTE CN 1022 and the data network 1036. The PGW 1032 may be coupled to the SGW 1026 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1032 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 1032 and the data network 1036 may be an operator external public, private PDN, or an intra-operator packet data network, e.g., for the provision of IMS services. The PGW 1032 may be coupled to the PCRF 1034 via a Gx reference point.

[0081] The PCRF 1034 is the policy and charging control element of the LTE CN 1022. The PCRF 1034 may be communicatively coupled to an app / content server 1038 to determine appropriate QoS and charging parameters for a service flow. The PCRF 1032 may provision the PCEF (via the Gx reference point) with the appropriate TFT and associated rules with the QCI.

[0082] In some embodiments, the CN 1020 may be a 5GC 1040. The 5GC 1040 may include an AUSF 1042, an AMF 1044, an SMF 1046, a UPF 1048, an NSSF 1050, an NEF 1052, an NRF 1054, a PCF 1056, a UDM 1058, and an AF 1060 coupled together through interfaces (or "reference points") as shown. The functionality of the elements of the 5GC 1040 may be briefly introduced as follows.

[0083] The AUSF 1042 may store data and handle authentication related functions for authentication of the UE 1002. The AUSF 1042 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 1040 through reference points as shown, the AUSF 1042 may present a Nausf service-based interface.

[0084] The AMF 1044 may allow other functions of the 5GC 1040 to communicate with the UE 1002 and the RAN 1004 and subscribe to notifications about mobility events regarding the UE 1002. The AMF 1044 may be responsible for registration management (e.g., for registering the UE 1002), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. The AMF 1044 may provide transport for SM messages between the UE 1002 and the SMF 1046 and act as a transparent proxy for routing SM messages. The AMF 1044 may also provide transport for SMS messages between the UE 1002 and the SMSF. The AMF 1044 may interact with the AUSF 1042 and the UE 1002 to perform various security anchor and context management functions. Additionally, the AMF 1044 may be a termination point of the RAN CP interface, which may include or be an N2 reference point between the RAN 1004 and the AMF 1044, and the AMF 1044 may be a termination point of NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 1044 may also support NAS signaling with the UE 1002 over an N3 IWF interface.

[0085] The SMF 1046 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 1048 and the AN 1008); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in the UPF 1048 to route traffic to the appropriate destination; termination of the interface to the policy control function; control of policy enforcement, charging, and parts of QoS; lawful interception (for SM events and the interface to the L1 system); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information sent over N2 to the AN 1008 via the AMF 1044; and determination of the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 1002 and the data network 1036.

[0086] The UPF 1048 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnection to the data network 1036, and a branch point to support multi-homed PDU sessions. The UPF 1048 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), transport transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1048 may include an uplink classifier to support routing of traffic flows to the data network.

[0087] The NSSF 1050 may select a set of network slice instances to serve the UE 1002. The NSSF 1050 may also determine the allowable NSSAIs and mapping to the subscribed S-NSSAIs, if necessary. The NSSF 1050 may also determine an AMF set, or a list of candidate AMFs, to be used to serve the UE 1002 based on a preferred configuration and possibly by querying the NRF 1054. The selection of a set of network slice instances for the UE 1002 may be triggered by the AMF 1044 to which the UE 1002 is registered, by interacting with the NSSF 1050, which may result in a change of AMF. The NSSF 1050 may interact with the AMF 1044 via the N22 reference point and may communicate with another NSSF in a visited network via the N31 reference point (not shown). In addition, the NSSF 1050 may exhibit an Nnssf service-based interface.

[0088] The NEF 1052 can securely expose services and capabilities offered by 3GPP network functions for third parties, internal publication / re-publication, AFs (e.g., AF 1060), edge computing or fog computing systems, etc. In such an embodiment, the NEF 1052 can authenticate, authorize, or throttle the AF. The NEF 1052 can also translate information exchanged with the AF 1060 and with internal network functions. For example, the NEF 1052 can translate between AF service identifiers and internal 5GC information. The NEF 1052 can also receive information from other NFs based on the published capabilities of the other NFs. This information may be stored in the NEF 1052 as structured data or in a data storage NF using a standardized interface. The stored information may then be re-published by the NEF 1052 to other NFs and AFs, or used for other purposes, such as analytics. Additionally, the NEF 1052 can exhibit Nnef service-based interfaces.

[0089] The NRF 1054 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to the NF instances. The NRF 1054 also maintains information of available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and an "instance" may refer to a concrete occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 1054 may expose an Nnrf service-based interface.

[0090] The PCF 1056 may provide policy rules to control plane functions that enforce them and may support a unified policy framework to govern network behavior. The PCF 1056 may also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 1058. In addition to communicating with functions through reference points as shown, the PCF 1056 also exhibits an NPCF service-based interface.

[0091] The UDM 1058 may process subscription related information to support network entity processing of communication sessions and may store subscription data for the UE 1002. For example, the subscription data may be communicated via an N8 reference point between the UDM 1058 and the AMF 1044. The UDM 1058 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1058 and the PCF 1056, and / or structured data for publishing and application data for the NEF 1052 (including PFD for application discovery, application request information for multiple UEs 1002). A Nudr service-based interface may be presented by the UDR 1021 to allow the UDM 1058, PCF 1056, and NEF 1052 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE responsible for credential handling, location management, subscription management, etc. Several different front-ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential handling, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 1058 may present a Nudr service-based interface.

[0092] The AF 1060 provides application influence over traffic routing, provides access to the NEF, and can interact with the policy framework for policy control.

[0093] In some embodiments, the 5GC 1040 may enable edge computing by selecting an operator / third party service to be geographically close to the point where the UE 1002 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementation, the 5GC 1040 may select a UPF 1048 close to the UE 1002 and perform traffic steering from the UPF 1048 to the data network 1036 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 1060. In this way, the AF 1060 may influence the UPF (re)selection and traffic routing. Based on the operator deployment, when the AF 1060 is considered to be a trusted entity, the network operator may allow the AF 1060 to directly interact with associated NFs. In addition, the AF 1060 may exhibit a Naf service-based interface.

[0094] Data network 1036 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers, including, for example, application / content server 1038 .

[0095] 11 illustrates a schematic of a wireless network 1100 in accordance with various embodiments. The wireless network 1100 may include a UE 1102 in wireless communication with an AN 1104. The UE 1102 and the AN 1104 may be similar to and substantially interchangeable with similarly named components described elsewhere herein.

[0096] The UE 1102 may be communicatively coupled to the AN 1104 via a connection 1106. The connection 1106 is shown as an air interface for enabling the communicative coupling and may be consistent with a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mm-wave or sub-6 GHz frequencies.

[0097] The UE 1102 may include a host platform 1108 coupled to a modem platform 1110. The host platform 1108 may include an application processing circuit 1112 that may be coupled to a protocol processing circuit 1114 of the modem platform 1110. The application processing circuit 1112 may execute various applications for the UE 1102 to source / sink application data. The application processing circuit 1112 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0098] The protocol processing circuit 1114 may implement one or more of the layer operations to facilitate transmission or reception of data over the connection 1106. The layer operations implemented by the protocol processing circuit 1114 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0099] The modem platform 1110 may further include digital baseband circuitry 1116 that may implement one or more layer operations that are "lower" layer operations in a network protocol stack performed by the protocol processing circuitry 1114. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port pre-coding / decoding that may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0100] The modem platform 1110 may further include transmit circuitry 1118, receive circuitry 1120, RF circuitry 1122, and an RF front end (RFFE) 1124, which may include or be connected to one or more antenna panels 1126. Briefly, the transmit circuitry 1118 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 1120 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 1122 may include low noise amplifiers, power amplifiers, power tracking components, etc.; the RFFE 1124 may include filters (e.g., surface / volume acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the transmit circuitry 1118, receive circuitry 1120, RF circuitry 1122, RFFE 1124, and antenna panel 1126 components (collectively referred to as "transmit and receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are at TDM or FDM, mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit and receive components may be arranged in multiple parallel transmit and receive chains, may be located on the same or different chips / modules, etc.

[0101] In some embodiments, the protocol processing circuit 1114 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting and receiving components.

[0102] UE reception may be established by and through the antenna panel 1126, the RFFE 1124, the RF circuitry 1122, the receive circuitry 1120, the digital baseband circuitry 1116, and the protocol processing circuitry 1114. In some embodiments, the antenna panel 1126 may receive transmissions from the AN 1104 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 1126.

[0103] UE transmissions may be established by and through the protocol processing circuitry 1114, the digital baseband circuitry 1116, the transmit circuitry 1118, the RF circuitry 1122, the RFFE 1124, and the antenna panel 1126. In some embodiments, the transmit components of the UE 1104 may apply spatial filters to data to be transmitted to form transmit beams emitted by antenna elements of the antenna panel 1126.

[0104] Similar to the UE 1102, the AN 1104 may include a host platform 1128 coupled to a modem platform 1130. The host platform 1128 may include an application processing circuit 1132 coupled to a protocol processing circuit 1134 of the modem platform 1130. The modem platform may further include a digital baseband circuit 1136, a transmit circuit 1138, a receive circuit 1140, an RF circuit 1142, an RFFE circuit 1144, and an antenna panel 1146. The components of the AN 1104 may be similar to and substantially interchangeable with similarly named components of the UE 1102. In addition to performing data transmission / reception as described above, the components of the AN 1108 may perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0105] 12 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods described herein, according to some example embodiments. Specifically, FIG. 12 illustrates a schematic diagram of hardware resources including one or more processors (or processor cores) 1210, one or more memory / storage devices 1220, and one or more communication resources 1230, each of which may be communicatively coupled via a bus 1240 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1202 may be executed to provide an execution environment in which one or more network slices / sub-slices utilize the hardware resources 1200.

[0106] Processor 1210 may include, for example, processor 1212 and processor 1214. Processor 1210 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0107] The memory / storage devices 1220 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 1220 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0108] Communications resources 1230 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1204 or one or more databases 1206 or other network elements over network 1208. For example, communications resources 1230 may include a wired communications component (e.g., for coupling via USB, Ethernet, etc.), a cellular communications component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communications components.

[0109] The instructions 1250 may include software, programs, applications, applets, apps, or other executable code for causing the processor 1210 to perform any one or more of the methods described herein. The instructions 1250 may reside completely or partially within at least one of the processor 1210 (e.g., in a cache memory of the processor), the memory / storage device 1220, or any suitable combination thereof. Furthermore, any portion of the instructions 1250 may be transferred to hardware resources from any combination of the peripheral device 1204 or the database 1206. Thus, the memory of the processor 1210, the memory / storage device 1220, the peripheral device 1204, and the database 1206 are examples of computer-readable and machine-readable media.

[0110] Exemplary Procedure In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s) of FIG. 10-FIG. 12 or some other figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. One such process 1300 is shown in FIG. 13. In some embodiments, the process 1300 may be performed by a UE or a portion thereof. At 1302, the process 1300 may include receiving downlink control information (DCI) from a next generation Node B (gNB) for scheduling a physical uplink shared channel (PUSCH), where the DCI includes an antenna port field for indicating a transmission port for a demodulation reference signal (DMRS) with up to eight transmission ports. At 1304, the process 1300 may further include encoding the DMRS for transmission using the PUSCH based on the antenna port field.

[0111] FIG. 14 illustrates another example process 1400 according to various embodiments. In some embodiments, the process 1400 may be performed by a gNB or a portion thereof. At 1402, the process 1400 may include encoding downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for transmission to a user equipment (UE), where the DCI includes an antenna port field for indicating a transmission port for a demodulation reference signal (DMRS) with up to eight transmission ports. At 1404, the process 1400 may further include receiving a PUSCH with the DMRS based on the DCI.

[0112] FIG. 15 illustrates another process 1500 according to various embodiments. In some embodiments, the process 1500 may be performed by a UE or a portion thereof. At 1502, the process 1500 may include generating a demodulation reference signal (DMRS) having a comb-2 structure for a physical uplink shared channel (PUSCH). At 1504, the process 1500 may further include applying an orthogonal cover code (OCC) having length 4 to the DMRS to generate eight DMRS ports. At 1506, the process 1500 may further include transmitting the PUSCH and the DMRS based on the eight DMRS ports.

[0113] For one or more embodiments, at least one of the components depicted in one or more of the preceding figures may be configured to perform one or more of the operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, the circuitry associated with the UE, base station, network element, etc. described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the Examples section. EXAMPLES

[0114] Working Example Example A1 may include a method of a gNB, in which the gNB configures a UE with a DMRS for uplink transmission.

[0115] Example A2 may include the method of example A1 or any other example herein, where for a CP-OFDM waveform, for a Type-1 DMRS, a larger comb size, e.g., Comb-4 and / or Comb-8, may be introduced to support uplink SU-MIMO transmission with up to 8 layers, or for a Type-1 DMRS, only a 2-symbol DMRS (with Comb-2) may be configured when the PUSCH transmission is more than 4 layers.

[0116] Example A3 may include the method of example A1 or any other example herein, and for a CP-OFDM waveform and a Type 1 DMRS, the DMRS is still based on a Comb-2 structure. A sequence is generated according to a sequence length based on Comb-2. Over one comb offset, the DMRS sequence is further applied with OCC to generate two ports. Port p i ' and port p i+4 The DMRS sequence of port p i Alternatively, over one comb offset, the DMRS sequence is further split into two parts without an OCC, one part is assigned to port p i ' and another part corresponds to port p i+4 ' (i=0,1,2,3). For example, ports p on RE #0, #2, #4, #6, #8, #10, ... 0 The sequence for RE #0, #4, #8, ... is divided into two parts. The sequence for RE #0, #4, #8, ... is 0 ', and the sequence of RE #2, #6, #10, ... is port p 4 ' to build. Example A4 may include the method of example A1 or any other example herein, and for a type-2 DMRS, when the PUSCH transmission is more than 6 layers, only a 2-symbol DMRS may be configured.

[0117] Example A5 may include the method of Example A1 or any other example herein, where for a CP-OFDM waveform and a Type-2 DMRS, the DMRS sequence length is still based on the legacy Type-2 DMRS structure. Over a pair of REs, the DMRS sequence is further applied with OCC to generate two ports. Port p i ' and port p i+6 The DMRS sequence of port p i , but with different OCCs (i=0,1,...,5). Alternatively, across the pair of REs, the DMRS sequence is further split into two parts without OCC, one part corresponding to one port. i The DMRS sequence of is split into two parts, one of which is assigned to port p i ', and the other part corresponds to port p i+6 For example, ports p on RE #0, #1, #6, #7, #12, #13, ... 0 The sequence for is divided into two parts: RE #0, #1, #12, #13, ... The above sequence is 0 ', RE #6, #7, #18, #19... the sequence above is port p 6 ' to build. Example A6 may include the method of example A1 or any other example herein, and a new type of DMRS may be defined to support uplink SU-MIMO transmission with up to 8 layers. The DMRS may occupy 4 consecutive REs, and an OCC of length 4 may be applied across the frequency domain.

[0118] Example A7 may include the method of Example A1 or any other example herein, and an additional cyclic shift may be introduced to support uplink SU-MIMO transmission with up to 4 layers and / or up to 8 layers for a DFT-s-OFDM waveform, which may be applied to both Type-1 DMRS (including 1-symbol DMRS and 2-symbol DMRS) and Type-2 DMRS (including 1-symbol DMRS and 2-symbol DMRS). The additional cyclic shift may be predefined or configured by higher layers.

[0119] Example A8 may include the method of example A1 or any other example herein, and for a DFT-s-OFDM waveform, a larger comb size, e.g., Comb-4 and / or Comb-8, may be introduced for Type-1 DMRS to support uplink SU-MIMO transmissions using up to 8 layers.

[0120] Example A9 may include the method of Example A1 or any other example herein, and for a DFT-s-OFDM waveform, a new type of DMRS may be defined to support uplink SU-MIMO transmission with up to 8 layers, where the DMRS occupies 4 consecutive REs and an OCC of length 4 may be applied across the frequency domain.

[0121] Example A10 may include a method for a UE, the method including: receiving configuration information from a gNB for configuring a demodulation reference signal (DMRS) for uplink single-user (SU) multiple-input multiple-output (MIMO) transmission using up to eight layers; The method includes encoding the uplink SU-MIMO transmission based on the configuration information.

[0122] Example A11 may include the method of Example A10 or any other example herein, wherein the DMRS has a comb size of comb-4 or comb-8.

[0123] Example A12 may include the method of Examples A10-A11 or any other example herein, where the DMRS is a Type 1 DMRS.

[0124] Example A13 may include the method of Examples A10-A12 or any other example herein, where the DMRS is a Type 2 DMRS.

[0125] Example A14 may include the method of Examples A10 to A13 or any other example herein, where only a two-symbol DMRS may be configured when the SU-MIMO transmission has more than a predetermined number of layers.

[0126] Example A15 may include the method of example A14, wherein the predetermined number is 4, 5, or 6.

[0127] Example B1 may include a method of operating a wireless network including a next generation Node B (gNB) adapted to configure a user equipment (UE) with DMRS for uplink transmissions.

[0128] Example B2 may include the method of example B1 or any other example herein, and for a CP-OFDM waveform, the antenna port field in the DCI scheduling the PUSCH may be extended to support 8-port DMRS.

[0129] Example B3 may include the method of example B2 or any other example herein, and a mapping between the antenna port field code points and the indicated DMRS ports should be defined for each rank value R, where R={1, 2, 3, ... 8}. The antenna port field length should be the same for each rank value, i.e., the field length is determined by the maximum bit width between each rank.

[0130] Example B4 may include the method of example B3 or any other example herein, where the mapping between antenna port field code points and the indicated DMRS ports for rank 1 to rank 8 is shown in Tables 1 to 8.

[0131] Example B5 may include the method of example B2 or any other example herein, and the mapping between the antenna port field code points and the indicated DMRS ports may be jointly encoded for all rank values ​​R, R={1, 2, 3, ... 8}, as shown in Table 9.

[0132] Example B6 may include the method of Example B2 or some other examples herein, where, to reduce DCI overhead, for an 8-port DMRS, if rank value R≦4, only the first four ports are used for the DMRS. If rank value R>4, the first four ports and some other ports are used (e.g., port(s) among ports #0-#3 and #4-#7 are used).

[0133] Example B7 may include the method of example B2 or any other example herein, where the antenna port field length may depend on the value of maxRank or maxMIMO-Layers, and the table of mappings between antenna port field code points and indicated DMRS ports should include rank values ​​less than or equal to maxRank or maxMIMO-Layers.

[0134] Example B8 may include the method of example B2 or any other example herein, and for uplink transmission using 8Tx, multiple codewords or multiple port groups may be used, e.g., two codewords / port groups are used, each codeword / port group corresponding to four DMRS ports.

[0135] Example B9 may include the method of example B8 or any other example herein, and when two codeword / port groups are configured, the field length of the antenna port field should be the same when only one codeword is enabled as when both codewords are enabled, as shown in Table 10.

[0136] Example B10 may include the method of example B2 or any other example herein, where for uplink transmission with 8Tx, multiple codewords or multiple port groups may be used, e.g., two codewords / port groups are used, each codeword / port group corresponding to four DMRS ports. Correspondingly, multiple antenna port fields, e.g., two antenna port fields, may be included in the DCI, one antenna port field corresponding to one codeword / port group.

[0137] Example B11 may include the method of example B1 or any other example herein, where for a DFT-s-OFDM waveform with rank-1 transmission, a DMRS with 8 ports is required to support 8Tx uplink transmission. Correspondingly, the antenna port field in the DCI scheduling the PUSCH should be enhanced to support the 8-port DMRS as shown in Table 11.

[0138] Example B12 includes a method for a next generation Node B (gNB), the method including: determining configuration information including an indication of an antenna port of a user equipment (UE) for supporting a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) transmission; and encoding a message for transmission to the UE that includes the configuration information.

[0139] Example B13 includes the method of example B12 or any other example herein, wherein the message includes downlink control information (DCI) that includes the configuration information.

[0140] Example B14 includes the method of example B12 or any other example herein, wherein the configuration information indicates a mapping between antenna port field code points and DMRS ports.

[0141] Example B15 includes the method of example B14 or any other example herein, wherein a mapping is defined for each of a plurality of rank values.

[0142] Example B16 includes the method of example B14 or any other example herein, wherein the mapping is common for multiple rank values.

[0143] Example B17 includes the method of example B12 or any other example herein, wherein the configuration information is applied to a subset of available antenna ports of the UE.

[0144] Example B18 includes the method of example B12 or any other example herein, wherein the configuration information is applied to a DMRS having a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform.

[0145] Example B19 is a method for a user equipment (UE), comprising: receiving, from a next generation Node B (gNB), a message including configuration information including an indication of an antenna port of the UE to support a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) transmission; encoding a PUSCH message for transmission based on the configuration information. method.

[0146] Example B20 includes the method of example B19 or any other example herein, wherein the message includes downlink control information (DCI) including the configuration information.

[0147] Example B21 includes the method of example B19 or any other example herein, wherein the configuration information indicates a mapping between antenna port field code points and DMRS ports.

[0148] Example B22 includes the method of example B21 or any other example herein, wherein a mapping is defined for each of a plurality of rank values.

[0149] Example B23 includes the method of example B21 or any other example herein, wherein the mapping is common to multiple rank values.

[0150] Example B24 includes the method of example B19 or any other example herein, wherein the configuration information is applied to a subset of available antenna ports of the UE.

[0151] Example B25 includes the method of example B19 or any other example herein, wherein the configuration information is applied to a DMRS having a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform.

[0152] Example C1 includes one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of a user equipment (UE), configure the UE to: receive downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from a next generation Node B (gNB), the DCI including an antenna port field for indicating a transmission port for a demodulation reference signal (DMRS) having up to eight transmission ports; and encode the DMRS for transmission using the PUSCH based on the antenna port field.

[0153] Example C2 includes one or more NTCRMs of example C1, wherein the transmit ports for the DMRS are indicated according to mapping information that maps code points in the antenna port field to corresponding transmit ports of the DMRS.

[0154] Example C3 includes one or more NTCRMs of example C2, wherein the mapping information is defined for each of a plurality of rank values, including rank value 8.

[0155] Example C4 includes one or more NTCRMs of Example C2, and the mapping information jointly maps code points in the antenna port field to corresponding transmit ports of the DMRS for multiple rank values, including rank value 8.

[0156] Example C5 includes one or more NTCRMs of example C2, wherein the mapping information is applied to code division multiplexing (CDM) groups each including a subset of available antenna ports of a UE.

[0157] Example C6 includes the one or more NTCRMs of example C1, wherein the DMRS is encoded for transmission based on a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform.

[0158] Example C7 includes the one or more NTCRMs of any one of Examples C1 to C6, wherein the DMRS is encoded for transmission based on an orthogonal cover code (OCC) having length four.

[0159] Example C8 includes one or more NTCRMs of example C7, wherein the DMRS is a Type 1 DMRS.

[0160] Example C9 includes one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of a next generation Node B (gNB), configure the gNB to: encode downlink control information (DCI) for transmission to a user equipment (UE) to schedule a physical uplink shared channel (PUSCH), the DCI including an antenna port field to indicate a transmit port for a demodulation reference signal (DMRS) having up to eight transmit ports; and receive the PUSCH using the DMRS based on the DCI.

[0161] Example C10 includes one or more NTCRMs of example C9, wherein transmit ports for the DMRS are indicated according to mapping information that maps code points in an antenna port field to corresponding transmit ports of the DMRS.

[0162] Example C11 includes one or more NTCRMs of example C10, wherein the mapping information is defined for each of a plurality of rank values, including rank value 8.

[0163] Example C12 includes one or more NTCRMs of example C10, wherein the mapping information jointly maps code points of the antenna port field to corresponding transmit ports of the DMRS for a plurality of rank values ​​including rank value 8.

[0164] Example C13 includes one or more NTCRMs of example C10, wherein the mapping information is applied to code division multiplexing (CDM) groups each including a subset of available antenna ports of a UE.

[0165] Example C14 includes the one or more NTCRMs of example C9, wherein the DMRS is based on a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform.

[0166] Example C15 includes one or more NTCRMs of any one of examples C9 to C14, wherein the DMRS has a comb-2 structure with an orthogonal cover code (OCC) having a length of 4 applied thereto.

[0167] Example C16 includes one or more NTCRMs of example C15, wherein the DMRS is a Type 1 DMRS.

[0168] Example C17 includes one or more non-transitory computer-readable media having instructions stored thereon that, when executed by one or more processors of a user equipment (UE), configure the UE to perform the following steps: generating a demodulation reference signal (DMRS) having a comb-2 structure for a physical uplink shared channel (PUSCH); applying an orthogonal cover code (OCC) having length 4 to the DMRS to generate eight DMRS ports; and transmitting the PUSCH and the DMRS based on the eight DMRS ports.

[0169] Example C18 includes one or more NTCRMs of example C17, wherein the DMRS is a Type 1 DMRS.

[0170] Example C19 includes one or more NTCRMs of example C17 or C18, wherein the instructions, when executed, further configure the UE to receive downlink control information (DCI) from a next generation Node B (gNB) to schedule a PUSCH, the DCI including an antenna port field to indicate a DMRS port for the DMRS.

[0171] Example C20 includes one or more NTCRMs of example C19, wherein a DMRS port for the DMRS is indicated according to mapping information that maps a code point in an antenna port field to a corresponding DMRS port for the DMRS.

[0172] Example Z01 may include an apparatus comprising means for performing one or more elements of a method described or related to any of Examples A1-A15, B1-B25, C1-C20, or any other method or process described herein.

[0173] Example Z02 may include one or more non-transitory computer-readable media containing instructions that, upon execution by one or more processors of the electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples A1-A15, B1-B25, C1-C20, or any other method or process described herein.

[0174] Example Z03 may include an apparatus having logic, modules, or circuitry for performing one or more elements of a method described or related to any of Examples A1-A15, B1-B25, C1-C20, or any other method or process described herein.

[0175] Example Z04 may include any method, technique, or process described or related to any of Examples A1-A15, B1-B25, C1-C20, or any portion or part thereof.

[0176] Example Z05 may include an apparatus having one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any or a portion of Examples A1-A15, B1-B25, C1-C20.

[0177] Example Z06 may include signals described or related to any of Examples A1-A15, B1-B25, C1-C20 or any part or portion thereof.

[0178] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described in or related to any of Examples A1-A15, B1-B25, C1-C20, or any portion or part thereof, or otherwise described in this disclosure.

[0179] Example Z08 may include a signal encoded with data described in or relating to any of Examples A1-A15, B1-B25, C1-C20 or any portion or part thereof, or otherwise described in this disclosure.

[0180] Example Z09 may include a signal that is encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples A1-A15, B1-B25, C1-C20, or any portion or part thereof, or otherwise described in this disclosure.

[0181] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, the execution of which by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any or some of Examples A1-A15, B1-B25, C1-C20.

[0182] Example Z11 may include a computer program including instructions, the execution of which by a processing element causes the processing element to perform a method, technique or process described in or related to any one or any part of Examples A1-A15, B1-B25, C1-C20.

[0183] Example Z12 may include a signal in a wireless network as shown and described herein.

[0184] Example Z13 may include a method of communicating in a wireless network as illustrated and described herein.

[0185] Example Z14 may include a system for providing wireless communication as illustrated and described herein.

[0186] Example Z15 may include a device for providing wireless communication as illustrated and described herein.

[0187] Any of the above examples can be combined with any other example (or combination of examples) unless expressly stated otherwise. The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0188] Abbreviation Unless used differently herein, terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR 21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein:

[0189] 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACR Application Context Relocation ACK Acknowledgement ACID Application Client Identification AF Application Function AM Acknowledged Mode Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function Access Network ANR Automatic Neighbour Relation AOA Angle of Arrival AP Application Protocol, Antenna Port, Access Point API Application Programming Interface APN Access Point Name Access Point Name ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access stratum ASP Application Service Provider Application Service Provider ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function Authentication Server Function AWGN Additive White Gaussian Noise BAP Backhaul Adaptation Protocol BCH Broadcast Channel BER Bit Error Ratio Bit Error Rate BFD Beam Failure Detection BLER Block Error Rate BPSK Binary Phase Shift Keying Two-state phase shift keying BRAS Broadband Remote Access Server Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity Cell Radio Network Temporary Identity CA Carrier Aggregation, Certification Authority CAPEX CAPital EXpenditure Capital Expenditure CBRA Contention Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Assessment CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM Content Delivery Network CDMA Code-Division Multiple Access CDR Charging Data Request CDR Charging Data Response CFRA Contention Free Random Access Contention Free Random Access CG Cell Group CGF Charging Gateway Function CHF Charging Function CI Cell Identity CID Cell-ID Cell ID (e.g. positioning method) CIM Common Information Model CIR Carrier to Interference Ratio CK Cipher Key CM Connection Management, Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System Cloud Management System CO Conditional Optional CoMP Coordinated Multi-Point CORESET Control Resource Set Control resource set COTS Commercial Off-The-Shelf CP Control Plane, Cyclic Prefix, Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSI processing unit CSI processing unit, Central Processing Unit C / R Command / Response field bit CRAN Cloud Radio Access Network Cloud Radio Access Network, Cloud RAN CRB Common Resource Block CRC Cyclic Redundancy Check Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI Cell RNTI CS Circuit Switched CSCF call session control function CSAR Cloud Service Archive Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Common Search Space, Cell-specific Search Space CTF Charging Trigger Function CTS Clear-to-Send Clear to send CW Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavour DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data network DNN Data Network Name Data Network Name DNAI Data Network Access Identifier DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL Domain Specific Language, Digital Subscriber Line DSLAM DSL Access Multiplexer DSL Access Multiplexer DwPTS Downlink Pilot Time Slot Downlink pilot time slot E-LAN ​​Ethernet Local Area Network E2E End-to-End EAS Edge Application Server Edge Application Server ECCA extended clear channel assessment, extended CCA ECCE Enhanced Control Channel Element, Enhanced CCE ED Energy Detection EDGE Enhanced Datarates for GSM Evolution EAS Edge Application Server Edge Application Server EASID Edge Application Server Identification Edge Application Server Identification ECS Edge Configuration Server ECSP Edge Computing Service Provider Edge Computing Service Provider EDN Edge Data Network Edge Data Network EEC Edge Enabler Client Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server Edge Enabler Server EESID Edge Enabler Server Identification Edge Enabler Server Identification EHE Edge Hosting Environment Edge Hosting Environment EGMF Exposure Governance Management Function Public Governance Table Management Function EGPRS Enhanced GPRS Enhanced GPRS EIR Equipment Identity Register eLAA enhanced Licensed Assisted Access, enhanced LAA EM, Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB Evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Channel EPRE Energy per resource element EPS Evolved Packet System EREG enhanced resource element groups ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC embedded UICC embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Improved V2X F1AP F1 Application Protocol F1 Application Protocol F1-C F1 Control plane interface F1-U F1 User plane interface F1 User plane interface FACCH Fast Associated Control CHannel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH Forward Access Channel FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC Federal Communications Commission FCCH Frequency Correction CHannel FDD Frequency Division Duplex FDM Frequency Division Multiplex FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA further enhanced Licensed Assisted Access, further enhanced LAA FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range FQDN Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN Radio Network Temporary Identity GERAN GSM EDGE RAN GSM EDGE RAN, GSM EDGE Radio Access Network GSM EDGE radio access network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB Next Generation NodeB Next Generation NodeB gNB-CU gNB-centralized unit gNB centralized unit, Next Generation NodeB centralized unit, Next Generation NodeB centralized unit gNB-DU gNB-distributed unit gNB distributed unit, Next Generation NodeB distributed unit Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GPSI Generic Public Subscription Identifer General Public Subscription Identifier GSM Global System for Mobile Communications Global System for Mobile Communications, Groupe Sp´ecial Mobile GSM Association GTP GPRS Tunneling Protocol GTP-U GPRS Tunnelling Protocol for User Plane GPRS Tunneling Protocol for User Plane GTS Go To Sleep Signal Sleep transition signal (WUS related) GUMMEI Globally Unique MME Identifier Globally Unique MME Identifier GUTI Globally Unique Temporary UE Identity Globally Unique Temporary UE Identity HARQ Hybrid ARQ Hybrid Automatic Repeat Request HANDO Handover HFN HyperFrame Number HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA High Speed ​​Downlink Packet Access HSN Hopping Sequence Number Hopping sequence number HSPA High Speed ​​Packet Access HSS Home Subscriber Server Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP Hyper Text Transfer Protocol HTTPS Hyper Text Transfer Protocol Secure (https is http / 1.1 over SSL, i.e. port 443) I-Block Information Block ICCID Integrated Circuit Card Identification IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, identifier IDFT Inverse Discrete Fourier Transform IE Information element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IIOT Industrial Internet of Things IM Interference Measurement, Intermodulation, IP Multimedia IMC IMS Credentials IMS Credentials IMEI International Mobile Equipment Identity IMGI International mobile group identity IMPI IP Multimedia Private Identity IP Multimedia Private Identity IMPU IP Multimedia PUblic identity IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT Internet of Things IP Internet Protocol Ipsec IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP Connectivity Access Network IP-M IP Multicast IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organisation for Standardisation ISP Internet Service Provider IWF Interworking-Function I-WLAN Interworking WLAN Constraint length of the convolutional code, USIM Individual key kB Kilobyte (1000 bytes) kbps kilo-bits per second Kc Ciphering key Ki Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (data link layer) L3 Layer 3 (network layer) LAA Licensed Assisted Access LAN Local Area Network LADN Local Area Data Network Local Area Data Network LBT Listen Before Talk LCM LifeCycle Management LCR Low Chip Rate LCS Location Services LCID Logical Channel ID Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Compatibility LMF Location Management Function LOS Line of Sight LPLMN Local PLMN LPP LTE Positioning Protocol LSB Least Significant Bit LTE Long Term Evolution LWA LTE-WLAN aggregation LTE-WLAN aggregation LWIP LTE / WLAN Radio Level Integration with IPsec Tunnel LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (context of protocol layering) MAC Message authentication code (security / encryption context) MAC-A MAC used for authentication and key agreement (TSG T WG3 context) MAC-I MAC used for data integrity of signalling messages (TSG T WG3 context) MANO Management and Orchestration Management, Operation and Orchestration MBMS Multimedia Broadcast and Multicast Service MBSFN Multimedia Broadcast multicast service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service Management Data Analytics Service MDT Minimization of Drive Tests ME Mobile Equipment MeNB master eNB MER Message Error Ratio Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period Measurement Gap Repetition Period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator MO Measurement Object, Mobile Originated MPBCH MTC Physical Broadcast CHannel MPDCCH MTC Physical Downlink Control CHannel MPDSCH MTC Physical Downlink Shared CHannel MPRACH MTC Physical Random Access CHannel MPUSCH MTC Physical Uplink Shared Channel MPLS MultiProtocol Label Switching MS Mobile Station Mobile station MSB Most Significant Bit MSC Mobile Switching Centre Mobile Switching Centre MSI Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated Mobile Termination MTC Machine-Type Communications mMTC massive MTC, massive Machine-Type Communications MU-MIMO Multi User MIMO MWUS MTC wake-up signal MTC wake-up signal, MTC WUS MTC WUS NACK Negative Acknowledgement NAI Network Access Identifier NAS Non-Access Stratum Non-Access Stratum layer NCT Network Connectivity Topology Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV Network Functions Virtualization NFVI NFV Infrastructure NFV Infrastructure NFVO NFV Orchestrator NFV Orchestrator NG Next Generation Next Generation, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB Narrowband MIB NPBCH Narrowband Physical Broadcast CHannel NPDCCH Narrowband Physical Downlink Control CHannel NPDSCH Narrowband Physical Downlink Shared CHannel NPRACH Narrowband Physical Random Access CHannel NPUSCH Narrowband Physical Uplink Shared CHannel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR New Radio, Neighbour Relation NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI NSSF Network Slice Selection Function NW Network NWUS Narrowband wake-up signal, Narrowband WUS NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical channel Data Unit - type 2 OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOB Out-of-band OOS Out of Sync OPEX OPerating EXpense OSI Other System Information Other system information OSS Operations Support System OTA over-the-air PAPR Peak-to-Average Power Ratio Peak-to-Average Power Ratio PAR Peak to Average Ratio PBCH Physical Broadcast Channel PC Power Control, Personal Computer PCC Primary Component Carrier, Primary CC P-CSCF Proxy CSCF PCell Primary Cell Main cell PCI Physical Cell ID Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function Policy control and charging rules function PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Data Network, Public Data Network PDSCH Physical Downlink Shared Channel Physical Downlink Shared Channel PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN Personal Identification Number PM Performance Measurement Performance measurement PMI Precoding Matrix Indicator PNF Physical Network Function PNFD Physical Network Function Descriptor PNFR Physical Network Function Record POC PTT over Cellular PTT over Cellular PP, PTP Point-to-Point PPP Point-to-Point Protocol PRACH Physical RACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe Proximity Services, Proximity-Based Services PRS Positioning Reference Signal PRR Packet Reception Radio PS Packet Services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell Primary SCell PSS Primary Synchronization Signal Primary synchronization signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation QCI QoS class of identifier QoS class of identifier QCL Quasi co-location QFI QoS Flow ID QoS Flow Identifier QoS Quality of Service QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI Random Access RNTI RAB Radio Access Bearer, Random Access Burst RACH Random Access Channel RADIUS Remote Authentication Dial In User Service RAN Radio Access Network RAND RANDom number Random number (used for authentication) RAR Random Access Response RAT Radio Access Technology RAU Routing Area Update RB Resource block, Radio Bearer RBG Resource block group REG Resource Element Group Release REQ REQuest Request RF Radio Frequency RI Rank Indicator RIV Resource indicator value RL Radio Link RLC Radio Link Control Radio Link Control layer RLC AM RLC Acknowledged Mode RLC UM RLC Unacknowledged Mode RLC Unacknowledged Mode RLF Radio Link Failure Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM Reference signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI, Remaining Minimum System Information RN Relay Node RNC Radio Network Controller RNL Radio Network Layer RNTI Radio Network Temporary Identifier ROHC RObust Header Compression RRC Radio Resource Control Radio resource control, Radio Resource Control layer Radio Resource Control Layer RRM Radio Resource Management Radio resource management RS Reference Signal Reference signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP Real Time Protocol RTS Ready-To-Send Ready to send RTT Round Trip Time Rx Reception, Receiving Receiver S1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 for the user plane S-CSCF serving CSCF serviceCSCF S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA Single Carrier Frequency Division Multiple Access SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol Service Data Adaptation Protocol layer SDL Supplementary Downlink SDNF Structured Data Storage Network Function SDP Session Description Protocol SDSF Structured Data Storage Function SDT Small Data Transmission SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPP Security Edge Protection Proxy SFI Slot format indication SFTD Space-Frequency Time Diversity, SFN and frame timing difference SFN System Frame Number SgNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Information RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiated Protocol SiP System in Package SL Sidelink SLA Service Level Agreement SM Session Management SMF Session Management Function SMS Short Message Service SMSF SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node, Sequence Number SoC System on Chip SON Self-Organizing Network SpCell Special Cell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signalling Radio Bearer SRS Sounding Reference Signal Detection reference signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID Service Set Identifier SS / PBCH Block SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator SS / PBCH Block Resource Indicator, Syncheronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio Synchronization Signal based Signal to Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO Single User MIMO SUL Supplementary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAI Tracking Area Identity TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD Time Division Duplex TDM Time Division Multiplexing TDMA Time Division Multiple Access TE Terminal Equipment TEID Tunnel End Point Identifier TFT Traffic Flow Template TMSI Temporary Mobile Subscriber Identity TNL Transport Network Layer TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report Technical Report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standard TTI Transmission Time Interval Tx Transmission, Transmitting, Transmitter U-RNTI UTRAN Radio Network Temporary Identity UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management UDP User Datagram Protocol UDSF Unstructured Data Storage Network Function UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode UML Unified Modelling Language UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network UwPTS Uplink Pilot Time Slot Uplink pilot time slot V2I Vehicle-to-Infrastruction V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link Virtual Link, VLAN Virtual LAN, Virtual Local Area Network VM Virtual Machine VNF Virtualized Network Function VNFFG VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VNF Manager VoIP Voice-over-IP, Voice-over-Internet Protocol Voice over IP, Voice over Internet Protocol VPLMN Visited Public Land Mobile Network VPN Virtual Private Network VRB Virtual Resource Block WiMAX Worldwide Interoperability for Microwave Access WLAN Wireless Local Area Network WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control plane X2 control plane X2-U X2-User plane X2 User plane XML eXtensible Markup Language XRES EXpected user RESponse Expected user response XOR eXclusive OR exclusive OR ZC Zadoff-Chu ZP Zero Power

[0190] terminology For purposes of this specification, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0191] The term "circuitry" as used herein refers to, is a part of, or includes hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high performance PLDs (HCPLDs), constructed ASICs, or programmable SoCs), digital signal processors (DSPs), etc., configured to provide the described functionality. In some embodiments, a circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0192] The term "processor circuitry" as used herein refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. The processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry."

[0193] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and / or the like.

[0194] The term "user equipment" or "UE" as used herein refers to a device having wireless communication capabilities and may represent a remote user of network resources in a communications network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio unit, reconfigurable radio unit, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0195] The term "network element" as used herein refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communications network services. The term "network element" may be considered synonymous with and / or may be referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or others.

[0196] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Additionally, the terms "computer system" and / or "system" may refer to multiple computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0197] As used herein, the terms "appliance," "computer appliance," and the like refer to a computing device or system having program code (e.g., software or firmware) specifically designed to provide particular computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computing appliance or is otherwise dedicated to providing particular computing resources.

[0198] The term "resources" as used herein refers to physical or virtual devices, components, and / or components within a particular device in a computing environment, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, etc. "Hardware resources" may refer to computational, storage, and / or network resources provided by a physical hardware element(s). "Virtualized resources" may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system over a communication network. The term "system resources" may refer to any type of shared entity for providing services and may include computing and / or network resources. A system resource may be viewed as a set of coherent functions, network data objects, or services that reside on a single host or on multiple hosts and are accessible through a clearly identifiable server.

[0199] The term "channel" as used herein refers to any transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar terminology indicating a path or medium over which data is communicated. Additionally, the term "link" as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0200] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" may also refer to a concrete occurrence of an object that may occur, for example, during the execution of program code.

[0201] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by a means of communication, such as through a wire or other interconnection, through a wireless communication channel or link, or the like.

[0202] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or the data element that contains the contents.

[0203] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term "SSB" refers to SS / PBCH block.

[0204] The term "Primary Cell" refers to an MCG cell operating on a primary frequency on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. The term "primary SCG cell" refers to the SCG cell to which the UE performs random access when performing a Reconfiguration with Sync procedure for DC operation. The term "secondary cell" refers to a cell that provides additional radio resources above the special cell for a UE configured with CA. The term "secondary cell group" refers to a subset of serving cells that includes a PSCell and zero or more secondary cells for a UE configured with a DC. The term "Serving Cell" refers to the primary cell for a UE that is in RRC_CONNECTED and is not configured with CA / DC, and there can be only one serving cell that is the primary cell. The term "serving cell" or "serving cells" refers to the set of cells including the special cell and all secondary cells for a UE that is in RRC_CONNECTED and configured with CA / . The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.

Claims

1. 1. An apparatus for use in a user equipment (UE), the apparatus comprising: a memory for storing downlink control information (DCI) received from a next generation Node B (gNB), the DCI for scheduling a physical uplink shared channel (PUSCH), the DCI including an antenna port field for indicating a transmission port for a demodulation reference signal (DMRS) having up to eight transmission ports; and one or more processors configured to encode the DMRS for transmission using the PUSCH based on the antenna port field. Device.

2. The apparatus of claim 1 , wherein the transmit ports for the DMRS are indicated according to mapping information that maps code points in the antenna port field to corresponding transmit ports of the DMRS.

3. The apparatus of claim 2 , wherein the mapping information is defined for each of a plurality of rank values, including rank value eight.

4. The apparatus of claim 2 , wherein the mapping information jointly maps the code points in the antenna port field to corresponding transmit ports of the DMRS for a plurality of rank values, including a rank value of eight.

5. The apparatus of claim 2 , wherein the mapping information is applied to code division multiplexing (CDM) groups, each CDM group including a subset of available antenna ports of the UE.

6. The apparatus of claim 1 , wherein the DMRS is encoded for transmission based on a Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform.

7. The apparatus of claim 1 , wherein the DMRS is encoded for transmission based on an orthogonal cover code (OCC) having length four.

8. The apparatus of claim 7 , wherein the DMRS is a Type 1 DMRS.

9. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors in a next generation Node B (gNB), perform the following: encoding downlink control information (DCI) for transmission to a user equipment (UE) for scheduling a physical uplink shared channel (PUSCH), the DCI including an antenna port field for indicating a transmission port for a demodulation reference signal (DMRS) having up to eight transmission ports; receiving the PUSCH using the DMRS based on the DCI; Configuring the gNB to perform One or more NTCRMs.

10. 10. The one or more NTCRMs of claim 9, wherein the transmit ports for the DMRS are indicated according to mapping information that maps code points in the antenna port field to corresponding transmit ports of the DMRS.

11. The one or more NTCRMs of claim 10 , wherein the mapping information is defined for each of a plurality of rank values, including rank value 8.

12. 11. The one or more NTCRMs of claim 10, wherein the mapping information jointly maps the code points of the antenna port field to corresponding transmit ports of the DMRS for a plurality of rank values, including a rank value of 8.

13. The one or more NTCRMs of claim 10, wherein the mapping information is applied to code division multiplexing (CDM) groups each including a subset of available antenna ports of the UE.

14. 14. The NTCRM or NTCRMs of any one of claims 9 to 13, wherein the DMRS is based on a Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform.

15. 14. The NTCRM or NTCRMs according to any one of claims 9 to 13, wherein the DMRS has a comb-2 structure with an orthogonal cover code (OCC) of length 4 applied.

16. The one or more NTCRMs according to claim 15, wherein the DMRS is a Type 1 DMRS.

17. One or more non-transitory computer-readable media having instructions stored thereon that, when executed by one or more processors of a user equipment (UE), can: generating a demodulation reference signal (DMRS) having a comb-2 structure for a physical uplink shared channel (PUSCH); applying an orthogonal cover code (OCC) having length 4 to the DMRS to generate eight DMRS ports; transmitting the PUSCH and the DMRS based on the eight DMRS ports; and configuring the UE to execute one or more NTCRMs.

18. The one or more NTCRMs according to claim 17, wherein the DMRS is a type 1 DMRS.

19. 19. One or more NTCRMs according to claim 17 or 18, wherein the instructions, when executed, further configure the UE to receive downlink control information (DCI) from a next generation Node B (gNB) to schedule the PUSCH, the DCI including an antenna port field to indicate the DMRS port for the DMRS.

20. 20. The one or more NTCRMs of claim 19, wherein the DMRS port for the DMRS is indicated according to mapping information that maps a code point in the antenna port field to a corresponding DMRS port of the DMRS.

Images