Patent ID: 12232123

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

Some embodiments are directed to a generation node B (gNB) for a fifth-generation (5G) new radio (NR) network is configured for slot-less operation at frequencies above a 52.6 GHz carrier frequency. The gNB may generate signalling to configure a user equipment (UE) with a gap between demodulation reference signal (DMRS) symbols for an associated physical downlink shared channel (PDSCH). The gNB may also encode the DMRS symbols for transmission in accordance with the gap and may encode the associated PDSCH for transmission during the gap between the DMRS symbol transmissions at symbol times following the DMRS symbols. Some embodiments are directed to a UE configured for slot-less operations.

FIG.1Aillustrates an architecture of a network in accordance with some embodiments. The network140A is shown to include user equipment (UE)101and UE102. The UEs101and102are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs101and102can be collectively referred to herein as UE101, and UE101can be used to perform one or more of the techniques disclosed herein.

Any of the radio links described herein (e.g., as used in the network140A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard.

LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE-Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

In some embodiments, any of the UEs101and102can comprise an Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some embodiments, any of the UEs101and102can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

In some embodiments, any of the UEs101and102can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

The UEs101and102may be configured to connect, e.g., communicatively couple, with a radio access network (RAN)110. The RAN110may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs101and102utilize connections103and104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections103and104are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

In an aspect, the UEs101and102may further directly exchange communication data via a ProSe interface105. The ProSe interface105may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

The UE102is shown to be configured to access an access point (AP)106via connection107. The connection107can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP106can comprise a wireless fidelity (WiFi®) router. In this example, the AP106is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

The RAN110can include one or more access nodes that enable the connections103and104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some embodiments, the communication nodes111and112can be transmission/reception points (TRPs). In instances when the communication nodes111and112are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN110may include one or more RAN nodes for providing macrocells, e.g., macro RAN node111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node112.

Any of the RAN nodes111and112can terminate the air interface protocol and can be the first point of contact for the UEs101and102. In some embodiments, any of the RAN nodes111and112can fulfill various logical functions for the RAN110including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes111and/or112can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

The RAN110is shown to be communicatively coupled to a core network (CN)120via an S1 interface113. In embodiments, the CN120may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference toFIGS.1B-1C). In this aspect, the S interface113is split into two parts: the S1-U interface114, which carries traffic data between the RAN nodes111and112and the serving gateway (S-GW)122, and the S-mobility management entity (MME) interface115, which is a signaling interface between the RAN nodes111and112and MMEs121.

In this aspect, the CN120comprises the MMEs121, the S-GW122, the Packet Data Network (PDN) Gateway (P-GW)123, and a home subscriber server (HSS)124. The MMEs121may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs121may manage mobility embodiments in access such as gateway selection and tracking area list management. The HSS124may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN120may comprise one or several HSSs124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS124can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

The S-GW122may terminate the S1 interface113towards the RAN110, and routes data packets between the RAN110and the CN120. In addition, the S-GW122may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW122may include a lawful intercept, charging, and some policy enforcement.

The P-GW123may terminate an SGi interface toward a PDN. The P-GW123may route data packets between the EPC network120and external networks such as a network including the application server184(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface125. The P-GW123can also communicate data to other external networks131A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server184may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW123is shown to be communicatively coupled to an application server184via an IP interface125. The application server184can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs101and102via the CN120.

The P-GW123may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF)126is the policy and charging control element of the CN120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF126may be communicatively coupled to the application server184via the P-GW123.

In some embodiments, the communication network140A can be an IoT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT).

An NG system architecture can include the RAN110and a 5G network core (5GC)120. The NG-RAN110can include a plurality of nodes, such as gNBs and NG-eNBs. The core network120(e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

In some embodiments, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some embodiments, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

FIG.1Billustrates a non-roaming 5G system architecture in accordance with some embodiments. Referring toFIG.1B, there is illustrated a 5G system architecture140B in a reference point representation. More specifically, UE102can be in communication with RAN110as well as one or more other 5G core (5GC) network entities. The 5G system architecture140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF)132, session management function (SMF)136, policy control function (PCF)148, application function (AF)150, user plane function (UPF)134, network slice selection function (NSSF)142, authentication server function (AUSF)144, and unified data management (UDM)/home subscriber server (HSS)146. The UPF134can provide a connection to a data network (DN)152, which can include, for example, operator services, Internet access, or third-party services. The AMF132can be used to manage access control and mobility and can also include network slice selection functionality. The SMF136can be configured to set up and manage various sessions according to network policy. The UPF134can be deployed in one or more configurations according to the desired service type. The PCF148can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

