Patent Description:
Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

<CIT> relates to the usage of dynamic cyclic prefix (CP) lengths in wireless communications. For example, the UE may determine a first CP length for a first symbol of a plurality of symbols and determine a second CP length, different from the first CP length, for a second symbol of the plurality of symbols. The symbols may be in the same TTI or different TTIs.

<CIT> relates to techniques for providing flexible sub-carrier spacing and symbol duration allocation according to different multiple access block (MAB) types. A plurality of MAB types are defined having frequency-time slots with at least one of the MAB types having at least one of a different sub-carrier spacing, a different useful symbol length and a different cyclic prefix length.

<CIT> relates to a UE forming a first symbol sequence comprising a first cyclic prefix, a first useful portion, and a first cyclic postfix for the reference signal. Also, the UE forms a second symbol sequence comprising a second cyclic prefix, a second useful portion, and a second cyclic postfix for the data. The first and second cyclic prefixes may have a first length of P<NUM>.

<CIT> discloses further forms of data signals that may be sent in a first and second type of data access. A first specified number of OFDM samples is equal to the second specified number of OFDM samples, and so the length D<NUM> is equal to the length D<NUM>, while the total length of the first signal, that is, (D<NUM> + L<NUM> + S<NUM>), is equal to the length of one of the time slots, and the total length of the second signal, that is, (O<NUM> + L<NUM>), is also equal to the length of one of the time slots.

<NPL>, discloses multiplexing of NCP and ECP symbols within a slot, wherein ECP UL symbols are aligned either at the end of the slot or with regard to NCP DL symbols.

For example, a fifth generation (<NUM>) wireless communications technology (which can be referred to as <NUM> new radio (<NUM> NR)) is envisaged to expand and support diverse usage scenarios and applications with respect to current mobile network generations. In an aspect, <NUM> communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information. As the demand for mobile broadband access continues to increase, however, further improvements in <NUM> communications technology and beyond may be desired.

Further improvements are facilitated by the invention recited in the independent claims. Advantageous embodiments area subject to the dependent claims.

The described features generally relate to supporting multiple cyclic prefix (CP) types in wireless communications. As described, nodes in a wireless network, such as a fifth generation (<NUM>) new radio (NR) configured network, can be configured with different CP types for different links, different signals transmitted over the different links, etc. In an example, a node can be configured to communicate (e.g., transmit or receive) signals with one or more other nodes using a different CP type for each of at least two signals, where using the different CP type may result in a different timeline for the communications as well. For example, a base station can transmit one or more broadcast signals using a normal CP and can multiplex, with the one or more broadcast signals, one or more unicast signals that use an extended CP. In this example, a user equipment (UE) or other node can receive the one or more broadcast signals and/or unicast signals, which can be multiplexed (e.g., in a given slot), and may each use a different CP type. In an example, a slot format configuration for the normal CP and extended CP communications can be coordinated to provide a desirable level of compatibility to minimize conflicting communication directions (e.g., uplink vs. downlink) between symbols in the slot.

For example, NR UEs can be semi-statically configured with a specific numerology (e.g., numerology can refer to a CP overhead and/or subcarrier spacing (SCS)), where NR can support extended CP at least for <NUM> kilohertz (kHz) SCS. In this configuration, for example, one slot can include <NUM> orthogonal frequency division multiplexing (OFDM) symbols. NR can also support normal CP where one slot can include <NUM> OFDM symbols. Additionally, in NR, uplink and downlink can be configured with different CP types (e.g., normal or extended CP). Additional configurations for using CP may be desired.

In addition, slot format configuration for wireless networks such as <NUM> NR can be semi-static and group-specific. Each slot can include a plurality of symbols, where each symbol can be configured for either downlink, uplink, or flexible communications. The slots configured for flexible communications can be dynamically reconfigured as downlink or uplink in a dynamic and/or UE-specific manner (e.g., by using group common physical downlink control channel (GC-PDCCH) to dynamically configure the flexible symbols). Additionally, for example, CP type or length (e.g., normal CP, extended CP, etc.) configuration can be semi-static and UE-specific, and different CP types can be associated with different timelines (e.g., a different number of symbols in a similar length slot, where a timeline can correspond to the number of symbols in a slot, a corresponding duration for the symbols or slot, etc.). In one specific example, some signals, such as primary synchronization signal (PSS), secondary synchronization signal (SSS), multicast physical downlink shared channel (PDSCH), etc., may be configured to use normal CP while other unicast transmissions maybe configured with extended CP in the same slot. This can result in multiplexing of normal CP and extended CP communications in the same slot. Normal CP slot formats can be based on using a first number of OFDM symbols (e.g., <NUM>) per slot, whereas extended CP slot formats can be based on using a second number of OFDM symbols (e.g., <NUM>) per slot, which can result in different communication timelines per slot.

Aspects described herein relate to multiplexing normal CP and extended CP communications, which may include adapting a slot format to use with one CP type based on the slot format defined for another CP type, where the slot formats may be based on different timelines. Adapting the slot format using concepts described herein can lessen or minimize conflict in transmission direction between symbols of the slot formats that occur at the same or similar times. In one example, network nodes can derive the slot format for one CP type based on the slot format for another CP type and/or based on associated timelines of the CP types. In another example, a network node (e.g., the base station) can configure another network node (e.g., the UE) with the slot formats to use for each CP type (e.g., by specifying an indicator representing the slot format, such as a slot format indicator (SFI) in the configuration), where the slot formats may exhibit some level of compatibility between the types of configured symbols in the slot. In any case, the network nodes can be accordingly configured to communicate multiplexed signals that are based on different CP types and/or associated with different corresponding timelines while decreasing conflict in communication direction between symbols on the multiple timelines.

