WO2020033730A1 - Préambule de nouvelle radio compatible wi-fi - Google Patents

Préambule de nouvelle radio compatible wi-fi Download PDF

Info

Publication number
WO2020033730A1
WO2020033730A1 PCT/US2019/045761 US2019045761W WO2020033730A1 WO 2020033730 A1 WO2020033730 A1 WO 2020033730A1 US 2019045761 W US2019045761 W US 2019045761W WO 2020033730 A1 WO2020033730 A1 WO 2020033730A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
sig
ieee
legacy
legacy preamble
Prior art date
Application number
PCT/US2019/045761
Other languages
English (en)
Inventor
Carlos Aldana
Jeongho Jeon
Laurent Cariou
Thomas J. Kenney
Xiaogang Chen
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2020033730A1 publication Critical patent/WO2020033730A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/261—Details of reference signals
    • H04L27/2613—Structure of the reference signals
    • H04L27/26132—Structure of the reference signals using repetition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/0006—Assessment of spectral gaps suitable for allocating digitally modulated signals, e.g. for carrier allocation in cognitive radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2603—Signal structure ensuring backward compatibility with legacy system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/261—Details of reference signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0092—Indication of how the channel is divided

Definitions

  • wireless communications Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and Institute of Electrical and Electronic Engineers (IEEE) 802.11 communication protocols.
  • 3GPP Third Generation Partnership Project
  • 3GPP LTE Long Term Evolution
  • 3GPP LTE-A Long Term Evolution Advanced
  • 5G networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and Institute of Electrical and Electronic Engineers (IEEE) 802.11 communication protocols.
  • 5G networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and Institute of Electrical and Electronic Engineers (IEEE) 802.11 communication protocols.
  • NR new radio
  • IEEE Institute of Electrical and Electronic Engineers
  • 5G-NR networks will continue to evolve based on 3 GPP LTE- Advanced with additional potential new radio access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and services.
  • RATs new radio access technologies
  • mmWave millimeter wave
  • MulteFire combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. 1B is a simplified diagram of an overall next generation
  • FIG. 1C illustrates a functional split between next generation radio access network (NG-RAN) and the 5G Core network (5GC), in accordance with some aspects.
  • NG-RAN next generation radio access network
  • 5GC 5G Core network
  • FIG. 1D illustrates an example Evolved Universal Terrestrial
  • E-UTRA E-UTRA New Radio Dual Connectivity (EN-DC) architecture, in accordance with some aspects;
  • FIG. 2 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects;
  • eNB evolved Node-B
  • gNB new generation Node-B
  • AP access point
  • STA wireless station
  • MS mobile station
  • UE user equipment
  • FIG. 3 illustrates a UE, in accordance with some embodiments
  • FIG. 4 illustrates an Institute of Electrical and Electronic
  • FIG. 5 illustrates an IEEE 1 ln packet, in accordance with some embodiments
  • FIG. 6 illustrates an IEEE 1 ln Greenfield (GF) packet, in accordance with some embodiments
  • FIG. 7 illustrates an IEEE 1 lac packet, in accordance with some embodiments.
  • FIG. 8 illustrates an IEEE 1 lax packet, in accordance with some embodiments.
  • FIG. 9 illustrates Binary Phase Shift Keying (BPSK)
  • Quadrature Phase Shift Keying (QBPSK), in accordance with some aspects
  • FIG. 10 illustrates a NR packet, in accordance with some embodiments
  • FIG. 11 illustrates a NR packet, in accordance with some embodiments.
  • FIG. 12 illustrates a NR packet, in accordance with some embodiments.
  • FIG. 13 illustrates a NR packet, in accordance with some embodiments
  • FIG. 14 illustrates a NR packet, in accordance with some embodiments.
  • FIG. 15 illustrates a NR packet, in accordance with some embodiments.
  • FIG. 16 illustrates a NR packet, in accordance with some embodiments.
  • FIG. 1 A illustrates an architecture of a network in accordance with some aspects.
  • the network 140 A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are 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.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • LTE and LTE- Advanced are standards for wireless
  • 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.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
  • LAA Licensed-Assisted Access
  • CA flexible carrier aggregation
  • Rel-l3 LAA system focuses on the design of downlink operation on unlicensed spectrum via CA
  • Rel-l4 enhanced LAA (eLAA) system focuses on the design of uplink operation on unlicensed spectrum via CA.
  • 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).
  • spectrum may be spectrums used by IEEE 802.11 compliant STAs 150, 151, e.g., 2.5 GHz, 5 GHz, and/or 6 GHz.
  • Applicable exemplary spectrum bands include IMT (International Mobile
  • IMT-advanced spectrum IMT -2020 spectrum (expected to include 3600-3800 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, for example), spectrum made available under the Federal Communications Commission’s "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.
  • the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) wherein particular the 400 MHz and 700 MHz bands can be employed.
  • TV White Space bands typically below 790 MHz
  • 400 MHz and 700 MHz bands can be employed.
  • PMSE Program Making and Special Events
  • medical, health, surgery, automotive, low-latency, drones, and the like are examples of vertical markets.
  • 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.
  • any of the UEs 101 and 102 can comprise an Internet-of-Things (IoT) UE or a Cellular IoT (CloT) EE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived EE connections.
  • IoT Internet-of-Things
  • CloT Cellular IoT
  • any of the EEs 101 and 102 can include a narrowband (NB) IoT EE (e.g., such as an enhanced NB- IoT (eNB-IoT) EE and Further Enhanced (FeNB-IoT) EE).
  • NB narrowband
  • eNB-IoT enhanced NB- IoT
  • FeNB-IoT Further Enhanced
  • An IoT EE 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.
  • M2M machine-to-machine
  • MTC machine-type communications
  • PLMN public land mobile network
  • D2D device-to-device
  • sensor networks or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network includes interconnecting IoT EEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT EEs may execute background
  • applications e.g., keep-alive messages, status updates, etc.
  • applications e.g., keep-alive messages, status updates, etc.
  • NB-IoT devices can be configured to operate in a single physical resource block (PRB) and may be instructed to retune two different PRBs within the system bandwidth.
  • an eNB-IoT EE can be configured to acquire system information in one PRB, and then it can retune to a different PRB to receive or transmit data.
  • any of the EEs 101 and 102 can include enhanced MTC (eMTC) EEs or further enhanced MTC (FeMTC) EEs.
  • the EEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, an
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are 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.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the network 140 A can include a core network (CN) 120.
  • CN core network
  • NG RAN and NG Core are discussed herein in reference to, e.g., FIG. 1B, FIG. 1C, and FIG. 1D.
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may 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).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point
  • connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity
  • WiFi® WiFi®
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system
  • the AP 106 and stations (STAs) 150, 151 may be configured to operate in accordance with one or more IEEE 802.11 protocols, e.g., IEEE 802.1 la/b/g/n/n-Greenfield
  • the UE 101, 102, AP 106, and STAs 150, 151 may be configured to operate in the 2.4/5/6 Gigahertz radio spectrum.
  • the UEs 101, 102, and RAN 110 e.g., NG interface to the 5GC l20_ may be configured to transmit a preamble as disclosed herein that is compatible with one or more preambles of IEEE 802.11. The preambles may be used to defer the AP 106 and/or STAs 150, 151.
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes 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).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs).
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, 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 node 112.
  • macrocells e.g., macro RAN node 111
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, 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.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a new generation node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
  • gNB new generation node-B
  • eNB evolved node-B
  • the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 111 and 112 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 111 and 112 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal
  • OFDM Orthogonal Frequency-Division Multiplexing
  • OFDMMA Frequency-Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 and 112 to the UEs 101 and 102, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time- frequency plane representation may be used for OFDM systems, which makes it applicable for radio resource allocation.
  • Each column and each row of the resource grid may correspond to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain may correspond to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid may be denoted as a resource element.
  • Each resource grid may comprise a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block may comprise a collection of resource elements; in the frequency domain, this may, in some embodiments, represent the smallest quantity of resources that currently can be allocated. There may be several different physical downlink channels that are conveyed using such resource blocks.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the EIEs 101 and 102.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the EIEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the TIE 102 within a cell) may be performed at any of the RAN nodes 111 and 112 based on channel quality information fed back from any of the EIEs 101 and 102.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG.
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some aspects may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some aspects may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs according to some arrangements.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs according to some arrangements.
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an Sl interface 113.
  • the CN 120 may 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 to FIGS. 1B-1D).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the Sl interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for
  • routing/roaming authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the Sl interface 113 towards the
  • the S-GW 122 may 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-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may 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.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 can 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 UEs 101 and 102 via the CN 120.
  • VoIP Voice-over- Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • IP-CAN Connectivity Access Network
  • HPLMN Home PCRF
  • V-PCRF Visited PCRF
  • VPN Visited Public Land Mobile Network
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.
  • the application server 184 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • QoS Quality of Service
  • the PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 184.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • any of the nodes 111 or 112 can be configured to communicate to the UEs 101, 102 (e.g., dynamically) an antenna panel selection and a receive (Rx) beam selection that can be used by the UE for data reception on a physical downlink shared channel (PDSCH) as well as for channel state information reference signal (CSI-RS) measurements and channel state information (CSI) calculation.
  • PDSCH physical downlink shared channel
  • CSI-RS channel state information reference signal
  • CSI channel state information
  • any of the nodes 111 or 112 can be configured to communicate to the UEs 101, 102 (e.g., dynamically) an antenna panel selection and a transmit (Tx) beam selection that can be used by the UE for data transmission on a physical uplink shared channel (PUSCH) as well as for sounding reference signal (SRS) transmission.
  • Tx transmit
  • PUSCH physical uplink shared channel
  • SRS sounding reference signal
  • the communication network 140A can be an IoT network.
  • IoT One of the current enablers of IoT is the narrowband-IoT (NB- IoT).
  • NB-IOT has objectives such as coverage extension, UE complexity reduction, long battery lifetime, and backward compatibility with the LTE network.
  • NB-IoT aims to offer deployment flexibility allowing an operator to introduce NB-IoT using a small portion of its existing available spectrum, and operate in one of the following three modalities: (a) standalone deployment (the network operates in re-farmed GSM spectrum); (b) in-band deployment (the network operates within the LTE channel); and (c) guard-band deployment (the network operates in the guard band of legacy LTE channels).
  • NB-IoT further enhanced NB-IoT
  • support for NB-IoT in small cells can be provided (e.g., in microcell, picocell or femtocell deployments).
  • NB-IoT systems face for small cell support is the UL/DL link imbalance, where for small cells the base stations have lower power available compared to macro-cells, and, consequently, the DL coverage can be affected and/or reduced.
  • some NB-IoT UEs can be configured to transmit at maximum power if repetitions are used for UL transmission. This may result in large inter-cell interference in dense small cell deployments.
  • the UE 101 can operate in dual connectivity (DC) configuration with a master node (MN) and a secondary node (SN).
  • the EE 101 can receive configuration information 190A (from MN or SN) via, e.g., higher layer signaling or other types of signaling.
  • configuration information 190A can include an indication for renegotiation of EE NR security capability, which can be used for activation of
  • the configuration information 190 A can be communicated directly by the SN via signaling radio bearer type 3 (SRB3) connection.
  • configuration information 192 A can be communicated from the EE 101 to the SN or the MN for purposes of activation of encryption/decryption and integrity protection of user plane and control plane communications.
  • configuration information 192 A can include EE NR - DC token which can be used in secure key derivation for protecting the user plane and control plane communications.
  • FIG. 1B is a simplified diagram of a next generation (NG) system architecture 140B in accordance with some aspects.
  • the NG system architecture 140B includes RAN 110 and a 5G network core (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs 128 and
  • the core network 120 e.g., a 5G core network or 5GC
  • the core network 120 can include an access and mobility management function (AMF) 132 and/or a user plane function (UPF) 134.
  • AMF access and mobility management function
  • UPF user plane function
  • the AMF 132 and the UPF 134 can be
  • the gNBs 128 and the NG-eNBs 130 can be connected to the AMF 132 by NG-C interfaces, and to the UPF 134 by NG-U interfaces.
  • the gNBs 128 and the NG-eNBs 130 can be coupled to each other via Xn interfaces.
  • a gNB 128 can include a node providing new radio (NR) user plane and control plane protocol termination towards the UE and is connected via the NG interface to the 5GC 120.
  • NR new radio
  • an NG-eNB 130 can include a node providing evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations towards the UE and is connected via the NG interface to the 5GC 120
  • E-UTRA evolved universal terrestrial radio access
  • the NG system architecture 140B can use reference points between various nodes as provided by 3GPP Technical
  • a base station 130 can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
  • node 128 can be a master node (MN) and node 130 can be a secondary node (SN) in a 5G architecture.
  • the MN 128 can be connected to the AMF 132 via an NG-C interface and to the SN 128 via an XN-C interface.
  • the MN 128 can be connected to the UPF 134 via an NG-U interface and to the SN 128 via an XN-U interface.
  • FIG. 1C illustrates a functional split between NG-RAN and the
  • 5G Core 5G Core in accordance with some aspects.
  • FIG. 1C there is illustrated a more detailed diagram of the functionalities that can be performed by the gNBs 128 and the NG-eNBs 130 within the NG-RAN 110, as well as the AMF 132, the UPF 134, and the SMF 136 within the 5GC 120.
  • the 5GC 120 can provide access to the Internet 138 to one or more devices via the NG-RAN 110.
  • the gNBs 128 and the NG-eNBs 130 can be configured to host the following functions: functions for Radio Resource Management (e.g., inter-cell radio resource management 129A, radio bearer control 129B, connection mobility control 129C, radio admission control 129D, dynamic allocation of resources to UEs in both uplink and downlink
  • Radio Resource Management e.g., inter-cell radio resource management 129A, radio bearer control 129B, connection mobility control 129C, radio admission control 129D, dynamic allocation of resources to UEs in both uplink and downlink
  • connection setup and release scheduling and transmission of paging messages (originated from the AMF); scheduling and transmission of system broadcast information (originated from the AMF or Operation and Maintenance);
  • the AMF 132 can be configured to host the following functions, for example: NAS signaling termination; NAS signaling security 133A; access stratum (AS) security control; inter-core network (CN) node signaling for mobility between 3 GPP access networks; idle state / mode mobility handling 133B, including mobile device, such as a UE reachability (e.g., control and execution of paging retransmission); registration area management; support of intra-system and inter-system mobility; access authentication; access authorization including check of roaming rights; mobility management control (subscription and policies); support of network slicing; and/or SMF selection, among other functions.
  • NAS signaling termination NAS signaling security 133A
  • AS access stratum
  • CN inter-core network
  • the UPF 134 can be configured to host the following functions, for example: mobility anchoring 135A (e.g., anchor point for Intra-/Inter-RAT mobility); packet data unit (PDU) handling 135B (e.g., external PDU session point of interconnect to data network); packet routing and forwarding; packet inspection and user plane part of policy rule enforcement; traffic usage reporting; uplink classifier to support routing traffic flows to a data network; branching point to support multi-homed PDU session; QoS handling for user plane, e.g., packet filtering, gating, UL/DL rate enforcement; uplink traffic verification (SDF to QoS flow mapping); and/or downlink packet buffering and downlink data notification triggering, among other functions.
  • mobility anchoring 135A e.g., anchor point for Intra-/Inter-RAT mobility
  • PDU packet data unit
  • packet routing and forwarding e.g., packet inspection and user plane part of policy rule enforcement
  • traffic usage reporting e.g., uplink classifier to support
  • the Session Management function (SMF) 136 can be configured to host the following functions, for example: session management; UE IP address allocation and management 137A; selection and control of user plane function (UPF); PDU session control 137B, including configuring traffic steering at UPF 134 to route traffic to proper destination; control part of policy enforcement and QoS; and/or downlink data notification, among other functions.
  • SMF Session Management function
  • FIG. 1D illustrates an example Evolved Universal Terrestrial
  • the EN-DC architecture 140D includes radio access network (or E-TRA network, or E-TRAN) 110 and EPC 120.
  • the EPC 120 can include MMEs 121 and S-GWs 122.
  • the E- UTRAN 110 can include nodes 111 (e.g., eNBs) as well as Evolved Universal Terrestrial Radio Access New Radio (EN) next generation evolved Node-Bs (en- gNBs) 128.
  • nodes 111 e.g., eNBs
  • EN Evolved Universal Terrestrial Radio Access New Radio
  • en- gNBs next generation evolved Node-Bs
  • en-gNBs 128 can be configured to provide
  • the eNBs 111 can be configured as master nodes (or MeNBs) and the eNBs 128 can be configured as secondary nodes (or SgNBs) in the EN-DC communication architecture 140D. As illustrated in FIG. 1D, the eNBs 111 are connected to the EPC 120 via the Sl interface and to the EN-gNBs 128 via the X2 interface. The EN-gNBs (or SgNBs) 128 may be connected to the EPC 120 via the Sl-U interface, and to other EN-gNBs via the X2-U interface.
  • the SgNB 128 can communicate with the UE 102 via a UU interface (e.g., using signaling radio bearer type 3, or SRB3 communications as illustrated in FIG. 1D), and with the MeNB 111 via an X2 interface (e.g., X2-C interface).
  • the MeNB 111 can communicate with the UE 102 via a UU interface.
  • FIG. 1D is described in connection with EN-DC communication environment, other types of dual connectivity communication architectures (e.g., when the EGE 102 is connected to a master node and a secondary node) can also use the techniques disclosed herein.
  • the MeNB 111 can be connected to the
  • the MeNB 111 can be connected to the SGW 122 via Sl-U interface and to the SgNB 128 via an X2-U interface.
  • the Master eNB can offload user plane traffic to the Secondary gNB (SgNB) via split bearer or SCG (Secondary Cell Group) split bearer.
  • FIG. 2 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a next generation Node-B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (EGE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 200 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • Circuitry e.g., processing circuitry
  • circuitry is a collection of circuits implemented intangible entities of the device 200 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating.
  • the hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired).
  • the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation.
  • the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa.
  • the instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation.
  • the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating.
  • any of the physical components may be used in more than one member of more than one circuitry.
  • execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device 200 follow.
  • the device 200 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 200 may operate in the capacity of a server communication device, a client communication device, or both in server-client network environments.
  • the communication device 200 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 200 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single
  • communication device is illustrated, the term "communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
  • cloud computing software as a service
  • SaaS software as a service
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device-readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • the software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Communication device 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204, a static memory 206, and mass storage 207 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 208.
  • a hardware processor 202 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 204 e.g., main memory 204
  • static memory 206 e.g., static memory
  • mass storage 207 e.g., hard drive, tape drive, flash storage, or other block or storage devices
  • the communication device 200 may further include a display device 210, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
  • UI user interface
  • the display device 210, input device 212 and UI navigation device 214 may be a touchscreen display.
  • the communication device 200 may additionally include a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors 221, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • GPS global positioning system
  • the communication device 200 may include an output controller 228, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 207 may include a communication device- readable medium 222, on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 202, the main memory 204, the static memory 206, and/or the mass storage 207 may be, or include (completely or at least partially), the device- readable medium 222, on which is stored the one or more sets of data structures or instructions 224, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the mass storage 216 may constitute the device-readable medium 222.
  • the term “device-readable medium” is interchangeable with“computer-readable medium” or“machine-readable medium”. While the communication device-readable medium 222 is illustrated as a single medium, the term “communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.
  • the term "communication device-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 224) for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • instructions e.g., instructions 224
  • communication device-readable medium examples may include solid-state memories and optical and magnetic media. Specific examples of
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory
  • communication device-readable media may include non-transitory
  • communication device-readable media may include communication device-readable media that is not a transitory propagating signal.
  • the instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols.
  • the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 226.
  • the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), MIMO, or multiple-input- single-output (MISO) techniques.
  • SIMO single-input-multiple-output
  • MISO multiple-input- single-output
  • the network interface device 220 may wirelessly communicate using Multiple ETser MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 200, and includes digital or analog communications signals or another intangible medium to facilitate
  • a transmission medium in the context of this disclosure is a device-readable medium.
  • FIG. 3 illustrates a TIE 302, in accordance with some
  • the TIE 302 may include energy detect level 302, preamble detect level 304, frequency spacing 306, protocols 308, bandwidth 310, frequency spectrum 312, and signal to noise ratio (SNR) 314.
  • the TIE 302 is configured to transmit a preamble that is compatible with IEEE 802.11 communication protocols, e.g., IEEE 802.11 a/n/ac/ax/EHT/ad/ah.
  • the UE 302 may be the same or similar as UE 101, 102.
  • the energy detect level 302 may be -62 dBm, in accordance with some embodiments.
  • Preamble detect level 304 may be -82 dBm, in accordance with some embodiments.
  • the energy detect level 302 may indicate an energy level that is used when a packet has not be detected or decoded.
  • the preamble detect level 304 may be an energy level for when a preamble of a packet is detected or decoded.
  • the preamble detect level 304 may be a different value, e.g., to comply with one or more of the IEEE 802.11 protocols.
  • the energy detect level 302 may be a different, e.g., to comply with one or more of the IEEE 802.11 protocols.
  • the TIE 302 is configured to use different values of the energy detect level 302 and preamble detect level 304 depending on the protocol, e.g., one of the standards disclosed in conjunction with FIG. 1 and an IEEE 802.11 standard.
  • the UE 302 may be configured to use an energy detect for the standard NR of -72 dBm or another value to be compliant with NR.
  • Frequency spacing 306 may be the subcarrier spacing of symbol transmission, e.g., 312.5 kHz for IEEE 802.1 la.
  • the symbols may have a duration as well as frequency spacing 306, e.g., 3.2 ps (lx), 6.4 ps (2x), and 12.8 ps (4x), where IEEE 802. l la is 3.2 ps and IEEE 802. l lax is 12.8 ps.
  • Protocols 308 may be the standards or communication protocols the UE 302 is configured to operate under, e.g, NR, IEEE 802.11, as well as the standards disclosed in conjunction with FIG. 1.
  • NR may be termed NR 3GPP.
  • Wi-Fi may refer to IEEE 802.11 standards, e.g., IEEE 802.1 lad, 802.1 lax, and 802.11EHT.
  • Bandwidth 310 may be a bandwidth that is used to transmit a packet, e.g., 20 MHz.
  • Frequency spectrum 312 may be the frequency spectrum 312 used by the UE 302 to transmit and receive, e.g., 2.4 GHz, 5 GHz, and 6 GHz for frequency spectrums 312 that may be used by both IEEE 802.11 standards and NR.
  • SNR 314 may be a SNR specified for the standard for receiving packets, e.g., for NR the SNR is to be less than 0.
  • Different protocols 308 may have different values for energy detect level 302, preamble detect level 304, frequency spacing 306 (and symbol duration), bandwidth 310, frequency spectrum 312, and SNR 314.
  • the UE 302 is configured to encode and transmit 20 MHz preambles for NR that are compatible with NR and IEEE 802.11 STAs 150, 151 with one or more frequency spectrums 312, e.g., 2.4 GHz, 5 GHz, and/or 6 GHz.
  • the STAs 150, 151 may decode the preambles and defer based on a time in legacy signal (L-SIG) field, e.g., L-SIG 706, 806, 1006, 1106, 1206, 1306, 1406, and 1506.
  • L-SIG legacy signal
  • UE 302 may transmit packets, e.g., a physical layer (PHY) protocol data unit (PPDU) with preambles that are compatible with one or more of the IEEE 802.11 standards.
  • packets e.g., a physical layer (PHY) protocol data unit (PPDU) with preambles that are compatible with one or more of the IEEE 802.11 standards.
  • PHY physical layer
  • PPDU protocol data unit
  • the UE 302 may be able to defer STAs 150, 151 more easily by transmitting preambles that are compatible with the STAs 150, 151 so that the STAs 150, 151 will defer at -82 dBm energy levels or greater and not -62 dBm energy levels or greater.
  • neighboring STAs 150, 151 will decode the NR transmission (e.g., a PPDU with an IEEE 802.11 compatible preamble) and defer.
  • FIG. 4 illustrates an Institute of Electrical and Electronic
  • the preamble 410 includes legacy (L) short training field (STF)(L- STF) 402, L-long training field (LTF)(L-LTF) 404, L-signal field (SIG)(L-SIG) 406, and rest of packet 412.
  • the L-STF 406 are training signals sent in accordance with IEEE 802.1 la.
  • the L-LTF 408 are training signals sent in accordance with IEEE 802.1 la.
  • the L-SIG 410 comprises a rate 414 field and length 416 field.
  • STAs 150, 151, and UEs 101, 102 that operate in accordance with IEEE 802.1 la are configured to decode the preamble 410 and determine the value of the rate 414 field and the value of the length 416 field.
  • a duration is determined, and the STAs 150, 151, and UEs 101, 102 are according to IEEE 802.1 la defer from transmitting on the frequency spectrum 312 (or the portion of the frequency spectrum 312 where the IEEE 802.1 la packet 400 was received) for a duration determined based on the value of the rate 414 field and the value of the length 416 field.
  • the rate 414 field and length 416 field may indicate the encoding of the rest of the packet 412.
  • the rest of the packet 412 may be a media access control (MAC) portion that includes data or other information that may be encoded as indicated by the L-SIG 406.
  • the preamble duration 410 is 20 ps.
  • the L-SIG 406 is encoded using Binary Phase Shift Keying (BPSK) as disclosed in conjunction with FIG. 9.
  • BPSK Binary Phase Shift Keying
  • FIG. 5 illustrates an IEEE 1 ln mixed mode packet 500, in accordance with some embodiments. Illustrated in FIG. 5 is IEEE 802.1 ln packet 500, preamble 510, and rest of packet 512.
  • the IEEE 802.1 ln packet 500 may be a PPDU.
  • the preamble 510 comprises legacy preamble 509 and high throughput (HT) preamble 511.
  • the legacy preamble 509 comprises L-STF 502, L-LTF 504, and L-SIG 506.
  • L-STF 502 may be the same or similar as L-STF 402.
  • L-LTF 504 may be the same or similar as L-LTF 404.
  • L-SIG 506 may be the same or similar as L-SIG 406.
  • L-SIG 506 may comprise a rate 514 field and length 516 field.
  • the value of the rate 514 field and the value of the length 516 field may be set to a total duration of the IEEE 802.1 ln packet 500 after the L- SIG 506, e.g., HT-SIG1 518, HT-SIG2 520, and rest of packet 512.
  • the rate 514 field and length 516 field may no longer indicate an encoding of subsequent data, but rather are used to defer other STAs 150, 151 (and UE 101, 102).
  • a STA 150, 151 configured to operate in accordance with IEEE 802.1 la would decode the L-SIG 506 and determine a time to defer.
  • the HT preamble 51 l include HT-SIG1 518 and HT-SIG2 520.
  • HT-SIG1 518 and HT-SIG2 520 may include encoding information for the rest of packet 512 that STAs 150, 151 configured to operate in accordance with IEEE 802.11h may use to decode rest of packet 512.
  • HT-SIG1 518 and HT-SIG2 520 may be encoded using Quadrature Phase Shift Keying (QBPSK) as disclosed in conjunction with FIG. 9.
  • QBPSK Quadrature Phase Shift Keying
  • the rest of packet 512 may include data or other information that is encoded in accordance with information in HT-SIG1 518 and/or HT-SIG2 520.
  • FIG. 6 illustrates an IEEE 1 ln Greenfield (GF) packet 600, in accordance with some embodiments. Illustrated in FIG. 6 is IEEE 802.1 lnGF packet 600, GF HT preamble 610, and rest of packet 612.
  • the IEEE 802.1 lnGF packet 600 may be a PPDU.
  • the GF HT preamble 610 includes HT-STF 602, HT-LTF 604, HT-SIG1 618, HT-SIG2 620, and rest of packet 612.
  • the HT- STF 602 and HT-LTF 604 may be signals that enable other devices to synchronize with the IEEE 802.1 ln GF packet 600.
  • the HT-SIG1 618 may be the same or similar as HT-SIG1 518.
  • HT-SIG2 620 may be the same or similar as HE-SIG2 520.
  • the rest of packet 612 may be the same or similar as rest of packet 512.
  • STAs 150, 151 and/or UEs 101, 102 that are not configured to operate in IEEE 802.1 ln would not be able to interpret the GF HT preamble 610 and thus would not defer based on a duration indicated (not illustrated) by HT- SIG1 618 and/or HT-SIG2 620.
  • STAs 150, 151 and/or UEs 101 , 102 that are not configured to operate in accordance with IEEE 802.1 ln would defer if the energy from receiving IEEE 802.1 lnGF packet 600 exceeded the energy detect level 302.
  • STAs 150, 151 and/or UEs 101, 102 that are configured to operate in accordance with IEEE 802.1 ln would decode the GF HT preamble 610 and defer for a duration indicated by the HT-SIG1 618 and/or HT-SIG2 620.
  • HT- SIG1 618 and HT-SIG2 620 are encoded using QBPSK as disclosed in conjunction with FIG. 9.
  • FIG. 7 illustrates an IEEE 1 lac packet 700, in accordance with some embodiments. Illustrated in FIG. 7 is IEEE 802.1 lac packet 700, preamble 710, and rest of packet 712.
  • the IEEE 1 lac packet 700 may be a PPDU.
  • the legacy preamble 709 may be the same or similar as legacy preamble 509 with the rate 714 filed and length 716 field set for a duration of the IEEE 802.1 lac packet 700.
  • the very-high throughput (VHT) preamble 711 includes VHT- SIGA1 718 and VHT-SIGA2 720.
  • VHT-SIGA1 718 and VHT-SIGA2 720 may include coding information regarding the rest of the packet 712.
  • the legacy preamble 709 enables STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.1 la to decode and defer based on duration indicated by rate 714 field and length 716 field.
  • VHT-SIGA1 718 and VHT- SIGA1 720 may be encoded using QBPSK as disclosed in accordance with FIG. 9.
  • STAs 150, 151 and UEs 101, 102 may determine whether a packet is encoded with IEEE 802.1 ln or IEEE 802.1 lac based on looking at whether the symbol after L-SIG of the legacy preamble is QBPSK encoded (1 ln) or BPSK encoded (1 lac).
  • FIG. 8 illustrates an IEEE 1 lax packet 800, in accordance with some embodiments. Illustrated in FIG. 8 is IEEE 802.1 lax packet 800, preamble 810, and rest of packet 812.
  • the IEEE 1 lax packet 800 may be a PPDU.
  • the legacy preamble 809 may be the same or similar as legacy preamble 509 with the rate 814 filed and length 816 field set for a duration of the IEEE 802.1 lax packet 800.
  • L-SIG 806 and RL-SIG 818 are similar to L-SIG 506 but with a few extra tones on the outside that are used (e.g., 2 on each side of the L-SIG 506).
  • the high-efficiency (HE) preamble 811 includes repetition (R)L- SIG 818.
  • the HE preamble 811 includes additional signal fields (not illustrated) that include coding information regarding the rest of the packet 812.
  • the legacy preamble 809 enables STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.1 la (and other IEEE 802.11 standards) to decode and defer based on duration indicated by rate 814 field and length 816 field.
  • RL-SIG 818 may be encoded using BPSK as disclosed in accordance with FIG. 9.
  • STAs 150, 151 and UEs 101, 102 may determine whether a packet is encoded in accordance with the IEEE 802.1 lax standard based on looking at whether the symbol after L-SIG 806 is a repetition RL-SIG 818 of L-SIG 806.
  • FIG. 9 illustrates Binary Phase Shift Keying (BPSK) 900
  • Quadrature Phase Shift Keying (QBPSK) 950, in accordance with some embodiments.
  • the solid dots indicate the data tone constellations.
  • STAs 150, 151 and UE 101, 102 can determine the difference between the BPSK 900 and QBPSK 950.
  • FIG. 10 illustrates a NR packet 1000, in accordance with some embodiments.
  • the NR packet 1000 include legacy preamble 809 and rest of packet 708.
  • the legacy preamble 1009 may be the same or similar as legacy preamble 509.
  • the legacy preamble 1009 may be decoded by STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.11 (e.g., 1 la/n/ac/ax/be).
  • the rest of packet 1012 may be encoded in accordance with NR standard.
  • the frequency spacing 306 may be 15 kHz with a symbol duration of approximately 70 ps for the NR standard (e.g., a protocol 308) where the frequency spacing for IEEE 802.1 la may be 312.5 kHz and a symbol duration of 3.2 ps.
  • the NR packet 1000 may enable UEs 101, 102 to have IEEE 802.11 defer with a lower energy (e.g., preamble detect level 304) than they would without being able to decode a legacy preamble 1009 (e.g., energy detect level 302).
  • the rest of packet 1012 may begin with a NR preamble. Note that there could be a gap between the last symbol of the L-SIG and the first symbol of the rest of packet 1012.
  • FIG. 11 illustrates a NR packet 1100, in accordance with some embodiments.
  • the NR packet 1100 include legacy preamble 1109 and rest of packet 1112.
  • the legacy preambles 1109 may be the same or similar as legacy preamble 509.
  • the legacy preambles 1109 may be the same or similar as one another except that the rate 1114 and length 1116 may be adjusted to indicate the duration of the remainder of the NR packet 1100 starting at the end of the corresponding L-SIG 1106.
  • the rate 1114.1 and length 1116.1 may indicate a longer duration than rate 1114.2 and length 1116.2 because of the shorter portion of NR packet 1100 remaining.
  • the legacy preamble 1109 may be decoded by STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.11 (e.g., 1 la/n/ac/ax/EHT).
  • the rest of packet 1112 may be the same or similar as rest of packet 1012, e.g., encoded in accordance with NR standard.
  • the repeated legacy preambles 1109 may reduce the SNR 314 to a value less than zero as the LIEs 101, 102 may combine the signals of the repeated legacy preambles 1109 to reduce the SNR 314 of the reception of the NR packet 1100.
  • the number of legacy preambles 1109 is 2 or greater.
  • FIG. 12 illustrates a NR packet 1200, in accordance with some embodiments.
  • the NR packet 1200 include legacy preamble 1209, random data 1208, and rest of packet 1212.
  • the legacy preamble 1109 may be the same or similar as legacy preamble 509.
  • the random data 1208 may be data that is generated so that other LIEs 101, 102 know the random pattern of data.
  • the random data 1208 may be generated based on a seed that is distributed or predetermined so that other UE 101, 102 can determine the random data 1208.
  • the random data 1208 may enable the UEs 101, 102 to reduce the SNR 314 to less than zero as is indicated in the NR communication standard.
  • the legacy preamble 1209 may be decoded by STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.11 (e.g., 1 la/n/ac/ax/EHT).
  • the rest of packet 1212 may be the same or similar as rest of packet 1012, e.g., encoded in accordance with NR standard.
  • the duration of the random data 1208 is a multiple of 4 ps. In some embodiments, the duration of the random data 1208 is a multiple of another number. In some embodiments, the duration of the random data 1208 is variable, which may depend on SNRs of previous NR packets 1200.
  • random data 1208 is encoded with BPSK. In some embodiments, a different encoding other than BPSK is used to encode random data 1208.
  • FIG. 13 illustrates a NR packet 1300, in accordance with some embodiments.
  • the NR packet 1300 includes legacy preamble 1309, L-LTF
  • L-LTF L-LTF
  • N may be modulated by one or more of + 1, j, -j, and -1.
  • the legacy preamble 1309 may be the same or similar as legacy preamble 509.
  • the L-LTF 1308.1 through 1308.N may be the same or similar L-LTF 1304. N may be 2 or more.
  • the legacy preamble 1309 may be decoded by STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.11 (e.g., 1 la/n/ac/ax/EHT).
  • the rest of packet 1312 may be the same or similar as rest of packet 1012, e.g., encoded in accordance with NR standard.
  • the L-LTFs 1308 being repeated may enable UE 101, 102 to reduce the operating SNR 314 to a value less than zero.
  • the UEs 101, 102 may combine the signals of the repeated L-LTFs 1308 to reduce the SNR 314 of the reception of the NR packet 1300, where the reduction of the SNR 314 may be required by a communication protocol.
  • the L-LTFs 1308 may be mixed with L-STFs 1302 and/or L-SIGs 1306, e.g., there may be a predetermined pattern of L-LTF, L-STF, L-LTF, etc.
  • the number of repetitions (e.g., N) may be a predetermined value or variable.
  • FIG. 14 illustrates a NR packet 1400, in accordance with some embodiments.
  • the NR packet 1400 include legacy preamble 1409, L-STF
  • L-STF 1408.1 through 1408.N may be the same or similar L-STF 1402. N may be 2 or more. In some embodiments, L-STF 1408.1 through 1408.N are modulated by one or more of
  • the legacy preamble 1409 may be decoded by STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.11 (e.g., 1 la/n/ac/ax/EHT).
  • the rest of packet 1412 may be the same or similar as rest of packet 1012, e.g., encoded in accordance with NR standard.
  • the L-STFs 1408 being repeated may enable TIE 101, 102 to reduce the SNR 314 to a value less than zero.
  • the EIEs 101, 102 may combine the signals of the repeated L- STFs 1408 to reduce the SNR 314 of the reception of the NR packet 1400.
  • the L-STFs 1408 may be mixed with L-STFs 1404 and/or L-SIGs 1406, e.g., there may be a predetermined pattern of L-LTF, L-STF, L- LTF, etc.
  • the number of repetitions (e.g., N) may be a predetermined value or variable.
  • FIG. 15 illustrates a NR packet 1500, in accordance with some embodiments.
  • the NR packet 1500 include legacy preamble 1509, RL-SIG 1508.1 through 1508.N, and rest of packet 1512.
  • the legacy preamble 1509 may be the same or similar as legacy preamble 509.
  • RL-SIG 1508.1 through 1408.N may be the same or similar L-SIG 1506.
  • N may be 2 or more.
  • RL-SIG 1508.1 through 1408.N are modulated by one or more of
  • the legacy preamble 1509 may be decoded by STAs 150, 151 and UEs 101, 102 that are configured to operate in accordance with IEEE 802.11 (e.g., 1 la/n/ac/ax/EHT).
  • the rest of packet 1512 may be the same or similar as rest of packet 1012, e.g., encoded in accordance with NR standard.
  • the RL- SIGs 1508 being repeated may enable UE 101, 102 to reduce the SNR 314 to a value less than zero, which in some embodiments is a requirement.
  • the UEs 101, 102 may combine the signals of the repeated RL-SIGs 1508 to reduce the SNR 314 of the reception of the NR packet 1500.
  • a reduction of the SNR 314 to a value of less than zero is a requirement of the communication protocol.
  • the RL-SIGs 1508 may be mixed with L-STFs 1504 and/or L-LTF 1504, e.g., there may be a predetermined pattern of RL-SIG, L-STF, L-LTF, etc. The number of repetitions (e.g., N) may be a predetermined value or variable.
  • the RL-SIG 1508 may be identical in some embodiments. In some embodiments, RL-SIG 1508 have different rate 1514 field and length 1516 fields to indicate the remaining duration of the NR packet 1500.
  • repetitions of portions of the preamble may increase the gain for the UE 101, 102, and STAs 150,151.
  • the gain is given by l0*logl0(K), where the Gain (dB) for K repetitions is given by Table 1.
  • N of FIG. 11 may be based on a Gain (dB) so that the SNR 314 for NR standard (e.g., protocols 308) is less than zero to comply with the NR standard.
  • the multiple (e.g., 4 ps) of the random data 1208 (FIG. 12) may be based on a Gain (dB) so that the SNR 314 for NR standard (e.g., protocols 308) is less than zero to comply with the NR standard.
  • the multiple of the number of L-LTF 1308 (FIG. 13) may be based on a Gain (dB) so that the SNR 314 for NR standard (e.g., protocols 308) is less than zero to comply with the NR standard.
  • the multiple of the number of L-STF 1408 may be based on a Gain (dB) so that the SNR 314 for NR standard (e.g., protocols 308) is less than zero to comply with the NR standard.
  • the multiple of the number of RL-SIGs 1508 may be based on a Gain (dB) so that the SNR 314 for NR standard (e.g., protocols 308) is less than zero to comply with the NR standard.
  • STAs 150, 151, and UEs 101, 102 are configured to set the rate field and the length field to indicate a duration that other devices should defer, in accordance with some embodiments.
  • UEs 101, 102 wait a period of time before transmitting the rest of packet 1012, 1112, 1212, 1312, 1412, and 1512.
  • the period of time may be 16-100 ps and may be a predetermined time such as 70 ps.
  • the UEs 101, 102 may need the time to switch from IEEE 802.11 transmissions to a 5G NR transmissions.
  • FIG. 16 illustrates a NR packet 1600, in accordance with some embodiments.
  • the NR packet 1600 includes legacy preamble 1609, NR portion 1608, pause 1610, and rest of packet 1612.
  • the legacy preamble 1609 may be the same or similar as legacy preamble 509.
  • the NR packet 1600 may be a portion for the NR communication protocol, e.g., NR portion 1608 may be nothing as indicated in FIG. 10, legacy preamble 1109.2 through 1109.N as indicated in FIG. 11, random data 1208 as indicated in FIG. 12, L-LTF 1308.1 through L-LTF 1308.N as indicated in FIG. 13, L-STF 1408.1 through L-STF 1408.N as indicated in FIG. 14, RL-SIG 1508.1 through RL-SIG 1508.N as indicated in FIG. 15, or another NR portion 1608, e.g., as disclosed herein.
  • the pause 1610 may be a predetermined duration.
  • the pause 1610 may be a duration of 16-100 ps and may be a predetermined time such as 70 ps.
  • the rest of packet 1612 may be the same or similar as the rest of packet as disclosed herein, e.g., FIGS. 10-15.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un équipement utilisateur (UE) qui est configuré pour : coder un paquet comprenant un préambule existant de l'Institute of Electrical and Electronic Engineers (IEEE), le préambule existant de l'IEEE comprenant un champ d'apprentissage court existant (L-STF), un champ d'apprentissage long existant (L-LTF), et un champ de signal existant (L-SIG), le L-SIG comprenant un champ de longueur et un champ de fréquence, une valeur du champ de longueur et une valeur du champ de fréquence combinées indiquant une durée du paquet après le préambule existant de l'IEEE. L'UE est en outre configuré pour coder le paquet pour inclure en outre une partie de nouvelle radio (NR) après le préambule existant de l'IEEE, la partie de NR étant codée conformément à une norme de NR de cinquième génération (5G), et configurer l'UE pour transmettre le préambule existant, mettre en pause une durée prédéfinie, et transmettre la partie de NR.
PCT/US2019/045761 2018-08-10 2019-08-08 Préambule de nouvelle radio compatible wi-fi WO2020033730A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862717537P 2018-08-10 2018-08-10
US62/717,537 2018-08-10

Publications (1)

Publication Number Publication Date
WO2020033730A1 true WO2020033730A1 (fr) 2020-02-13

Family

ID=69415665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/045761 WO2020033730A1 (fr) 2018-08-10 2019-08-08 Préambule de nouvelle radio compatible wi-fi

Country Status (1)

Country Link
WO (1) WO2020033730A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150163045A1 (en) * 2011-05-12 2015-06-11 Micrel, Inc. Adaptive pause time energy efficient ethernet phy
US20160345202A1 (en) * 2015-05-22 2016-11-24 Qualcomm Incorporated Techniques for signal extension signaling
US9699727B2 (en) * 2014-11-04 2017-07-04 Intel IP Corporation Method, apparatus, and computer readable medium for signaling high efficiency preambles

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150163045A1 (en) * 2011-05-12 2015-06-11 Micrel, Inc. Adaptive pause time energy efficient ethernet phy
US9699727B2 (en) * 2014-11-04 2017-07-04 Intel IP Corporation Method, apparatus, and computer readable medium for signaling high efficiency preambles
US20160345202A1 (en) * 2015-05-22 2016-11-24 Qualcomm Incorporated Techniques for signal extension signaling

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HOWARD THOMAS(VIAVI: "Intelligent converged network consolidating radio and optical access around user equipment", 20 February 2018 (2018-02-20), XP055483024 *
RUI CAO ET AL.: "WUR Legacy Preamble Design", IEEE 802.11-17/0647R4, 10 May 2017 (2017-05-10), XP068115821 *
YOUHAN KIM ET AL.: "Duration in L-SIG", IEEE 802.11-10/0534RL, 17 May 2010 (2010-05-17) *

Similar Documents

Publication Publication Date Title
US10868607B2 (en) Phase tracking reference signal (PT-RS) power boosting
US11102764B2 (en) Minimization of padding and resource wastage in message 3 (MSG3) for early data transmission (EDT)
US11558790B2 (en) Configuration of multiple measurement gap patterns
US11129057B2 (en) Bandwidth part (BWP) switching
US10993216B2 (en) Flexible slot format indication (SFI) monitoring for new radio unlicensed communications
US12089068B2 (en) TCI and QCL configuration in 5G networks
US11051363B2 (en) Management of enhanced coverage (EC) in fifth generation (5G) systems
US12088382B2 (en) Configuration and design of CQI and MCS tables for 5G communications
EP3603304B1 (fr) Améliorations de l'internet des objets à bande étroite (nb-iot)
US20240121041A1 (en) Collision Handling of Reference Signals
US11304157B2 (en) Collision handling of synchronization signal (SS) blocks
US20190342874A1 (en) Interlace-Based Uplink Physical Channel Design for New Radio-Unlicensed (NR-U)
US11026147B2 (en) Dynamic adaptation of maximum packet loss rate (PLR) for single radio voice call continuity (SRVCC) handover optimization using session description protocol (SDP)
US11147124B2 (en) Flexible resource allocation for even further enhanced machine type communication (EFEMTC)
US10470044B2 (en) Resolving bidding down attacks for multi-connectivity
US11949613B2 (en) Scheduling for new radio in unlicensed spectrum (NR-U)
WO2020033730A1 (fr) Préambule de nouvelle radio compatible wi-fi

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19847265

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19847265

Country of ref document: EP

Kind code of ref document: A1