[go: up one dir, main page]

WO2018144892A1 - Dispositions facilitant la transition et la mesure d'adaptation de bande passante - Google Patents

Dispositions facilitant la transition et la mesure d'adaptation de bande passante Download PDF

Info

Publication number
WO2018144892A1
WO2018144892A1 PCT/US2018/016679 US2018016679W WO2018144892A1 WO 2018144892 A1 WO2018144892 A1 WO 2018144892A1 US 2018016679 W US2018016679 W US 2018016679W WO 2018144892 A1 WO2018144892 A1 WO 2018144892A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwa
bandwidth
transition
communication
circuitry
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2018/016679
Other languages
English (en)
Inventor
Rui Huang
Yang Tang
Jie Cui
Hong He
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel IP Corp
Original Assignee
Intel IP Corp
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 IP Corp filed Critical Intel IP Corp
Priority to DE112018000223.3T priority Critical patent/DE112018000223T5/de
Publication of WO2018144892A1 publication Critical patent/WO2018144892A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0087—Timing of allocation when data requirements change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • FIG. 4A illustrates an exemplary millimeter wave communication circuitry according to some aspects.
  • FIG. 5 illustrates protocol functions that may be implemented in a wireless communication device according to some aspects.
  • FIG. 8 is a simplified timing diagram illustrating BWA operation according to some aspects.
  • FIG. 13 illustrates an architecture of a system of a network in accordance with some embodiments.
  • FIG. 16 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • FIG. 19 is a block diagram illustrating components, according to some example embodiments, of a system 1900 to support network functions virtualization.
  • FIG. 20 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • BS base station
  • AP wireless access point
  • UE user equipment
  • ST As mobile stations
  • a UE may operate in a power-efficient narrowband state, and higher- performing wideband state. Each state is associated to data-carrying resource elements (REs) over which the UE is assumed to be able to receive control/data).
  • the wideband state generally provides more REs than the narrowband state.
  • the UE When the UE is not scheduled to transmit or receive data, or is scheduled to transmit or receive low-data-rate service (such as voice service), the UE can operate in the narrowband state to reduce power consumption. Power is conserved as the analog-to-digital converter (ADC) circuitry power consumption is generally proportional to the bandwidth.
  • ADC analog-to-digital converter
  • the BS can command the UE to operate in the wideband state.
  • a UE While a UE is configured in the narrowband state it may also be receiving a relatively small amount of data (e.g. control information, transmission control protocol (TCP) positive or negative acknowledgements (ACKs/NACKs, etc.).
  • data e.g. control information, transmission control protocol (TCP) positive or negative acknowledgements (ACKs/NACKs, etc.).
  • TCP transmission control protocol
  • ACKs/NACKs negative acknowledgements
  • the UE may still be able to receive data normally as long as the data transmission falls within the UE's narrow operating bandwidth.
  • having less-active UEs operate in their respective narrowband states advantageously frees up resource elements of the serving BS to be allocated to UEs that are more active.
  • power is saved in the less-active UEs, while the more active UEs may have more communications resources scheduled to facilitate improved data-communications performance.
  • the adaptive bandwidth of a given UE may be controlled by the BS using signaling over a control channel such as the physical downlink control channel (PDCCH), for instance, to command the UE to operate in a selected mode.
  • the UE may select its adaptive-bandwidth mode, and report its selection to the BS over a control channel such as the physical uplink control channel (PUCCH).
  • PUCCH physical downlink control channel
  • both approaches, BS-controlled, and UE- selected, BWA may be employed.
  • the BS may have ultimate authority over the adaptive bandwidth for the UEs that it server; however, UEs may send a request for a certain adaptive-bandwidth operating mode to the BS according to their individual preferential determination.
  • transition time As a UE's radio changes from one bandwidth to another.
  • the UE's baseband processor interprets and executes the transition command, and the UE's radio circuitry performs RF retuning, analog-to-digital conversion settings changes, and automatic gain control (AGC) adjustment, among other operations.
  • AGC automatic gain control
  • These operations have a settling time during which the radio circuitry approaches a steady state.
  • the UE is not able to properly receive control or data messaging.
  • the UE may not be able to properly transmit control or data messaging.
  • a minimum level of communication performance may be defined as a limit for missed frame acknowledgements (e.g., ACK, NACK messages).
  • An example of such a limit is a maximum probability of 0.5% of missed ACK/NACK messages attributable to the BWA transition time.
  • the BWA transition time for a given UE is known.
  • the transition time may be reported to the BS explicitly or implicitly, and the BS may schedule BWA transitions, and likewise the BS may schedule communications with the UE following each BWA transition such that messaging between the BS and the UE is suppressed or avoided during the UE's BWA transition time.
  • explicit reporting of the BWA transition time includes the UE providing an indicator that either includes a value of the BWA transition time, or is otherwise associated with a predefined transition time or range of transition times, as part of the control-channel configuration information exchange between the UE and the BS.
  • implicit reporting of the BWA transition time involves the BS having advance knowledge of different types or classes of UEs, and likewise having advance knowledge of the BWA transition times for the various types or classes.
  • the BS may simply receive and decode the UE type indicator from the UE and, using this information, the BS may determine, using its advance knowledge, the corresponding BWA transition time that was pre-associated with the UE type.
  • some embodiments are directed to radio link monitoring during BWA transitions. Due to BWA, the bandwidth of the physical downlink control channel (PDCCH) may be changed during the reception of control signaling by the UE, from which the UE is to perform radio link monitoring (RLM). The change in bandwidth mid-stream during the RLM may adversely affect the accuracy of the RLM measurements and link quality assessment. Accordingly, various embodiments include variation of RLM evaluation criteria commensurately with transition of bandwidth as part of the BWA operations.
  • PDCCH physical downlink control channel
  • RLM radio link monitoring
  • FIG. 1 is a functional diagram of a 3GPP network in accordance with some embodiments.
  • the network comprises a radio access network (RAN) (e.g., as depicted, the E-UTRAN or evolved universal terrestrial radio access network) 101 and the core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an SI interface 115.
  • RAN radio access network
  • EPC evolved packet core
  • the core network 120 includes a mobility management entity (MME) 122, a serving gateway (serving GW) 124, and packet data network gateway (PDN GW) 126.
  • MME mobility management entity
  • serving GW serving gateway
  • PDN GW packet data network gateway
  • the RAN 101 includes one or more BSs, such as evolved Node-B (eNB) 104, new-radio Node Bs (gNB) 106, or the like, for communicating with user equipment (UE) 102.
  • eNB evolved Node-B
  • gNB new-radio Node Bs
  • BS BS
  • the BSs 104, 106 may include macro eNBs and low power (LP) eNBs.
  • the BSs 104, 106 may transmit a downlink control message to the UE 102 to indicate an allocation of physical uplink control channel (PUCCH) channel resources.
  • the UE 102 may receive the downlink control message from the BSs 104, 106, and may transmit an uplink control message to the BSs 104, 106 in at least a portion of the PUCCH channel resources.
  • the MME 122 is similar in function to the control plane of legacy Serving GPRS Support Nodes (SGSN).
  • the MME 122 manages mobility aspects in access such as gateway selection and tracking area list management.
  • the serving GW 124 terminates the interface toward the RAN 101, and routes data packets between the RAN 101 and the core network 120. In addition, it may be a local mobility anchor point for inter-eNB handoffs and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.
  • the PDN GW 126 terminates a SGi interface toward the packet data network (PDN).
  • PDN packet data network
  • the PDN GW 126 routes data packets between the EPC 120 and the external PDN, and may be a key node for policy enforcement and charging data collection. It may also provide an anchor point for mobility with non-LTE accesses.
  • the external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain.
  • IMS IP Multimedia Subsystem
  • the PDN GW 126 and the serving GW 124 may be implemented in one physical node or separated physical nodes.
  • the BSs 104, 106 terminate the air interface protocol and may be the first point of contact for a UE 102.
  • a BS 104, 106 may fulfill various logical functions for the RAN 101 including but not limited to RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller functions
  • UE 102 may be configured to communicate with a BS 104, 106 over a multipath fading channel in accordance with an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique.
  • OFDM signals may comprise a plurality of orthogonal subcarriers.
  • the SI interface 115 is the interface that separates the RAN 101 and the EPC 120. It is split into two parts: the Sl-U, which carries traffic data between the BSs 104, 106 and the serving GW 124, and the SI -MME, which is a signaling interface between the BS 104, 106 and the MME 122.
  • the X2 interface is the interface between BS 104, 106.
  • the X2 interface comprises two parts, the X2-C and X2-U.
  • the X2-C is the control plane interface between the BS 104, 106
  • the X2-U is the user plane interface between the BSs 104, 106.
  • LP cells are typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with very dense phone usage, such as train stations.
  • the term low power (LP) eNB or gNB refers to any suitable relatively low power eNB or gNB for implementing a narrower cell (narrower than a macro cell) such as a femtocell, a picocell, or a micro cell.
  • Femtocell eNBs or gNBs are typically provided by a mobile network operator to its residential or enterprise customers.
  • a femtocell is typically the size of a residential gateway or smaller and generally connects to the user's broadband line.
  • a picocell is a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in-aircraft.
  • a picocell eNB or gNB can generally connect through the X2 link to another eNB or gNB such as a macro eNB or gNB through its BS controller (BSC) functionality.
  • BSC BS controller
  • LP eNB or gNB may be implemented with a picocell since it is coupled to a macro eNB via an X2 interface.
  • Picocells or other LP BSs may incorporate some or all functionality of a macro BS. In some cases, this may be referred to as an access point BS or enterprise femtocell.
  • a downlink resource grid may be used for downlink transmissions from a BS 104, 106 to a UE 102, while uplink transmission from the UE 102 to the BS 104, 106 may utilize similar techniques.
  • the grid may 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 is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid correspond to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • Each resource grid comprises a number of resource blocks (RBs), which describe the mapping of certain physical channels to resource elements.
  • RBs resource blocks
  • Each resource block comprises a collection of resource elements in the frequency domain and may represent the smallest quanta of resources that currently can be allocated.
  • the physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to a UE 102 (FIG. 1).
  • the physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UE 102 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel.
  • HARQ hybrid automatic repeat request
  • downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 102 within a cell) may be performed at the BS 104, 106 based on channel quality information fed back from the UE 102 to the BS 104, 106, and then the downlink resource assignment information may be sent to the UE 102 on the control channel (PDCCH) used for (assigned to) the UE 102.
  • PDCCH control channel
  • the PDCCH uses CCEs (control channel elements) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex- valued symbols are first organized into quadruplets, which are then permuted using a sub-block inter-leaver for rate matching.
  • Each PDCCH is transmitted using one or more of these control channel elements (CCEs), where each CCE corresponds to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • Four QPSK symbols are mapped to each REG.
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There may 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).
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware engines that include instruction-execution hardware.
  • circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware or software.
  • FIG. 2 is a functional diagram of a user device 200, also referred to as user equipment (UE) in accordance with some embodiments.
  • the UE 200 may be a mobile device in some aspects and includes an application processor 205, baseband processor 210 (also referred to as a baseband module), radio front end module (RFEM) 215, memory 220, connectivity module 225, near field communication (NFC) controller 230, audio driver 235, camera driver 240, touch screen 245, display driver 250, sensors 255, removable memory 260, power management integrated circuit (PMIC) 265 and smart battery 270.
  • RFEM radio front end module
  • application processor 205 may include, for example, one or more CPU cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I2C) or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (IO), memory card controllers such as secure digital / multi-media card (SD/MMC) or similar, universal serial bus (USB) interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I2C) or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (IO), memory card controllers such as secure digital / multi-media card (SD/M
  • baseband module 210 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, and/or a multi-chip module containing two or more integrated circuits.
  • FIG. 3 illustrates a BS or infrastructure equipment radio head 300 in accordance with an example.
  • the BS radio head 300 may include one or more of application processor 305, baseband modules 310, one or more radio front end modules 315, memory 320, power management circuitry 325, power tee circuitry 330, network controller 335, network interface connector 340, satellite navigation receiver module 345, and user interface 350.
  • application processor 305 may include one or more CPU cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose 10, memory card controllers such as SD/MMC or similar, USB interfaces, MIPI interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I2C or universal programmable serial interface module
  • RTC real time clock
  • timer-counters including interval and watchdog timers
  • general purpose 10 memory card controllers such as SD/MMC or similar
  • USB interfaces such as SD/MMC or similar
  • MIPI interfaces Joint Test Access Group (JTAG) test access ports.
  • JTAG Joint Test Access Group
  • baseband processor 310 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • memory 320 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including highspeed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM) and/or a three-dimensional crosspoint memory.
  • volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including highspeed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM) and/or a three-dimensional crosspoint memory.
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • NVM nonvolatile memory
  • Flash memory highspeed electrically erasable memory
  • PRAM phase change random access memory
  • MRAM magnetoresistive random access memory
  • Memory 320 may be implemented as
  • power management integrated circuitry 325 may include one or more of voltage regulators, surge protectors, power alarm detection circuitry and one or more backup power sources such as a battery or capacitor.
  • Power alarm detection circuitry may detect one or more of brown out (under- voltage) and surge (over-voltage) conditions.
  • power tee circuitry 330 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the BS radio head 300 using a single cable.
  • network controller 335 may provide connectivity to a network using a standard network interface protocol such as Ethernet.
  • Network connectivity may be provided using a physical connection which is one of electrical (commonly referred to as copper interconnect), optical or wireless.
  • satellite navigation receiver module 345 may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations such as the global positioning system (GPS), Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS), Galileo and/or BeiDou.
  • the receiver 345 may provide data to application processor 305 which may include one or more of position data or time data.
  • Application processor 305 may use time data to synchronize operations with other radio BSs.
  • user interface 350 may include one or more of physical or virtual buttons, such as a reset button, one or more indicators such as light emitting diodes (LEDs) and a display screen.
  • buttons such as a reset button
  • indicators such as light emitting diodes (LEDs)
  • display screen may include one or more of physical or virtual buttons, such as a reset button, one or more indicators such as light emitting diodes (LEDs) and a display screen.
  • LEDs light emitting diodes
  • FIG. 4A illustrates an exemplary communication circuitry 400 according to some aspects.
  • Communication circuitry 400 is alternatively grouped according to functions. Components as shown in FIG. 4 are shown here for illustrative purposes and may include other components not shown.
  • Communication circuitry 400 may include protocol processing circuitry 405, which may implement one or more of medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) and non-access stratum (NAS) functions.
  • Protocol processing circuitry 405 may include one or more processing cores (not shown) to execute instructions and one or more memory structures (not shown) to store program and data information.
  • Communication circuitry 400 may further include digital baseband circuitry 410, which may implement physical layer (PHY) functions including one or more of hybrid automatic repeat request (HARQ) functions, scrambling and/or descrambling, coding and/or decoding, layer mapping and/or de-mapping, modulation symbol mapping, received symbol and/or bit metric determination, multi-antenna port pre- coding and/or decoding which may include one or more of space-time, space- frequency or spatial coding, reference signal generation and/or detection, preamble sequence generation and/or decoding, synchronization sequence generation and/or detection, control channel signal blind decoding, and other related functions.
  • PHY physical layer
  • HARQ hybrid automatic repeat request
  • Communication circuitry 400 may further include transmit circuitry 415, receive circuitry 420 and/or antenna array circuitry 430.
  • Communication circuitry 400 may further include radio frequency (RF) circuitry 425.
  • RF circuitry 425 may include multiple parallel RF chains for one or more of transmit or receive functions, each connected to one or more antennas of the antenna array 430.
  • protocol processing circuitry 405 may include one or more instances of control circuitry (not shown) to provide control functions for one or more of digital baseband circuitry 410, transmit circuitry 415, receive circuitry 420, and/or radio frequency circuitry 425.
  • Figures 4B and 4C illustrate examples for transmit circuitry 415 in FIG. 4 A in some aspects.
  • the exemplary transmit circuitry 415 of FIG. 4B may include one or more of digital to analog converters (DACs) 440, analog baseband circuitry 445, up-conversion circuitry 450 and filtering and amplification circuitry 455.
  • 4C illustrates an exemplary transmit circuitry 415 which includes digital transmit circuitry 465 and output circuitry 470.
  • FIG. 4D illustrates an exemplary radio frequency circuitry 425 in FIG. 4A according to some aspects.
  • Radio frequency circuitry 425 may include one or more instances of radio chain circuitry 472, which in some aspects may include one or more filters, power amplifiers, low noise amplifiers, programmable phase shifters and power supplies (not shown).
  • Radio frequency circuitry 425 may include power combining and dividing circuitry 474 in some aspects.
  • power combining and dividing circuitry 474 may operate bidirectionally, such that the same physical circuitry may be configured to operate as a power divider when the device is transmitting, and as a power combiner when the device is receiving.
  • power combining and dividing circuitry 474 may one or more include wholly or partially separate circuitries to perform power dividing when the device is transmitting and power combining when the device is receiving.
  • power combining and dividing circuitry 474 may include passive circuitry comprising one or more two- way power divider/combiners arranged in a tree.
  • power combining and dividing circuitry 474 may include active circuitry comprising amplifier circuits.
  • radio frequency circuitry 425 may connect to transmit circuitry 415 and receive circuitry 420 in FIG. 4 A via one or more radio chain interfaces 476 or a combined radio chain interface 478.
  • one or more radio chain interfaces 476 may provide one or more interfaces to one or more receive or transmit signals, each associated with a single antenna structure which may comprise one or more antennas.
  • the combined radio chain interface 478 may provide a single interface to one or more receive or transmit signals, each associated with a group of antenna structures comprising one or more antennas.
  • FIG. 4E illustrates exemplary receive circuitry 420 in FIG. 4A according to some aspects.
  • Receive circuitry 420 may include one or more of parallel receive circuitry 482 and/or one or more of combined receive circuitry 484.
  • the one or more parallel receive circuitry 482 and one or more combined receive circuitry 484 may include one or more Intermediate
  • ADC analog-to- digital converter
  • FIG. 5 An illustration of protocol functions that may be implemented in a wireless communication device according to some aspects is illustrated in FIG. 5.
  • protocol layers may include one or more of physical layer (PHY) 510, medium access control layer (MAC) 520, radio link control layer (RLC) 530, packet data convergence protocol layer (PDCP) 540, service data adaptation protocol (SDAP) layer 547, radio resource control layer (RRC) 555, and non-access stratum (NAS) layer 557, in addition to other higher layer functions not illustrated.
  • PHY physical layer
  • MAC medium access control layer
  • RLC radio link control layer
  • PDCP packet data convergence protocol layer
  • SDAP service data adaptation protocol
  • RRC radio resource control layer
  • NAS non-access stratum
  • protocol layers may include one or more service access points that may provide communication between two or more protocol layers.
  • PHY 510 may transmit and receive physical layer signals 505 that may be received or transmitted respectively by one or more other communication devices.
  • physical layer signals 505 may comprise one or more physical channels.
  • an instance of PDCP 540 may process requests from and provide indications to one or more of an instance of RRC 555 and one or more instances of SDAP 547 via one or more packet data convergence protocol service access points (PDCP-SAP) 545.
  • requests and indications communicated via PDCP-SAP 545 may comprise one or more radio bearers.
  • a sub-component of a transmitted signal constituting one subcarrier in the frequency domain and one symbol interval in the time domain may be termed a resource element.
  • Resource elements may be depicted in a grid form as shown in FIG. 7 A and FIG. 7B.
  • resource elements may be grouped into rectangular resource blocks 700 consisting of 12 subcarriers in the frequency domain and the P symbols in the time domain, where P may correspond to the number of symbols contained in one slot, and may be 6, 7, or any other suitable number of symbols.
  • resource elements may be grouped into resource blocks 700 consisting of 12 subcarriers in the frequency domain and one symbol in the time domain.
  • BWA transition time 812 represents the time between narrowband state 802 and wideband state 804 during which the UE is not able to conduct normal communications activity due to one or more of: the processing time of UE RF BWA command, the settling time of RF retuning, the settling time of AID or D/A conversion, the settling time of AGC, and the like.
  • the BS maintains knowledge of a UE's BWA transition time 812, and schedules communication with a bandwidth-adapting UE in such a manner that no uplink or downlink communications are scheduled for the UE during BWA transition time 812.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, engines, engines, or circuitry which for the sake of consistency are termed engines, although it will be understood that these terms may be used interchangeably.
  • Engines may be hardware, software, or firmware communicatively coupled to one or more processors in order to carry out the operations described herein.
  • Engines may be hardware engines, and as such engines may be considered tangible entities 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 an engine.
  • the BS facilitates random access by a UE.
  • This operation may include a series of operations that carry out a random-access protocol, including such operations as responding to a random access preamble, radio resource control (RRC) signaling, and the like.
  • RRC radio resource control
  • the BS obtains UE type information from the UE, which may provide (explicitly or implicitly) the UE's BWA capability, and BWA performance parameters, which in turn may include the BWA transition time of the UE.
  • Various UEs may have different BWA transition times. It is also contemplated that certain classes of UEs may conform to a standardized BWA transition time limit that is known by the BS.
  • the BS (e.g., via resource scheduler 906) refrains from scheduling communications with the transitioning UE during the UE's BWA transition time.
  • various different UEs or types of UEs being served by the BS may have different BWA transition times; accordingly, the time duration during which the BS refrains from communicating with the individual UEs may be variable, and UE- specific.
  • Radio link quality measurement parameter selector 1110 is constructed, programmed, or otherwise configured, to automatically vary radio link quality measurement parameters to vary the RLM evaluation criteria commensurately with transition of bandwidth as part of the BWA operations.
  • the RAN 1310 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UE 1302 is shown to be configured to access an access point (AP) 1306 via connection 1307.
  • the connection 1307 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1306 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 1306 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 1310 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1311, 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 1312.
  • macro RAN node 1311 e.g., macro RAN node 1311
  • 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 1311 and 1312 can terminate the air interface protocol and can be the first point of contact for the UEs 1301 and 1302.
  • any of the RAN nodes 1311 and 1312 can fulfill various logical functions for the RAN 1310 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
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 1311 and 1312 based on channel quality information fed back from any of the UEs 1301 and 1302.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 1301 and 1302.
  • the RAN 1310 is shown to be communicatively coupled to a core network (CN) 1320 -via an SI interface 1313.
  • the CN 1320 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 1313 is split into two parts: the Sl-U interface 1314, which carries traffic data between the RAN nodes 1311 and 1312 and the serving gateway (S-GW) 1322, and the Sl-mobility management entity (MME) interface 1315, which is a signaling interface between the RAN nodes 1311 and 1312 and MMEs 1321.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • PCRF 1326 may be communicatively coupled to the application server 1330 via the P-GW 1323.
  • the application server 1330 may signal the PCRF 1326 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • QoS Quality of Service
  • the PCRF 1326 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 1330.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 14 illustrates example components of a device 1400 in accordance with some embodiments.
  • the device 1400 may include application circuitry 1402, baseband circuitry 1404, Radio Frequency (RF) circuitry 1406, front-end module (FEM) circuitry 1408, one or more antennas 1410, and power management circuitry (PMC) 1412 coupled together at least as shown.
  • the components of the illustrated device 1400 may be included in a UE or a RAN node.
  • the device 1400 may include less elements (e.g., a RAN node may not utilize application circuitry 1402, and instead include a processor/controller to process IP data received from an EPC).
  • the device 1400 may include additional elements such as, for example, memory/storage, display, camera, ?sensor, or input/output (I/O) interface.?
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C- RAN) implementations).
  • the application circuitry 1402 may include one or more application processors.
  • the application circuitry 1402 may include circuitry such as, but not limited to, one ?or more single-core or multi-core processors.
  • the processor(s) may include any combination of ?general-purpose processors and ?dedicated processors (e.g., graphics processors, application ?processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to ?execute instructions stored in the memory/storage to enable various applications or ?operating systems to run on the device 1400.
  • processors of application circuitry 1402 may process IP data packets received from an EPC.
  • the baseband circuitry 1404 may include circuitry such as, but not limited to, one ?or more single-core or multi-core processors.
  • the baseband circuitry 1404 may include one or more baseband ?processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1406 and to generate baseband signals for a transmit signal path of the RF circuitry 1406.
  • Baseband processing circuity 1404 may interface with the application circuitry 1402 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1406.
  • the baseband circuitry 1404 may include a third generation (3G) baseband processor 1404 A, a fourth generation (4G) baseband processor 1404B, a fifth generation (5G) baseband processor 1404C, or other baseband processor(s) 1404D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 1404 e.g., one or more of baseband processors 1404A-D
  • baseband processors 1404A-D may be included in modules stored in the memory 1404G and executed via a Central Processing Unit (CPU) 1404E.
  • the radio control functions ? may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency ?shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 1404 may include Fast- Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast- Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 1404 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 1404 may include one or more audio digital signal processor(s) (DSP) 1404F.
  • the audio DSP(s) 1404F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband ?circuitry 1404 and the application circuitry 1402 may be implemented ?together such as, for example, on a system on a chip (SOC). ?
  • the baseband circuitry 1404 may provide for communication ?compatible with one or more radio technologies.
  • the ?baseband circuitry 1404 may support communication with an evolved universal terrestrial radio ?access network (EUTRAN) or other wireless metropolitan area networks WMA ), a ?wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio ?access network
  • WMA wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in ?which the baseband circuitry 1404 is configured to support radio communications of more than ?one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 1406 may enable communication with wireless networks using ?modulated ?electromagnetic radiation through a non-solid medium.
  • the ?RF circuitry 1406 may include switches, filters, amplifiers, etc. to facilitate the communication ?with the wireless network.
  • RF circuitry 1406 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1408 and provide baseband signals to the baseband circuitry 1404.
  • RF circuitry 1406 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1404 and provide RF output signals to the FEM circuitry 1408 for transmission.
  • the receive signal path of the RF circuitry 1406 may include mixer circuitry 1406a, amplifier circuitry 1406b and filter circuitry 1406c.
  • the transmit signal path of the RF circuitry 1406 may include filter circuitry 1406c and mixer circuitry 1406a.
  • RF circuitry 1406 may also include synthesizer circuitry 1406d for synthesizing a frequency for use by the mixer circuitry 1406a of the receive signal path and the transmit signal path.
  • the mixer circuitry 1406a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1408 based on the synthesized frequency provided by synthesizer circuitry 1406d.
  • the amplifier circuitry 1406b may be configured to amplify the down-converted signals and the filter circuitry 1406c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 1404 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1406a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1406a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1406d to generate RF output signals for the FEM circuitry 1408.
  • the baseband signals may be provided by the baseband circuitry 1404 and may be filtered by filter circuitry 1406c.
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 1406 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1404 may include a digital baseband interface to communicate with the RF circuitry 1406.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • the synthesizer circuitry 1406d may be a fractional- N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1406d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1406d may be configured to synthesize an output frequency for use by the mixer circuitry 1406a of the RF circuitry 1406 based on a frequency input and a divider control input.
  • the synthesizer circuitry 1406d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1404 or the applications processor 1402 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1402.
  • Synthesizer circuitry 1406d of the RF circuitry 1406 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 1406d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 1406 may include an IQ/polar converter.
  • FEM circuitry 1408 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1410, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1406 for further processing.
  • FEM circuitry 1408 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1406 for transmission by one or more of the one or more antennas 1410.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1406, solely in the FEM 1408, or in both the RF circuitry 1406 and the FEM 1408.
  • the FEM circuitry 1408 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1406).
  • the transmit signal path of the FEM circuitry 1408 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1406), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1410).
  • PA power amplifier
  • the PMC 1412 may manage power provided to the baseband circuitry 1404.
  • the PMC 1412 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 1412 may often be included when the device 1400 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 1412 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 14 shows the PMC 1412 coupled only with the baseband circuitry 1404.
  • the PMC 14 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1402, RF circuitry 1406, or FEM 1408.
  • the PMC 1412 may control, or otherwise be part of, various power saving mechanisms of the device 1400. For example, if the device 1400 is in an RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1400 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 1400 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 1400 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 1400 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 1402 and processors of the baseband circuitry 1404 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 1404 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1404 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 15 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 1404 of FIG. 14 may comprise processors 1404A-1404E and a memory 1404G utilized by said processors.
  • Each of the processors 1404A-1404E may include a memory interface, 1504A-1504E, respectively, to send/receive data to/from the memory 1404G.
  • the baseband circuitry 1404 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1512 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1404), an application circuitry interface 1514 (e.g., an interface to send/receive data to/from the application circuitry 1402 of FIG. 14), an RF circuitry interface 1516 (e.g., an interface to send/receive data to/from RF circuitry 1406 of FIG. 14), a wireless hardware connectivity interface 1518 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components,
  • NFC Near Field Communication
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components, and other communication components
  • power management interface 1520 e.g., an interface to send/receive power or control signals to/from the PMC 1412.
  • FIG. 16 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 1600 is shown as a communications protocol stack between the UE 1301 (or alternatively, the UE 1302), the RAN node 1311 (or alternatively, the RAN node 1312), and the MME 1321.
  • the PHY layer 1601 may transmit or receive information used by the MAC layer 1602 over one or more air interfaces.
  • the PHY layer 1601 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 1605.
  • AMC link adaptation or adaptive modulation and coding
  • the PHY layer 1601 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer 1602 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • the RLC layer 1603 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • the RLC layer 1603 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • PDUs protocol data units
  • ARQ automatic repeat request
  • the RLC layer 1603 may also execute re- segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • the PDCP layer 1604 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer 1605 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.
  • the UE 1301 and the RAN node 1311 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 1601, the MAC layer 1602, the RLC layer 1603, the PDCP layer 1604, and the RRC layer 1605.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 1606 form the highest stratum of the control plane between the UE 1301 and the MME 1321.
  • the NAS protocols 1606 support the mobility of the UE 1301 and the session management procedures to establish and maintain IP connectivity between the UE 1301 and the P-GW 1323.
  • the SI Application Protocol (Sl-AP) layer 1615 may support the functions of the SI interface and comprise Elementary Procedures (EPs).
  • An EP is a unit of interaction between the RAN node 1311 and the CN 1320.
  • the Sl-AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 1614 may ensure reliable delivery of signaling messages between the RAN node 1311 and the MME 1321 based, in part, on the IP protocol, supported by the IP layer 1613.
  • the L2 layer 1612 and the LI layer 1611 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 1311 and the MME 1321 may utilize an S 1 -MME interface to exchange control plane data via a protocol stack comprising the LI layer 1611, the L2 layer 1612, the IP layer 1613, the SCTP layer 1614, and the Sl-AP layer 1615.
  • FIG. 17 is an illustration of a user plane protocol stack in accordance with some embodiments.
  • a user plane 1700 is shown as a
  • the user plane 1700 may utilize at least some of the same protocol layers as the control plane 1600.
  • the UE 1301 and the RAN node 1311 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 1601, the MAC layer 1602, the RLC layer 1603, the PDCP layer 1604.
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 1704 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 1703 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 1311 and the S-GW 1322 may utilize an Sl-U interface to exchange user plane data via a protocol stack comprising the LI layer 1611, the L2 layer 1612, the UDP/IP layer 1703, and the GTP-U layer 1704.
  • the S-GW 1322 and the P-GW 1323 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 1611, the L2 layer 1612, the UDP/IP layer 1703, and the GTP-U layer 1704.
  • NAS protocols support the mobility of the UE 1301 and the session management procedures to establish and maintain IP connectivity between the UE 1301 and the P-GW 1323.
  • FIG. 18 illustrates components of a core network in accordance with some embodiments.
  • the components of the CN 1320 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non- transitory machine-readable storage medium).
  • Network Functions Virtualization NFV is utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums (described in further detail below).
  • a logical instantiation of the CN 1320 may be referred to as a network slice 1801.
  • a logical instantiation of a portion of the CN 1320 may be referred to as a network sub-slice 1802 (e.g., the network sub-slice 1802 is shown to include the PGW 1323 and the PCRF 1326).
  • NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • FIG. 19 is a block diagram illustrating components, according to some example embodiments, of a system 1900 to support NFV.
  • the system 1900 is illustrated as including a virtualized infrastructure manager (VIM) 1902, a network function virtualization infrastructure (NFVI) 1904, a VNF manager (VNFM) 1906, virtualized network functions (VNFs) 1908, an element manager (EM) 1910, an NFV Orchestrator (NFVO) 1912, and a network manager (NM) 1914.
  • VIP virtualized infrastructure manager
  • NFVI network function virtualization infrastructure
  • VNFM VNF manager
  • VNFs virtualized network functions
  • EM element manager
  • NFVO NFV Orchestrator
  • NM network manager
  • the VIM 1902 manages the resources of the NFVI 1904.
  • the NFVI 1904 can include physical or virtual resources and applications (including hypervisors) used to execute the system 1900.
  • the VIM 1902 may manage the life cycle of virtual resources with the FVI 1904 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.
  • VMs virtual machines
  • the VNFM 1906 may manage the VNFs 1908.
  • the VNFs 1908 may be used to execute EPC components/functions.
  • the VNFM 1906 may manage the life cycle of the VNFs 1908 and track performance, fault and security of the virtual aspects of VNFs 1908.
  • the EM 1910 may track the performance, fault and security of the functional aspects of VNFs 1908.
  • the tracking data from the VNFM 1906 and the EM 1910 may comprise, for example, performance measurement (PM) data used by the VIM 1902 or the NFVI 1904. Both the VNFM 1906 and the EM 1910 can scale up/down the quantity of VNFs of the system 1900.
  • PM performance measurement
  • the NFVO 1912 may coordinate, authorize, release and engage resources of the NFVI 1904 in order to provide the requested service (e.g., to execute an EPC function, component, or slice).
  • the NM 1914 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 1910).
  • FIG. 20 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG. 20 shows a diagrammatic representation of hardware resources 2000 including one or more processors (or processor cores) 2010, one or more memory/ storage devices 2020, and one or more communication resources 2030, each of which may be communicatively coupled via a bus 2040.
  • a hypervisor 2002 may be executed to provide an execution environment for one or more network slices/ sub-slices to utilize the hardware resources 2000
  • the processors 2010 may include, for example, a processor 2012 and a processor 2014.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the communication resources 2030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 2004 or one or more databases 2006 via a network 2008.
  • the communication resources 2030 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • wired communication components e.g., for coupling via a Universal Serial Bus (USB)
  • cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
  • NFC components e.g., NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • Instructions 2050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 2010 to perform any one or more of the methodologies discussed herein.
  • the instructions 2050 may reside, completely or partially, within at least one of the processors 2010 (e.g., within the processor's cache memory), the memory/storage devices 2020, or any suitable combination thereof.
  • any portion of the instructions 2050 may be transferred to the hardware resources 2000 from any combination of the peripheral devices 2004 or the databases 2006. Accordingly, the memory of processors 2010, the memory/storage devices 2020, the peripheral devices 2004, and the databases 2006 are examples of computer-readable and machine-readable media.
  • Example 1 is apparatus of a base station (BS) configurable for controlling bandwidth adaptation (BWA) operation of a user equipment (UE), the apparatus comprising: memory to store BWA capability information of the UE; and processing circuitry to: determine a call for BWA for the UE, wherein communication bandwidth of the UE is variably changed between a relatively narrower bandwidth during relatively low UE communication activity, and a relatively wider bandwidth during relatively high UE communication activity; determine BWA transition time of the UE based on the BWA capability information, the BWA transition time corresponding to a time interval during which the UE is unable to meet a minimum level of communication performance; generate a BWA transition command for transmission to the UE, the BWA transition command indicating a communication bandwidth change for the UE to institute; and in response to the BWA transition command, refrain from communicating with the UE during the BWA transition time.
  • BS base station
  • BWA transition command refrain from communicating with the UE during the BWA transition time.
  • Example 2 the subject matter of Example 1 includes, wherein the BWA operation includes variability of communication bandwidth of at least one channel selected from the group consisting of: a physical downlink control channel
  • PDCCH physical downlink shared channel
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • Example 3 the subject matter of Examples 1-2 includes, wherein the communication bandwidth change varies between a first bandwidth and a second bandwidth, wherein the first bandwidth is relatively wider than the second bandwidth.
  • Example 4 the subject matter of Examples 1-3 includes, wherein the minimum level of communication performance is defined in terms of probability of missed message acknowledgement messaging.
  • Example 5 the subject matter of Example 4 includes, wherein the minimum level of communication performance is defined as a probability of missed message acknowledgement messaging not exceeding 0.5%.
  • Example 6 the subject matter of Examples 1-5 includes, wherein the BWA capability information includes a UE-specific BWA transition time value.
  • Example 7 the subject matter of Examples 1-6 includes, wherein the BWA capability information includes a UE type indicator, and wherein the memory of the BS is to store a BWA transition time value corresponding to the UE type indicator.
  • Example 11 the subject matter of Examples 1-10 includes, wherein the memory and processing circuitry are incorporated as part of baseband processor circuitry.
  • Example 20 the subject matter of Examples 12-19 includes, wherein the memory and processing circuitry are incorporated as part of application processor circuitry.
  • Example 21 the subject matter of Examples 12-20 includes, wherein the memory and processing circuitry are incorporated as part of baseband processor circuitry.
  • BWA transition time of the UE based on the BWA capability information, the BWA transition time corresponding to a time interval during which the UE fails to meet a minimum level of communication performance; generate a BWA transition command for transmission to the UE, the BWA transition command indicating a communication bandwidth change for the UE to institute; and in response to the BWA transition command, refrain from communicating with the UE during the BWA transition time.
  • Example 30 the subject matter of Examples 26-29 includes, wherein the BWA capability information includes a UE-specific BWA transition time value.
  • Example 31 the subject matter of Examples 26-30 includes, wherein the BWA capability information includes a UE type indicator, and wherein the BS is to store a BWA transition time value corresponding to the UE type indicator.
  • a user equipment configurable for controlling bandwidth adaptation (BWA) and to communicate with a base station (BS)
  • BWA bandwidth adaptation
  • BS base station
  • the UE when executed on processing circuitry of a user equipment (UE) configurable for controlling bandwidth adaptation (BWA) and to communicate with a base station (BS), cause the UE to: communicate with the BS within a first bandwidth; determine a call for BWA transition, wherein communication bandwidth of the UE is variably changed between a relatively narrower bandwidth during relatively low UE communication activity, and a relatively wider bandwidth during relatively high UE communication activity; generate a BWA transition request in response to the call for BWA transition, the BWA transition request being encoded for transmission to the BS; decode a BWA transition command received from the BS, the BWA transition command indicating a communication bandwidth change for the UE to institute; in response to the BWA transition command, cause the UE to transition to communicating with the BS within a second bandwidth, wherein the second bandwidth is different from the first bandwidth, and wherein the transition from
  • Example 35 the subject matter of Example 34 includes, wherein the instructions are to further cause the UE to communicate with the BS within the first bandwidth while meeting the minimum level of communication performance, and wherein the instructions are to further cause the UE to communicate with the BS within the second bandwidth while meeting the minimum level of communication performance.
  • Example 36 the subject matter of Examples 34-35 includes, wherein the minimum level of communication performance is defined in terms of probability of missed message acknowledgement messaging.
  • Example 40 the subject matter of Examples 34-39 includes, wherein the instructions are to cause the UE to assess radio link quality based on measurement of reference signaling from the BS, wherein the radio link quality is assessed based on comparison of reference signaling measurement to radio link assessment criteria; and in response to the BWA transition command, the instructions are to vary the radio link assessment criteria commensurately with the transition from the first bandwidth to the second bandwidth.
  • Example 42 the subject matter of Example 41 includes, wherein the instructions are to cause the UE to: determine a call for BWA transition, wherein communication bandwidth of the UE is variably changed between a relatively narrower bandwidth during relatively low UE communication activity, and a relatively wider bandwidth during relatively high UE communication activity; and generate a BWA transition request in response to the call for BWA transition, the BWA transition request being encoded for transmission to the BS.
  • Example 45 the subject matter of Examples 43-44 includes, wherein the minimum level of communication performance is defined in terms of probability of missed message acknowledgement messaging.
  • Example 46 the subject matter of Example 45 includes, wherein the minimum level of communication performance is defined as a probability of missed message acknowledgement messaging not exceeding 0.5%.
  • Example 50 the subject matter of Examples 43-49 includes, wherein the means for refraining from communicating with the UE during the BWA transition time include means for allocating time-frequency resource elements during the BWA transition time to devices other than the UE.
  • Example 52 the subject matter of Example 51 includes, means for causing the UE to communicate with the BS within the first bandwidth while meeting the minimum level of communication performance, and means for further causing the UE to communicate with the BS within the second bandwidth while meeting the minimum level of communication performance.
  • Example 58 the subject matter of Examples 51-57 includes, means for causing the UE to assess radio link quality based on measurement of reference signaling from the BS, wherein the radio link quality is assessed based on comparison of reference signaling measurement to radio link assessment criteria; and means for varying the radio link assessment criteria commensurately with the transition from the first bandwidth to the second bandwidth in response to the BWA transition command.
  • Example 61 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-60.

Landscapes

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

Abstract

Une station de base (BS) est configurable pour commander le fonctionnement en adaptation de bande passante (BWA) d'un équipement d'utilisateur (UE). La BS détermine un temps de transition de BWA de l'UE sur la base des informations de capacité de BWA. Le temps de transition de BWA correspond à un intervalle de temps pendant lequel l'UE ne satisfait pas un niveau minimal défini de performances de communication. La BS génère une consigne de transition de BWA en vue d'un envoi à l'UE, la consigne de transition de BWA indiquant un changement de bande passante de communication à instaurer par l'UE. En réaction à la consigne de transition de BWA, la BS s'abstient de communiquer avec l'UE pendant le temps de transition de BWA.
PCT/US2018/016679 2017-02-03 2018-02-02 Dispositions facilitant la transition et la mesure d'adaptation de bande passante Ceased WO2018144892A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112018000223.3T DE112018000223T5 (de) 2017-02-03 2018-02-02 Massnahmen zum Ermöglichen des Übergangs und des Messens einer Bandbreitenanpassung

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762454457P 2017-02-03 2017-02-03
US62/454,457 2017-02-03

Publications (1)

Publication Number Publication Date
WO2018144892A1 true WO2018144892A1 (fr) 2018-08-09

Family

ID=63041129

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/016679 Ceased WO2018144892A1 (fr) 2017-02-03 2018-02-02 Dispositions facilitant la transition et la mesure d'adaptation de bande passante

Country Status (2)

Country Link
DE (1) DE112018000223T5 (fr)
WO (1) WO2018144892A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210337472A1 (en) * 2019-01-08 2021-10-28 Huawei Technologies Co., Ltd. Bwp adjustment method and apparatus

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040131016A1 (en) * 2003-01-08 2004-07-08 Hundal Sukhdeep S. System and method for adaptive bandwidth utilization for interoperability
US20060291432A1 (en) * 2005-06-22 2006-12-28 Xhafa Ariton E Methods and apparatus to perform dynamic channel management and dynamic bandwidth changes in wireless local area networks
US20110292915A1 (en) * 2009-12-08 2011-12-01 Qualcomm Incorporated Multiple carrier activation/deactivation in wireless communications
US20130242936A1 (en) * 2012-03-13 2013-09-19 Frederick J. Igo, JR. Time Slot and Frequency Allocation in Wireless Communication Networks
US20160127991A1 (en) * 2014-10-31 2016-05-05 Qualcomm Incorporated Dynamic bandwidth switching for reducing power consumption in wireless communication devices

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040131016A1 (en) * 2003-01-08 2004-07-08 Hundal Sukhdeep S. System and method for adaptive bandwidth utilization for interoperability
US20060291432A1 (en) * 2005-06-22 2006-12-28 Xhafa Ariton E Methods and apparatus to perform dynamic channel management and dynamic bandwidth changes in wireless local area networks
US20110292915A1 (en) * 2009-12-08 2011-12-01 Qualcomm Incorporated Multiple carrier activation/deactivation in wireless communications
US20130242936A1 (en) * 2012-03-13 2013-09-19 Frederick J. Igo, JR. Time Slot and Frequency Allocation in Wireless Communication Networks
US20160127991A1 (en) * 2014-10-31 2016-05-05 Qualcomm Incorporated Dynamic bandwidth switching for reducing power consumption in wireless communication devices

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210337472A1 (en) * 2019-01-08 2021-10-28 Huawei Technologies Co., Ltd. Bwp adjustment method and apparatus
US12108331B2 (en) * 2019-01-08 2024-10-01 Huawei Technologies Co., Ltd. BWP adjustment method and apparatus

Also Published As

Publication number Publication date
DE112018000223T5 (de) 2019-09-05

Similar Documents

Publication Publication Date Title
US11917626B2 (en) Uplink transmission for multi-panel operation
US12231182B2 (en) Radio link monitoring (RLM) evaluation mechanism for new radio (NR) systems
US11595995B2 (en) Intra- and inter-Rat co-existence and congestion control for LTE PC5-based vehicle-to-vehicle (V2V)
US12101153B2 (en) Group based beam reporting and channel state information reference signal configuration in new radio systems
US10771214B2 (en) System and method for uplink power contrl framework
CN110365458B (zh) 准共位（qcl）指示的系统和方法
US11824814B2 (en) Physical resource block indexing for coexistence of narrow band, carrier aggregation, and wide band user equipment in new radio
EP3682588B1 (fr) Rapport d'informations d'état de canal sur un canal partagé de liaison montante physique dans nouvelle radio
US20190173622A1 (en) Channel state and beam related information reporting
US11265091B2 (en) Apparatus and method for RSRP measurement and allocation of downlink transmission resources
US10812169B2 (en) User equipment measurements for new radio
WO2018064182A1 (fr) Adaptation de liaison pour une communication à faible latence ultra-fiable
US20190373497A1 (en) Measurement gap configuration for new radio (nr) systems
US20200107357A1 (en) Grantless uplink (gul) configuration
WO2018031649A1 (fr) Accès à des technologies existantes au moyen d'un équipement utilisateur
WO2019050544A1 (fr) Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral
WO2018144892A1 (fr) Dispositions facilitant la transition et la mesure d'adaptation de bande passante

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: 18747611

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 18747611

Country of ref document: EP

Kind code of ref document: A1