In some embodiments, the 5G system architecture140B includes an IP multimedia subsystem (IMS)168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS168B includes a CSCF, which can act as a proxy CSCF (P-CSCF)162BE, a serving CSCF (S-CSCF)164B, an emergency CSCF (E-CSCF) (not illustrated inFIG.1B), or interrogating CSCF (I-CSCF)166B. The P-CSCF162B can be configured to be the first contact point for the UE102within the IM subsystem (IMS)168B. The S-CSCF164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some embodiments, the I-CSCF166B can be connected to another IP multimedia network170E, e.g. an IMS operated by a different network operator.

In some embodiments, the UDM/HSS146can be coupled to an application server160E, which can include a telephony application server (TAS) or another application server (AS). The AS160B can be coupled to the IMS168B via the S-CSCF164B or the I-CSCF166B.

A reference point representation shows that interaction can exist between corresponding NF services. For example,FIG.1Billustrates the following reference points: N1 (between the UE102and the AMF132), N2 (between the RAN110and the AMF132), N3 (between the RAN110and the UPF134), N4 (between the SMF136and the UPF134), N5 (between the PCF148and the AF150, not shown), N6 (between the UPF134and the DN152), N7 (between the SMF136and the PCF148, not shown), N8 (between the UDM146and the AMF132, not shown), N9 (between two UPFs134, not shown), N10 (between the UDM146and the SMF136, not shown), N11 (between the AMF132and the SMF136, not shown), N12 (between the AUSF144and the AMF132, not shown), N13 (between the AUSF144and the UDM146, not shown), N14 (between two AMFs132, not shown), N15 (between the PCF148and the AMF132in case of a non-roaming scenario, or between the PCF148and a visited network and AMF132in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF132and NSSF142, not shown). Other reference point representations not shown inFIG.1Bcan also be used.

FIG.1Cillustrates a 5G system architecture140C and a service-based representation. In addition to the network entities illustrated inFIG.1B, system architecture140C can also include a network exposure function (NEF)154and a network repository function (NRF)156. In some embodiments, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

