WO2018118788A1 - Reporting supported cellular capability combinations of a mobile user device - Google Patents

Reporting supported cellular capability combinations of a mobile user device Download PDF

Info

Publication number
WO2018118788A1
WO2018118788A1 PCT/US2017/067044 US2017067044W WO2018118788A1 WO 2018118788 A1 WO2018118788 A1 WO 2018118788A1 US 2017067044 W US2017067044 W US 2017067044W WO 2018118788 A1 WO2018118788 A1 WO 2018118788A1
Authority
WO
WIPO (PCT)
Prior art keywords
combination
capability
numerology
cellular
combinations
Prior art date
Application number
PCT/US2017/067044
Other languages
English (en)
French (fr)
Inventor
Jie Cui
Yang Tang
Candy YIU
Rui Huang
Original Assignee
Intel IP 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 IP Corporation filed Critical Intel IP Corporation
Priority to CN201780078559.8A priority Critical patent/CN110089064A/zh
Publication of WO2018118788A1 publication Critical patent/WO2018118788A1/en

Links

Classifications

    • 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/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present disclosure relates to cellular communications and more specifically to user equipment (UE) supported cellular capability combinations, including the combination information of frequency bands, numerology and/or beam capabilities.
  • UE user equipment
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
  • Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi.
  • 3GPP 3rd Generation Partnership Project
  • LTE long term evolution
  • IEEE 802.16 which is commonly known to industry groups as worldwide interoperability for microwave access
  • Wi-Fi wireless local area networks
  • the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Nodes can include a 5G Node, new radio (NR) node or g Node B (gNB).
  • NR new radio
  • gNB g Node B
  • RANs use a radio access technology (RAT) to communicate between the RAN Node and UE.
  • RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network.
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN enhanced data rates for GSM evolution
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN which provide access to communication services through a core network.
  • Each of the RANs operates according to a specific 3GPP RAT.
  • the GERAN implements GSM and/or EDGE RAT
  • the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
  • E- UTRAN implements LTE RAT.
  • UMTS universal mobile telecommunication system
  • a core network can be connected to the UE through the RAN Node.
  • the core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).
  • SGW serving gateway
  • PGW packet data network gateway
  • ANDSF access network detection and selection function
  • ePDG enhanced packet data gateway
  • MME mobility management entity
  • FIG. 1 is a ladder diagram illustrating a numerology capability enquiry consistent with embodiments disclosed herein.
  • FIG. 2 is a ladder diagram illustrating a beam capability enquiry consistent with embodiments disclosed herein.
  • FIG. 3 is a ladder diagram illustrating a new radio capability enquiry consistent with embodiments disclosed herein.
  • FIG. 4 is a flow chart illustrating a method for determining cellular combination capability for a user equipment for combinations of band, numerology or beam consistent with embodiments disclosed herein.
  • FIG. 5 is a schematic diagram illustrating the structure of a long term evolution (LTE) communication frame consistent with embodiments disclosed herein.
  • LTE long term evolution
  • FIG. 6 is a diagram illustrating an architecture of a system of a network consistent with embodiments disclosed herein.
  • FIG. 7 is a diagram illustrating example components of a device consistent with embodiments disclosed herein.
  • FIG. 8 is a diagram illustrating example interfaces of baseband circuitry consistent with embodiments disclosed herein.
  • FIG. 9 is a diagram illustrating a control plane protocol stack consistent with embodiments disclosed herein.
  • FIG. 10 is a block diagram illustrating components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies discussed herein.
  • a user equipment to communicate cellular combination capabilities, such as a combination of supported frequency band, beam and/or numerology, to a radio access network (RAN) node.
  • RAN radio access network
  • the network uses UE capability to determine how to provide the data.
  • NR new radio
  • NR can provide support for carrier aggregation (CA), including different carriers having same or different numerologies.
  • CA carrier aggregation
  • DC dual connectivity
  • NR+LTE combination can also be NR scenarios.
  • the UE reports the carrier combination capability to network and then network can configure the supported carriers for this UE.
  • the UE can report the UE capability to network, e.g. carrier/band combination capability, numerology combination capability and/or beam combination capability. Even though the band/numerology/beam combination capability can be reported to the network individually, it is also important to build some relations among these three dimensions.
  • the reporting mechanism can include more information, such as UE supported cellular capability combinations, for the NR systems to fix the separated reporting problem.
  • the capability reporting from UE may include the combination information of bands, numerology and beam.
  • FIG. 1 is a ladder diagram 100 illustrating a numerology capability enquiry.
  • a network 104 such as a gNB, can transmit a UENumerologyCapability Enquiry message 106 to a UE 102.
  • the UE 102 responds with a UENumerologyCapability Information message 108 to the network 104.
  • the messages 106 and 108 can include the information described in the following embodiments and/or examples.
  • Embodiment 1 individual numerology combination capability reporting is used.
  • the UE may report the supported combination of numerology on different carriers. If this UE supports a specific combination of numerology, e.g. subcarrier spacing, UE may report the possible supported combination on downlink (DL) and/or uplink (UL).
  • DL downlink
  • UL uplink
  • the network can send a numerology capability enquiry to UE to request the UE capability (e.g. the supported subcarrier spacing). After receiving this enquiry message, the UE reports its capability of numerology to the network.
  • UE e.g. the supported subcarrier spacing
  • the UE may report ⁇ nl, n2 ⁇ to the network, nl and n2 are two different numerologies, such as subcarrier spacing.
  • the UE can support simultaneous reception and/or transmitting with nl and n2 on different carriers under CA or DC. If nk(k>l) is subcarrier spacing numerology, it may represent (but is not limited to) 3.75kHz or 7.5kHz or 15kHz or 30kHz or 60kHz and so on.
  • the UE may report ⁇ nl, n2, ...nk ⁇ to network, nl, n2 and nk(k>l) are different numerologies, such as subcarrier spacing, which means UE can support simultaneous reception and/or transmitting with nl, n2 and nk(k>l) on different carriers under CA or DC. If nk(k>l) is subcarrier spacing numerology, it may represent (but is not limited to) 3.75kHz or 7.5kHz or 15kHz or 30kHz or 60kHz and so on.
  • the UE may report ⁇ nl, n2, ...nk ⁇ to network for downlink only or/and uplink only, nl, n2 and nk(k>l) are different numerologies, such as subcarrier spacing, which means UE can support simultaneous reception and/or transmitting with nl, n2 and nk(k>l) on different carriers under CA or DC. If nk(k>l) is subcarrier spacing numerology, it may represent (but is not limited to) 3.75kHz or 7.5kHz or 15kHz or 30kHz or 60kHz and so on.
  • FIG. 2 is a ladder diagram 200 illustrating a beam capability enquiry.
  • a network 204 such as a gNB, can transmit a UEBeamCapabilityEnquiry message 206 to a UE 202.
  • the UE 202 responds with a UEBeamCapabilitylnformation message 208 to the network 204.
  • the messages 206 and 208 can include the information described in the following embodiments and/or examples.
  • the UE can provided individual beam capability reporting. The UE may report whether it supports beam based measurement on multiple carriers or not for transmission (Tx) or/and reception (Rx). If this UE supports beam based measurement on the carriers for Tx or/and Rx, it reports this capability to network.
  • Tx transmission
  • Rx reception
  • the network can send a capability enquiry of beam based measurement and/or data reception/transmission to UE to request the UE capability (e.g. the supported beam based measurement and/or data reception/transmission in the component carriers). After receiving this enquiry message, the UE reports its capability of beam based measurement and/or data reception/transmission to the network.
  • the UE capability e.g. the supported beam based measurement and/or data reception/transmission in the component carriers.
  • UE reports 'false' or '0' or another indicator to the network to indicate that UE only supports beam based measurement and/or data reception/transmission on the primary carrier/cell.
  • This negative indicator means that on other component carriers/cells, except the primary carrier/cell, the UE can only conduct omni-directional measurement and/or data reception/transmission.
  • the UE reports 'true' or T or another indicator to network to indicate that UE supports beam based measurement and/or data reception/transmission on the component carriers/cell.
  • FIG. 3 is a ladder diagram 300 illustrating a new radio capability enquiry.
  • a network 304 such as a g B, can transmit a UE RCapabilityEnquiry message 306 to a UE 302.
  • the UE 302 responds with a UE RCapabilitylnformation message 308 to the network 304.
  • the messages 306 and 308 can include the information described in the following embodiments.
  • the UE can provide coupled capability reporting.
  • a supported numerology and/or beam based measurement/data-reception/data-transmission and/or duplex- mode is associated with the band combination or individual band in the combination.
  • This combination reporting allows the UE to report the numerology and/or beam and/or duplex- mode capability within the capability information of CA or DC.
  • the network sends a capability enquiry of R band combination to the UE to request the UE capability (e.g. the band combination capability and the supported numerology on component carriers). After receiving this enquiry message, the UE reports its capability of NR band combination to the network.
  • a first example combination can be band + numerology information. If a UE supports CA or DC of band A and band B, but the UE only supports some numerologies on band A and some numerologies on band B, the UE may report the capability to network by combinations.
  • the CA or DC band combination capability can include a Band indicator 1 : band A, supported numerologies on band A: e.g. subcarrier spacing information (all supported subcarrier spacing on this band); Band indicator 2: band B, supported
  • numerologies on band B e.g. subcarrier spacing information (all supported subcarrier spacing on this band). If the UE supports more than two component carriers, the signaling structure described above can be used, and the additional band indicator and associated supported numerology can be added.
  • a second example combination can be band + beam information. If a UE supports CA or DC of n bands, but the UE only supports beam based measurement and/or data reception/transmission on some of those bands, the UE can report the capability to network as combinations.
  • the CA or DC band combination capability can include a Band indicator 1 : band A, the UE supports beam based measurement and/or data reception/transmission on band A: Yes; Band indicator 2: band B, the UE supports beam based measurement and/or data reception/transmission on band B: No. If the UE supports more than two component carriers, the signaling structure described above can be used, and the additional band indicator and associated beam capability indicator can be added.
  • a third example combination can be band + numerology + beam information. If a UE supports CA or DC of band A and band B, but the UE only supports some numerologies on band A and some numerologies on band B, and the UE only supports beam based
  • the UE can report the capability to the network as combinations.
  • the CA or DC band combination capability can include a Band indicator 1 : band A, supported numerologies on band A: e.g. subcarrier spacing information (all supported subcarrier spacing on this band), the UE supports beam based measurement and/or data reception/transmission on band A: Yes; a Band indicator 2: band B, supported numerologies on band B: e.g. subcarrier spacing information (all supported subcarrier spacing on this band), UE supports beam based measurement and/or data reception/transmission on band B: No. If the UE supports more than two component carriers, the signaling structure described above can be used, and the additional band indicator and associated supported numerology and beam capability indicator can be added.
  • a fourth example combination can be numerology + beam information. If the UE supports CA or DC of numerology A and numerology B, but the UE only supports beam based measurement and/or data reception/transmission for numerology A, the UE can report the capability to network as combinations.
  • the CA or DC band combination capability can include supported numerologies A: e.g. subcarrier spacing information (all supported subcarrier spacing on this band), UE supports beam based measurement and/or data reception/transmission for numerology A: Yes; supported numerologies B: e.g. subcarrier spacing information (all supported subcarrier spacing on this band), UE supports beam based measurement and/or data reception/transmission for numerology B: No. If the UE supports more than two numerology combinations, the signaling structure described above can be used, and the additional numerology indicator and associated supported beam capability indicator can be added.
  • a fifth example combination can be numerology + duplex mode information. If the UE supports CA or DC of numerology A and numerology B, but the UE supports one or more specific duplex modes for numerology A and supports one or more specific duplex modes for numerology B, the UE reports the capability to network as combinations.
  • the CA or DC band combination capability can include supported numerologies A: subcarrier spacing information (supported subcarrier spacing on this band), UE support for duplex mode for numerology A: duplex mode x (e.g. FDD and/or TDD); supported numerologies B:
  • UE support for duplex mode for numerology B duplex mode y (e.g. FDD and/or TDD). If UE supports more than two numerology combinations, the signaling structure described above can be used, and the additional numerology indicator and associated supported duplex mode indicator could be added.
  • a sixth example combination can be band + numerology + beam + duplex mode information.
  • the UE supports CA or DC of band A and band B, but the UE only supports some numerologies on band A and some numerologies on band B, the UE only supports beam based measurement and/or data reception/transmission on specific band(s), and the UE only supports some duplex modes on band A or B.
  • the UE may report the capability to network as combinations.
  • the CA or DC band combination capability can include Band indicator 1 : band A, supported numerologies on band A: e.g.
  • subcarrier spacing information (all supported subcarrier spacing on this band), UE support for beam based measurement and/or data reception/transmission on band A: Yes, UE support for duplex mode on band A: duplex mode x (e.g. FDD and/or TDD); Band indicator 2: band B, supported numerologies on band B: subcarrier spacing information (supported subcarrier spacing on this band), UE support for beam based measurement and/or data reception/transmission on band B: No, UE support for duplex mode on band B: duplex mode y (e.g. FDD and/or TDD). If the UE supports more than two component carriers, the signaling structure described above can be used and the additional band indicator, associated supported numerology and beam capability indicator and associated supported duplex modes can be added.
  • duplex mode x e.g. FDD and/or TDD
  • Band indicator 2 band B, supported numerologies on band B: subcarrier spacing information (supported subcarrier spacing on this band)
  • a seventh example combination can be numerology + beam + duplex mode information.
  • the UE supports CA or DC of numerology A and numerology B, but the UE only supports beam based measurement and/or data reception/transmission for numerology A, supports one or more specific duplex modes for numerology A, and supports one or more specific duplex modes for numerology B.
  • the UE reports the capability to network as combinations.
  • the CA or DC band combination capability can include supported
  • numerologies A e.g. subcarrier spacing information (supported subcarrier spacing on this band), UE support for beam based measurement and/or data reception/transmission for numerology A: Yes, UE support for duplex mode for numerology A: duplex mode x (e.g. FDD and/or TDD); supported numerologies B: e.g. subcarrier spacing information (all supported subcarrier spacing on this band), UE support for beam based measurement and/or data reception/transmission for numerology B: Yes, UE support for duplex mode for numerology B: duplex mode y (e.g. FDD and/or TDD).
  • the signaling structure described above can be used and the additional numerology indicator, associated supported beam information and associated supported duplex mode indicator can be added.
  • the UE reports a number of carriers on which UE can conduct beam based measurement and/or data reception/transmission.
  • the network sends a capability enquiry of beam based measurement and/or data reception/transmission to target UE. After receiving this enquiry message, the UE reports its capability of the number of carriers for which this UE can conduct beam based measurement and/or data reception/transmission. For example, the UE is able to support beam based measurement and/or data
  • the UE will report this information to the network.
  • the signaling can include UE beam capability for CA or DC that includes carrier number and/or carrier index.
  • the carrier number represents the maximum number of carriers on which this UE is able to conduct the beam based measurement and/or data
  • the carrier index represents the index of a carrier on which this UE is able to conduct the beam based measurement and/or data reception/transmission.
  • FIG. 4 is a flow chart illustrating a method 400 for determining cellular combination capability for a user equipment for combinations of band, numerology or beam.
  • the method can be accomplished by systems such as those shown in FIGs. 1-3 and 6. This includes UE 102 and network 104 (or e B or gNB).
  • the UE processes, from the RAN node using an interface, a request for a cellular combination capability that includes one or more UE supported combinations of band capabilities, numerology capabilities or beam
  • the UE determines the cellular combination capability for the UE based on at least two UE capabilities forming at least one UE supported combination, the UE capabilities from at least two different categories, the categories including band capabilities, numerology capabilities and beam capabilities.
  • the UE generates a response indicating the cellular combination capability.
  • the UE provides the response to the interface for transmission to the RAN node.
  • FIG. 5 is a schematic diagram 500 illustrating the structure of a long term evolution (LTE) communication frame 505. While a NR frame can vary in numerology and other ways, description of an LTE frame can help to understand frame terminology.
  • a frame 505 has a duration of 10 milliseconds (ms).
  • the frame 505 includes ten subframes 510, each having a duration of 1 ms.
  • Each subframe 510 includes two slots 515, each having a duration of 0.5 ms. Therefore, the frame 505 includes 20 slots 515.
  • Each slot 515 includes six or seven orthogonal frequency-division multiplexing (OFDM) symbols 520.
  • the number of OFDM symbols 520 in each slot 515 is based on the size of the cyclic prefixes (CP) 525. For example, the number of OFDM symbols 520 in the slot 515 is seven while in normal mode CP and six in extended mode CP.
  • CP cyclic prefixes
  • the smallest allocable unit for transmission is a resource block 530 (i.e., physical resource block (PRB) 530). Transmissions are scheduled by PRB 530.
  • a PRB 530 consists of 12 consecutive subcarriers 535, or 180 kHz, for the duration of one slot 515 (0.5 ms).
  • Each PRB 530 consists of 72 resource elements 540 in the case of extended mode CP.
  • FIG. 6 illustrates an architecture of a system 600 of a network in accordance with some embodiments.
  • the system 600 is shown to include a user equipment (UE) 601 and a UE 602.
  • the UEs 601 and 602 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • any of the UEs 601 and 602 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity -Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • background applications e.g., keep-alive messages, status updates, etc.
  • the UEs 601 and 602 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 610.
  • the RAN 610 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 UEs 601 and 602 utilize connections 603 and 604, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 603 and 604 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 3 GPP 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 UEs 601 and 602 may further directly exchange
  • the ProSe interface 605 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 (PS SCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink
  • PSCCH Physical Sidelink Control Channel
  • PS SCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Broadcast Channel
  • the UE 602 is shown to be configured to access an access point (AP) 606 via connection 607.
  • the connection 607 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 606 would comprise a wireless fidelity (WiFi®) router.
  • the AP 606 may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 610 can include one or more access nodes that enable the connections 603 and 604.
  • the access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 610 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 611, 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 612.
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g
  • any of the RAN nodes 611 and 612 can terminate the air interface protocol and can be the first point of contact for the UEs 601 and 602.
  • any of the RAN nodes 611 and 612 can fulfill various logical functions for the RAN 610 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
  • the UEs 601 and 602 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 611 and 612 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink
  • 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 is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds 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.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are 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 UEs 601 and 602.
  • 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 UEs 601 and 602 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 UE 602 within a cell) may be performed at any of the RAN nodes 611 and 612 based on channel quality information fed back from any of the UEs 601 and 602.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 601 and 602.
  • 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).
  • RAGs resource element groups
  • 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 embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments 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 the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 610 is shown to be communicatively coupled to a core network (CN) 620 — via an SI interface 613.
  • the CN 620 may be an evolved packet core (EPC) network, a NextGen Packet Core ( PC) network, or some other type of CN.
  • EPC evolved packet core
  • PC NextGen Packet Core
  • the SI interface 613 is split into two parts: the Sl-U interface 614, which carries traffic data between the RAN nodes 611 and 612 and a serving gateway (S-GW) 622, and an SI -mobility management entity (MME) interface 615, which is a signaling interface between the RAN nodes 611 and 612 and MMEs 621.
  • S-GW serving gateway
  • MME SI -mobility management entity
  • the CN 620 comprises the MMEs 621, the S-GW 622, a Packet Data Network (PDN) Gateway (P-GW) 623, and a home subscriber server (HSS) 624.
  • the MMEs 621 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 621 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 624 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 620 may comprise one or several HSSs 624, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 624 can provide support for routing/roaming, authentication, authorization,
  • the S-GW 622 may terminate the SI interface 613 towards the RAN 610, and routes data packets between the RAN 610 and the CN 620.
  • the S-GW 622 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 623 may terminate an SGi interface toward a PDN.
  • the P-GW 623 may route data packets between the CN 620 (e.g., an EPC network) and external networks such as a network including the application server 630 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 625.
  • an application server 630 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.).
  • the P-GW 623 is shown to be communicatively coupled to an application server 630 via an IP communications interface 625.
  • the application server 630 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 601 and 602 via the CN 620.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 623 may further be a node for policy enforcement and charging data collection.
  • a Policy and Charging Enforcement Function (PCRF) 626 is the policy and charging control element of the CN 620.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 626 may be communicatively coupled to the application server 630 via the P-GW 623.
  • the application server 630 may signal the PCRF 626 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 626 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 630.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 7 illustrates example components of a device 700 in accordance with some embodiments.
  • the device 700 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry 706, front-end module (FEM) circuitry 708, one or more antennas 710, and power management circuitry (PMC) 712 coupled together at least as shown.
  • the components of the illustrated device 700 may be included in a UE or a RAN node.
  • the device 700 may include fewer elements (e.g., a RAN node may not utilize application circuitry 702, and instead include a processor/controller to process IP data received from an EPC).
  • the device 700 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).
  • C-RAN Cloud-RAN
  • the application circuitry 702 may include one or more application processors.
  • the application circuitry 702 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
  • the baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706.
  • Baseband processing circuity 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706.
  • the baseband circuitry 704 may include a third generation (3G) baseband processor 704 A, a fourth generation (4G) baseband processor 704B, a fifth generation (5G) baseband processor 704C, or other baseband processor(s) 704D 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 704 e.g., one or more of baseband processors 704A-D
  • baseband processors 704 A-D may be included in modules stored in the memory 704G and executed via a Central Processing Unit (CPU) 704E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation,
  • modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 704 may include one or more audio digital signal processor(s) (DSP) 704F.
  • the audio DSP(s) 704F 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 704 and the application circuitry 702 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 704 may provide for example, on a system on a chip (SOC).
  • the baseband circuitry 704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 706 may enable communication with wireless networks
  • the RF circuitry 706 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 706 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704.
  • RF circuitry 706 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.
  • the receive signal path of the RF circuitry 706 may include mixer circuitry 706A, amplifier circuitry 706B and filter circuitry 706C. In some embodiments,
  • the transmit signal path of the RF circuitry 706 may include filter circuitry 706C and mixer circuitry 706 A.
  • RF circuitry 706 may also include synthesizer circuitry 706D for synthesizing a frequency for use by the mixer circuitry 706A of the receive signal path and the transmit signal path.
  • the mixer circuitry 706A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706D.
  • the amplifier circuitry 706B may be configured to amplify the down-converted signals and the filter circuitry 706C 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 704 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • the mixer circuitry 706A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 706A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706D to generate RF output signals for the FEM circuitry 708.
  • the baseband signals may be provided by the baseband circuitry 704 and may be filtered by the filter circuitry 706C.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A 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 706A of the receive signal path and the mixer circuitry 706A may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A 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 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 706.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 706D 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 706D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 706D may be configured to synthesize an output frequency for use by the mixer circuitry 706A of the RF circuitry 706 based on a frequency input and a divider control input.
  • the synthesizer circuitry 706D 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 704 or the application circuitry 702 (such as an applications processor) 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 application circuitry 702.
  • Synthesizer circuitry 706D of the RF circuitry 706 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.
  • the synthesizer circuitry 706D 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 706 may include an IQ/polar converter.
  • FEM circuitry 708 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing.
  • the FEM circuitry 708 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of the one or more antennas 710.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 706, solely in the FEM circuitry 708, or in both the RF circuitry 706 and the FEM circuitry 708.
  • the FEM circuitry 708 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 708 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 708 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 706).
  • the transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 710).
  • PA power amplifier
  • the PMC 712 may manage power provided to the baseband circuitry 704.
  • the PMC 712 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 712 may often be included when the device 700 is capable of being powered by a battery, for example, when the device 700 is included in a UE.
  • the PMC 712 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 7 shows the PMC 712 coupled only with the baseband circuitry 704.
  • the PMC 712 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 702, the RF circuitry 706, or the FEM circuitry 708.
  • the PMC 712 may control, or otherwise be part of, various power saving mechanisms of the device 700. For example, if the device 700 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 700 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 700 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 700 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 700 may not receive data in this state, and in order to receive data, it transitions back to an 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 702 and processors of the baseband circuitry 704 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 704 may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 702 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.
  • 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. 8 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 704 of FIG. 7 may comprise processors 704A-704E and a memory 704G utilized by said processors.
  • Each of the processors 704A-704E may include a memory interface, 804A-804E, respectively, to send/receive data to/from the memory 704G.
  • the baseband circuitry 704 may further include one or more interfaces to
  • a memory interface 812 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704
  • an application circuitry interface 814 e.g., an interface to send/receive data to/from the application circuitry 702 of FIG. 7
  • an RF circuitry interface 816 e.g., an interface to send/receive data to/from RF circuitry 706 of FIG.
  • a wireless hardware connectivity interface 818 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 820 e.g., an interface to send/receive power or control signals to/from the PMC 712.
  • FIG. 9 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 900 is shown as a communications protocol stack between the UE 601 (or alternatively, the UE 602), the RAN node 611 (or alternatively, the RAN node 612), and the MME 621.
  • a PHY layer 901 may transmit or receive information used by the MAC layer 902 over one or more air interfaces.
  • the PHY layer 901 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 an RRC layer 905.
  • the PHY layer 901 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 902 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
  • An RLC layer 903 may operate in a plurality of modes of operation, including:
  • the RLC layer 903 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.
  • the RLC layer 903 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.
  • a PDCP layer 904 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.).
  • SNs PDCP Sequence Numbers
  • the main services and functions of the RRC layer 905 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System
  • SIBs Information Blocks 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.
  • Said MIBs and SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.
  • IEs information elements
  • the UE 601 and the RAN node 611 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 901, the MAC layer 902, the RLC layer 903, the PDCP layer 904, and the RRC layer 905.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 906 form the highest stratum of the control plane between the UE 601 and the MME 621.
  • the NAS protocols 906 support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.
  • the SI Application Protocol (Sl-AP) layer 915 may support the functions of the SI interface and comprise Elementary Procedures (EPs).
  • An EP is a unit of interaction between the RAN node 611 and the CN 620.
  • 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 stream control transmission protocol/internet protocol (SCTP/IP) layer) 914 may ensure reliable delivery of signaling messages between the RAN node 611 and the MME 621 based, in part, on the IP protocol, supported by an IP layer 913.
  • An L2 layer 912 and an LI layer 911 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 611 and the MME 621 may utilize an SI -MME interface to exchange control plane data via a protocol stack comprising the LI layer 911, the L2 layer 912, the IP layer 913, the SCTP layer 914, and the Sl-AP layer 915.
  • FIG. 10 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.
  • FIG. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040.
  • node virtualization e.g., NFV
  • a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.
  • the processors 1010 may include, for example, a processor 1012 and a processor 1014.
  • 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 memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1020 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008.
  • the communication resources 1030 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 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein.
  • the instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor's cache memory), the memory/storage devices 1020, or any suitable combination thereof.
  • any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.
  • Example 1 is an apparatus of a user equipment (UE), comprising an interface and a processor.
  • the interface is configured to provide, for a radio access network (RAN) node, a cellular combination capability including a frequency band combination capability or a supported numerology capability.
  • RAN radio access network
  • the processor is coupled to the interface and configured to: process a request for the cellular combination capability that includes one or more UE supported combinations of frequency band capabilities, numerology capabilities or beam capabilities, wherein the request is received from the interface; determine the cellular combination capability for the UE based on at least two UE capabilities forming at least one UE supported combination, the UE capabilities from at least two different categories, the categories including frequency band capabilities, numerology capabilities and beam capabilities; generate a response indicating the cellular combination capability; and provide the response to the interface for transmission to the RAN node.
  • Example 2 is the apparatus of Example 1, wherein the processor is further configured to process a transmission from the RAN node using UE supported combinations indicated by the cellular combination capability.
  • Example 3 is the apparatus of Example 1, wherein the cellular combination capability comprises UE supported combinations of: frequency bands and numerology combinations; frequency bands and beam combinations; numerology and beam
  • Example 4 is the apparatus of Example 1, wherein the interface is a fifth generation new radio (5G NR) cellular interface.
  • 5G NR fifth generation new radio
  • Example 5 is the apparatus of Example 1, wherein the cellular combination capability comprises a combination of a frequency band indicator with: a subcarrier spacing support indicator, a beam based measurement support indicator, a beam based data transmission support indicator, a beam based data reception support indicator, or a duplex mode support indicator.
  • Example 6 is the apparatus of Example 1, wherein the cellular combination capability comprises a combination of a beam based measurement indicator with: a subcarrier spacing support indicator, or a duplex mode support indicator.
  • Example 7 is the apparatus of any of Examples 1-6, wherein the processor is a baseband processor.
  • Example 8 is an apparatus of a cellular base station, comprising: a memory interface to send and retrieve a cellular combination capability of a user equipment (UE); and a processor coupled to the memory interface.
  • the processor is configured to: generate a request for the cellular combination capability of the UE; provide the request for transmission to the UE; process a response from the UE including the cellular combination capability for the UE, the cellular combination capability including a supported combination of at least two UE capabilities from at least two different UE capability categories, the UE capability categories including frequency band, numerology and beam; and select a combination of frequency band, numerology and beam for use with the UE based at least in part on the cellular combination capability provided by the UE.
  • Example 9 is the apparatus of Example 8, wherein the cellular combination capability includes at least one supported combination of indicators, the at least one supported combination of indicators including at least two indicators selected from different categories, the categories comprising: a frequency band indicator, a subcarrier spacing support indicator, a beam based measurement support indicator, a beam based data transmission support indicator, a beam based data reception support indicator, and a duplex mode support indicator.
  • Example 10 is the apparatus of Example 8, wherein the request is a new radio capability enquiry request.
  • Example 11 is the apparatus of Example 8, wherein the response is a new radio capability information response.
  • Example 12 is the apparatus of any of Examples 8-11, wherein the cellular combination capability includes an indicator that indicates whether the cellular combination capability applies to uplink (UL) communications or downlink (DL) communications.
  • UL uplink
  • DL downlink
  • Example 13 is the apparatus of any of Examples 8-11, wherein the processor is a baseband processor.
  • Example 14 is a method of determining user equipment (UE) capability for combinations of frequency band, numerology or beam, the method comprising: generating a request for a combination capability of a UE, the combination capability including at least one supported combination selected from: frequency band and numerology combinations; frequency band and beam combinations; numerology and beam combinations; or frequency bands, numerology and beam combinations; transmitting the request to the UE; processing a response from the UE including the combination capability for the UE based on UE supported combinations; and selecting a combination of frequency band, numerology and beam based at least in part on the combination capability provided by the UE.
  • UE user equipment
  • Example 15 is the method of Example 14, wherein the combination capability indicates support for a first combination of a first frequency band and a first numerology combination, a second combination of the first frequency band and a second numerology combination, a third combination of a second frequency band and the first numerology combination, but not a fourth combination of the second frequency band and the second numerology combination.
  • Example 16 is the method of Example 14, wherein the combination capability indicates support for a first combination of a first beam and a first numerology combination, a second combination of the first beam and a second numerology combination, a third combination of a second beam and the first numerology combination, but not a fourth combination of the second beam and the second numerology combination.
  • Example 17 is the method of Example 14, wherein the request is a new radio numerology capability enquiry request, new radio beam capability request or new radio capability enquiry.
  • Example 18 is an apparatus comprising means to perform a method as claimed in any of Examples 14-17.
  • Example 19 is a machine-readable storage including machine-readable
  • Example 20 is a machine readable medium including code, when executed, to cause a machine to perform the method of any one of Examples 14-17.
  • Example 21 is a computer program product comprising a computer-readable storage medium that stores instructions for execution by a processor to perform operations of a cellular base station, the operations, when executed by the processor, to perform a method, the method comprising: generating a request for a combination capability of the UE, the combination capability including at least one supported combination selected from: band and numerology combinations; band and beam combinations; numerology and beam
  • Example 22 is an apparatus of a radio access network (RAN) node, the apparatus comprising: means for generating a request for a combination capability of the UE, the combination capability including at least one supported combination selected from: band and numerology combinations; band and beam combinations; numerology and beam
  • RAN radio access network
  • Additional Example 1 may be an apparatus comprising: means for identifying or causing to identify a received signal containing a capability enquiry; means for determining or causing to determine a capability of a UE, wherein the capability is a numerology, beam- based measurement, data reception, data transmission, or duplex mode; and means for transmitting or causing to transmit the determined capability to a network.
  • Additional Example 2 may include the subject matter of Additional Example 1, or of any other Additional Example herein, wherein the numerology includes subcarrier spacing information.
  • Additional Example 3 may include the subject matter of Additional Example 1, or of any other Additional Example herein, wherein the capability may include support of one or more numerologies on each band.
  • Additional Example 4 may include the subject matter of Additional Example 1, or of any other Additional Example herein, wherein the capability may include support of beam- based measurement or data reception, or data transmission on each band.
  • Additional Example 5 may include the subject matter of Additional Example 1, or of any other Additional Example herein, wherein the capability may include support of beam- based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 6 may include the subject matter of Additional Example 1, or of any other Additional Example herein, wherein the capability may include support of duplex modes, beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 7 may include the subject matter of Additional Example 1, or of any other Additional Example herein wherein the capability may include the number of carriers or index of carriers on which the UE apparatus may conduct a beam-based measurement, data reception, or data transmission.
  • Additional Example 8 may include the subject matter of Additional Example 1, or of any other Additional Example herein, wherein the duplex mode may include frequency domain duplexing (FDD) or time domain duplexing (TDD).
  • FDD frequency domain duplexing
  • TDD time domain duplexing
  • Additional Example 9 may include the subject matter of any one of Additional Examples 1-8, wherein the apparatus is a user equipment (UE) or a portion thereof.
  • UE user equipment
  • Additional Example 10 may be an apparatus comprising: means for transmitting or causing to transmit a capability inquiry to a UE; means for identifying or causing to identify a received signal from the UE; and means for determining or causing to determine, based upon the received signal, a capability of the UE, wherein the capability is a
  • numerology numerology, beam-based measurement, data reception, data transmission, or duplex mode of the UE.
  • Additional Example 11 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the numerology includes subcarrier spacing information.
  • Additional Example 12 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the capability may include support of one or more numerologies on each band.
  • Additional Example 13 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement or data reception, or data transmission on each band.
  • Additional Example 14 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 15 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the capability may include support of duplex modes, beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 16 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the capability may include the number of carriers or index of carriers on which the UE apparatus may conduct a beam-based measurement, data reception, or data transmission.
  • Additional Example 17 may include the subject matter of Additional Example 10, or of any other Additional Example herein, wherein the duplex mode may include frequency domain duplexing (FDD) or time domain duplexing (TDD).
  • FDD frequency domain duplexing
  • TDD time domain duplexing
  • Additional Example 18 may include the subject matter of any one of Additional Examples 10-17, wherein the apparatus is performed by a next generation NodeB (gNB) or a portion thereof.
  • gNB next generation NodeB
  • Additional Example 19 may include the UE that may report the capability of numerology (e.g. subcarrier spacing information), and/or beam based measurement and/or data reception/transmission, and/or duplex mode together with band indicator to network.
  • numerology e.g. subcarrier spacing information
  • Additional Example 20 may include the UE that may report capability of supporting one or more numerologies on each band to network.
  • Additional Example 21 may include the UE that may report capability of supporting beam based measurement and/or data reception/transmission on each band to network.
  • Additional Example 22 may include the UE that may report capability of supporting beam based measurement and/or data reception/transmission for each associated numerology (e.g. subcarrier spacing information) to network.
  • numerology e.g. subcarrier spacing information
  • Additional Example 23 may include the UE that may report capability of supporting duplex modes for each associated numerology (e.g. subcarrier spacing
  • Additional Example 24 may include the UE that may report capability of supporting duplex modes, and/or beam based measurement and/or data
  • reception/transmission for each associated numerology (e.g. subcarrier spacing information) to network.
  • numerology e.g. subcarrier spacing information
  • Additional Example 25 may include the UE that may report number and/or index of carriers on which UE can conduct beam based measurement and/or data
  • Additional Example 26 may be a user equipment (UE) apparatus to: identify or cause to identify a received signal containing a capability enquiry; determine a capability of the UE, wherein the capability is a numerology, beam-based measurement, data reception, data transmission, or duplex mode; and transmit the determined capability to a network.
  • UE user equipment
  • Additional Example 27 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the numerology includes subcarrier spacing information.
  • Additional Example 28 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the capability may include support of one or more numerologies on each band.
  • Additional Example 29 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement or data reception, or data transmission on each band.
  • Additional Example 30 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 31 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the capability may include support of duplex modes, beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 32 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the capability may include the number of carriers or index of carriers on which the UE apparatus may conduct a beam-based measurement, data reception, or data transmission.
  • Additional Example 33 may include the subject matter of Additional Example 26, or of any other Additional Example herein, wherein the duplex mode may include frequency domain duplexing (FDD) or time domain duplexing (TDD).
  • FDD frequency domain duplexing
  • TDD time domain duplexing
  • Additional Example 34 may be a next generation NodeB (g B) apparatus to: transmit or cause to transmit a capability inquiry to a UE; identify or cause to identify a received signal from the UE; and determine, based upon the received signal, a capability of the UE, wherein the capability is a numerology, beam-based measurement, data reception, data transmission, or duplex mode of the UE.
  • g B next generation NodeB
  • Additional Example 35 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the numerology includes subcarrier spacing information.
  • Additional Example 36 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the capability may include support of one or more numerologies on each band.
  • Additional Example 37 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement or data reception, or data transmission on each band.
  • Additional Example 38 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement, data reception, or data transmission for each associated
  • Additional Example 39 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the capability may include support of duplex modes, beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 40 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the capability may include the number of carriers or index of carriers on which the UE apparatus may conduct a beam-based measurement, data reception, or data transmission.
  • Additional Example 41 may include the subject matter of Additional Example 34, or of any other Additional Example herein, wherein the duplex mode may include frequency domain duplexing (FDD) or time domain duplexing (TDD).
  • FDD frequency domain duplexing
  • TDD time domain duplexing
  • Additional Example 42 may be a method comprising: identifying or causing to identify a received signal containing a capability enquiry; determining or causing to determine a capability of a UE, wherein the capability is a numerology, beam-based measurement, data reception, data transmission, or duplex mode; and transmitting or causing to transmit the determined capability to a network.
  • Additional Example 43 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the numerology includes subcarrier spacing information.
  • Additional Example 44 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the capability may include support of one or more numerologies on each band.
  • Additional Example 45 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the capability may include support of beam- based measurement or data reception, or data transmission on each band.
  • Additional Example 46 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the capability may include support of beam- based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 47 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the capability may include support of duplex modes, beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 48 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the capability may include the number of carriers or index of carriers on which the UE apparatus may conduct a beam-based measurement, data reception, or data transmission.
  • Additional Example 49 may include the subject matter of Additional Example 42, or any other Additional Example herein, wherein the duplex mode may include frequency domain duplexing (FDD) or time domain duplexing (TDD).
  • FDD frequency domain duplexing
  • TDD time domain duplexing
  • Additional Example 50 may include the method of Additional Example 42, or of any other Additional Example herein, wherein the method is performed by a user
  • UE user equipment
  • Additional Example 51 may be a method comprising: transmitting or causing to transmit a capability inquiry to a UE; identifying or causing to identify a received signal from the UE; determining or causing to determine, based upon the received signal, a capability of the UE, wherein the capability is a numerology, beam-based measurement, data reception, data transmission, or duplex mode of the UE.
  • Additional Example 52 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the numerology includes subcarrier spacing information.
  • Additional Example 53 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the capability may include support of one or more numerologies on each band.
  • Additional Example 54 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement or data reception, or data transmission on each band.
  • Additional Example 55 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the capability may include support of beam-based measurement, data reception, or data transmission for each associated
  • Additional Example 56 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the capability may include support of duplex modes, beam-based measurement, data reception, or data transmission for each associated numerology.
  • Additional Example 57 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the capability may include the number of carriers or index of carriers on which the UE apparatus may conduct a beam-based measurement, data reception, or data transmission.
  • Additional Example 58 may include the subject matter of Additional Example 51, or of any other Additional Example herein, wherein the duplex mode may include frequency domain duplexing (FDD) or time domain duplexing (TDD).
  • FDD frequency domain duplexing
  • TDD time domain duplexing
  • Additional Example 59 may include the method of Additional Example 51, or of any other Additional Example herein, wherein the method is performed by a next generation NodeB (g B) or a portion thereof.
  • g B next generation NodeB
  • Additional Example 60 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of Additional Examples 1- 59, or any other method or process described herein.
  • Additional Example 61 may include one or more non-transitory computer- readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of Additional Examples 1- 59, or any other method or process described herein.
  • Additional Example 62 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of Additional Examples 1- 59, or any other method or process described herein.
  • Additional Example 63 may include a method, technique, or process as described in or related to any of Additional Examples 1- 59, or portions or parts thereof.
  • Additional Example 64 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of Additional Examples 1- 59, or portions thereof.
  • Additional Example 65 may include a method of communicating in a wireless network as shown and described herein.
  • Additional Example 66 may include a system for providing wireless
  • Additional Example 67 may include a device for providing wireless
  • Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
  • a computer system may include one or more general- purpose or special-purpose computers (or other electronic devices).
  • the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
  • Suitable networks for configuration and/or use as described herein include one or more local area networks, wide area networks, metropolitan area networks, and/or Internet or IP networks, such as the World Wide Web, a private Internet, a secure Internet, a value-added network, a virtual private network, an extranet, an intranet, or even stand-alone machines which communicate with other machines by physical transport of media.
  • a suitable network may be formed from parts or entireties of two or more other networks, including networks using disparate hardware and network communication technologies.
  • One suitable network includes a server and one or more clients; other suitable networks may contain other combinations of servers, clients, and/or peer-to-peer nodes, and a given computer system may function both as a client and as a server.
  • Each network includes at least two computers or computer systems, such as the server and/or clients.
  • a computer system may include a workstation, laptop computer, disconnectable mobile computer, server, mainframe, cluster, so-called “network computer” or "thin client,” tablet, smart phone, personal digital assistant or other hand-held computing device, "smart” consumer electronics device or appliance, medical device, or a combination thereof.
  • Suitable networks may include communications or networking software, such as the software available from Novell®, Microsoft®, and other vendors, and may operate using TCP/IP, SPX, IPX, and other protocols over twisted pair, coaxial, or optical fiber cables, telephone lines, radio waves, satellites, microwave relays, modulated AC power lines, physical media transfer, and/or other data transmission "wires" known to those of skill in the art.
  • the network may encompass smaller networks and/or be connectable to other networks through a gateway or similar mechanism.
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD- ROMs, hard drives, magnetic or optical cards, solid-state memory devices, a nontransitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and nonvolatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or other medium for storing electronic data.
  • the eNB (or g B or other base station) and UE (or other mobile station) may also include a transceiver component, a counter component, a processing component, and/or a clock component or timer component.
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
  • API application programming interface
  • Each computer system includes one or more processors and/or memory; computer systems may also include various input devices and/or output devices.
  • the processor may include a general purpose device, such as an Intel®, AMD®, or other "off-the-shelf microprocessor.
  • the processor may include a special purpose processing device, such as ASIC, SoC, SiP, FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.
  • the memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, or other computer storage medium.
  • the input device(s) may include a keyboard, mouse, touch screen, light pen, tablet, microphone, sensor, or other hardware with accompanying firmware and/or software.
  • the output device(s) may include a monitor or other display, printer, speech or text synthesizer, switch, signal line, or other hardware with accompanying firmware and/or software.
  • a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, or off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very large scale integration
  • a component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • Components may also be implemented in software for execution by various types of processors.
  • An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function. Nevertheless, the executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.
  • a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within components, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the components may be passive or active, including agents operable to perform desired functions.
  • a software module or component may include any type of computer instruction or computer-executable code located within a memory device.
  • a software module may, for instance, include one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that perform one or more tasks or implement particular data types. It is appreciated that a software module may be implemented in hardware and/or firmware instead of or in addition to software.
  • One or more of the functional modules described herein may be separated into sub-modules and/or combined into a single or smaller number of modules.
  • a particular software module may include disparate instructions stored in different locations of a memory device, different memory devices, or different computers, which together implement the described functionality of the module.
  • a module may include a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices.
  • Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network.
  • software modules may be located in local and/or remote memory storage devices.
  • data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.
  • parameters/attributes/aspects/etc. of one embodiment can be used in another embodiment.
  • the parameters/attributes/aspects /etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters/attributes/aspects /etc. can be combined with or substituted for

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/US2017/067044 2016-12-19 2017-12-18 Reporting supported cellular capability combinations of a mobile user device WO2018118788A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201780078559.8A CN110089064A (zh) 2016-12-19 2017-12-18 上报移动用户设备所支持的蜂窝能力组合

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662436300P 2016-12-19 2016-12-19
US62/436,300 2016-12-19

Publications (1)

Publication Number Publication Date
WO2018118788A1 true WO2018118788A1 (en) 2018-06-28

Family

ID=61007795

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/067044 WO2018118788A1 (en) 2016-12-19 2017-12-18 Reporting supported cellular capability combinations of a mobile user device

Country Status (2)

Country Link
CN (1) CN110089064A (zh)
WO (1) WO2018118788A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112586015A (zh) * 2018-09-14 2021-03-30 谷歌有限责任公司 传送用户设备能力
CN112740826A (zh) * 2018-12-29 2021-04-30 华为技术有限公司 一种能力上报方法及终端设备
US11223981B2 (en) 2018-08-23 2022-01-11 Google Llc Managing inter-radio access technology capabilities of a user equipment
US20220240080A1 (en) * 2019-05-17 2022-07-28 Ntt Docomo, Inc. User equipment and base station apparatus
WO2024092832A1 (zh) * 2022-11-04 2024-05-10 北京小米移动软件有限公司 通信方法、装置、电子设备以及介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116634412A (zh) * 2022-02-11 2023-08-22 维沃移动通信有限公司 终端目标面能力上报、获取方法、终端及网络设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110319069A1 (en) * 2010-06-25 2011-12-29 Htc Corporation Apparatuses and methods for mobile capability signaling
US20160262053A1 (en) * 2014-03-20 2016-09-08 Telefonaktiebolaget L M Ericsson (Publ) Node and Method for Carrier Aggregation Compatibility Reporting of a Wireless Device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110319069A1 (en) * 2010-06-25 2011-12-29 Htc Corporation Apparatuses and methods for mobile capability signaling
US20160262053A1 (en) * 2014-03-20 2016-09-08 Telefonaktiebolaget L M Ericsson (Publ) Node and Method for Carrier Aggregation Compatibility Reporting of a Wireless Device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Frequency scalable NR design from <1 GHz to mmW", vol. RAN WG1, no. Busan, Korea; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051080020, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160402] *
ZAIDI ALI A ET AL: "Waveform and Numerology to Support 5G Services and Requirements", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER, PISCATAWAY, US, vol. 54, no. 11, 1 November 2016 (2016-11-01), pages 90 - 98, XP011634872, ISSN: 0163-6804, [retrieved on 20161115], DOI: 10.1109/MCOM.2016.1600336CM *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11223981B2 (en) 2018-08-23 2022-01-11 Google Llc Managing inter-radio access technology capabilities of a user equipment
CN112586015A (zh) * 2018-09-14 2021-03-30 谷歌有限责任公司 传送用户设备能力
CN112740826A (zh) * 2018-12-29 2021-04-30 华为技术有限公司 一种能力上报方法及终端设备
CN112740826B (zh) * 2018-12-29 2022-10-28 华为技术有限公司 一种能力上报方法及终端设备
US20220240080A1 (en) * 2019-05-17 2022-07-28 Ntt Docomo, Inc. User equipment and base station apparatus
WO2024092832A1 (zh) * 2022-11-04 2024-05-10 北京小米移动软件有限公司 通信方法、装置、电子设备以及介质

Also Published As

Publication number Publication date
CN110089064A (zh) 2019-08-02

Similar Documents

Publication Publication Date Title
EP3482602B1 (en) Systems, methods and devices for control-user plane separation for 5g radio access networks
US11122453B2 (en) Systems, methods and devices for measurement configuration by a secondary node in EN-DC
US10749587B2 (en) Systems, methods and devices for using S-measure with new radio
WO2018231813A1 (en) Systems, methods and devices for legacy system fallback in a cellular communications system
US10764822B2 (en) Systems, methods and devices for selecting a public land mobile network using coverage enhancement indicators
EP3590297B1 (en) Txop with continued lbt after a pause
US20220416986A1 (en) Physical Resource Block Indexing for Coexistence of Narrow Band, Carrier Aggregation, and Wide Band User Equipment in New Radio
US11044626B2 (en) Systems, methods, and apparatuses for configuring measurement gap per frequency group and per cell
US11265884B2 (en) Systems, methods and devices for uplink bearer and access category mapping
WO2018081597A1 (en) Ue behavior during srs switching among tdd component carriers
WO2018063998A1 (en) Systems, methods and devices for a mac-phy split interface
US11812414B2 (en) Interruption and delay for V2X sidelink carrier aggregation
US11265837B2 (en) System, method, and product for selecting timing information based on subcarrier spacing
US11082901B2 (en) Signaling of support for network controlled small gap, NCSG, for interruption control
WO2018125795A1 (en) Systems, methods and devices for congestion control for transport of user data via a control plane
US10856169B2 (en) Beam measurement and reporting in cellular networks
WO2018118788A1 (en) Reporting supported cellular capability combinations of a mobile user device
WO2018031135A1 (en) Systems, methods and devices for reporting and selecting medium access control and physical layer capabilities
WO2018063997A1 (en) Systems, methods and devices for selecting a measurement bandwidth
WO2018089213A1 (en) Systems, methods and devices for reducing network configuration searches by mapping physical cell identifiers to network configuration information
WO2018128894A1 (en) Systems, methods and devices for alarm notification in a network function virtualization infrastructure
WO2018102098A1 (en) Systems, methods and devices for managing harq buffer status
WO2018085029A1 (en) Srs switching to a target tdd-cc in a carrier aggegation based wireless communications system
US20210297867A1 (en) Measurement configuration techniques for wideband coverage enhancement (wce)-capable devices

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

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

Country of ref document: EP

Kind code of ref document: A1