As used in this application, the terms "component," "module," "system" and the like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.

Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" may often be used interchangeably. IS-<NUM> Releases <NUM> and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-<NUM> (TIA-<NUM>) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to <NUM> networks or other next generation communication systems).

<FIG> illustrates an example of a wireless communication system <NUM> in accordance with various aspects of the present disclosure. The wireless communication system <NUM> may include one or more base stations <NUM>, one or more UEs <NUM>, and a core network <NUM>. The core network <NUM> may provide user authentication, access authorization, tracking, internet protocol (IP) connectivity, and other access, routing, or mobility functions. The base stations <NUM> may interface with the core network <NUM> through backhaul links <NUM> (e.g., S1, etc.). The base stations <NUM> may perform radio configuration and scheduling for communication with the UEs <NUM>, or may operate under the control of a base station controller (not shown). In various examples, the base stations <NUM> may communicate, either directly or indirectly (e.g., through core network <NUM>), with one another over backhaul links <NUM> (e.g., X2, etc.), which may be wired or wireless communication links.

The base stations <NUM> may wirelessly communicate with the UEs <NUM> via one or more base station antennas. In some examples, base stations <NUM> may be referred to as a network entity, a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNodeB (eNB), Home NodeB, a Home eNodeB, gNB (e.g., in <NUM> NR) or some other suitable terminology. The geographic coverage area <NUM> for a base station <NUM> may be divided into sectors making up only a portion of the coverage area (not shown). The wireless communication system <NUM> may include base stations <NUM> of different types (e.g., macro or small cell base stations). There may be overlapping geographic coverage areas <NUM> for different technologies.

In some examples, the wireless communication system <NUM> may be or include a Long Term Evolution (LTE) or LTE-Advanced (LTE-A) network. The wireless communication system <NUM> may also be a next generation network, such as a <NUM> wireless communication network. In LTE/LTE-A networks, the term evolved node B (eNB) (e.g., or gNB in <NUM> networks), etc. may be generally used to describe the base stations <NUM>, while the term UE may be generally used to describe the UEs <NUM>. The wireless communication system <NUM> may be a heterogeneous LTE/LTE-A network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB or base station <NUM> may provide communication coverage for a macro cell, a small cell, or other types of cell. The term "cell" is a 3GPP term that can be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs <NUM> with service subscriptions with the network provider.

A small cell may include a lower-powered base station, as compared with a macro cell, that may operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. An eNB for a macro cell may be referred to as a macro eNB, gNB, etc. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB.

The communication networks that may accommodate some of the various disclosed examples may be packet-based networks that operate according to a layered protocol stack and data in the user plane may be based on the IP. A packet data convergence protocol (PDCP) layer can provide header compression, ciphering, integrity protection, etc. of IP packets. A radio link control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A media access control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use HARQ to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE <NUM> and the base stations <NUM>. The RRC protocol layer may also be used for core network <NUM> support of radio bearers for the user plane data. At the physical (PHY) layer, the transport channels may be mapped to physical channels.

The UEs <NUM> may be dispersed throughout the wireless communication system <NUM>, and each UE <NUM> may be stationary or mobile. A UE <NUM> may also include or be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, an entertainment device, a vehicular component, or the like. A UE may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, relay base stations, and the like.

The communication links <NUM> shown in wireless communication system <NUM> may carry UL transmissions from a UE <NUM> to a base station <NUM>, or downlink (DL) transmissions, from a base station <NUM> to a UE <NUM>. The downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions. Each communication link <NUM> may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies) modulated according to the various radio technologies described above. Each modulated signal may be sent on a different sub-carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. The communication links <NUM> may transmit bidirectional communications using frequency division duplex (FDD) (e.g., using paired spectrum resources) or time division duplex (TDD) operation (e.g., using unpaired spectrum resources). Frame structures may be defined for FDD (e.g., frame structure type <NUM>) and TDD (e.g., frame structure type <NUM>).

In aspects of the wireless communication system <NUM>, base stations <NUM> or UEs <NUM> may include multiple antennas for employing antenna diversity schemes to improve communication quality and reliability between base stations <NUM> and UEs <NUM>. Additionally or alternatively, base stations <NUM> or UEs <NUM> may employ multiple input multiple output (MIMO) techniques that may take advantage of multi-path environments to transmit multiple spatial layers carrying the same or different coded data.

Wireless communication system <NUM> may support operation on multiple cells or carriers, a feature which may be referred to as carrier aggregation (CA) or multi-carrier operation. A carrier may also be referred to as a component carrier (CC), a layer, a channel, etc. The terms "carrier," "component carrier," "cell," and "channel" may be used interchangeably herein. A UE <NUM> may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation.