In some embodiments, as illustrated inFIG.1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture140C can include the following service-based interfaces: Namf158H (a service-based interface exhibited by the AMF132), Nsmf158I (a service-based interface exhibited by the SMF136), Nnef158B (a service-based interface exhibited by the NEF154), Npcf158D (a service-based interface exhibited by the PCF148), a Nudm158E (a service-based interface exhibited by the UDM146), Naf158F (a service-based interface exhibited by the AF150), Nnrf158C (a service-based interface exhibited by the NRF156), Nnssf158A (a service-based interface exhibited by the NSSF142), Nausf158G (a service-based interface exhibited by the AUSF144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown inFIG.1Ccan also be used.

In some embodiments, any of the UEs or base stations described in connection withFIGS.1A-1Ccan be configured to perform the functionalities described herein.

Embodiments are directed to reference signal generation for slot-less operation. Some embodiments are directed to slot-less operation at frequencies above a 52.6 GHz carrier frequency. In some of these embodiments, a generation node B (gNB) configured for operating in a fifth-generation (5G) new radio (NR) or a sixth-generation (6G) network may generate signalling to configure a user equipment (UE) with a gap between demodulation reference signal (DMRS) symbols for an associated physical downlink shared channel (PDSCH). The gNB may also encode the DMRS symbols for transmission in accordance with the gap. The associated PDSCH may be transmitted during the gap between the DMRS symbol transmissions at symbol times following the DMRS symbols. Examples of these embodiments are illustrated inFIG.2(described in more detail below). As illustrated inFIG.2, a single PDSCH is transmitted. Within the PDSCH there are multiple PDSCH symbols with may be uniformly distributed. In these embodiments, the gap can be either configured by higher layers or dynamically indicated in a downlink control information (DCI) format. Thus, for different PDSCHs, the gap between DMRS symbols can be different. Accordingly, a subsequent PDSCH can be configured with a different gap between the DMRS transmissions.

In some embodiments, the signalling to configure the UE with the gap comprises a downlink control information (DCI) format, the DCI format to dynamically indicate the gap to the UE. In some embodiments, the gNB may encode a second DCI format to configure the UE with a second gap for a subsequent associated PDSCH and may encode subsequent DMRS symbols for transmission in accordance with the second gap for the subsequent associated PDSCH.

In some embodiments, the PDSCH comprises a plurality of code block groups (CBGs). In these embodiments, the gNB may encode a physical downlink control channel (PDCCH) for transmission comprising a DCI format that scheduled the PDSCH. In some embodiments, the DCI format may comprise a starting symbol and length indicator value (SLIV) of a first CBG of the PDSCH. In some embodiments, the gap in indicated by the SLIV, and the DMRS symbols are encoded for transmission outside the SLIV for each CBG of the PDSCH. In some embodiments, a first of the DMRS symbols may be encoded for transmission at a symbol time prior to a first CBG of the PDSCH. Examples of these embodiments are illustrated inFIG.3(described in more detail below).

In some embodiments, for DMRS symbols that are allocated inside the SLIV, the DMRS symbols collide with a CBG of the PDSCH. Examples of these embodiments are illustrated inFIG.4(described in more detail below).

In some embodiments, when a DMRS symbol is indicated to overlap with a rate-matched resource or a CBG based on the gap and the SLIV, the gNB may shift the overlapping DMRS symbol transmission to a first data symbol after rate-matched resource or a CBG. Examples of these embodiments are illustrated inFIG.5(described in more detail below).

In some embodiments, the rate-matched resource may comprise a control resource set (CORESET) for a physical downlink control channel (PDCCH) transmission. In these embodiments, the PDSCH may be rate-matched around the CORESET and a DMRS symbol that overlaps with the CORESET for a PDCCH transmission may be shifted.

In some embodiments, the gap may be a uniform gap configured to provide a same number of PDSCH symbols between DMRS transmissions, although the scope of the embodiments is not limited in this respect

In some embodiments, the gap may be a non-uniform gap configured by higher-layer signalling. In these embodiments, a first gap between first and second DMRS symbols may be less than a second gap between the second and a third DMRS symbols. Examples of these embodiments are illustrated inFIG.6(described in more detail below). These embodiments may be utilized to help the receiver to perform timing/frequency offset tracking, although the scope of the embodiments is not limited in this respect.

In some embodiments, the gNB may generate the DMRS based on either a Gold sequence with pi/2 BPSK modulation or a Zadoff-Chu (ZC) sequence.

In some embodiments, the signalling to configure the UE with the gap may comprise higher-layer signalling. In some embodiments, the higher-layer signalling may comprise radio-resource control (RRC) signalling.

In some embodiments, the gNB may decode a physical uplink shared channel (PUSCH) received from the UE based on DMRS symbols transmitted by the UE in accordance with the configured gap.

These embodiments are described in more detail below

Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and services.

Rel-15 NR systems are designed to operate on the licensed spectrum. The NR-unlicensed (NR-U), a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.

In Rel-15, resource allocation of one data transmission is confined within a slot, where one slot has 14 symbols. For systems operating above 52.6 GHz carrier frequency, it is envisioned that a larger subcarrier spacing is needed to combat severe phase noise. In cases when a larger subcarrier spacing, e.g., 1.92 MHz or 3.84 MHz is employed, the slot duration can be very short. For instance, for 1.92 MHz subcarrier spacing, one slot duration is approximately 7.8 μs as shown inFIG.2. This extremely short slot duration may not be sufficient for higher layer processing, including Medium Access Layer (MAC) and Radio Link Control (RLC), etc.

To address this issue, one option is to increase the number of symbols within a slot. Alternatively, a gNB may schedule the DL or UL data transmission across slot boundary. This option may indicate that the concept of slot may not be necessary, which may provide maximal flexibility at gNB on the data scheduling.

In Rel-15, reference signals, including demodulation reference signal (DMRS), channel state information reference signal (CSI-RS), phase tracking reference signal (PT-RS), tracking reference signal (TRS), sounding reference signal (SRS), etc., are generated as a function of symbol and slot index. In case when slot-less operation is used for system operating above 52.6 GHz, embodiments of the present disclosure may be used for the generation of a reference signal.

Among other things, embodiments of the present disclosure are directed to reference signal design for slot-less operation, particularly for systems operating above the 52.6 GHz carrier frequency. In particular, some embodiments may be directed to: Mechanisms on reference signal generation for slot-less operation and DMRS pattern for slot-less operation

Reference Signal Generation for Slot-Less Operation

Note that in Rel-15, for PUSCH with Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform, DMRS sequence is generated based on Zadoff-Chu (ZC) sequence in the frequency domain. Furthermore, in Rel-16, to further reduce the peak-to-average power ratio (PAPR), Gold sequence with pi/2 BPSK modulation in pre-DFT time domain was defined for DMRS sequence generation.

For systems operating above 52.6 GHz, a gNB may schedule the DL or UL data transmission across slot boundary. This option may indicate that the concept of slot may not be necessary, which may provide maximal flexibility at the gNB for data scheduling. For slot-less operation, design changes on the reference signal generation including DMRS, CSI-RS, TRS, SRS, PT-RS may need to be considered for system operating above 52.6 GHz carrier frequency. Embodiments for reference signal generation for slot-less operation are provided as follows:

In one embodiment, a reference signal in DL and/or UL can be generated based on either Gold sequence with pi/2 BPSK modulation or Zadoff-Chu (ZC) sequence. The reference signal may include, but may not be limited to DMRS, CSI-RS, TRS, SRS, PT-RS.

In one embodiment, reference signal generation is defined as a function of symbol index. Further, the symbol index is defined with respect to a reference timing. In particular, the reference timing can be 1 ms subframe boundary or 10 ms frame boundary. Given that slot index is not defined for slot-less operation, symbol index can be used for reference signal generation for inter-cell interference randomization.

In one embodiment, when Gold sequence with pi/2 BPSK modulation is applied for the reference signal generation, initialization seed of sequence generation can be defined as

cinit=(217⁢(f⁡(l)+1)⁢(2⁢NIDnSCID+1)+2⁢NIDnSCID+nSCID)⁢mod⁢231Wherel is the symbol index with respect to reference timing and ƒ(l) is a function of l.

nSCID={0,1}. For physical downlink shared channel (PDSCH) and/or physical uplink shared channel (PUSCH) which is scheduled by fallback downlink control information (DCI), e.g., DCI format 0_0 and/or 1_0, or for configured grant PUSCH based transmission, nSCID=0. For DSCH and/or PUSCH which is scheduled by non-fallback downlink control information (DCI), e.g., DCI format 0_1, 0_2 and/or 1_1, 1_2, nSCIDcan be dynamically indicated by the DCI.

NID0,NID1
can be configured by higher layers via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signalling. A default value

NIDnSCID=NIDcell,
where

NIDcell
is the physical cell ID.

In one example, ƒ(l)=l, the reference signal can be initialized as:

cinit=(217⁢(l+1)⁢(2⁢NIDnSCID+1)+2⁢NIDnSCID+nSCID)⁢mod⁢231

In another example, ƒ(l)=mod(l, N), the reference signal can be initialized as:

cinit=(217⁢(mod⁡(l,N)+1)⁢(2⁢NIDnSCID+1)+2⁢NIDnSCID+nSCID)⁢mod⁢231

Note that in the equation, N can be predefined in the specification, e.g., N=2n, and n is a positive integer or configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling.

Yet in another example,

f⁡(l)=⌊lN⌋,
the reference signal can be initialized as:

cinit=(217⁢(⌊lN⌋+1)⁢(2⁢NIDnSCID+1)+2⁢NIDnSCID+nSCID)⁢mod⁢231

In another embodiment multiple DM-RS ports, each corresponding to a MIMO layer, can be multiplexed in each DM-RS symbol. In one example, a comb-2 (or comb-3) resource mapping, with DM-RS sequences from the same ports occupying alternate (or every third) REs in PRB can be used to multiplex 2 (or 3) DM-RS ports, one in each comb. Additionally, code division multiplexing of two DM-RS ports can be achieved within each comb by using orthogonal cover codes. For the case when more than one DM-RS port is multiplexed within a DM-RS symbol, the initialization of the Gold sequence can be port or comb specific e.g.,

cinit=(217⁢(f⁡(l)+1)⁢(2⁢NIDnSCID+1)+217⁢g⁡(λ)+2⁢NIDnSCIDλ+nSCIDλ)⁢mod⁢231where nSCIDλ∈{0,1} changes as a function of the comb index (or CDM group index) λ∈{0,1,2} and the function g(λ) is a function of λ. As an example, the function can be:
g(λ)=└λ/2┘OR we can have the function:g(λ)=λ, for λ∈0,1,2.

For reference signals including CSI-RS, TRS, PT-RS, SRS, the initialization seed of reference signal can be given by:
cinit=(217(ƒ(l)+l+1)(2NID+1)+2NID)mod 231

Where NIDcan be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling. Note that ƒ(l) can be generated in the same manner as the aforementioned examples.

In another embodiment, when a ZC sequence is used for the reference signal generation, for group and sequence hopping, the root sequence can be generated as a function of symbol index.

In one example, the grouping and sequence hopping for ZC sequence generation for DMRS in Section 6.3.2.2 in TS38.211 [1] can be updated as shown below:if group hopping is enabled and sequence hopping is disabled

fgh=(∑m=07⁢2m⁢c⁡(8·f⁡(l)+m))⁢mod⁢30⁢v=0where the pseudo-random sequence c(i) is defined by clause 5.2.1 and shall be initialized with

cinit=⌊nIDRS/30⌋
at the beginning of each radio frameif sequence hopping is enabled and group hopping is disabled fgh=0

v={c⁡(f⁡(l))if⁢MZC≥6⁢NscRB0otherwisewhere the pseudo-random sequence c(i) is defined by clause 5.2.1 and shall be initialized with

cinit=nIDRS
at the beginning of each radio frame.

Note that similarly, ƒ(l) can be generated same as aforementioned examples.

When cyclic shift hopping is applied for the ZC sequence generation, cyclic shift can be defined as a function of symbol index. In one example, the cyclic shift for ZC sequence generation for DMRS in Section 6.3.2.2 in TS38.211 [1] can be updated as shown below:

The function ncs(l) is given by

ncs(l)=∑m=072m⁢c⁡(Bf⁡(l)+m)

where the pseudo-random sequence c(i) is defined by clause 5.2.1. The pseudo-random sequence generator shall be initialized with cinit=nID, where nIDis given by the higher-layer parameter hoppingId if configured, otherwise nID=NIDcell.

Note that ƒ(l) can be generated the same as in the aforementioned examples.

In another embodiment, for PUSCH transmission with 1, 2, 3 or 4 PRBs, sets of K binary computer generated sequences (CGS) modulated by pi/2 BPSK can be used where K∈{15, 30}. Alternately, CGS sequence generated from M-PSK constellation in the time domain with M∈{4,8,16}. For CGS sequences, group hopping based on symbol index, where the root sequence is chosen from the set of K sequences can be used as mentioned in the previous examples.

In another example of using CGS sequences, complementary CGS can be used wherein for every pair of DM-RS symbols, a pair of pre-defined complementary sequences are used such that the joint autocorrelation of the sequence pair is ideal or almost ideal. When complementary sequence pairs are used and uniform spacing of 0 OFDM symbols between any two DM-RS symbols are assumed, grouping and sequence hopping for sequence generation for DMRS in Section 6.3.2.2 in TS38.211 [1] can be updated as shown below such that the hopping occurs over every pair of DM-RS symbols:if group hopping is enabled and sequence hopping is disabled

fgh=(∑m=07⁢2m⁢c⁡(8·f⁡(⌈l-g2⋆g⌉)+m))⁢mod⁢30⁢v=0where the pseudo-random sequence c(i) is defined by clause 5.2.1 and shall be initialized with

cinit=⌊nIDRS/30⌋
at the beginning of each radio frame, g is the gap in OFDM symbols between any two DM-RS symbols.

In another embodiment for DMRS sequence generation, the symbol index can be defined with respect to the starting symbol of scheduled PDSCH and/or PUSCH transmission. In another option, the symbol index can be defined with respect to the starting or ending symbol of scheduling PDCCH or the starting or ending symbol of CORESET which includes the scheduling PDCCH.

Note in case of cross-numerology scheduling where different numerologies are employed for scheduling PDCCH and scheduled PDSCH and/or PUSCH, the symbol index is defined in accordance with the scheduled PDSCH and/or PUSCH transmission. In particular, l=0 may correspond to the last symbol index of PDSCH and/or PUSCH which overlaps with the last symbol of PDCCH.

In one example, when Gold sequence with pi/2 BPSK modulation is applied for the reference signal generation, initialization seed of sequence generation of DMRS can be defined as:

cinit=(217⁢(l+1)⁢(2⁢NIDnSCID+1)+2⁢NIDnSCID+nSCID)⁢mod⁢231

Where l is the symbol index of DMRS symbol with respect to the ending symbol of corresponding PDCCH.

In another embodiment, the DM-RS sequence generation doesn't depend on the OFDM symbol index, e.g. l=0 in the aforementioned equations.

As a further extension, reference signal generation may not be defined as a function of symbol index.

DMRS Pattern for Slot-Less Operation

For slot-less operation, it is possible that the number of symbols allocated for data transmission, including physical downlink shared channel (PDSCH) and/or physical uplink shared channel (PUSCH), can be relatively large. For instance, the date transmission duration can span larger than 14 symbols. In this case, the DMRS pattern as defined in NR Rel-15 may not be directly reused. To resolve this issue, certain design changes need to be considered for DMRS pattern of data transmission when slot-less operation is employed for systems operating above 52.6 GHz.

Embodiments of DMRS pattern of data transmission for slot-less operation are provided as follows:

In one embodiment, front-loaded DMRS is used for slot-less operation. Further, additional DMRS symbol(s) can be configured by higher layers via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signaling or dynamically indicated in the downlink control information (DCI) or a combination thereof.

In one option, a set of positions regarding additional DMRS symbols can be predefined in the specification or configured by higher layers. Further, one field in the DCI may be dynamically indicated which position from the set of the position for additional DMRS symbols. For example, RRC signaling can be used to configure multiple additional DM-RS patterns and MAC-CE signaling can then be used to down-select from these patterns to form a sub-set of patterns and finally dynamic signaling using a DCI field can indicate of the down-selected patterns.

In another option, 1-bit indicator can be configured by higher layers or dynamically indicated in the DCI to indicate whether additional symbols are employed for the transmission of PDSCH and/or PUSCH. More specifically, bit “0” may indicate that only front-loaded DMRS is employed while bit “1” may indicate that front-loaded DMRS and additional DMRS symbols are employed for the PDSCH and/or PUSCH transmission. Note that in this case, additional DMRS symbols may be configured by higher layers.

In another embodiment, uniformly distributed DMRS symbols can be employed for the PDSCH and PUSCH transmission. In one option, the gap between first symbol of front-loaded DMRS symbol(s) and additional symbol(s), as well as between additional symbol(s) can be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signaling or dynamically indicated in the DCI or a combination thereof. Based on the gap between the DMRS symbols and length of PDSCH and/or PUSCH transmission, UE can derive the additional DMRS symbol position.

In another option, the number of DMRS symbols including front-loaded DMRS symbol can be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signaling or dynamically indicated in the DCI or a combination thereof. Based on the total number of DMRS symbols and length of PDSCH and/or PUSCH transmission, UE can derive the additional DMRS symbol position.

FIG.3illustrates one example of a uniform DMRS pattern for slot-less operation. In the example, 4 DMRS symbols are associated with the PDSCH transmission. Further, the gap between DMRS symbols is 7 symbols, which can be configured by higher layers via RRC signaling.

In another embodiment, in case of single PDSCH scheduling with one or more code blocks (CB) or code block groups (CBG) or multiple PDSCH scheduling, it is expected that one CB or CBG in case of single PDSCH scheduling or one PDSCH in case of multiple PDSCH scheduling is aligned with the symbol boundary. In this case, the starting symbol and length indicator value (SLIV) of first CB/CBG or PDSCH can be indicated in the DCI for scheduling PDSCH. As a further extension, the number of symbols or length of the CB/CBG or PDSCH transmission can be same during PDSCH transmission.

For DMRS associated with PDSCH transmission, DMRS is allocated independent of SLIV for each CB/CBG or PDSCH transmission. More specifically, DMRS symbols are configured first during PDSCH transmission and then CB/CBG or PDSCH is mapped in accordance with the indicated SLIV after DMRS symbols are mapped.

Note that for this option, transport block size (TBS) for one CBG or PDSCH can be derived in accordance with SLIV, without considering the DMRS overhead.

In one option, DMRS symbols are allocated outside the SLIV for each CB/CBG or PDSCH. Further, the gap between DMRS symbols can be k*length which is indicated by SLIV, where k can be predefined in the specification, configured by higher layers via RMSI (SIB1), OSI or RRC signaling, or can be derived based on the length which is indicated by SLIV and the maximum duration of PDSCH or PUSCH if uniform DMRS pattern is employed. In one example, k=1, which indicates that DMRS symbols are inserted before each CB/CBG or PDSCH transmission.

FIG.4illustrates one example of DMRS pattern for slot-less operation when DMRS symbols are allocated outside the SLIV for each CB/CBG or PDSCH. In the example, each CBG spans 4 symbols. The first DMRS symbol is located before the first CBG, or CBG #0. The gap between the first and second DMRS symbol is 8 symbols or 2 times of the length which is indicated by SLIV, i.e., k=2.

In another option, DMRS symbols can be allocated inside the SILV for each CB/CBG or PDSCH. Further, the gap between DMRS symbols can be configured by higher layers via RMSI(SIB1), OSI or RRC signalling or can be derived based on the maximum duration of PDSCH or PUSCH if uniform DMRS pattern is employed. Note that when DMRS symbols collide with CB/CBG or PDSCH, the impacted CB/CBG or PDSCH continues to be mapped and spans the number of symbols or length which is indicated by SLIV.

FIG.5illustrates one example of DMRS pattern for slot-less operation when DMRS symbols can be allocated inside the SLIV for each CB/CBG or PDSCH. In the example, each CBG spans 4 symbols. The first DMRS symbol is located before the first CBG, or CBG #0. The gap between the first and second DMRS symbol is 6 symbols. In this case, the second DMRS symbol collides with CBG #1. Note that CBG #1 continues to be mapped and spans 4 symbols.

In another embodiment, the gap between DMRS may be aligned with the length of symbol group. Note that the symbol group or a number of symbols within a symbol group can be viewed as basic scheduling unit or resource allocation unit for PDSCH and/or PUSCH transmission. Further, the length of symbol group can be predefined in the specification or configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signaling. For instance, when the length of symbol group is configured as 7, the gap between DMRS can be 7. In other words, DMRS symbols are inserted at the beginning of each symbol group for PDSCH and/or PUSCH transmission.

In another embodiment, the DM-RS is transmitted every N-th group of PDSCH/PUSCH symbols, where N can be indicated by higher layer or by DCI or a combination thereof. The group of OFDM symbols can be used to determine code-block segmentation.

In another embodiment, for PDSCH carrying RMSI, the gap between DMRS symbols or total number of DMRS symbols can be predefined in the specification. In one example, the gap between DMRS symbols can be fixed to 7. In another option, a set of the gap values between or total number of DMRS symbols can be predefined in the specification or configured by MSI. Further, one field in the DCI may be used to indicate one value from the set of the gap values or the total number of DMRS symbols to determine the DMRS symbol position, respectively.

For PDSCH carrying OSI or SIB or common control message including random access response (RAR) and paging, or for data transmission scheduled by fallback DCI or DCI format 1_0 or 0_0, the gap between DMRS symbols or total number of DMRS symbols can be directly configured by RMSI. In another option, a set of the gap values between or total number of DMRS symbols can be configured by RMSI. Further, one field in the DCI may be used to indicate one value from the set of the gap values or the total number of DMRS symbols to determine the DMRS symbol position, respectively.

Further, for data transmissions scheduled by non-fallback DCI or DCI format 1_1, 1_2, 0_1 or 0_2, the gap between DMRS symbols or total number of DMRS symbols can be configured by RRC signaling. In another option, a set of the gap values between DMRS symbols or total number of DMRS symbols can be configured by RRC signaling. Further, one field in the DCI may be used to indicate one value from the set of the gap values or the total number of DMRS symbols to determine the DMRS symbol position, respectively.

Note that the configuration, including the set of the gap values, may be separately configured for PDSCH and PUSCH.

In another embodiment, when a DMRS symbol overlaps with rate-matched resource, e.g., control resource set (CORESET) for physical downlink control channel (PDCCH) transmission, the DMRS symbol is shifted to the first data symbol after the rate-matched resource. Note that rate-matched resource indicates the resource where PDSCH and/or PUSCH is rate-matched around and DM-RS overlap with such resources is not allowed.

FIG.6illustrates one example of a DMRS pattern when colliding with rate-matched resources. In the figure, PDSCH is rate-matched around the CORESET and third DMRS symbol overlaps with the CORESET for PDCCH transmission. In this case, third DMRS symbol is shifted after the CORESET.

Note that the above embodiments can be extended to cases when a double-symbol DMRS is used for DMRS transmission.

In another embodiment, a non-uniform DMRS pattern can be employed for the transmission of PDSCH and/or PUSCH. In one option, to allow the receiver to perform timing/frequency offset tracking, a first gap with smaller value can be used between a first and second DMRS symbol. Further, a second gap with larger value can be used between the remaining DMRS symbols. Note that the first and second gap can be predefined in the specification or configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signaling, which can be similar to the aforementioned embodiments.

FIG.7illustrates one example of a non-uniform DMRS pattern for slot-less operation. In the example, 5 DMRS symbols are associated with the PDSCH transmission. Further, the first gap between the first and second DMRS symbols is 2 symbols, and the second gap between the remaining DMRS symbols is 7 symbols, which can be configured by higher layers via RRC signaling.

FIG.8illustrates a function block diagram of a communication station in accordance with some embodiments. In some embodiments, communication station may be suitable for use as a user equipment (UE) or a node B (gNB, eNB) configured for operation in a 5G or 6G cellular network. The communication station800may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.

The communication station800may include communications circuitry802and a transceiver810for transmitting and receiving signals to and from other communication stations using one or more antennas801. The communications circuitry802may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station800may also include processing circuitry806and memory808arranged to perform the operations described herein. In some embodiments, the communications circuitry802and the processing circuitry806may be configured to perform operations detailed in the above figures, diagrams, and flows.

In accordance with some embodiments, the communications circuitry802may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry802may be arranged to transmit and receive signals. The communications circuitry802may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry806of the communication station800may include one or more processors. In other embodiments, two or more antennas801may be coupled to the communications circuitry802arranged for sending and receiving signals. The memory808may store information for configuring the processing circuitry806to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory808may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory808may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

In some embodiments, the communication station800may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

In some embodiments, the communication station800may include one or more antennas801. The antennas801may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.

In some embodiments, the communication station800may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

Although the communication station800is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station800may refer to one or more processes operating on one or more processing elements.

The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.