WO2017197248A1 - Mappage de canal de transport sur canal physique à intervalles de temps de transmission extensibles - Google Patents

Mappage de canal de transport sur canal physique à intervalles de temps de transmission extensibles Download PDF

Info

Publication number
WO2017197248A1
WO2017197248A1 PCT/US2017/032380 US2017032380W WO2017197248A1 WO 2017197248 A1 WO2017197248 A1 WO 2017197248A1 US 2017032380 W US2017032380 W US 2017032380W WO 2017197248 A1 WO2017197248 A1 WO 2017197248A1
Authority
WO
WIPO (PCT)
Prior art keywords
mapping
tti
circuitry
physical
phy layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2017/032380
Other languages
English (en)
Inventor
Ralf Bendlin
Joonyoung Cho
Umesh PHUYAL
Hong He
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel IP Corp
Original Assignee
Intel IP Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corp filed Critical Intel IP Corp
Priority to DE112017002461.7T priority Critical patent/DE112017002461T5/de
Publication of WO2017197248A1 publication Critical patent/WO2017197248A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • 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) or 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/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority

Definitions

  • the present disclosure relates to mobile communication and, more
  • Mobile communication including cellular communication, involves the transfer of data between mobile devices.
  • the use of mobile communication is continuously increasing. Additionally, the bandwidth or data rate used and needed for mobile communications is continuously increasing.
  • FIG. 1 is a diagram illustrating an arrangement for mobile communications that facilitates transport channel to physical channel mapping with scalable or reduced transmission time intervals.
  • FIG. 2 is a diagram illustrating examples of subcarrier spacing for varied frequencies.
  • FIG. 3 is a diagram illustrating transport channel to PHY layer mappings in accordance with an embodiment.
  • FIG. 4 is a diagram illustrating transport channel to PHY layer mappings in accordance with an embodiment.
  • FIG. 5 is a flow diagram illustrating a method of mapping transport channel transport blocks to physical layer symbols by a node in accordance with an
  • FIG. 6 is a diagram illustrating transport channel to PHY layer mappings using a queue and a transmission time interval of 0.5 ms in accordance with an embodiment.
  • FIG. 7 is a diagram illustrating transport channel to PHY layer mappings using a queue and a transmission time interval of 0.25 ms in accordance with an embodiment.
  • FIG. 8 is a diagram illustrating transport channel to PHY layer mappings using a queue and a transmission time interval of 0.125 in accordance with an embodiment.
  • FIGS. 9A and 9B are diagrams illustrating transport channel to PHY layer mappings using a 17.5 subcarrier frequency in accordance with an embodiment.
  • FIG. 10 illustrates an architecture of a system of a network in accordance with some embodiments.
  • FIG. 1 1 illustrates example components of a device in accordance with some embodiments.
  • FIG. 12 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • FIG. 13 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • FIG. 14 is an illustration of a user plane protocol stack in accordance with some embodiments.
  • FIG. 15 illustrates components of a core network in accordance with some embodiments.
  • FIG. 16 is a block diagram illustrating components, according to some example embodiments, of a system to support NFV.
  • FIG. 17 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer- readable medium e.g., a non-transitory machine-readable storage medium
  • a component can be a processor (e.g., a processor
  • microprocessor a controller, or other processing device
  • a process running on a processor a controller, an object, an executable, a program, a storage device, a computer, a tablet PC, an electronic circuit and/or a mobile phone with a processing device.
  • an application running on a server and the server can also be a component.
  • One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers.
  • a set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more.”
  • these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example.
  • the components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors.
  • the one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application.
  • a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • LTE Long-term Evolution
  • 3GPP Third Generation Partnership Project
  • numerologies such as subcarrier spacings (7.5kHz and 15kHz), cyclic prefix (CP) lengths (normal and extended CP), transmission time interval (TTI) durations (1 ms and 40ms), system bandwidths (1 .4, 3, 5, 10, 15, 20MHz).
  • OFDM orthogonal frequency division multiplexing
  • the subcarrier spacing is an important design parameter for orthogonal frequency-division multiple access (OFDMA) systems. It can mitigate against oscillator phase noise and Doppler spread. Further, since the subcarrier spacing is reciprocal to the OFDM symbol duration, it impacts the number of OFDM symbols per subframe (assuming the latter is a time interval of fixed length) as well as the CP duration if the overhead induced from the CP is designed to be roughly constant. For instance, if the CP overhead is chosen to be x% of the useful symbol duration, increasing the subcarrier spacing would reduce the CP length.
  • OFDMMA orthogonal frequency-division multiple access
  • 5G fifth generation
  • NR new radio access technologies
  • derivative subcarrier spacings f sc can be defined based on scaling laws and the following two alternatives are considered:
  • TTI scalability is a feature.
  • a transmission time interval indicates inter-arrival time of transport blocks (TBs) on a given transport channel (TrCH).
  • TTI transmission time interval
  • PHY physical layer
  • N TBs once every TTI for the case of one TB per TTI per user equipment (UE). If N TBs are to be transmitted to a given UE in one TTI, N TBs arrive once per TTI.
  • LTE defines
  • TrCHs define the interface between the Medium
  • MAC Access
  • the TrCH for user data transmission is called DL-SCH and the corresponding physical channel is the Physical Downlink Shared Channel (PDSCH).
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • TTI scalability describes the technique to shorten or extend the inter-arrival time of TBs on a given TrCH (e.g., DL-SCH or UL-SCH). TTI shortening is an important technology for ultra-reliable low latency communications (URLLC).
  • URLLC ultra-reliable low latency communications
  • TTI shortening also typically requires adaptations in the PHY.
  • the TTI is defined as 1 ms, i.e., the length of one subframe.
  • Various embodiments are provided that facilitate handling channel mapping of various cases of TTI, including those where the number of symbols per subframe (or fixed time interval) is not a power of two.
  • FIG. 1 is a diagram illustrating an arrangement 1 00 for mobile
  • the arrangement 1 00 and/or portions of the arrangement 1 00 can also be incorporated into an apparatus, device and the like.
  • data arrives at a physical (PHY) layer in the form of transport blocks (TB) on transport channels (TrCH).
  • PHY physical
  • TTI transmission time intervals
  • numerology can include subcarrier spacing, TTI, symbols per subframe and the like.
  • the arrangement 100 includes a user equipment (UE) device 102, a transceiver 106, and nodes 120.
  • the nodes 120 include components/entities such as, but not limited to, a packet gateway (PGW), a secondary gateway (SGW), a mobility management entity (MME), a packet data network (PDN), UE devices, evolved Node Bs (eNodeB) or (eNB), access points (AP), base stations (BS) and the like.
  • the nodes 1 20 can also include network (NW) nodes.
  • the term network node refers to a node operated by a network operator and may share information with other nodes, such as UE devices.
  • a node 124 is shown as an eNodeB.
  • the UE 102 includes the transceiver 106, a storage component 1 18, and control circuitry or controller 104.
  • the storage component 1 18 includes a memory, storage element and the like and is configured to store information for the UE 102.
  • the controller 104 is configured to perform various operations associated with the UE 1 02.
  • the controller 104 can include logic, components, circuitry, one or more processors and the like. Further, the controller 104 can include and/or be part of baseband circuitry.
  • the transceiver 106 includes transmitter functionality and receiver functionality and can utilize an interface, referred to as an over the air interface. Further, the transceiver 106 is associated with RF circuitry.
  • the UE 102 also includes one or more antenna 108 for communications with the network entities 120.
  • the eNodeB 124 includes a transceiver, a storage component, and control circuitry or controller.
  • the storage component includes a memory, storage element and the like and is configured to store information for the eNodeB 124.
  • the controller is configured to perform various operations associated with the eNodeB 124.
  • the controller can include logic, components, circuitry, one or more processors and the like.
  • the transceiver 106 includes transmitter functionality and receiver functionality.
  • the eNodeB 124 can also include one or more antenna for communications with the nodes 120 and/or other UEs.
  • the control circuitry 104 of the UE 102 is configured to map transport blocks of transport channels of the MAC layer to the PHY layer using scalable numerology.
  • the PHY layer or physical channel uses a physical downlink shared channel (PDSCH) for downlink communications from the eNodeB 124 to the UE 102 and a physical uplink shared channel (PUSCH) for uplink communications to the eNodeB 124.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the control circuitry 104 is configured to adjust PHY layer parameters of the PHY layer to perform the mapping and, for example to shorten the TTI.
  • the PHY layer parameters include TTI, OFDM symbol length, use of guard periods (GP), use of control channels, symbol length of physical channels, subframe spacing, slot duration, and the like.
  • the PHY layer parameters can include and/or be part of the scalable numerology. Additional examples are provided below.
  • the control circuitry 104 is configured to adjust the PHY layer parameters, such as the TTI, based on communication characteristics. For example, the TTI can be reduced from 1 ms to 0.25 ms to improve reliability.
  • the communication characteristics include latency, data rate, reliability and the like.
  • the communication characteristics can be associated with a particular node, such as the eNodeB 124.
  • the mapping is performed by generating a mapping of the TBs to the PHY layer that includes guard periods (GP), control channels (CC), and the like.
  • the mapping is based on the determined PHY layer parameters.
  • the TBs are then mapped to the PHY layer based on the mapping.
  • the mapping is based on a first-in-first-out queue, where transport blocks are mapped to physical channels in the order received.
  • mapping involves identifying and arranging a number of physical channels, inserting gaps and/or adjusting resource span time.
  • the transceiver 106 is configured to transmit or receive the PHY layer, including physical channels, subframe, and/or the like.
  • the PHY layer parameter adjustment and/or mapping can be configured to achieve the communication
  • the control circuitry 104 can configured to reduce TTIs by reducing its original length by half.
  • a subframe having a TTI of 1 can be reduced to 0.5 by reducing the number of symbols in half, such as by 16 to 8.
  • control circuitry 104 is configured to reduce TTIs by inserting gaps as shown below with regard to FIG. 2.
  • control channels are used as gaps to perform suitable mapping.
  • the control channels can include a physical downlink control channel (PDCCH) symbol, so that a suitable mapping is obtained.
  • FIG. 3 describes examples of suitable techniques to perform the mapping using control channel symbols.
  • nodes including the eNodeB 1 24, can be configured to perform channel mapping as shown by the UE 102.
  • FIG. 2 is a diagram illustrating examples 200 of subcarrier spacing for varied frequencies.
  • the examples 200 are provided for illustrated purposes and to facilitate understanding. It is appreciated that the arrangement 100 and variations thereof can be utilized with the examples 200. Further, it is appreciated that embodiments are not limited to the example values provided.
  • the diagram depicts a 1 ms subframe from left to right and includes a 0.5 ms slot for a PHY layer.
  • the diagram shows a first example 201 , where its numerology includes a subcarrier spacing or derivative subcarrier spacing f sc of 15 kHz.
  • the diagram also shows a second example 202, where its numerology includes a subcarrier spacing or derivative subcarrier spacing f sc of 17.5 kHz. OFDM symbols are shown and have a fixed symbol length.
  • the slot length is 7 symbols.
  • the slot length is 8 symbols.
  • the TTIs can be shortened by reducing an original length of the TTI by half.
  • an original TTI of length 16 can be reduced to 8; an original TTI of length 8, can be reduced to 4 and so on.
  • the number of symbols per subframe is 16 OFDM symbols.
  • an original TTI of 16 symbols (1 ms) can be reduced by half, to 8 symbols (0.5 ms).
  • the reduced TTI is 8 symbols.
  • the number of symbols per subframe is 14, which is not a power of two.
  • reducing the TTI from its original length includes modifying PHY layer parameters and generating a mapping, including inserting gaps, guard periods, control channels, and the like.
  • FIG. 3 is a diagram illustrating transport channel to PHY layer mappings 300 in accordance with an embodiment.
  • the mappings 300 are provided for illustrated purposes and to facilitate understanding. It is appreciated that the arrangement 100 and variations thereof can be utilized with the shown mappings.
  • the mappings 300 are based on a subframe length of 1 ms, 15 kHz subcarrier spacing, and 14 OFDM symbols per subframe. It is appreciated that other numerologies can be utilized.
  • transport blocks of the transport channel are mapped to physical channels of the PHY layer.
  • transport channels such as downlink shared channel (DL-SCH) and uplink shared channel (UL-SCH)
  • PHY layer channels such as physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH) have lengths of equal duration.
  • a resource time span for the PHY layer channels is set to 3 OFDM symbols.
  • the number of OFDM symbols in the subframe is not a power of two, thus TTI reductions cannot be simply halved from original TTIs.
  • transport blocks are mapped to an integer number of physical channels. Symbols not used by or assigned to the physical channels can be used for other purposes and referred to as gaps.
  • the gaps include control channels, guard periods (GP) and the like.
  • the gaps can be inserted into the subframe at its beginning, end, and elsewhere in between as shown in the below examples.
  • a first mapping 301 uses 4 PDSCHs, each assigned a TTI and length of 3 symbols.
  • the 4 PDSCHs are for TBs using DL-SCHs.
  • a physical downlink control channel (PDCCH) is inserted at a beginning and a second PDCCH is inserted in a middle of the subframe.
  • PDCH physical downlink control channel
  • a second mapping 302 uses 4 PDSCHs for 4 TBs.
  • the 4 PDSCHs are arranged consecutively and two PDCCHs are inserted at a beginning of the subframe.
  • a third mapping 303 uses 3 PDSCHs for 3 TBs. Thus, there are 5 unused symbols.
  • two PDCCHs are inserted at a beginning of the subframe and a guard period (GP) and physical uplink control channel (PUCCH) are inserted at an end of the subframe as shown.
  • GP guard period
  • PUCCH physical uplink control channel
  • a fourth mapping 304 uses 4 physical uplink shared channels (PUSCH), which are arranged consecutively.
  • PUSCH physical uplink shared channels
  • a PDCCH and GP are inserted at a beginning of the subframe.
  • a fifth mapping 305 uses 3 PUSCH, instead of 4.
  • a PDCCH and GP are inserted at a beginning of the subframe.
  • a sounding reference signal (SRS) and PUCCH are attached at an end of the subframe.
  • the mappings 300 involve identifying and arranging a number of physical channels (PDSCH and/or PUSCH) to accommodate the transport blocks and inserting gaps.
  • FIG. 4 is a diagram illustrating transport channel to PHY layer mappings 400 in accordance with an embodiment.
  • the mappings 400 are provided for illustrated purposes and to facilitate understanding. It is appreciated that the arrangement 100 and variations thereof can be utilized with the shown mappings.
  • the mappings 400 are based on a subframe length of 1 ms, 15 kHz subcarrier spacing, and 14 OFDM symbols per subframe. It is appreciated that other numerologies can be utilized. A resource span time for each of the TTIs is variable, in this example.
  • transport blocks of the transport channel are mapped to physical channels of the PHY layer.
  • transport channels such as downlink shared channel (DL-SCH) and uplink shared channel (UL-SCH) have
  • PHY layer channels such as physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH) have lengths of equal duration.
  • DL-SCH downlink shared channel
  • UL-SCH uplink shared channel
  • PHY layer channels such as physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH) have lengths of equal duration.
  • PDSCH physical downlink shared channels
  • PUSCH physical uplink shared channels
  • the transport blocks are mapped to an integer number of physical channels. Symbols not used by or assigned to the physical channels can be used for other purposes and referred to as gaps.
  • the gaps include control channels, guard periods (GP) and the like.
  • the gaps can be inserted into the subframe at its beginning, end, and elsewhere in between as shown in the below examples.
  • the TTI resource times are variable and are not limited to only including PDSCH and PUSCH.
  • a first mapping 401 uses 4 PDSCHs, each assigned a TTI and length of 3 symbols.
  • the 4 PDSCHs are for TBs using DL-SCHs.
  • a physical downlink control channel (PDCCH) is inserted at a beginning and a second PDCCH is inserted in a middle of the subframe.
  • TTI resource times have been selected to include the PDCCHs.
  • TTI #1 has a length of 4 OFDM symbols and includes the first PDCCH
  • the TTI #2 has a length of 3 OFDM symbols
  • the TTI #3 has a length of 4 OFDM symbols and includes the second PDCCH
  • the TTI #4 has a length of 3 OFDM symbols.
  • a second mapping 402 uses 4 PDSCHs for 4 TBs.
  • the 4 PDSCHs are arranged consecutively and two PDCCHs are inserted at a beginning of the subframe.
  • the TTI #1 has a length of 5 OFDM symbols and includes the first PDCCH and the second PDCCH
  • the TTI #2 has a length of 3 OFDM symbols
  • the TTI #3 has a length of 3 OFDM symbols
  • the TTI #4 has a length of 3 OFDM symbols.
  • a third mapping 403 uses 3 PDSCHs for 3 TBs.
  • two PDSCHs for 3 TBs.
  • two PDSCHs for 3 TBs.
  • PDCCHs are inserted at a beginning of the subframe and a guard period (GP) and physical uplink control channel (PUCCH) are inserted at an end of the subframe as shown.
  • the TTI #1 has a length of 5 OFDM symbols and includes the first PDCCH and the second PDCCH, the TTI #2 has a length of 3 OFDM symbols, and the TTI #3 has a length of 3 OFDM symbols. It is noted that a TTI is not used for the GP and PUCCH.
  • a fourth mapping 404 uses 4 physical uplink shared channels (PUSCH), which are arranged consecutively.
  • PUSCH physical uplink shared channels
  • a PDCCH and GP are inserted at a beginning of the subframe.
  • the TTI #1 has a length of 5 OFDM symbols and includes the PDCCH and the GP
  • the TTI #2 has a length of 3 OFDM symbols
  • the TTI #3 has a length of 3 OFDM symbols
  • the TTI #4 has a length of 3 OFDM symbols.
  • a fifth mapping 405 uses 3 PUSCH.
  • a PDCCH and GP are inserted at a beginning of the subframe. Additionally, a sounding reference signal (SRS) and
  • the TTI #1 has a length of 5 OFDM symbols and includes the first PDCCH and the second PDCCH, the TTI #2 has a length of 3 OFDM symbols, and the TTI #3 has a length of 3 OFDM symbols. It is noted that a TTI is not used for the GP and PUCCH.
  • mappings 400 involve identifying and arranging a number of physical channels (PDSCH and/or PUSCH), inserting gaps and adjusting resource span time.
  • FIG. 5 is a flow diagram illustrating a method 500 of mapping transport channel transport blocks to physical layer symbols in accordance with an embodiment.
  • the mapping is done with adjustable numerologies or PHY layer parameters, such as TTI.
  • the method 500 can be understood and utilized with reference to the arrangement 100 and variations thereof, described above.
  • the method can be performed by a node that is a type of node including, but not limited to, a UE device, eNodeB, AP, BS, and the like.
  • the node is the UE device 102, shown above.
  • the blocks can be performed by a transmitter and/or circuitry of the node.
  • Physical layer symbols are arranged by a node or circuitry of the node into one or more groups of symbols at block 502.
  • the symbols can be OFDM symbols.
  • the one or more groups may have an unequal or equal numbers of symbols.
  • the one or more groups each include one or more consecutive symbols.
  • the physical layer symbols comprise a subframe.
  • the one or more groups can be referred to as PHY groups.
  • PHY layer parameters associated with the symbols. These parameters can be adjusted and/or selected based on communication characteristics.
  • One or more groups of the PHY groups are selected by the node or circuitry of the node to map transport channel transport blocks at block 504.
  • One or more of the PHY groups may remain unselected and/or unused.
  • the unselected groups can be unselected for reasons including, but not limited to its symbols being required for reference signals and/or control channels.
  • the node or circuitry of the node maps the transport blocks to the selected groups at block 506.
  • the resource time span for a given transport block and its mapped to group can be identical or different, including a different TTI.
  • the number of symbols within each group varies and the time span of the groups the TTI of the transport block can be different.
  • the number of symbols in a group is 7, the subframe duration includes two 0.5 ms TTIs, and the time span and the TTI can be identical.
  • the node maps the transport blocks to symbols of the selected groups at block 508. In one example, information from each block is consecutively mapped to symbols of the associated, selected group.
  • the node can also include gaps, control channels and the like in the physical layer symbols.
  • the node transmits the symbols at block 508.
  • the transmitted symbols are of the selected PHY groups and include data from the TBs.
  • a transceiver and/or RF circuitry can be utilized.
  • Figs. 6, 7 and 8 illustrate mappings that utilize a first-in-first-out (FIFO) type of queue.
  • a first transport block is passed and mapped from the MAC layer to the PHY layer first and is transmitted by the PHY layer first.
  • the number of transport blocks arriving to the PHY layer from the MAC layer on a transport channel during one subframe should be less than or equal to K * M, where " is the number of supportable transport block per physical channel and M is the number of physical channels per subframe.
  • the queue is empty.
  • the next K transport blocks may not or should not arrive until the previous transport blocks have been scheduled.
  • there can be TTIs where there may not be any data due to the above constraints.
  • FIG. 6 is a diagram illustrating transport channel to PHY layer mappings 600 using a queue and a transmission time interval of 0.5 ms in accordance with an embodiment.
  • the mappings 600 are provided for illustrative purposes and to facilitate understanding. It is appreciated that the arrangement 100 and variations thereof can be utilized with the shown mappings.
  • a MAC layer is shown passing transport blocks to a PHY layer.
  • the PHY layer maps and transmits associated physical data channels in order.
  • the physical channels have equal TTI lengths and in another, the physical channels can have varied TTI lengths.
  • mappings 600 utilize transport blocks and physical data channels having
  • mappings 600 utilize a first-in-first-out
  • a first transport block is passed and mapped from the MAC layer to the PHY layer first and is transmitted by the PHY layer first.
  • the mappings 600 are based on a subframe length of 1 ms, 15 kHz subcarrier spacing, and 14 OFDM symbols per subframe. It is appreciated that other numerologies can be utilized.
  • a TTI for the subframe is 0.5 ms.
  • the transport blocks are provided as DL-SCH and the physical channels or physical data channels are provided as PDSCH.
  • the mappings 600 include a first mapping 601 and a second mapping 602.
  • the first mapping 601 is shown in an upper portion of the diagram and the second mapping 602 is shown in a lower portion of the diagram.
  • the first mapping 601 illustrates a first DL-SCH passed to the PHY layer in a first TTI and a second DL-SCH passed to the PHY layer in a second TTI.
  • the first and second DL-SCH are mapped to first and second PDSCHs having lengths of 6 OFDM symbols. A gap or unused symbol is inserted at the beginning of each TTI.
  • the second mapping 602 illustrates a first DL-SCH passed to the PHY layer in the first TTI and a second DL-SCH passed to the PHY layer in the second TTI.
  • the first DL-SCH is mapped to a first PDSCH having lengths of 4 OFDM symbols.
  • a gap or unused symbol is inserted at the beginning of the first slot and two gaps are appended at the end of the first PDSCH.
  • the second DL-SCH is mapped to a second PDSCH having lengths of 4 OFDM symbols.
  • a gap or unused symbol is inserted at the beginning of the first slot and two gaps are appended at the end of the second PDSCH.
  • FIG. 7 is a diagram illustrating transport channel to PHY layer mappings 700 using a queue and a transmission time interval of 0.25 ms in accordance with an embodiment.
  • the mappings 700 are provided for illustrative purposes and to facilitate understanding. It is appreciated that the arrangement 100 and variations thereof can be utilized with the mappings.
  • a MAC layer is shown passing transport blocks to a PHY layer.
  • the PHY layer maps and transmits associated physical data channels in order.
  • mappings 700 utilize transport blocks and physical data channels having
  • mappings 700 utilize a first-in-first-out
  • a first transport block is passed and mapped from the MAC layer to the PHY layer first and is transmitted by the PHY layer first.
  • the mappings 700 are based on a subframe length of 1 ms, 15 kHz subcarrier spacing, and 14 OFDM symbols per subframe. It is appreciated that other numerologies can be utilized.
  • the PHY layer TTI for the subframe is set to 0.25 ms.
  • the transport blocks are provided as DL-SCH and the physical channels or physical data channels are provided as PDSCH.
  • the mappings 700 include a first mapping 701 and a second mapping 702.
  • the first mapping 701 is shown in an upper portion of the diagram and the second mapping 702 is shown in a lower portion of the diagram.
  • the first mapping 701 illustrates a first DL-SCH passed in a first TTI, a second DL-SCH passed to the PHY layer in a second TTI, a third DL-SCH passed to the PHY layer in a third TTI, and a fourth DL-SCH passed to the PHY layer in a fourth TTI.
  • the terms first, second, ... TTI here also refers to a group of consecutive symbols of the physical layer.
  • the first, second, and third DL-SCH are mapped to first, second and third PDSCHs as shown. A gap or unused symbol is inserted at the beginning of each slot. There is an incremental delay in mapping the DL-SCHs increasing from 1 symbol, to 1 .5 symbols, to 2 symbols.
  • a delay shown at 703 in mapping for the fourth DL-SCH does not allow the fourth DL-SCH to be mapped to a PDSCH.
  • the fourth DL-SCH is delayed, blocked, or resent by the MAC layer. This mapping accommodates 3 transport blocks.
  • the second mapping 702 illustrates a first DL-SCH passed in a first TTI, a second DL-SCH passed to the PHY layer in a second TTI, and a third DL-SCH passed to the PHY layer in a third TTI.
  • the first, second, and third DL-SCH are mapped to first, second and third PDSCHs as shown. This mapping accommodates 3 transport blocks, so all of the transport blocks are mapped.
  • FIG. 8 is a diagram illustrating transport channel to PHY layer mappings 800 using a queue and a transmission time interval of 0.125 in accordance with an embodiment.
  • the mappings 800 are provided for illustrative purposes and to facilitate understanding. It is appreciated that the arrangement 100 and variations thereof can be utilized with the mappings.
  • a MAC layer is shown passing transport blocks to a PHY layer.
  • the PHY layer maps and transmits associated physical data channels in order.
  • mappings 800 utilize transport blocks and physical data channels having
  • mappings 800 utilize a first-in-first-out
  • a first transport block is passed and mapped from the MAC layer to the PHY layer first and is transmitted by the PHY layer first.
  • the mappings 800 are based on a subframe length of 1 ms, 15 kHz subcarrier spacing, and 14 OFDM symbols per subframe. It is appreciated that other numerologies can be utilized.
  • the PHY layer TTI for the subframe is set to 0.125 ms.
  • the transport blocks are provided as DL-SCH and the physical channels or physical data channels are provided as PDSCH.
  • the mappings 800 include a first mapping 801 and a second mapping 802.
  • the first mapping 801 is shown in an upper portion of the diagram and the second mapping 802 is shown in a lower portion of the diagram.
  • the first mapping 801 illustrates a number of DL-SCHs passed to the PHY layer and mapped to PDSCHs. It can be seen that this mapping supports 7 transport blocks. Transports blocks after 803 are not able to be mapped within the subframe.
  • the second mapping 802 only utilizes 6 transport blocks, shown as DL-SCHs. Thus, at 804, no more transport blocks are mapped to the subframe.
  • Figs. 9A and 9B are diagrams illustrating transport channel to PHY layer mappings 900 using a 17.5 subcarrier frequency in accordance with an embodiment.
  • the mappings 900 are provided for illustrated purposes and to facilitate understanding and include the mappings 900a shown in FIG. 9A and the mappings 900b, shown in FIG. 9B. It is appreciated that the arrangement 100 and variations thereof can be utilized with the shown mappings.
  • the mappings 900 are based on a subframe length of 1 ms, 17.5 kHz subcarrier spacing, and 16 OFDM symbols per subframe.
  • the subframe includes a power of 2 OFDM symbols. As a result, evenly splitting the TTIs is possible. However, non-data symbols can be present, thus some of the OFDM symbols may not be used for m.
  • transport blocks of the transport channel are mapped to physical channels of the PHY layer.
  • transport channels such as downlink shared channel (DL-SCH) and uplink shared channel (UL-SCH)
  • PHY layer channels such as physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH) have lengths of equal duration.
  • the transport blocks are mapped to an integer number of physical channels. Symbols not used by or assigned to the physical channels are used for other purposes and referred to as gaps.
  • the gaps include control channels, guard periods (GP) and the like.
  • the gaps can be inserted into the subframe at its beginning, end, and elsewhere in between as shown in the below examples.
  • a first mapping 901 evenly divides the subframe into 4 TTIs or groups, each having 4 symbols.
  • the TTIs each include a PDCCH of length 1 and a PDSCH of length 3 symbols.
  • the TTIs or resource time spans are extended to include the non data symbols, the PDCCH.
  • a second mapping 902 incorporates non data symbols/channels including a downlink reference signal (DL RS), GP and a PUCCH. Thus, the mapping 902 uses only 3 TTIs or groups. The final 4 symbols incorporate a DL RS, GP and a PUCCH.
  • a second mapping 902 incorporates non data symbols/channels including a downlink reference signal (DL RS), GP and a PUCCH. Thus, the mapping 902 uses only 3 TTIs or groups. The final 4 symbols incorporate a DL RS, GP and a PUCCH.
  • a third mapping 903 incorporates non data symbols/channels including a GP, SRS and a PUCCH. Thus, the mapping 903 uses only 3 TTIs or groups. The final 4 symbols incorporate the GP, SRS and the PUCCH.
  • a fourth mapping 904 incorporates non data symbols/channels including a first SRS, a second SRS and a PUCCH.
  • the mapping 904 uses 3 TTIs or groups.
  • the final 4 symbols incorporate the first SRS, the second SRS and the PUCCH.
  • a fifth mapping 905 utilizes smaller TTIs or groups, which in this example are at lengths of 0.125.
  • the TTIs only include data channels of PDSCH or PUSCH.
  • the control channels and GP are not within the TTIs or groups, non data symbols/channels including a first SRS, a second SRS and a PUCCH.
  • the mapping 904 uses 3 TTIs or groups. The final 4 symbols incorporate the first SRS, the second SRS and the PUCCH.
  • a sixth mapping 906 uses overlapping TTIs or groups.
  • a the TTI #1 includes a first four symbols of the subframe.
  • the TTI #2 includes the first eight symbols, which includes the first four symbols of the subframe.
  • the last 4 symbols are used for a GP, a SRS and a PUCCH.
  • a seventh mapping 907 also uses overlapping TTIs or groups.
  • the TTI #1 includes a first four symbols of the subframe.
  • the TTI #2 includes the first eight symbols, which includes the first four symbols of the subframe.
  • the last 4 symbols are used for a first SRS, a second SRS and a PUCCH.
  • FIG. 10 illustrates an architecture of a system 1000 of a network in accordance with some embodiments.
  • the system 1000 is shown to include a user equipment (UE) 1001 and a UE 1002.
  • the UEs 1001 and 1002 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
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets or any computing device including a wireless
  • any of the UEs 1001 and 1002 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.
  • An loT 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 loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • loT network describes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • the UEs 1001 and 1002 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 101 0— the RAN 1010 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.
  • RAN radio access network
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 1001 and 1 002 utilize connections 1003 and 1004, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 1003 and 1004 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 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
  • UMTS Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 1001 and 1002 may further directly exchange communication data via a ProSe interface 1005.
  • the ProSe interface 1005 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 1002 is shown to be configured to access an access point (AP) 1006 via connection 1007.
  • the connection 1007 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 1006 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 1006 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 1010 can include one or more access nodes that enable the connections 1 003 and 1004.
  • 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 1010 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 101 1 , 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 1012.
  • 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.
  • any of the RAN nodes 101 1 and 1012 can terminate the air interface protocol and can be the first point of contact for the UEs 1001 and 1 002.
  • any of the RAN nodes 101 1 and 1012 can fulfill various logical functions for the RAN 1010 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 1001 and 1002 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 101 1 and 1 012 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 transmissions from any of the RAN nodes 101 1 and 1012 to the UEs 1001 and 1002, while uplink transmissions can utilize similar techniques.
  • the grid can be a time- frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane
  • 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 1001 and 1002.
  • 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 1001 and 1 002 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 102 within a cell) may be performed at any of the RAN nodes 101 1 and 1012 based on channel quality information fed back from any of the UEs 1001 and 1002.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 1001 and 1002.
  • 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 1 , 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 an 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 an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 1010 is shown to be communicatively coupled to a core network (CN) 1 020—via an S1 interface 1013.
  • the CN 1020 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S1 interface 1013 is split into two parts: the S1 -U interface 1014, which carries traffic data between the RAN nodes 101 1 and 1012 and the serving gateway (S-GW) 1022, and the S1 -mobility management entity (MME) interface 1015, which is a signaling interface between the RAN nodes 101 1 and 101 2 and MMEs 1021 .
  • MME mobility management entity
  • the CN 1 020 comprises the MMEs 1021 , the S-GW 1022, the Packet Data Network (PDN) Gateway (P-GW) 1023, and a home subscriber server (HSS) 1024.
  • the MMEs 1021 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 1021 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 1 024 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 1020 may comprise one or several HSSs 1024, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 1024 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 1022 may terminate the S1 interface 1013 towards the RAN 1010, and routes data packets between the RAN 1 010 and the CN 1020.
  • the S- GW 1022 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 1023 may terminate an SGi interface toward a PDN.
  • the P-GW 1023 may route data packets between the EPC network 1023 and e1 l ernal networks such as a network including the application server 1030 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 1025.
  • the application server 1030 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 1023 is shown to be communicatively coupled to an application server 1030 via an IP communications interface 1025.
  • the application server 1030 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 1001 and 1002 via the CN 1020.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 1023 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 1026 is the policy and charging control element of the CN 1020.
  • 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 1026 may be communicatively coupled to the application server 1030 via the P-GW 1023.
  • the application server 1030 may signal the PCRF 1026 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 1026 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 1030.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 1 1 illustrates example components of a device 1 100 in accordance with some embodiments.
  • the device 1 100 may include application circuitry 1 1 02, baseband circuitry 1 104, Radio Frequency (RF) circuitry 1 106, front-end module (FEM) circuitry 1 1 08, one or more antennas 1 1 10, and power management circuitry (PMC) 1 1 12 coupled together at least as shown.
  • the components of the illustrated device 1 100 may be included in a UE or a RAN node.
  • the device 1 100 may include less elements (e.g., a RAN node may not utilize
  • the application circuitry 1 102 may include one or more application circuitry 1 102, and instead include a processor/controller to process IP data received from an EPC).
  • the device 1 100 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • the application circuitry 1 102 may include one or more application circuitry 1 102, and instead include a processor/controller to process IP data received from an EPC).
  • the device 1 100 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • the application circuitry 1 102 may
  • the application circuitry 1 102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1 100.
  • processors of application circuitry 1 1 02 may process IP data packets received from an EPC.
  • the baseband circuitry 1 104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1 104 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1 106 and to generate baseband signals for a transmit signal path of the RF circuitry 1 106.
  • Baseband processing circuity 1 1 04 may interface with the application circuitry 1 102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1 1 06.
  • the baseband circuitry 1 104 may include a third generation (3G) baseband processor 1 104A, a fourth generation (4G) baseband processor 1 104B, a fifth generation (5G) baseband processor 1 1 04C, or other baseband processor(s) 1 1 04D for other existing generations, generations in
  • the baseband circuitry 1 104 may handle various radio control functions that
  • baseband processors 1 104A-D may be included in modules stored in the memory 1 104G and executed via a Central Processing Unit (CPU) 1 1 04E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 1 1 04 may include Fast-Fourier Transform (FFT), precoding, or constellation
  • encoding/decoding circuitry of the baseband circuitry 1 1 04 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 1 1 04 may include one or more audio digital signal processor(s) (DSP) 1 1 04F.
  • the audio DSP(s) 1 104F 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 1 104 and the application circuitry 1 1 02 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 1 1 04 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 1 104 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), 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
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 1 104 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 1 106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1 106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1 1 08 and provide baseband signals to the baseband circuitry 1 104.
  • RF circuitry 1 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1 104 and provide RF output signals to the FEM circuitry 1 1 08 for transmission.
  • the receive signal path of the RF circuitry 1 1 06 may include mixer circuitry 1 1 06a, amplifier circuitry 1 106b and filter circuitry 1 106c.
  • the transmit signal path of the RF circuitry 1 106 may include filter circuitry 1 1 06c and mixer circuitry 1 106a.
  • RF circuitry 1 106 may also include synthesizer circuitry 1 1 06d for synthesizing a frequency for use by the mixer circuitry 1 106a of the receive signal path and the transmit signal path.
  • the mixer circuitry 1 106a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1 108 based on the synthesized frequency provided by synthesizer circuitry 1 106d.
  • the amplifier circuitry 1 106b may be configured to amplify the down-converted signals and the filter circuitry 1 106c 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.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 1 104 for further processing.
  • the output baseband signals may be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1 106a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1 106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1 1 06d to generate RF output signals for the FEM circuitry 1 108.
  • the baseband signals may be provided by the baseband circuitry 1 1 04 and may be filtered by filter circuitry 1 1 06c.
  • the mixer circuitry 1 106a of the receive signal path and the mixer circuitry 1 1 06a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 1 1 06a of the receive signal path and the mixer circuitry 1 106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • image rejection e.g., Hartley image rejection
  • the mixer circuitry 1 106a of the receive signal path and the mixer circuitry 1 1 06a may be arranged for direct downconversion and direct upconversion
  • the mixer circuitry 1 106a of the receive signal path and the mixer circuitry 1 1 06a of the transmit signal path may be configured for superheterodyne 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 1 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1 104 may include a digital baseband interface to communicate with the RF circuitry 1 106.
  • 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
  • the synthesizer circuitry 1 106d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1 106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1 106d may be configured to synthesize an output frequency for use by the mixer circuitry 1 106a of the RF circuitry 1 106 based on a frequency input and a divider control input.
  • the synthesizer circuitry 1 1 06d may be a fractional N/N+1 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 1 1 04 or the applications processor 1 102 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1 102.
  • Synthesizer circuitry 1 106d of the RF circuitry 1 106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • DLL delay-locked loop
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • synthesizer circuitry 1 106d 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 1 106 may include an IQ/polar converter.
  • FEM circuitry 1 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1 1 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1 106 for further processing.
  • FEM circuitry 1 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1 106 for transmission by one or more of the one or more antennas 1 1 10.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1 106, solely in the FEM 1 1 08, or in both the RF circuitry 1 106 and the FEM 1 108.
  • the FEM circuitry 1 1 08 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1 106).
  • the transmit signal path of the FEM circuitry 1 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1 1 10).
  • PA power amplifier
  • the PMC 1 1 12 may manage power provided to the baseband circuitry 1 104.
  • the PMC 1 1 12 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 1 1 12 may often be included when the device 1 100 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 1 1 12 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 1 1 shows the PMC 1 1 12 coupled only with the baseband circuitry 1 1 04.
  • the PMC 1 1 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1 102, RF circuitry 1 106, or FEM 1 108.
  • the PMC 1 1 12 may control, or otherwise be part of, various power saving mechanisms of the device 1 100.
  • the device 1 1 00 may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1 1 00 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 1 1 00 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 1 1 00 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 1 1 00 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 1 1 02 and processors of the baseband circuitry 1 1 04 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 1 104 alone or in
  • 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. 12 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 1 1 04 of FIG. 1 1 may comprise processors 1 104A-1 1 04E and a memory 1 104G utilized by said processors.
  • Each of the processors 1 104A-1 104E may include a memory interface, 1204A-1204E, respectively, to send/receive data to/from the memory 1 104G.
  • the baseband circuitry 1 104 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1 21 2 (e.g., an interface to send/receive data to/from memory e1 l ernal to the baseband circuitry 1 1 04), an application circuitry interface 1214 (e.g., an interface to send/receive data to/from the application circuitry 1 102 of FIG. 1 1 ), an RF circuitry interface 121 6 (e.g., an interface to send/receive data to/from RF circuitry 1 106 of FIG. 1 1 ), a wireless hardware connectivity interface 1218 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g.,
  • NFC Near Field Communication
  • Bluetooth® components e.g.,
  • a power management interface 1220 e.g., an interface to send/receive power or control signals to/from the PMC 1 1 12.
  • FIG. 13 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 1 300 is shown as a communications protocol stack between the UE 1001 (or alternatively, the UE 1002), the RAN node 101 1 (or alternatively, the RAN node 1 012), and the MME 1021 .
  • the PHY layer 1301 may transmit or receive information used by the MAC layer 1 302 over one or more air interfaces.
  • the PHY layer 1301 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 1305.
  • AMC link adaptation or adaptive modulation and coding
  • the PHY layer 1301 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 1 302 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.
  • the RLC layer 1303 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • the RLC layer 1303 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 1 303 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re- establishment.
  • the PDCP layer 1304 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer 1305 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • MIBs and SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures.
  • the UE 1001 and the RAN node 101 1 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 1301 , the MAC layer 1302, the RLC layer 1303, the PDCP layer 1304, and the RRC layer 1 305.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 1306 form the highest stratum of the control plane between the UE 1001 and the MME 1021 .
  • the NAS protocols 1306 support the mobility of the UE 1001 and the session management procedures to establish and maintain IP connectivity between the UE 1001 and the P-GW 1023.
  • the S1 Application Protocol (S1 -AP) layer 1315 may support the functions of the S1 interface and comprise Elementary Procedures (EPs).
  • An EP is a unit of interaction between the RAN node 101 1 and the CN 1020.
  • the S1 -AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 1314 may ensure reliable delivery of signaling messages between the RAN node 101 1 and the MME 1021 based, in part, on the IP protocol, supported by the IP layer 131 3.
  • the L2 layer 1 312 and the L1 layer 131 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 101 1 and the MME 1021 may utilize an S1 -MME interface to exchange control plane data via a protocol stack comprising the L1 layer 131 1 , the L2 layer 1 31 2, the IP layer 1313, the SCTP layer 1314, and the S1 -AP layer 1 315.
  • FIG. 14 is an illustration of a user plane protocol stack in accordance with some embodiments.
  • a user plane 1400 is shown as a
  • the user plane 1400 may utilize at least some of the same protocol layers as the control plane 1300.
  • the UE 1001 and the RAN node 101 1 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 1301 , the MAC layer 1302, the RLC layer 1303, the PDCP layer 1304.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 1404 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 1403 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 101 1 and the S-GW 1022 may utilize an S1 -U interface to exchange user plane data via a protocol stack comprising the L1 layer 131 1 , the L2 layer 1312, the UDP/IP layer 1403, and the GTP-U layer 1404.
  • the S-GW 1022 and the P-GW 1023 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 131 1 , the L2 layer 1 31 2, the UDP/IP layer 1403, and the GTP-U layer 1404.
  • NAS protocols support the mobility of the UE 1001 and the session management procedures to establish and maintain IP connectivity between the UE 1001 and the P-GW 1023.
  • FIG. 15 illustrates components of a core network in accordance with some embodiments.
  • the components of the CN 1 020 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine- readable storage medium).
  • NFV Network Functions Virtualization
  • a logical instantiation of the CN 1020 may be referred to as a network slice 1501 .
  • a logical instantiation of a portion of the CN 1020 may be referred to as a network sub-slice 1 502 (e.g., the network sub-slice 1502 is shown to include the PGW 1023 and the PCRF 1026).
  • NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • FIG. 16 is a block diagram illustrating components, according to some example embodiments, of a system 1600 to support NFV.
  • the system 1600 is illustrated as including a virtualized infrastructure manager (VIM) 1602, a network function virtualization infrastructure (NFVI) 1604, a VNF manager (VNFM) 1 606, virtualized network functions (VNFs) 1608, an element manager (EM) 1610, an NFV Orchestrator (NFVO) 1 612, and a network manager (NM) 1 614.
  • VIP virtualized infrastructure manager
  • NFVI network function virtualization infrastructure
  • VNFM VNF manager
  • VNFs virtualized network functions
  • EM element manager
  • NFVO NFV Orchestrator
  • NM network manager
  • the VIM 1 602 manages the resources of the NFVI 1604.
  • the NFVI 1604 can include physical or virtual resources and applications (including hypervisors) used to execute the system 1 600.
  • the VIM 1602 may manage the life cycle of virtual resources with the NFVI 1604 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.
  • VMs virtual machines
  • the VNFM 1606 may manage the VNFs 1 608.
  • the VNFs 1608 may be used to execute EPC components/functions.
  • the VNFM 1606 may manage the life cycle of the VNFs 1 608 and track performance, fault and security of the virtual aspects of VNFs 1608.
  • the EM 1610 may track the performance, fault and security of the functional aspects of VNFs 1608.
  • the tracking data from the VNFM 1606 and the EM 161 0 may comprise, for example, performance measurement (PM) data used by the VIM 1602 or the NFVI 1604. Both the VNFM 1606 and the EM 161 0 can scale up/down the quantity of VNFs of the system 1600.
  • PM performance measurement
  • the NFVO 1 612 may coordinate, authorize, release and engage resources of the NFVI 1604 in order to provide the requested service (e.g., to execute an EPC function, component, or slice).
  • the NM 1614 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 1610).
  • FIG. 17 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. 17 shows a diagrammatic representation of hardware resources 1700 including one or more processors (or processor cores) 1710, one or more memory/storage devices 1720, and one or more communication resources 1730, each of which may be communicatively coupled via a bus 1740.
  • node virtualization e.g., NFV
  • a hypervisor 1702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1700
  • the processors 1710 may include, for example, a processor 1712 and a processor 1714.
  • 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 1720 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1720 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 readonly 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 readonly memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1730 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1704 or one or more databases 1706 via a network 1708.
  • the communication resources 1730 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular
  • Bluetooth® Low Energy Wi-Fi® components
  • other communication components Bluetooth® Low Energy
  • Instructions 1750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1710 to perform any one or more of the methodologies discussed herein.
  • the instructions 1750 may reside, completely or partially, within at least one of the processors 1710 (e.g., within the processor's cache memory), the memory/storage devices 1720, or any suitable combination thereof.
  • any portion of the instructions 1750 may be transferred to the hardware resources 1700 from any combination of the peripheral devices 1704 or the databases 1706. Accordingly, the memory of processors 1710, the memory/storage devices 1720, the peripheral devices 1704, and the databases 1706 are examples of computer-readable and machine-readable media.
  • Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described.
  • a machine e.g., a processor with memory or the like
  • Example 1 is an apparatus configured to be employed within one or more user equipment (UE) devices.
  • the apparatus comprises baseband circuitry, which includes one or more processors.
  • the one or more processors are configured to determine a transmission time interval (TTI) for a physical (PHY) layer based on communication characteristics, the PHY layer comprising physical channels.
  • the one or more processors are also configured to generate a mapping for one or more transport blocks of a transport channel based on the determined TTI and map the one or more transport blocks to the PHY layer based on the generated mapping.
  • TTI transmission time interval
  • PHY physical
  • Example 2 includes the subject matter of Example 1 , including or omitting optional elements, where the baseband circuitry further includes a radio frequency (RF) circuitry interface to send transmission data to RF circuitry, the transmission data generated based on the generated mapping.
  • RF radio frequency
  • Example 3 includes the subject matter of any of Examples 1 -2, including or omitting optional elements, where the determined TTI is varied for each of the one or more transport blocks.
  • Example 4 includes the subject matter of any of Examples 1 -3, including or omitting optional elements, where the mapping identifies one of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) for each of the one or more transport blocks.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • Example 5 includes the subject matter of any of Examples 1 -4, including or omitting optional elements, where the one or more transport blocks include a downlink shared channel (DL-SCH) of the transport channel of a medium access (MAC) layer.
  • DL-SCH downlink shared channel
  • MAC medium access
  • Example 6 includes the subject matter of any of Examples 1 -5, including or omitting optional elements, where the determined TTI is reduced from an original TTI.
  • Example 7 includes the subject matter of any of Examples 1 -6, including or omitting optional elements, where the determined TTI is less than a subframe duration of 1 mili-second (ms).
  • Example 8 includes the subject matter of any of Examples 1 -7, including or omitting optional elements, where the mapping includes one or more gaps inserted in a subframe.
  • Example 9 includes the subject matter of any of Examples 1 -8, including or omitting optional elements, where the mapping includes one or more groups of orthogonal frequency division multiplexing (OFDM) symbols.
  • OFDM orthogonal frequency division multiplexing
  • Example 10 includes the subject matter of any of Examples 1 -9, including or omitting optional elements, where each of the one or more groups is matched with one of the one or more transport blocks.
  • Example 1 1 includes the subject matter of any of Examples 1 -1 0, including or omitting optional elements, where the mapping utilizes a first-in-first-out (FIFO) queue to map the one or more transport blocks to one or more physical channels.
  • FIFO first-in-first-out
  • Example 12 includes the subject matter of any of Examples 1 -1 1 , including or omitting optional elements, where the communication characteristics comprise one or more of latency, reliability and data rate.
  • Example 13 is an apparatus configured to be employed within an evolved Node B (eNodeB).
  • the apparatus comprises baseband circuitry, which includes one or more processors.
  • the one or more processors are configured to determine physical (PHY) layer parameters of a PHY layer based on communication characteristics, wherein the numerology includes a transmission time interval (TTI) and wherein the communication characteristics include reliability.
  • the physical layer comprises physical channels.
  • the one or more processors are also configured to generate a mapping for one or more transport blocks based on the determined PHY layer parameters and map the one or more transport blocks to a subframe of the PHY layer.
  • Example 14 includes the subject matter of Example 13, including or omitting optional elements, where the baseband circuitry further includes a radio frequency (RF) circuitry interface to send transmission data to RF circuitry, the transmission data generated based on the subframe.
  • RF radio frequency
  • Example 15 includes the subject matter of any of Examples 13-14, including or omitting optional elements, where the mapping includes arranging one or more physical channels, inserting gaps and adjusting resource span times.
  • Example 16 includes the subject matter of any of Examples 13-15, including or omitting optional elements, where the PHY layer uses a subcarrier frequency of 15 kHz.
  • Example 17 includes the subject matter of any of Examples 13-16, including or omitting optional elements, where the communication characteristics further include latency.
  • Example 18 is one or more computer-readable media having instructions. When executed, the instructions cause one or more nodes to generate a mapping for one or more transport blocks of a transport channel based on the determined TTI, map the one or more transport blocks to one or more physical channels of the PHY layer based on the generated mapping, and transmit the physical channels using the determined TTI.
  • Example 19 includes the subject matter of Example 18, including or omitting optional elements, where the instructions further cause the one or more nodes to map each transport block of the one or more transport blocks to a group of consecutive orthogonal frequency division multiplexing (OFDM) symbols.
  • OFDM orthogonal frequency division multiplexing
  • Example 20 includes the subject matter of any of Examples 18-19, including or omitting optional elements, where the instructions further cause the one or more nodes to insert a physical downlink control channel (PDCCH) into a subframe of the PHY layer based on the mapping.
  • PDCCH physical downlink control channel
  • Example 21 includes the subject matter of any of Examples 18-20, including or omitting optional elements, where the instructions further cause the one or more nodes to insert a physical uplink control channel (PUCCH) into a subframe of the PHY layer based on the mapping, wherein the subframe has a length greater than the determined TTI.
  • PUCCH physical uplink control channel
  • Example 22 is an apparatus configured to be employed within one or more user equipment (UE) devices.
  • the apparatus includes a means to determine one or more physical (PHY) layer parameters based on communication characteristics, a means to generate a mapping for a plurality of transport blocks from a transport channel to a plurality of physical channels of a PHY layer based on the determined one or more PHY layer parameters, a means to map the plurality of transport blocks to the plurality of physical channels based on the generated mapping, and a means to transmit the plurality of physical channels.
  • PHY physical
  • Example 23 includes the subject matter of Example 22, including or omitting optional elements, further comprising a means to determine an inter-arrival time for the transport blocks.
  • Example 24 includes the subject matter of any of Examples 22-23, including or omitting optional elements, where the one or more PHY layer parameters include a transmission time interval (TTI) for the plurality of physical channels.
  • TTI transmission time interval
  • Example 25 is an apparatus configured to be employed within an access point (AP).
  • the apparatus comprises baseband circuitry, which includes one or more processors.
  • the one or more processors are configured to determine a transmission time interval (TTI) for a physical (PHY) layer based on communication characteristics, the PHY layer comprising physical channels.
  • the one or more processors are also configured to generate a mapping for one or more transport blocks of a transport channel based on the determined TTI and map the one or more transport blocks to the PHY layer based on the generated mapping.
  • TTI transmission time interval
  • PHY physical
  • the one or more processors are also configured to generate a mapping for one or more transport blocks of a transport channel based on the determined TTI and map the one or more transport blocks to the PHY layer based on the generated mapping.
  • Example 26 includes the subject matter of Example 25, including or omitting optional elements, where the baseband circuitry further includes a radio frequency (RF) circuitry interface to send transmission data to RF circuitry, the transmission data generated based on the generated mapping.
  • RF radio frequency