In aspects of the wireless communication system <NUM>, one or more of the base stations <NUM> may include a multiplexing component <NUM> for multiplexing communications using different CP types for communication according to different timelines, which may be based on a length associated with the CP type. One or more of the UEs <NUM> may include a communicating component <NUM> for receiving and decoding multiplexed communications that are based on the different CP types. Additionally, in some examples, the one or more UEs <NUM> may additionally or alternatively include a multiplexing component <NUM> to multiplex communications of different CP types, according to aspects described herein, and/or the one or more base stations <NUM> may include a communicating component <NUM> for receiving and decoding the multiplexed communications. Moreover, in an example, different UEs <NUM> may include the multiplexing component <NUM> and/or communicating component <NUM> to facilitate UE-to-UE communications, etc..

Turning now to <FIG>, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below in <FIG> are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by a specially-programmed processor, a processor executing specially-programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions.

Referring to <FIG>, a block diagram <NUM> is shown that includes a portion of a wireless communications system having multiple UEs <NUM> in communication with a base station <NUM> via communication links <NUM>, where the base station <NUM> is also connected to a network <NUM>. The UEs <NUM> may be examples of the UEs described in the present disclosure that are configured to receive and decode multiplexed communications of different CP types (e.g., communications that may overlap in a time domain). Moreover the base station <NUM> may be an example of the base stations described in the present disclosure (e.g., eNB, gNB, other types of access points, etc. providing one or more macrocells, small cells, etc.) that are configured to multiplex and transmit communications that use different CP types that may correspond to different communication timelines.

In an aspect, the base station in <FIG> may include one or more processors <NUM> and/or memory <NUM> that may operate in combination with a multiplexing component <NUM> to perform the functions, methods (e.g., method <NUM> of <FIG>), etc. presented in the present disclosure. In accordance with aspects of the present disclosure, the multiplexing component <NUM> may include one or more components for multiplexing communications having different CP types (and thus perhaps different communication timelines). In an example, multiplexing component <NUM> may include a slot format indicating component <NUM> for indicating a slot format associated with a first CP type, and/or a slot format deriving component <NUM> for deriving or interpolating (and/or additionally indicating) a second slot format associated with a second CP type.

The one or more processors <NUM> may include a modem <NUM> that uses one or more modem processors. The various functions related to the multiplexing component <NUM>, and/or its sub-components, may be included in modem <NUM> and/or processor <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a transceiver processor associated with transceiver <NUM>, or a system-on-chip (SoC). In particular, the one or more processors <NUM> may execute functions and components included in the multiplexing component <NUM>. In another example, multiplexing component <NUM> may operate at one or more communication layers, such as a physical layer (e.g., layer <NUM> (L1)), media access control (MAC) layer (e.g., layer <NUM> (L2)), PDCP layer or RLC layer (e.g., layer <NUM> (L3)), etc., to multiplex communications and/or transmit an indication of a slot format for one or more CP types, etc..

In some examples, the multiplexing component <NUM> and each of the sub-components may comprise hardware, firmware, and/or software and may be configured to execute code or perform instructions stored in a memory (e.g., a computer-readable storage medium, such as memory <NUM> discussed below). Moreover, in an aspect, the base station <NUM> in <FIG> may include a radio frequency (RF) front end <NUM> and transceiver <NUM> for receiving and transmitting radio transmissions to, for example, UEs <NUM>. The transceiver <NUM> may coordinate with the modem <NUM> to receive signals for, or transmit signals generated by, the multiplexing component <NUM> to the UEs. RF front end <NUM> may be connected to one or more antennas <NUM> and can include one or more switches <NUM>, one or more amplifiers (e.g., power amplifiers (PAs) <NUM> and/or low-noise amplifiers <NUM>), and one or more filters <NUM> for transmitting and receiving RF signals on uplink channels and downlink channels, transmitting and receiving signals, etc. In an aspect, the components of the RF front end <NUM> can connect with transceiver <NUM>. The transceiver <NUM> may connect to one or more of modem <NUM> and processors <NUM>.

The transceiver <NUM> may be configured to transmit (e.g., via transmitter (TX) radio <NUM>) and receive (e.g., via receiver (RX) radio <NUM>) wireless signals through antennas <NUM> via the RF front end <NUM>. In an aspect, the transceiver <NUM> may be tuned to operate at specified frequencies such that the base station <NUM> can communicate with, for example, UEs <NUM>. In an aspect, for example, the modem <NUM> can configure the transceiver <NUM> to operate at a specified frequency and power level based on the configuration of the base station <NUM> and communication protocol used by the modem <NUM>.

The base station <NUM> in <FIG> may further include a memory <NUM>, such as for storing data used herein and/or local versions of applications or multiplexing component <NUM> and/or one or more of its sub-components being executed by processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a computer-readable storage medium that stores one or more computer-executable codes defining multiplexing component <NUM> and/or one or more of its sub-components. Additionally or alternatively, the base station <NUM> may include a bus <NUM> for coupling one or more of the RF front end <NUM>, the transceiver <NUM>, the memory <NUM>, or the processor <NUM>, and to exchange signaling information between each of the components and/or sub-components of the base station <NUM>.

In an aspect, the UE <NUM> in <FIG> may include one or more processors <NUM> and/or memory <NUM> that may operate in combination with a communicating component <NUM> to perform the functions, methods (e.g., method <NUM> of <FIG>), etc., presented in the present disclosure. In accordance with aspects of the present disclosure, the communicating component <NUM> may include one or more components for receiving and decoding multiplexed communications having different CP types. For example, communicating component <NUM> can include a slot format determining component <NUM> for determining a slot format for a received communication related to a first CP type, and/or a slot format deriving component <NUM> for deriving a slot format for a received communications related to a second CP type. In an example, communicating component <NUM> can receive and decode communications received according to the first and second CP types.

The one or more processors <NUM> may include a modem <NUM> that uses one or more modem processors. The various functions related to the communicating component <NUM>, and/or its sub-components, may be included in modem <NUM> and/or processor <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a transceiver processor associated with transceiver <NUM>, or a system-on-chip (SoC). In particular, the one or more processors <NUM> may execute functions and components included in the communicating component <NUM>. In another example, communicating component <NUM> may operate at one or more communication layers, such as physical layer or L1, MAC layer or L2, a PDCP/RLC layer or L3, etc., to receive communications having different CP types, receive slot format indicators for communications related to the one or more of the different CP types, etc..

In some examples, the communicating component <NUM> and each of the sub-components may comprise hardware, firmware, and/or software and may be configured to execute code or perform instructions stored in a memory (e.g., a computer-readable storage medium, such as memory <NUM> discussed below). Moreover, in an aspect, the UE <NUM> in <FIG> may include an RF front end <NUM> and transceiver <NUM> for receiving and transmitting radio transmissions to, for example, base stations <NUM>. The transceiver <NUM> may coordinate with the modem <NUM> to receive signals that include packets (e.g., and/or one or more related PDUs). RF front end <NUM> may be connected to one or more antennas <NUM> and can include one or more switches <NUM>, one or more amplifiers (e.g., PAs <NUM> and/or LNAs <NUM>), and one or more filters <NUM> for transmitting and receiving RF signals on uplink channels and downlink channels. In an aspect, the components of the RF front end <NUM> can connect with transceiver <NUM>. The transceiver <NUM> may connect to one or more of modem <NUM> and processors <NUM>.

The transceiver <NUM> may be configured to transmit (e.g., via transmitter (TX) radio <NUM>) and receive (e.g., via receiver (RX) radio <NUM>) wireless signals through antennas <NUM> via the RF front end <NUM>. In an aspect, the transceiver <NUM> may be tuned to operate at specified frequencies such that the UE <NUM> can communicate with, for example, base stations <NUM>. In an aspect, for example, the modem <NUM> can configure the transceiver <NUM> to operate at a specified frequency and power level based on the configuration of the UE <NUM> and communication protocol used by the modem <NUM>.

The UE <NUM> in <FIG> may further include a memory <NUM>, such as for storing data used herein and/or local versions of applications or communicating component <NUM> and/or one or more of its sub-components being executed by processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or processor <NUM>, such as RAM, ROM, tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a computer-readable storage medium that stores one or more computer-executable codes defining communicating component <NUM> and/or one or more of its sub-components. Additionally or alternatively, the UE <NUM> may include a bus <NUM> for coupling one or more of the RF front end <NUM>, the transceiver <NUM>, the memory <NUM>, or the processor <NUM>, and to exchange signaling information between each of the components and/or sub-components of the UE <NUM>.

<FIG> illustrates a flow chart of an example of a method <NUM> for multiplexing (e.g., by a base station) communications having different CP types. In an example, a UE can also perform the functions described in method <NUM> and/or include the corresponding components of <FIG> to multiplex communications having different CP types.

At Block <NUM>, a first slot format for a first CP type can be determined. In an aspect, slot format indicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, multiplexing component <NUM>, etc., determines a first slot format for a first CP type. For example, slot format indicating component <NUM> can select the first slot format based on one or more parameters related to communicating with a UE <NUM>, such as a signal strength or quality, a load at the base station <NUM>, a buffer status report from the UE <NUM> indicating an amount of data to transmit, a quality of service (QoS), bit rate, or other performance metric for one or more links or bearers, etc. For example, the slot format may correspond to defining a number and/or pattern of symbols in a slot for a communication direction (e.g., downlink, uplink, etc.). The slot format also includes one or more flexible symbols that may be dynamically configured for downlink or uplink communications. In an example, a wireless technology, such as <NUM> NR, may define a number of slot formats that specify a number and/or pattern of downlink, uplink, or flexible symbols in a slot.

For example, <FIG> illustrates an example of slot formats <NUM>, <NUM> that are defined in <NUM> NR for normal CP. For example, slot format <NUM> includes three downlink symbols, followed by eight flexible symbols, followed by three uplink symbols, for a total of <NUM> symbols in the slot. In another example, slot format <NUM> includes two downlink symbols, followed by a flexible symbol, followed by four uplink symbols, followed by two downlink symbols, followed by a flexible symbol, followed by three uplink symbols for a total of <NUM> symbols in the slot. In an example, slot format indicating component <NUM> can select the slot format for a first CP type (e.g., normal CP) based on one or more slot formats defined in a wireless communication technology, such as <NUM> NR.