Landscapes

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

Abstract

L'invention concerne un appareil configuré pour être utilisé dans au moins un équipement utilisateur (UE). L'appareil selon l'invention comprend un ensemble de circuits de bande de base comprenant au moins un processeur. Ledit processeur au moins est configuré pour déterminer un intervalle de temps de transmission (TTI) pour une couche physique (PHY) en fonction de caractéristiques de communication, la couche physiques comprenant des canaux physiques. Ledit processeur au moins est également configuré pour générer un mappage pour au moins un bloc de transport d'un canal de transport selon le TTI déterminé, et mapper ledit bloc de transport au moins sur la couche physique selon le mappage généré.
PCT/US2017/032380 2016-05-13 2017-05-12 Mappage de canal de transport sur canal physique à intervalles de temps de transmission extensibles Ceased WO2017197248A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112017002461.7T DE112017002461T5 (de) 2016-05-13 2017-05-12 Transportkanal-physikalischer kanal-mapping mit skalierbaren übertragungszeitintervallen

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662336464P 2016-05-13 2016-05-13
US62/336,464 2016-05-13

Publications (1)

Publication Number Publication Date
WO2017197248A1 true WO2017197248A1 (fr) 2017-11-16

Family

ID=58765977

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/032380 Ceased WO2017197248A1 (fr) 2016-05-13 2017-05-12 Mappage de canal de transport sur canal physique à intervalles de temps de transmission extensibles

Country Status (2)

Country Link
DE (1) DE112017002461T5 (fr)
WO (1) WO2017197248A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Physical layer aspect of processing time for shortened TTI", vol. RAN WG1, no. Busan, Korea; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051080247, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160402] *
LG ELECTRONICS: "Study on TTI shortening for downlink transmissions", vol. RAN WG1, no. St Julian's, Malta; 20160215 - 20160219, 14 February 2016 (2016-02-14), XP051053978, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20160214] *

Also Published As

Publication number Publication date
DE112017002461T5 (de) 2019-01-24

Similar Documents

Publication Publication Date Title
US11304185B2 (en) Bandwidth part (BWP) switching delays for new radio (NR)
US11171746B2 (en) Channel state and beam related information reporting
US11824814B2 (en) Physical resource block indexing for coexistence of narrow band, carrier aggregation, and wide band user equipment in new radio
EP4459936A2 (fr) Ral de commande/canal de données et dm-rs pour nr, et mécanisme d&#39;activation, aspects de planification et blocs de signal de synchronisation
EP4135254B1 (fr) Rapport d&#39;informations d&#39;état de canal sur un canal partagé de liaison montante physique dans une nouvelle radio
US20190387578A1 (en) Handling multiple sr configurations and corresponding ul grants
US11277191B2 (en) Radio link monitoring, beam recovery and radio link failure handling
US20200110627A1 (en) Centralized unit and distributed unit connection in a virtualized radio access network
US10841808B2 (en) Apparatus and medium for enabling multi-carrier operation
US10812169B2 (en) User equipment measurements for new radio
WO2018200733A1 (fr) Gestion améliorée de tranche de réseau pour communications sans fil
US11082901B2 (en) Signaling of support for network controlled small gap, NCSG, for interruption control
US20190373497A1 (en) Measurement gap configuration for new radio (nr) systems
WO2018106911A2 (fr) Équipement d&#39;utilisateur multefire pour une transmission de liaison montante sans octroi
US11818793B2 (en) Devices and methods for UE-specific RAN-CN associations
EP3462654A1 (fr) Appareil pour prendre en charge une modulation d&#39;amplitude en quadrature 1 024
US20200107357A1 (en) Grantless uplink (gul) configuration
WO2018031649A1 (fr) Accès à des technologies existantes au moyen d&#39;un équipement utilisateur
US20190044810A1 (en) Channel whitelist and flexible frame design for enhanced machine-type communications systems in unlicensed spectrum
WO2017197248A1 (fr) Mappage de canal de transport sur canal physique à intervalles de temps de transmission extensibles

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

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17725463

Country of ref document: EP

Kind code of ref document: A1