Optionally, at Block <NUM>, an indicator for the first slot format can be transmitted. In an aspect, slot format indicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, multiplexing component <NUM>, etc., can transmit the indicator of the first slot format. For example, slot format indicating component <NUM> can transmit the indicator to one or more UEs <NUM> by using an indicator in a configuration or related signaling, such as in downlink control information (DCI) in a downlink control channel (e.g., PDCCH), etc. Moreover, in an example, slot format indicating component <NUM> may determine and/or indicate a communication direction (e.g., downlink or uplink) for the flexible symbols of the slot in a separate configuration. As described, slot format indicating component <NUM> can determine and/or transmit the indicator semi-statically, dynamically, etc., as the selected format may be UE-specific, group-specific, etc. For example, slot format indicating component <NUM> can transmit a slot format or related indicator in a radio resource control (RRC) signal, a dedicated control channel communication, and/or the like. In one example, slot format indicating component <NUM> may indicate an initial slot format and may override the initial slot format with a new slot format in dynamic signaling.

At Block <NUM>, a second slot format for a second CP type is derived based on the first slot format. In an aspect, slot format deriving component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, multiplexing component <NUM>, etc., derives the second slot format for the second CP type based on the first slot format. As described further herein, this may include interpolating the second slot format from the first slot format such that one or more symbols are defined in the second slot format for downlink, uplink, flexible, etc. communications based on how symbols are defined in the first slot format. In another example, this may include selecting a slot format for the second CP type that is indicated as compatible with (or otherwise mapped to) the first slot format for the first CP type, and/or the like. In the latter example, the base station <NUM> can include (e.g., stored in memory <NUM>) a mapping between slot formats for the first CP type (e.g., normal CP) and slot formats for the second CP type (e.g., extended CP) that can be used to multiplex communications.

Moreover, for example, the CP types can have different numerologies, and can thus be associated with different timelines for communications. For example, in <NUM> NR, communication resources can be defined as a collection of frequency resources (e.g., multiple subcarriers) over a collection of time resources (e.g., multiple OFDM symbols). In an example, in <NUM> NR, a slot can be defined to include a plurality of OFDM symbols that each have a number of subcarriers determined based on a subcarrier spacing, and the number of OFDM symbols in the slot can be at least partially determined based on a CP type used for the slot (e.g., normal CP, extended CP, etc.) In an example, <NUM> NR can support OFDM symbol-level time division multiplexing of different CP types, as described herein. Allocation of OFDM symbols in each numerology or CP type can be based on a corresponding OFDM symbol grid, where the OFDM symbol grid can be defined per <NUM> millisecond (ms) duration and repeated every <NUM>.

For example, for a subcarrier spacing SCSNCP = <NUM>µNCP · <NUM>[kHz], a normal CP symbol grid can be defined as: <MAT> <MAT> <MAT> <MAT> In another example, for a subcarrier spacing SCSECP = <NUM>µECP · <NUM>[kHz], an extended CP symbol grid can be defined as <MAT> <MAT> <MAT> In <NUM> NR, for example, the same subcarrier spacing (SCS) can be assumed to be configured for different CP types (e.g., µNCP = µECP), but it can also be possible to configure different SCS for different CP types. In an example, uplink and downlink communications for either CP type can use different SCS within a slot, and/or the different CP types can use different SCS within a slot. In addition, sub-band level frequency division multiplexing of different CP types may be used. In any case, using symbol grids for normal CP and extended CP type communications, as defined above, to determine symbol alignment within a slot and corresponding slot formats can be desirable for coexistence between these signals in <NUM> NR and normal/extended CP LTE signals.

For example, because the different CP types may have different numbers of symbols per slot (e.g., and thus may be associated with different timelines for a given slot), the symbol boundaries may not align, and deriving slot formats that are compatible (or mostly compatible) in communication direction may be based on logic for resolving possible conflicts where a symbol for one CP type overlaps symbols for the other CP type that have different communication directions (e.g., downlink, uplink, flexible, etc.). In an example, slot format deriving component <NUM> derives slot format for the second CP type based on the slot format for the first CP type using this logic, or the slot formats may be associated in a configuration and the association may be based on the logic.

An example is shown in <FIG>, which illustrates slot formats <NUM>, <NUM> for normal CP and corresponding slot formats <NUM>, <NUM> for extended CP that may be defined as compatible with the slot formats <NUM>, <NUM>. As shown, slot formats <NUM>, <NUM> can be defined based on a numerology of <NUM> OFDM symbols per slot (e.g., for normal CP) and can correspond, respectively, to slot formats <NUM> and <NUM> defined in <NUM> NR. In addition, for example, slot formats <NUM>, <NUM> can be defined based on a numerology of <NUM> OFDM symbols per slot (e.g., for extended CP). In the depicted example, slot formats <NUM>, <NUM> can have some level of compatibility (or can be said to be compatible) such that at least some symbols in slot format <NUM> having a certain communication direction (e.g., downlink, uplink, or flexible) overlap, in a time domain, with at least some other symbols in slot format <NUM> having a similar communication direction. Similarly, slot formats <NUM>, <NUM> similarly have a level of compatibility. In an example, the slot formats <NUM>, <NUM> can be defined for <NUM> NR communication, and can be associated with one another, in a configuration, as compatible slot formats (and similarly slot formats <NUM>, <NUM>). In another example, however, slot format deriving component <NUM> can interpolate slot format <NUM> for extended CP based on the determined slot format determined and/or indicated by slot format indicating component <NUM>. The interpolation may be performed based on a set of rules, which may be configured at the base station <NUM> or UE <NUM>, provided to the UE <NUM> in a configuration from the base station <NUM>, and/or the like, for example. Using the rules for determining slot format(s), for example, can help to avoid severe intersymbol/inter-carrier interference between the communications.

<FIG> illustrates partial slot formats depicting examples of rules for determining communication direction for symbols in an extended CP slot format based on a determined or indicated normal CP slot format. For example, as shown at <NUM>, when two downlink symbols in the normal CP slot format overlap a symbol in the extended CP slot format, the symbol in the extended CP slot format is interpolated as a downlink symbol. For example, as shown at <NUM>, when two uplink symbols in the normal CP slot format overlap a symbol in the extended CP slot format, the symbol in the extended CP slot format is interpolated as an uplink symbol.

For example, when a downlink symbol and an adjacent flexible symbol in the normal CP slot format overlap a symbol in the extended CP slot format, the symbol in the extended CP slot format is interpolated as a flexible symbol, as shown at <NUM>. Similarly, for example, when an uplink symbol and an adjacent flexible symbol in the normal CP slot format overlap a symbol in the extended CP slot format, the symbol in the extended CP slot format is interpolated as a flexible symbol, as shown at <NUM>. In an example, rules for determining whether the symbol in the extended slot format is downlink/uplink or flexible may be based on one or more measureable criteria, such as a portion of the symbol in the normal CP slot format that overlaps the symbol in the extended CP slot format (e.g., the symbol in the extended CP format can interpolated as downlink/uplink where more of the downlink/uplink symbol in the normal CP slot format overlaps the symbol in the extended CP format than does the flexible symbol).

In another example, when a downlink symbol and an adjacent uplink symbol in the normal CP slot format overlap a symbol in the extended CP slot format, the symbol in the extended CP slot format can be interpolated as a downlink symbol as shown at <NUM>, an uplink symbol, as shown at <NUM>, or a reserved symbol (e.g., where a reserved symbol can indicate any transmitting or receiving over the symbol is forbidden), as shown at <NUM>. In an example, rules for determining whether the symbol in the extended slot format is downlink, uplink, or reserved may indicate or otherwise be based on one or more measureable criteria, such as a portion of the symbol in the normal CP slot format that overlaps the symbol in the extended CP slot format, an interference criteria, and/or the like. In any case, in a specific example, slot format deriving component <NUM> can derive slot format <NUM> from slot format <NUM>, and/or can derive slot format <NUM> based on slot format <NUM>, using the set of rules. In any case, the derived slot format for the second CP (e.g., extended CP) can have at least some level of compatibility with the first slot format for the first CP (e.g., normal CP) such that at least some overlapping symbols can have at least some portion of time with the same communication direction (or one or more reserved symbols over which communication is not allowed). This can allow transmissions from a base station (or from a UE) that are separately based on the first CP and the second CP to be multiplexed and/or otherwise coexist in a slot. In one example, the base station <NUM> (e.g., via multiplexing component <NUM>) can configure the UE <NUM> with the one or more rules, or some indication as to the one or more rules, (e.g., via RRC or higher layer signaling) to ensure the UE <NUM> can derive the second slot format based on the first slot format as well. In this example, the rules may be UE-specific, based on an indicated UE-capability (e.g., indicated via RRC or higher layer signaling), etc..

Referring back to <FIG>, optionally at Block <NUM>, an indicator for the second slot format can be transmitted. In an aspect, slot format deriving component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, multiplexing component <NUM>, etc., can transmit the indicator of the second slot format. For example, slot format deriving component <NUM> can transmit the indicator to one or more UEs <NUM> by using an indicator in a configuration or related signaling, such as in downlink control information (DCI) in a downlink control channel (e.g., PDCCH), a value map with values indicating a communication direction for each symbol in the second slot format, etc..

In method <NUM>, at Block <NUM>, a first communication based on the first CP type and a second communication based on the second CP type is multiplexed within a slot. In an aspect, multiplexing component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., multiplexes within the slot, the first communication based on the first CP type and the second communication based on the second CP type. As described, the first communication is prepared for transmission based on a first slot format and timeline associated with the first CP, such that the first communication can be prepared for transmission in a symbol with an appropriate communication direction (e.g., downlink for base station <NUM> transmissions or uplink for UE <NUM> transmissions). Similarly, the second communication is prepared for transmission based on a second slot format and timeline associated with the second CP, such that the second communication can be prepared for transmission in a symbol with an appropriate communication direction (e.g., downlink for base station <NUM> transmissions or uplink for UE <NUM> transmissions). The first and second communications are multiplexed for transmission in the same slot. In one specific example, the first and second communications may overlap in a time domain within the slot and their corresponding symbols may be associated with the same communication direction based on the defined slot formats.

In method <NUM>, at Block <NUM>, within the slot, the first communication is transmitted based on a first timeline and the second communication is transmitted based on a second timeline. In an aspect, multiplexing component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., transmits, within the slot, the first communication based on the first timeline and the second communication based on the second timeline. In this regard, the first communication and second communication can be transmitted in symbols of the first and second timelines, respectively, that can occur within the same slot. Additionally, as described, the base station <NUM> can include components to additionally receive a multiplexed first communication (based on a first CP type) and second communication (based on a second CP type) from a UE <NUM> within the slot.

In an example, transmitting the first and second communication at Block <NUM> may optionally include, at Block <NUM>, defining one or more time gaps between the first communication and the second communication. In an aspect, multiplexing component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can define the one or more time gaps between the first communication and the second communication. For example, multiplexing component <NUM> can define the one or more time gaps, during which communications can be prohibited, to somewhat align the first communication with the first timeline (e.g., with a symbol boundary of the first timeline) and/or the second communication with the second timeline (e.g., with a symbol boundary of the second timeline) to minimize occurrence of conflicting symbol directions in respective slot formats. An example is shown in <FIG>.

<FIG> illustrates an example of a timeline <NUM> for communicating based on a first timeline for a normal CP type (including <NUM> OFDM symbols) and a second timeline for an extended CP type (including <NUM> OFDM symbols). In this example, after transmitting extended CP (ECP) control <NUM> and ECP data <NUM> in the first three symbols of the extended CP timeline, multiplexing component <NUM> can define the time gap (e.g., guard time <NUM>) before transmitting normal CP (NCP) communications <NUM> to align the communications <NUM> at a fifth symbol of the NCP timeline, and NCP communications <NUM> at the seventh symbol. As shown, the time gap can include a fraction of an OFDM symbol in one timeline or the other such to align with the next OFDM symbol boundary. Similarly, multiplexing component <NUM> can define the time gap (e.g., guard time <NUM>) before transmitting additional ECP data <NUM> to align the ECP data <NUM> with the tenth symbol of the ECP timeline.

<FIG> illustrates a flow chart an example of a method <NUM> for receiving and/or decoding (e.g., by a UE) communications having different CP types. In an example, a base station can also perform the functions described in method <NUM> and/or include the corresponding components of <FIG> to receive and decode multiplexed communications having different CP types.

In method <NUM>, at Block <NUM>, a first slot format indicator is received. In an aspect, slot format determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., receives the first slot format indicator. For example, slot format determining component <NUM> can receive the first slot format indicator from a configuration, in a control channel communication (e.g., from a base station <NUM>), and/or the like. In one example, as described, the indicator may be a value indicated in a configuration, where the value may correspond to a slot format defined in <NUM> NR (e.g., slot format <NUM> or <NUM>, as shown in <FIG>). In another example, the indicator may include a value map where each value indicates whether a corresponding symbol in the slot is downlink, uplink, flexible, etc. As described, slot format determining component <NUM> can receive or otherwise determine the indicator semi-statically, dynamically, etc. (e.g., in RRC signaling, dedicated control signaling, etc.), as the selected format may be UE-specific, group-specific, etc..

In method <NUM>, at Block <NUM>, a first slot format for a first CP type is determined based on the first slot format indicator. In an aspect, slot format determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., determines the first slot format for the first CP type based on the first slot format indicator. For example, the slot format determining component <NUM> can determine a communication direction (e.g., downlink, uplink, flexible, etc.) for each symbol in a slot based on the slot format indicator. In addition, in an example, the slot format determining component <NUM> may determine a communication for the flexible symbols based on a separate configuration (e.g., from the base station <NUM>, etc.). The symbols can be aligned with a symbol grid corresponding to the first CP type (e.g., based on a number of symbols configured for the first CP type).

In method <NUM>, at Block <NUM>, a second slot format is derived. In an aspect, slot format deriving component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., derives the second slot format. For example, the slot format deriving component <NUM> derives the second slot format based on the first slot format (e.g., based on one or more rules as described with reference to <FIG> and <FIG>). In an example, in this regard, the base station <NUM> and the UE <NUM> can use the same or a similar set of rules, as described above, to derive the second slot format based on the first slot format to ensure the base station <NUM> and UE <NUM> derive the same slot formats. In one example, slot format deriving component <NUM> can receive the set of rules, or some indicator as to the set of rules, (e.g., via RRC or higher layer signaling) from the base station <NUM>. In an example, in this regard, the set of rules may be UE-specific and/or based on an indicated UE capability (e.g., indicated via RRC or higher layer signaling). In another example, slot format deriving component <NUM> can derive the second slot format based on a separate slot format indicator configured for the second slot format (e.g., received in a configuration from a base station <NUM>, which may include a value indicating the format, a value map indicating a communication direction for each symbol in the slot, etc.).

In addition, the first slot format relates to communications using a first CP type, and the second slot format relates to communications using a second CP type. Moreover, in this regard, the first slot format is based on a first timeline associated with the first CP type and the second slot format is based on a second timeline associated with the second CP type, where the first and second timelines are different based on having a different number of symbols per slot. The symbols can be aligned with a symbol grid corresponding to the second CP type (e.g., based on a number of symbols configured for the second CP type). As described, the symbol grids for the first and second CP types may not be aligned within a slot. In any case, the UE and base station can communicate based on the determined symbol locations and communication directions.

For example, this can include, at Block <NUM>, receiving a first communication according to a first timeline and/or first slot format based on a first CP type. In an aspect, communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., receives the first communication (e.g., a transmission from the base station <NUM>) according to a first timeline and/or first slot format based on a first CP type (e.g., based on determining the symbol is a downlink symbol for the first CP type). As described, the first slot format for the first CP type includes symbols with a specified communication direction, and the communicating component <NUM> receives the first communication in the symbol having the appropriate communication direction (e.g., downlink for a UE receiving the signal or uplink for a base station receiving the signal).

Communicating based on the determined symbol locations and communication directions also includes, at Block <NUM>, receiving a second communication according to a second timeline and/or second slot format based on a second CP type, where the second communication is multiplexed with the first communication in the same slot. In an aspect, communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., receives the second communication (e.g., another transmission) according to the second timeline and/or second slot format based on the second CP type (e.g., based on determining the symbol is a downlink symbol for the second CP type). The second communication is multiplexed with the first communication in the same slot, as described, and are thus transmitted in symbols of respective timelines, which may have a same communication direction (e.g., downlink for a UE receiving the signal or uplink for a base station receiving the signal). As described, the second slot format for the second CP type can include symbols with a specified communication direction, which may overlap in time with symbols of the first slot format having the same specified communication direction. Thus, the communicating component <NUM> can receive the first communication in a first symbol according to the first timeline and the second communication in a second symbol according to the second timeline, which may have the same communication direction and/or may overlap in a time domain or otherwise (e.g., downlink for a UE receiving the signal or uplink for a base station receiving the signal). In one example, communicating component <NUM> can receive the first and second communications subject to one or more time gaps, as described in reference to <FIG>, that can separate the communications such that the communications can align with appropriate symbol boundaries for their associated timelines defined based on their associated CP types. Additionally, as described, the UE <NUM> can include components to additionally transmit, within the slot, a multiplexed first communication (based on a first CP type) and second communication (based on a second CP type) to the base station <NUM>.

In method <NUM>, at Block <NUM>, the first communication is decoded based on a first length of the first CP type, and at Block <NUM>, the second communication is decoded based on a second length of the second CP type. In an aspect, communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., decodes the first communication based on the first length of the first CP type and decodes the second communication based on the second length of the second CP type. For example, communicating component <NUM> can use the appropriate length of the given CP to verify the received signal and/or to determine missing data from the beginning of the signal based on data at the end of the signal corresponding to the CP length.

<FIG> is a block diagram of a MIMO communication system <NUM> including a base station <NUM> and a UE <NUM>. The MIMO communication system <NUM> may illustrate aspects of the wireless communication system <NUM> described with reference to <FIG>. The base station <NUM> may be an example of aspects of the base station <NUM> described with reference to <FIG>. The base station <NUM> may be equipped with antennas <NUM> and <NUM>, and the UE <NUM> may be equipped with antennas <NUM> and <NUM>. In the MIMO communication system <NUM>, the base station <NUM> may be able to send data over multiple communication links at the same time. Each communication link may be called a "layer" and the "rank" of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station <NUM> transmits two "layers," the rank of the communication link between the base station <NUM> and the UE <NUM> is two.

The UE <NUM> may be an example of aspects of the UEs <NUM> described with reference to <FIG>. At the UE <NUM>, the UE antennas <NUM> and <NUM> may receive the DL signals from the base station <NUM> and may provide the received signals to the modulator/demodulators <NUM> and <NUM>, respectively. Each modulator/demodulator <NUM> through <NUM> may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator <NUM> through <NUM> may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <NUM> may obtain received symbols from the modulator/demodulators <NUM> and <NUM>, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE <NUM> to a data output, and provide decoded control information to a processor <NUM>, or memory <NUM>.

The processor <NUM> may in some cases execute stored instructions to instantiate a communicating component <NUM> (see e.g., <FIG> and <FIG>).

The processor <NUM> may in some cases execute stored instructions to instantiate a multiplexing component <NUM> (see e.g., <FIG> and <FIG>).

Claim 1:
A method for wireless communication by a user equipment, UE, comprising:
receiving (<NUM>) a first slot format indicator indicating a first slot format for communication based on a first cyclic prefix, CP, type in a slot, wherein the first slot format determines for all symbols of the first CP type in the slot whether each symbol is a downlink, uplink, or flexible symbol;
determining (<NUM>), based on the first slot format, a second slot format for communication based on a second CP type in the slot, wherein the second slot format determines for all symbols of the second CP type in the slot whether each symbol is a downlink, uplink, or flexible symbols,
wherein determining the second slot format comprises:
for each symbol of the second slot format that is overlapping with only downlink symbols of the first slot format, determining that symbol to be a downlink symbol,
for each symbol of the second slot format that is overlapping with only uplink symbols of the first slot format, determining that symbol to be an uplink symbol, and
for each symbol of the second slot format that is overlapping with a flexible symbol of the first slot format, determining that symbol to be a flexible symbol;
receiving (<NUM>), within the slot, a first communication according to a first timeline in symbols determined as downlink symbols based on the first slot format, wherein the first timeline is associated with the first CP type;
receiving (<NUM>), within the slot, a second communication according to a second timeline in symbols determined as downlink symbols based on the second slot format, wherein the second timeline is associated with the second CP type,
wherein the second communication is multiplexed with the first communication in the slot, and wherein a slot for communication based on the second CP type has less symbols than a slot for communication based on the first CP type; and
decoding (<NUM>) the first communication based on a first length of the first CP type;
decoding (<NUM>) the second communication based on a second length of the second CP type.