WO2018063845A1 - Support de saut de fréquence avec un nombre différent de blocs de ressources physiques dans différentes régions de fréquence sautées - Google Patents

Support de saut de fréquence avec un nombre différent de blocs de ressources physiques dans différentes régions de fréquence sautées Download PDF

Info

Publication number
WO2018063845A1
WO2018063845A1 PCT/US2017/052104 US2017052104W WO2018063845A1 WO 2018063845 A1 WO2018063845 A1 WO 2018063845A1 US 2017052104 W US2017052104 W US 2017052104W WO 2018063845 A1 WO2018063845 A1 WO 2018063845A1
Authority
WO
WIPO (PCT)
Prior art keywords
physical resource
resource blocks
resources
aggregation
allocation
Prior art date
Application number
PCT/US2017/052104
Other languages
English (en)
Inventor
Seunghee Han
Debdeep CHATTERJEE
Wenting CHANG
Qiaoyang Ye
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Priority to DE112017003821.9T priority Critical patent/DE112017003821T5/de
Publication of WO2018063845A1 publication Critical patent/WO2018063845A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/0012—Hopping in multicarrier systems

Definitions

  • Embodiments of the present disclosure generally relate to the field of networks, and more particularly, to apparatuses, systems, and methods for supporting frequency hopping with different number of physical resource blocks in different hopped frequency regions.
  • FeMTC machine-type communication
  • HARQ-ACK hybrid automatic repeat request- acknowledgment
  • CE coverage enhancement
  • HD-FDD half duplex-frequency division duplexing
  • TBS maximum transport block size
  • PBS physical downlink shared channel
  • PDSCH Physical uplink shared channel
  • PUSCH physical uplink shared channel
  • bandwidth-reduced, low- complexity (“BL”) user equipments (“UEs”) in CE mode A may have a 5 MHz maximum UE channel bandwidth for PDSCH and PUSCH in radio resource control (“RRC”) connected mode. This may be larger for non-BL UEs.
  • RRC radio resource control
  • Figure 1 illustrates an architecture of a system of a network in accordance with some embodiments.
  • Figure 2 illustrates a plurality of configurations for various system bandwidths that may be used for uplink or downlink communication according to various embodiments.
  • FIG. 3 illustrates extended narrowband resource allocations in various configurations in accordance with some embodiments.
  • Figure 4 illustrates an example of coding that may be used to transmit shared channel transmissions according to some embodiments.
  • Figure 5 illustrates an example operation flow/algorithmic structure of a user equipment or access node according to some embodiments.
  • Figure 6 illustrates a device according to some embodiments.
  • FIG. 7 illustrates hardware resources in accordance with some embodiments.
  • phrases “A or B,” “A and/or B,” and “A/B” mean (A), (B), or (A and B).
  • FeMTC UEs may support larger and larger maximum channel bandwidths in order to support higher data rate operation.
  • RF radio-frequency
  • the UEs may need to accommodate PDSCH and PUSCH resource allocations in the frequency dimension that span more than a single narrowband (“NB").
  • a narrowband may be defined as a set of six contiguous in-frequency physical resource blocks (“PRBs").
  • Various embodiments are described herein to support frequency hopping for UEs with larger bandwidth support. Some embodiments describe supporting frequency hopping where a number of PRBs in each hopped frequency region may be different.
  • the UEs described herein may support larger bandwidth and may be FeMTC UEs. While many embodiments are described based on an assumption that a maximum supported bandwidth is 5 MHz for the FeMTC UEs, other embodiments may be applied to other values of maximum supported bandwidth greater than 1.4 MHz.
  • FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments.
  • the system 100 is shown to include a UE 104, which may be an FeMTC UE supporting increased maximum bandwidth.
  • the UE 104 may be a smartphone (for example, a handheld touchscreen mobile computing device 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, Internet of things (“IoT”) devices, smart sensors, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • IoT Internet of things
  • smart sensors laptop computers
  • desktop computers desktop computers
  • wireless handsets wireless handsets
  • An IoT UE can utilize technologies such as machine-to-machine (“M2M”) or 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”)
  • M2M machine-to-machine
  • PLMN public land mobile network
  • ProSe Proximity -Based Service
  • D2D device-to-device
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (for example, keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UE 104 may be configured to connect, for example, communicatively couple, with an access node ("AN") 108 of a radio access network (“RAN”) 110 via a Uu interface.
  • the RAN 110 may be, for example, an Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) in which case the access node 108 may be an evolved node B (“eNB”), a NextGen RAN (“NG RAN”) in which case the access node 108 may be a next generation node B (“gNB”), or some other type of RAN.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNB evolved node B
  • NG RAN NextGen RAN
  • the UE 104 may utilize an air-interface protocol to enable communicative coupling over the Uu interface.
  • the air-interface protocol can be consistent with cellular communications protocols such as a Global System for Mobile Communications (“GSM”) protocol, a code-division multiple access (“CDMA”) network protocol, a push-to-talk (“PTT”) protocol, a PTT over cellular (“POC”) protocol, a Universal Mobile Telecommunications System (“UMTS”) protocol, a 3GPP Long Term Evolution (“LTE”) protocol, a fifth generation (“5G”) protocol, a New Radio (“NR”) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT push-to-talk
  • POC PTT over cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE 3GPP Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the access node 108 can terminate the air-interface protocol and can be the first point of contact for the UE 104.
  • the access node 108 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller ("RNC") functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UE 104 may perform a number of operations.
  • the first operation may include, for example, synchronizing with a frequency to identify an operator with which the UE 104 is to connect.
  • the UE 104 may be able to read and process information blocks such as, for example, a master information block ("MIB”) and system information blocks (“SIBs”), to obtain information used to access a cell provided by the access node 108.
  • MIB master information block
  • SIBs system information blocks
  • the UE 104 may then perform a random access procedure to request the access node 108 to provide the UE 104 temporary resources for initial communication.
  • the UE 104 may establish an RRC connection by sending an RRC connection request message, which may also be referred to as an RRC Msg 3; receiving an RRC connection setup message; and sending an RRC connection setup complete message, which may be referred to as an RRC Msg 5.
  • the UE 104 may be in an RRC-CON ECTED state after sending the RRC connection setup complete message.
  • the RRC connection request message may include a UE identity, which may include a temporary mobile subscriber identity ("TMSI”) or a random value, and a connection establishment cause.
  • the RRC connection setup message may include a default configuration for a first signaling radio bearer (SRBl) and other configuration information related to, for example, PUSCH, physical uplink control channel (“PUCCH”), PDSCH, channel quality indicator ("CQI") report, sounding reference signal, antenna configuration, scheduling request, etc.
  • the RRC connection setup complete message may include information about a selected PLMN and UE-specified NAS layer information.
  • the UE 104 can be configured to communicate using Orthogonal Frequency-Division Multiplexing ("OFDM") communication signals with other UEs or with the access node 108 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (“OFDMA”) communication technique (for example, for downlink communications) or a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) communication technique (for example, 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 the access node 108 to the UE 104, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of PRBs, which describe the mapping of certain physical channels to resource elements.
  • PRB (or simply "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.
  • resource blocks There are several different physical channels that are conveyed using such resource blocks. These include PUSCH and the PDSCH.
  • the PDSCH may carry user data and higher-layer signaling to the UE 104.
  • the PUSCH may be used to carry RRC signaling messages, uplink control information, and application data to the AN 108.
  • the physical downlink control channel may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UE 104 about the transport format, resource allocation, and HARQ information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 104 within a cell) may be performed at the access node 108 based on channel quality information fed back from the UE 104.
  • the downlink resource assignment information may be sent on the PDCCH used for (for example, assigned to) the UE 104.
  • the RAN 110 may be communicatively coupled to a core network ("CN") 116 through an SI interface.
  • the communications over the SI interface may be compatible with an SI Application protocol (SI AP).
  • the CN 116 may be an evolved packet core (“EPC") network, a NextGen Packet Core (“NPC”) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface may be split into two parts: an Sl-U interface, which carries traffic data between the access node 108 and serving gateway (“S-GW”) 120, and an SI -mobility management entity (“MME”) interface, which is a signaling interface between the access node 108 and an MME 124.
  • S-GW serving gateway
  • MME SI -mobility management entity
  • the CN 116 comprises the S-GW 120, the MME 124, a packet gateway (“P-GW”) 128, a policy charging rules function (“PCRF”) 132, and a home subscriber server (“HSS”) 136.
  • the MME 124 may be similar in function to the control plane of legacy Serving General Packet Radio Service (“GPRS”) Support Nodes (“SGSN").
  • GPRS General Packet Radio Service
  • SGSN Serving General Packet Radio Service
  • the MME 124 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the S-GW 120 may terminate the SI -U interface towards the RAN 110, and may route data packets between the RAN 110 and the CN 116.
  • the S-GW 120 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 128 may terminate an SGi interface toward a packet data network (“PDN").
  • the P-GW 128 may route data packets between the CN 116 and external networks such as a PDN.
  • the PDN may include an application server ("AS") 140 (alternatively referred to as application function ("AF")) that is communicatively coupled with the CN 116 via an Intemet Protocol (“IP") interface.
  • AS application server
  • AF application function
  • IP Intemet Protocol
  • the application server 140 may be an element offering applications that use IP bearer resources with the CN 116 (for example, UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • the application server 140 can also be configured to support one or more communication services (for example, Voice- over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 104 via the CN 116.
  • VoIP Voice- over-Internet Protocol
  • the P-GW 128 may further be a node for policy enforcement and charging data collection.
  • Policy and charging rules function (“PCRF”) 132 is the policy and charging control element of the CN 116.
  • PCRF Policy and charging rules function
  • HPLMN home public land mobile network
  • IP-CAN Internet Protocol connectivity access network
  • PCRF Policy and charging rules function
  • the application server 140 may signal the PCRF 132 to indicate a new service flow and select the appropriate quality of service (“QoS”) and charging parameters.
  • the PCRF 132 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 140.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • the HSS 136 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 116 may comprise one or several HSSs 136, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 136 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • Figure 2 illustrates a plurality of configurations for various system bandwidths that may be used for UL communication, from UE 104 to AN 108, or DL communication, from AN 108 to UE 104, according to various embodiments.
  • Figure 2 illustrates a first configuration 204 for a system bandwidth of 3 MHz, a second configuration 208 for a system bandwidth of 5 MHz, a third configuration 212 for a system bandwidth of 10 MHz, a fourth configuration 216 for a system bandwidth of 15 MHz, and a fifth configuration 220 for a system bandwidth of 20 MHz.
  • the AN 108 may configure the UE 104 with a frequency hopping pattern based on a number of sets of resources such as, but not limited to, narrowbands ("NBs").
  • the AN 108 may configure the UE by using RRC signaling or some other type of control signaling.
  • a narrowband may be defined as a set of six contiguous PRBs.
  • Narrowbands may be non- overlapping and may be numbered in order of increasing PRB number.
  • Nj3 ⁇ 4 is a number of resource blocks configured for downlink transmission.
  • Physical resource blocks that do not fit in the narrowbands may be divided evenly at both ends of the system bandwidth (for example, RB 0 and RB 49 of third configuration 212, RB 0 and 74 of fourth configuration 216, and RBs 0, 1, 98, and 99 of fifth configuration 220) or in the middle of the system bandwidth (for example, RB 7 of first configuration 204, RB 12 of second configuration 208, and RB 37 of fourth configuration 216).
  • the initial location of a narrowband may be determined based on an indication in the DCI, while cell-specific offsets may be used to determine other narrowband(s).
  • the frequency hopping may occur in a cyclic manner. For example, if two narrowbands are configured for frequency hopping, the frequency hopping pattern may include transmissions on NB0, NB1, NBO, etc. For another example, if four narrowbands are configured for frequency hopping, the frequency hopping partem may include transmissions on NBO, NB1, NB2, NB3, NBO, etc.
  • FH offset is the configured cell-specific frequency hopping
  • BW system bandwidth
  • the AN 108 may enable or disable frequency hopping by configuring the UE 104 via UE- specific, higher-layer signaling, for example, dedicated RRC signaling.
  • the AN 108 may configure UEs differently based on whether they are operating in a first CE mode, for example, CE mode A, or a second CE mode, for example, CE mode B.
  • a UE operating in CE mode A may only require a small number of repetitions, if any.
  • a UE operating in CE mode B may require a relatively larger number of repetitions.
  • the AN 108 may indicate whether or not a UE operating in CE mode A is to use or not use frequency hopping (once enabled by higher-layer configuration) in a dynamic manner via the DCI that indicates the DL assignment or UL grant.
  • the resource allocation can be larger than a single NB and in this case, direct application of previous frequency hopping methods can result in fragmentation of the PDSCH or PUSCH bandwidth at the band edges due to the wrap-around operation.
  • an extended narrowband may be defined as a resource allocation having an aggregation of more than six PRBs that are contiguous infrequency.
  • the number of PRBs aggregated may depend on the system bandwidth.
  • the extended narrowband concept may apply only to systems having a bandwidth greater than 1.4 MHz.
  • the extended narrowband definition would degenerate to a definition of a narrowband (for example, six PRBs that are contiguous infrequency) in a situation in which a system has a bandwidth of 1.4 MHz.
  • Configurations having an odd number of PRBs will have a central PRB that does not belong to any narrowband.
  • An extended narrowband in these configurations may or may not include the central PRB, depending on a location of the extended narrowbands and the configurations.
  • edge PRBs that do not belong to any narrowband (for example, configurations 204, 212, 216, and 220). Similar to above, an extended narrowband in these configurations may or may not include the edge PRBs, depending on a location of the extended narrowbands and the configurations.
  • Figure 3 illustrates extended narrowband resource allocations in the fourth configuration 216 and the fifth configuration 220 in accordance with some embodiments.
  • the resource allocations may be for PDSCH or PUSCH transmissions.
  • resources may be allocated in terms of extended narrowband 0 ("ENB #0"), extended narrowband 1 ("ENB #1”), and extended narrowband 2 ("ENB #2").
  • Extended narrowband 0 and extended narrowband 2 both have 24 PRBs (from their four narrowbands).
  • Extended narrowband 1 has 25 PRBs, from its four narrowbands in addition to central PRB 37. If frequency hopping is performed between extended narrowband 1 and either extended narrowband 0 or 2, the number of PRBs before and after hopping will not be the same.
  • resources may be allocated in terms of extended narrowband 0 ("ENB #0"), extended narrowband 1 ("ENB #1”), extended narrowband 2 (“ENB #2”), and extended narrowband 3 (“ENB #3").
  • Extended narrowbands 0 and 3 have 26 PRBs from their four narrowbands and two edge PRBs.
  • Extended narrowbands 1 and 2 have 24 narrowbands from their four narrowbands.
  • Figure 4 illustrates an example of coding 400 that may be used by the AN 108 to transmit PDSCH or by the UE 104 to transmit PUSCH according to some embodiments.
  • the coding 400 may include one or more physical coding processes 405 that may be used to provide coding for a physical channel that may encode data or control information.
  • Coding 400 may also include data, control multiplexing and channel interleaving 435 that generates combined coded information by combining information from one or more sources, which may include one of more of data information and control information, and which may have been encoded by one or more physical coding processes 405.
  • Combined coded information may be input to a block for scrambling 440, which may generate scrambled coded information.
  • Physical coding process 405 may include one or more of CRC attachment 410, code block segmentation 415, channel coding 420, rate matching 425 and code block concatenation 430.
  • CRC attachment 410 may calculate parity bits denoted:
  • boD ⁇ - 1 + b t D A+L - 2 + - + b ⁇ D 1 + b A+L _ t has a predetermined remainder when divided by a predetermined generator polynomial g(D) of order L.
  • the predetermined remainder may be zero
  • L may be 24
  • the predetermined polynomial g(D) may be:
  • code block segmentation 415 may generate one or more segmented code blocks, each containing a portion of the data input to code block segmentation 415.
  • Code block segmentation 415 may have minimum and maximum block size constraints as parameters, determined according to a selected channel coding scheme.
  • Code block segmentation 415 may add filler bits to one or more output segmented code blocks, in order to ensure that the minimum block size constraint is met.
  • Code block segmentation 415 may divide data input to the process into blocks in order to ensure that the maximum block size constraint is met.
  • code block segmentation 415 may append parity bits to each segmented code block. Such appending of parity bits may be determined based on one or more of the selected coding scheme and whether the number of segmented code blocks to be generated is greater than one.
  • channel coding 420 may generate code words from segmented code blocks according to one or more of a number of coding schemes. As an example, channel coding 420 may make use of one or more of convolutional coding, tail biting
  • PCCC parallel concatenated convolutional coding
  • LDPC low density parity check
  • rate matching 425 may be used to adjust a total number of bits to match a capacity of allocated resource blocks.
  • the total number of bits may be increased using repetition or decreased using puncturing.
  • Rate matching 425 for turbo coded transport channel may include a plurality of sub-block interleavers, for example, three sub-block interleavers, that interleave a corresponding plurality of information bit streams.
  • the plurality of information bit streams may include a systematic part, a parity 0, and a parity 1.
  • An output buffer which may be referred to as virtual circular buffer (“VCB”), may be formed by concatenating the rearranged systematic bits with the interlacing of the two rearranged parity streams.
  • VFB virtual circular buffer
  • the coded bits for transmission may be serially read out of the output buffer from any starting point, which could be indicated by a redundancy version. If an end of the output buffer is reached during the read out, the output may wrap around to the beginning of the output buffer.
  • the code block concatenation 430 may sequentially concatenate the output from the rate matching 425 for the different code blocks.
  • channel processing 444 may occur after scrambling 440 based on PUSCH or PDSCH processing techniques. These could include, for example: modulation mapping to modulate scrambled bits to generate complex-valued symbols; layer mapping to map the complex-valued modulation symbols onto one or more transmission layers; transform pre-coding to generate complex-valued symbols; and pre-coding of the complex-valued symbols.
  • Resource element mapping 448 may map the precoded complex-valued symbols to resource elements.
  • Signal generating 452 may then generate a complex-valued time domain signal (SC-FDMA for the PUSCH or OFDMA for the PDSCH) for each antenna port.
  • SC-FDMA complex-valued time domain signal
  • the coding 400 may be configured to code PDSCH/PUSCH based on whether an initial resource allocation is within an extended narrowband that has more or fewer PRBs than an extended narrowband having a subsequent resource allocation.
  • An initial resource allocation as used herein, may refer to the resources to be used before frequency hopping and a subsequent resource allocation may refer to resources to be used after frequency hopping.
  • resource allocation and frequency hopping may be defined using six-PRB narrowbands or PRBs.
  • a first case may include an initial resource allocation being within an extended narrowband that has more PRBs than an extended narrowband having a subsequent resource allocation.
  • the initial resource allocation may be within extended narrowband 1 and the subsequent resource allocation may be within extended narrowband 2. Two options may be considered for this case.
  • transmission on resource elements within the extra PRBs may be punctured at the UE transmitter in the hopped transmission.
  • the resource elements that exist in the initial allocation but not in the subsequent allocation are counted in the rate matching of the PUSCH/PDSCH, but not used for transmission.
  • the fourth configuration 216 of Figure 3 in which an initial allocation is within extended narrowband 1 and the subsequent allocation is within extended narrowband 2.
  • the initial allocation has 25 PRBs, ranging from PRB 25 to 49, and the subsequent allocation has 24 PRBs, ranging from 50 to 73.
  • the coded bit sequence received from the channel coding 420 may be rate matched to be carried on the 25 PRBs.
  • the UE transmitter may apply rate matching independently to the initial and subsequent allocations. For example, the resource elements that exist in the initial allocation but not in the subsequent allocation are not counted in rate matching of the PUSCH/PDSCH for the subsequent allocation.
  • the coded bit sequence received from the channel coding 420 may be rate matched to be carried on the 25 PRBs.
  • the coded bit sequence, ai-cik being mapped to 25 PRBs of the extended narrowband 1 resulting in a rate-matched bit sequence, bi-b25, with bi being the group of bits transmitted by a first PRB of the extended narrowband 1, PRB 25, 3 ⁇ 4 being the group of bits transmitted by the second PRB of the extended narrowband 1, PRB 26, and so on.
  • the coded bit sequence, ai-ck may be mapped to the 24 PRBs of the extended narrowband 2 resulting in another rate-matched bit sequence, ci-C24, which may be different from the rate-matched sequence bi-b25, with a being the group of bits transmitted by a first PRB of the extended narrowband 2, PRB 50, C2 being the group of bits transmitted by the second PRB of the extended narrowband 2, PRB 51, and so on.
  • the PRBs of extended narrowbands 1 and 2 carry the same coded bit sequence
  • the groups of bits carried by respective PRBs of the two extended narrowbands may be different.
  • an initial resource allocation may be within an extended narrowband that has fewer PRBs than an extended narrowband having a subsequent resource allocation, used for a hopped transmission.
  • the extended narrowband used after the frequency hopping may include a central or edge PRBs that do not belong to the extended narrowband used before the frequency hopping.
  • the initial resource allocation may be within extended narrowband 0 and the subsequent resource allocation may be within extended narrowband 1.
  • the rate matching may be the same for the initial and the hopped transmission. The rate matching considering the resource elements available for initial transmission may be applied.
  • the resource elements within the extra PRBs may be counted in resource element mapping, and thus the first or last several REs may be left blank in the hopped transmission.
  • the edge PRBs may be left blank.
  • the fourth configuration 216 of Figure 3 in which an initial allocation is within extended narrowband 0 and the subsequent allocation is within extended narrowband 1.
  • the initial allocation has 24 PRBs and the subsequent allocation is on non-contiguous NBs divided by a central PRB in the middle and, therefore, spans 25 PRBs.
  • the coded bit sequence received from the channel coding 420 may be rate matched to be carried on the 24 PRBs.
  • the coded bit sequence, ai-ak being mapped to 24 PRBs of the extended narrowband 0 resulting in a rate-matched bit sequence, bi-b24, with bi being the group of bits transmitted by a first PRB of the extended narrowband 0, PRB 1, b2 being the group of bits transmitted by the second PRB of the extended narrowband 0, PRB 2, and so on.
  • the same rate-matched bit sequence, bi-b24 may be transmitted by 24 PRBs of the extended narrowband 1.
  • the 24 PRBs may be PRBs 25-48, in which case PRB 49 would be left blank, or PRBs 26-49, in which case PRB 25 would be left blank.
  • the rate matching may be based on the resource elements available for the hopped transmission.
  • the transmissions on resource elements within the extra PRB(s), which are not included in initial allocation but are included in the hopped resources may be punctured in initial transmission.
  • the fourth configuration 216 of Figure 3 in which an initial allocation is within extended narrowband 0 and the subsequent allocation is within extended narrowband 1.
  • the initial allocation has 24 PRBs and the subsequent allocation has 25 PRBs.
  • the coded bit sequence received from the channel coding 420 may be rate matched to be carried on the 25 PRBs (even though extended narrowband 0 only has 24 PRBs).
  • ai-cik being mapped to 25 PRBs resulting in a rate-matched bit sequence, bi-b25, with bi being the group of bits to be transmitted by a first PRB of the extended narrowband 0, PRB 1, 3 ⁇ 4 being the group of bits transmitted by the second PRB of the extended narrowband 0, PRB 2, and so on.
  • bl3 the group of bits that corresponds to the middle PRB, would be skipped. Therefore, bu would be transmitted by the thirteenth PRB of the extended narrowband 0, PRB 13, and so on.
  • all of the rate-matched bit sequences, bi-b25 may be transmitted by the 25 PRBs of the extended narrowband 1.
  • transmissions mapped to a central PRB may be punctured in the initial transmission. This option may require consideration of future hopped resources at the time of performing an initial transmission.
  • rate matching may be applied to initial and hopped transmission depending on the number of allocated resource elements.
  • rate matching for a hopped transmission may take into account the additional resource elements that are available for the hopped transmission, and the transmission may be mapped to more resource elements.
  • the coded bit sequence received from the channel coding 420 may be rate matched to be carried on the 24 PRBs.
  • the coded bit sequence, ai-cik being mapped to 24 PRBs of the extended narrowband 1 resulting in a rate-matched bit sequence, bi-b24, with bi being the group of bits transmitted by a first PRB of the extended narrowband 0, PRB 1, b2 being the group of bits transmitted by the second PRB of the extended narrowband 0, PRB 2, and so on.
  • the coded bit sequence, ai-cik may be mapped to the 25 PRBs of the extended narrowband 1 resulting in another rate-matched bit sequence, ci-C25, which may be different from the rate-matched sequence bi-b24, with ci being the group of bits transmitted by a first PRB of the extended narrowband 1, PRB 25, C2 being the group of bits transmitted by the second PRB of the extended narrowband 1, PRB 26, and so on.
  • the PRBs of extended narrowbands 1 and 2 carry the same coded bit sequence
  • the groups of bits carried by respective PRBs of the two extended narrowbands may be different. This may be similar to the second option for the first case.
  • the resource elements within the extra PRBs may be left blank.
  • the central PRB may be left blank for a PDSCH transmission, but it may not be appropriate for a PUSCH transmission due to a single carrier constraint for single-carrier frequency-division multiple access ("SC-FDMA") based transmissions.
  • SC-FDMA single-carrier frequency-division multiple access
  • the coded bit sequence received from the channel coding 420 may be rate matched to be carried on the 24 PRBs.
  • the coded bit sequence, ai-cik being mapped to 24 PRBs of the extended narrowband 0 resulting in a rate-matched bit sequence, bi-b24, with bi being the group of bits transmitted by a first PRB of the extended narrowband 0, PRB 1, b2 being the group of bits transmitted by the second PRB of the extended narrowband 0, PRB 2, and so on.
  • the same rate-matched bit sequence, bi-b24 may be transmitted by 24 PRBs of the extended narrowband 1. This is similar to the first option for the second case except that in this instance, the central PRB of extended narrowband 1, PRB 37, is left blank.
  • resource allocation may be limited to extended narrowbands that consist of the same number of PRBs.
  • a resource allocation may be limited to only extended narrowbands that include 12 PRBs (for example, two contiguous narrowbands) on each side of the central PRB, PRB 12.
  • a resource allocation may be limited to either narrowbands ⁇ 0, 1 , 2, 3, 4, 5 ⁇ or narrowbands ⁇ 6, 7, 8, 9, 10, 1 1 ⁇ if a maximum UE bandwidth is 20 MHz, or be limited to either narrowbands ⁇ 0, 1, 2, 3 ⁇ or narrowbands ⁇ 8, 9, 10, 1 1 ⁇ if a maximum UE bandwidth is 5 MHz.
  • limitations on resource allocation may be used to ensure that the number of PRBs allocated before the frequency hopping is the same as the number of PRBs allocated after frequency hopping. This may be done, for example, by preventing allocation of any PRB that does not belong to a narrowband.
  • Limiting resource allocations in this manner may only occur when frequency hopping is applied in accordance with some embodiments. If the frequency hopping is not configured for a UE via higher layers, or is disabled via DCI even if configured via higher layers, the extended narrowband containing the central or edge PRBs may still be included in resource allocations.
  • an eNB may configured a UE with frequency hopping information to restrict a number of allocated PRBs before and after frequency hopping to be the same.
  • an access node may impose a constraint on frequency hopping.
  • the frequency hopping can be configured to ensure that the number of PRBs before and after frequency hopping are the same. Specifically, frequency hopping may be disabled if the initial allocation is within an extended narrowband that has a different number of PRBs from other extended narrowbands.
  • the disabling of frequency hopping may be explicit, for example, by control signaling sent from the access node to the UE, or implicit, for example, the UE/access node both understand that if a first frequency hopping region includes a different number of PRBs than a second frequency hopping region, frequency hopping will be disabled.
  • the frequency hopping offset may be set to ensure that the hopped extended narrowband is the one that has the same PRBs as initial allocation.
  • extended narrowband #0 and extended narrowband #2 both include 24 PRBs, while the extended narrowband #1 includes 25 PRBs (including the central PRB).
  • the frequency hopping may be disabled explicitly or implicitly, with the explicit enabling/disabling of frequency hopping indicated via the existing FH field in the DCI for UEs in CEModeA.
  • the frequency hopping offset may be set to ensure the hopped extended narrowband is either #2 or #0, for example, the frequency hopping offset may be set to eight NBs.
  • Figure 5 illustrates an example operation flow/algorithmic structure 500 of an encoding process according to some embodiments.
  • the flow/structure 500 may include, at 504, identifying initial allocation of resources. In some embodiments identification of the initial allocation of resources may be based on downlink control information transmitted from AN 108 to UE 104.
  • the flow/structure 500 may further include, at 508, identifying frequency hopping information. In some embodiments, some of the frequency hopping information may be provided to the UE 104 through higher-layer signaling such as, but not limited to, RRC signaling. For example, initial configuration parameters for frequency hopping may be configured by RRC signaling.
  • the initial configuration parameters may be used to establish a frequency hopping pattern including, but not limited to, a number of subframes in which a PDSCH/PUSCH transmission is to repeat in initial frequency domain resources before hopping and transmitting the PDSCH/PUSCH transmission in subsequent frequency domain resources; or a frequency hopping offset, which may be in terms of PRBs, NB, etc.
  • some of the frequency hopping information may be dynamically provided to the UE 104 through DCI.
  • DCI may have a frequency hopping flag to indicate whether frequency hopping is enabled or disabled.
  • the flow/structure 500 may further include, at 512, determining whether the initial ENB that includes the initial allocated frequency resources has more PRBs than a subsequent ENB that includes the subsequent allocated frequency resources after the frequency hopping.
  • the flow/structure 500 may further include, at 516, encoding shared channel transmission according to a first or second option of case 1 described above.
  • the flow/structure 500 may further include, at 520, encoding shared channel transmission according to a first, second, or third option of case 2 described above.
  • the flow/structure 500 may further include causing a shared channel transmission to be transmitted in an initial allocation and a repetition of the shared channel transmission to be transmitted in a subsequent allocation at 524.
  • FIG. 6 illustrates, for one embodiment, example components of an electronic device 600.
  • the electronic device 600 may be, implement, be incorporated into, or otherwise be a part of UE 104, AN 108, or some other device.
  • the electronic device 600 may include application circuitry 602, baseband circuitry 604, radio frequency (RF) circuitry 606, front-end module (FEM) circuitry 608 and one or more antennas 610, coupled together at least as shown.
  • RF radio frequency
  • FEM front-end module
  • the electronic device 600 may also include network interface circuitry (not shown) for communicating over a wired interface (for example, an X2 interface, an SI interface, and the like).
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • the application circuitry 602 may include one or more application processors.
  • the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors 602a.
  • the processor(s) 602a may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors 602a may be coupled with or may include computer-readable media 602b (also referred to as "CRM 602b,” “memory 602b,” “storage 102b,” or “memory /storage 602b") and may be configured to execute instructions stored in the CRM 602b to enable various applications or operating systems to run on the system.
  • the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
  • Baseband circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 604 may include a second generation (2G) baseband processor 604a, third generation (3G) baseband processor 604b, fourth generation (4G) baseband processor 604c, fifth generation (5G) baseband processor 604h, or other baseband processor(s) 604d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 604 e.g., one or more of baseband processors 604a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like.
  • modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 604, which may implement coding 400 of Figure 4 in some embodiments, may include convolution, tail- biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 604 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), or radio resource control (RRC) elements.
  • E-UTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 604e of the baseband circuitry 604 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP or RRC layers.
  • the CPU 604e may provide frequency hopping configuration by identifying frequency hopping information and determining a frequency hopping pattern that may be used by the encoding/decoding circuitry.
  • the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604f.
  • the audio DSP(s) 604f may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • the baseband circuitry 604 may further include computer-readable media 604b (also referred to as "CRM 604b,” “memory 604b,” “storage 604b,” or “CRM 604b”).
  • the CRM 604g may be used to load and store data or instructions for operations performed by the processors of the baseband circuitry 604.
  • CRM 604g for one embodiment may include any combination of suitable volatile memory or non-volatile memory.
  • the CRM 604g may include any combination of various levels of memory /storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.).
  • ROM read-only memory
  • DRAM dynamic random access memory
  • the CRM 604g may be shared among the various processors or dedicated to particular processors.
  • Components of the baseband circuitry 604 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 604 and the application circuitry 602 may be implemented together, such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 604 may support communication with an E-UTRAN or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 606 may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
  • RF circuitry 606 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the RF circuitry 606 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c 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 604 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the filter circuitry 606c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion or upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be arranged for direct downconversion or direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input.
  • the synthesizer circuitry 606d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 604 or the application circuitry 602 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay -locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+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.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 606d 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 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
  • the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 608 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 608 may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606).
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).
  • PA power amplifier
  • the electronic device 600 may include additional elements such as, for example, a display, a camera, one or more sensors, or interface circuitry (for example, input/output (I/O) interfaces or buses) (not shown).
  • the electronic device 600 may include network interface circuitry.
  • the network interface circuitry may be one or more computer hardware components that connect electronic device 600 to one or more network elements, such as one or more servers within a core network or one or more other eNBs via a wired connection.
  • the network interface circuitry may include one or more dedicated processors or field programmable gate arrays (FPGAs) to communicate using one or more network communications protocols such as X2 application protocol (AP), S I AP, Stream Control Transmission Protocol (SCTP), Ethernet, Point-to-Point (PPP), Fiber Distributed Data Interface (FDDI), or any other suitable network communications protocols.
  • FPGAs field programmable gate arrays
  • the electronic device 600 may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.
  • the electronic device 600 may implement the coding 400 of Figure 4 or the flows/structures 500 of Figure 5.
  • Figure 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 7 shows a diagrammatic representation of hardware resources 700 including one or more processors (or processor cores) 710, one or more memory /storage devices 720, and one or more communication resources 730, each of which may be communicatively coupled via a bus 740.
  • node virtualization for example, network function virtualization (“NFV")
  • a hypervisor 702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 700.
  • NFV network function virtualization
  • the processors 710 may include, for example, a processor, a reduced instruction set computing (“RISC”) processor, a complex instruction set computing (“CISC”) processor, a graphics processing unit (“GPU”), a digital signal processor (“DSP”) such as a baseband processor, an application specific integrated circuit (“ASIC”), a radio-frequency integrated circuit (“RFIC”), another processor, or any suitable combination thereof
  • 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 processors may correspond to any processors of application circuitry 602 or baseband circuitry 604 of Figure 6.
  • the memory /storage devices 720 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 720 may include, but are not limited to, any type of volatile or non-volatile memory such as dynamic random access memory (“DRAM”), static random-access memory (“SRAM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • the memory /storage devices 720 may correspond to any processors of application circuitry 602 or baseband circuitry 604 of Figure 6.
  • the communication resources 730 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 704 or one or more databases 706 via a network 708.
  • the communication resources 730 may include wired communication components (for example, for coupling via a Universal Serial Bus (“USB”)), cellular communication components, near-field communication (“NFC”) components, Bluetooth® components (for example, Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • wired communication components for example, for coupling via a Universal Serial Bus (“USB”)
  • USB Universal Serial Bus
  • NFC near-field communication
  • Bluetooth® components for example, Bluetooth® Low Energy
  • Wi-Fi® components and other communication components.
  • Instructions 750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 710 to perform any one or more of the methodologies discussed herein.
  • the instructions 750 may cause the processors 710 to perform the operation
  • the instructions 750 may reside, completely or partially, within at least one of the processors 710 (for example, within the processor's cache memory), the memory /storage devices 720, or any suitable combination thereof. Furthermore, any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral devices 704 or the databases 706. Accordingly, the memory of processors 710, the memory /storage devices 720, the peripheral devices 704, and the databases 706 are examples of computer-readable and machine-readable media.
  • the resources described in Figure 7 may also be referred to as circuitry.
  • communication resources 730 may also be referred to as communication circuitry 730.
  • Example 1 includes one or more computer-readable media having instructions that, when executed, cause a user equipment ("UE") to: identify, based on downlink control information (“DCI"), an initial allocation of resources in a first aggregation of physical resource blocks to be used for a physical uplink shared channel (“PUSCH”) transmission in a first subframe; identify, based on a frequency hopping offset, a subsequent allocation of resources in a second aggregation of physical resource blocks to be used for a repetition of the PUSCH transmission in a second subframe, wherein the first aggregation of physical resource blocks includes a different number of physical resource blocks than the second aggregation of physical resource blocks; and cause the PUSCH transmission to be transmitted in the initial allocation of resources and the repetition of the PUSCH transmission to be transmitted in the subsequent allocation of resources.
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • Example 2 includes the one or more computer-readable media of example 1, wherein the first or second aggregation of physical resource blocks includes a physical resource block that is at a center of an uplink system bandwidth.
  • Example 3 includes the one or more computer-readable media of example 1 or 2, wherein the instructions, when executed, further cause the UE to operate in a coverage
  • Example 4 includes the one or more computer-readable media of example 1 or 2, wherein the UE is a bandwidth-reduced, low-complexity UE.
  • Example 5 includes the one or more computer-readable media of example 1 or 2, wherein the first aggregation of physical resource blocks includes a first plurality of narrowbands, the second aggregation of resource blocks includes a second plurality of narrowbands, and either the first or the second aggregation of physical resource blocks further includes one or more physical resource blocks not included in a narrowband.
  • Example 6 includes the one or more computer-readable media of example 1 or 2, wherein the initial allocation of resources comprises a first plurality of allocated physical resource blocks that are contiguous in frequency within the first aggregation of physical resource blocks and the subsequent allocation of resources comprises a second plurality of allocated physical resource blocks that are contiguous in frequency within the second aggregation of physical resource blocks, the first plurality being equal to the second plurality.
  • Example 7 includes the one or more computer-readable media of example 1 or 2, wherein the first aggregation of physical resource blocks includes more physical resource blocks than the second aggregation of physical resource blocks.
  • Example 8 includes the one or more computer-readable media of example 7, wherein the first aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the instructions, when executed, are to further cause a transmission on resource elements with the one or more edge or central physical resource blocks to be punctured with respect to the repetition of the PUSCH to be transmitted in the subsequent allocation of resources.
  • Example 9 includes the one or more computer-readable media of example 1 or 2, wherein the instructions, when executed, are to further cause the UE to apply rate matching independently to the initial allocation of resources and the subsequent allocation of resources.
  • Example 10 includes the one or more computer-readable media of example 1 or 2, wherein the first aggregation of physical resource blocks includes fewer physical resource blocks than the second aggregation of physical resource blocks.
  • Example 11 includes the one or more computer-readable media of example 10, wherein the instructions, when executed, are to further cause a UE to apply rate matching, based on the first aggregation of physical resource blocks, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 12 includes the one or more computer-readable media of example 11, wherein the second aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the instructions, when executed, further cause the UE to leave the one or more edge or central physical resource blocks blank in the repetition of the PUSCH transmission.
  • Example 13 includes the one or more computer-readable media of example 10, wherein the instructions, when executed, further to cause the UE to apply rate matching, based on the second aggregation of physical resource blocks, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 14 includes the one or more computer-readable media of example 13, wherein the second aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the instructions, when executed, further cause the UE to puncture transmissions corresponding to the one or more edge or central physical resource blocks in the PUSCH transmission to be transmitted in the initial allocation of resources.
  • Example 15 includes the one or more computer-readable media of example 10, wherein the second aggregation of physical resource blocks includes one or more central or edge physical resource blocks that are not included in a narrowband and the instructions, when executed, further cause the UE to leave one or more starting or ending physical resource blocks of the second aggregation of physical resource bloks blank while a number of used physical resource blocks are the same as initial transmission in the repetition of the PUSCH transmission to be transmitted in the subsequent allocation of resources.
  • Example 16 includes the one or more computer-readable media of example 1, wherein the initial allocation of resources in the first aggregation of physical resource blocks are to be used for a plurality of subframes, including the first subframe, before transmission of the repetition of the PUSCH transmission in the second subframe and the subsequent allocation of resources in the second aggregation of physical resource blocks are to be used for another plurality of subframes, including the second subframe.
  • Example 17 includes the one or more computer-readable media of example 1, wherein the first aggregation of physical resources are contiguous in frequency and the second aggregation of physical resource blocks are contiguous in frequency.
  • Example 18 includes an apparatus comprising: a central processing unit to determine a frequency hopping pattern; and encoding circuitry, coupled with the central processing unit, to: encode, based on the frequency hopping partem, a shared channel transmission using an initial allocation of resources in a first extended narrowband; and encode, based on the frequency hopping pattern, the repetition of the shared channel transmission using a subsequent allocation of resources in a second extended narrowband, wherein either the first or the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband.
  • Example 19 includes the apparatus of example 18, wherein the first or second extended narrowbands includes a physical resource block that is at a center of an uplink system bandwidth.
  • Example 20 includes the apparatus of example 18 or 19, wherein the central processing unit is to configure a UE to operate in a coverage enhancement mode A.
  • Example 21 includes the apparatus of example 18 or 19, wherein the first extended narrowband includes a first plurality of narrowbands, the second extended narrowband includes a second plurality of narrowbands, and either the first or the second extended narrowbands further includes a physical resource block not included in a narrowband.
  • Example 22 includes the apparatus of example 18 or 19, wherein the first extended narrowband includes more physical resource blocks than the second extended narrowband.
  • Example 23 includes the apparatus of example 22, wherein the first extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding circuitry is to encode the repetition of the shared channel transmission in a manner such that a transmission on resource elements with the one or more edge or central physical resource blocks are punctured with respect to the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 24 includes the apparatus of example 18 or 19, wherein the encoding circuitry is to apply rate matching independently to the initial allocation of resources and the subsequent allocation of resources.
  • Example 25 includes the apparatus of example 18 or 19, wherein the first extended narrowband includes fewer physical resource blocks than the second extended
  • Example 26 includes the apparatus of example 25, wherein the encoding circuitry is to apply rate matching, based on the first extended narrowband, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 27 includes the apparatus of example 25, wherein the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding circuitry is to leave the one or more edge or central physical resource blocks blank in the repetition of the shared channel transmission.
  • Example 28 includes the apparatus of example 25, wherein the encoding circuitry is to apply rate matching, based on the second extended narrowband, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 29 includes the apparatus of example 28, wherein the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding circuitry is to puncture transmissions corresponding to the one or more edge or central physical resource blocks in the shared channel transmission to be transmitted in the initial allocation of resources.
  • Example 30 includes the apparatus of example 28, wherein the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding circuitry is further to leave one or more starting or ending physical resource blocks of the second extended narrowband blank in the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 31 includes the apparatus of example 18 or 19, wherein the shared channel transmission is a physical downlink shared channel (“PDSCH”) transmission or a physical uplink shared channel (“PUSCH”) transmission.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • Example 32 includes the apparatus of example 18 or 19, wherein the central processing unit is further to receive a configuration, through radio resource control (“RRC”) signaling, to enable frequency hopping.
  • Example 33 includes one or more computer-readable media having instructions that, when executed, cause an evolved node B (“eNB") to: configure a user equipment (“UE”) with frequency hopping information to restrict a number of allocated physical resource blocks before and after frequency hopping to be the same; and enable frequency hopping based on the frequency hopping information.
  • eNB evolved node B
  • UE user equipment
  • Example 34 includes the one or more computer-readable media of example 33, wherein the instructions, when executed, further cause the eNB to process a shared channel transmission based on the frequency hopping information.
  • Example 35 includes the one or more computer-readable media of example 34, wherein the shared channel transmission is a physical uplink shared channel transmission or a physical downlink shared channel transmission.
  • Example 36 includes the one or more computer-readable media of example 33, where the frequency hopping information includes a frequency hopping offset.
  • Example 37 includes an apparatus comprising circuitry to: configure a user equipment (“UE") with a frequency hopping pattern to transmit or receive a shared channel transmission in at least two extended narrowbands; and limit resource allocation to a same number of physical resource blocks in each of the at least two extended narrowbands.
  • UE user equipment
  • Example 38 includes the apparatus of example 37, wherein the circuitry is further to limit resource allocation to physical resource blocks that are included in respective
  • Example 39 includes the apparatus of example 37, wherein the circuitry is further to process a shared channel transmission based on frequency hopping information.
  • Example 40 includes the apparatus of example 39, wherein the shared channel transmission is a physical uplink shared channel transmission or a physical downlink shared channel transmission.
  • Example 41 includes an apparatus comprising: means for identifying an initial allocation of resources in a first aggregation of physical resource blocks to be used for a shared channel transmission in a first subframe; means for identifying a subsequent allocation of resources in a second aggregation of physical resource blocks to be used for a repetition of the shared channel transmission in a second subframe, wherein the first aggregation of physical resource blocks includes a different number of physical resource blocks than the second aggregation of physical resource blocks; and cause the shared channel transmission to be transmitted in the initial allocation of resources and the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 42 includes the apparatus of example 41, wherein the shared channel transmission is a physical uplink shared channel transmission or a physical downlink shared channel transmission.
  • Example 43 includes the apparatus of example 41, wherein the first or second aggregation of physical resource blocks includes a physical resource block that is at a center of an uplink system bandwidth.
  • Example 44 includes the apparatus of any one of examples 41-43, wherein the apparatus is a bandwidth-reduced, low-complexity user equipment.
  • Example 45 includes the apparatus of any one of examples 41-44, wherein the first aggregation of physical resource blocks includes a first plurality of narrowbands, the second aggregation of resource blocks includes a second plurality of narrowbands, and either the first or the second aggregation of physical resource blocks further includes one or more physical resource blocks not included in a narrowband.
  • Example 46 includes the apparatus of any one of examples 41-45, wherein the initial allocation of resources comprises a first plurality of allocated physical resource blocks that are contiguous in frequency within the first aggregation of physical resource blocks and the subsequent allocation of resources comprises a second plurality of allocated physical resource blocks that are contiguous in frequency within the second aggregation of physical resource blocks, the first plurality being equal to the second plurality.
  • Example 47 includes the apparatus of any one of examples 41-46, wherein the first aggregation of physical resource blocks includes more physical resource blocks than the second aggregation of physical resource blocks.
  • Example 48 includes the apparatus of example 47, wherein the first aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the apparatus further comprises means for causing a transmission on resource elements with the one or more edge or central physical resource blocks to be punctured with respect to the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 49 includes the apparatus of any one of examples 41-48, wherein the apparatus further comprises means for applying rate matching independently to the initial allocation of resources and the subsequent allocation of resources.
  • Example 50 includes the apparatus of any one of examples 41-46, wherein the first aggregation of physical resource blocks includes fewer physical resource blocks than the second aggregation of physical resource blocks.
  • Example 51 includes the apparatus of example 50, wherein the apparatus further comprises means for applying rate matching, based on the first aggregation of physical resource blocks, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 52 includes the apparatus of example 51, wherein the second aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the apparatus further comprises means for leaving the one or more edge or central physical resource blocks blank in the repetition of the shared channel transmission.
  • Example 53 includes the apparatus of example 50, wherein the apparatus further comprises means for applying rate matching, based on the second aggregation of physical resource blocks, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 54 includes the apparatus of example 53, wherein the second aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the apparatus further comprises means for puncturing transmissions corresponding to the one or more edge or central physical resource blocks in the shared channel transmission to be transmitted in the initial allocation of resources.
  • Example 55 includes the apparatus of example 50, wherein the second aggregation of physical resource blocks includes one or more central or edge physical resource blocks that are not included in a narrowband and the apparatus further comprises means for leaving one or more starting or ending physical resource blocks of the second aggregation of physical resource blocks blank while a number of used physical resource blocks are the same as initial transmisison in the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 56 includes the apparatus of any one of examples 41-55, wherein the initial allocation of resources in the first aggregation of physical resource blocks are to be used for a plurality of subframes, including the first subframe, before transmission of the repetition of the shared channel transmission in the second subframe and the subsequent allocation of resources in the second aggregation of physical resource blocks are to be used for another plurality of subframes, including the second subframe.
  • Example 57 includes the apparatus of any one of examples 41-56, wherein the first aggregation of physical resource blocks are contiguous in frequency and the second aggregation of physical resource blocks are contiguous in frequency.
  • Example 58 includes a method comprising: identifying an initial allocation of resources in a first aggregation of physical resource blocks to be used for a shared channel transmission in a first subframe; identifying, based on a frequency hopping offset, a subsequent allocation of resources in a second aggregation of physical resource blocks to be used for a repetition of the shared channel transmission in a second subframe, wherein the first aggregation of physical resource blocks includes a different number of physical resource blocks than the second aggregation of physical resource blocks; and causing the shared channel transmission to be transmitted in the initial allocation of resources and the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 59 includes the method of example 58, wherein the first or second aggregation of physical resource blocks includes a physical resource block that is at a center of an uplink system bandwidth.
  • Example 60 includes the method of example 58 or 59, wherein the first aggregation of physical resource blocks includes a first plurality of narrowbands, the second aggregation of resource blocks includes a second plurality of narrowbands, and either the first or the second aggregation of physical resource blocks further includes one or more physical resource blocks not included in a narrowband.
  • Example 61 includes the method of any one of examples 58-60, wherein the initial allocation of resources comprises a first plurality of allocated physical resource blocks that are contiguous in frequency within the first aggregation of physical resource blocks, and the subsequent allocation of resources comprises a second plurality of allocated physical resource blocks that are contiguous in frequency within the second aggregation of physical resource blocks, the first plurality being equal to the second plurality.
  • Example 62 includes the method of any one of examples 58-61, wherein the first aggregation of physical resource blocks includes more physical resource blocks than the second aggregation of physical resource blocks.
  • Example 63 includes the method of example 62, wherein the first aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the method further comprises causing a transmission on resource elements with the one or more edge or central physical resource blocks to be punctured with respect to the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 64 includes the method of any one of examples 58-63, wherein the method further comprises causing a user equipment to apply rate matching independently to the initial allocation of resources and the subsequent allocation of resources.
  • Example 65 includes the method of any one of examples 58-61, wherein the first aggregation of physical resource blocks includes fewer physical resource blocks than the second aggregation of physical resource blocks.
  • Example 66 includes the method of example 65, wherein the method further comprises causing a user equipment to apply rate matching, based on the first aggregation of physical resource blocks, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 67 includes the method of example 66, wherein the second aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the method further comprises causing the user equipment to leave the one or more edge or central physical resource blocks blank in the repetition of the shared channel transmission.
  • Example 68 includes the method of example 65, wherein the method further comprises causing a user equipment to apply rate matching, based on the second aggregation of physical resource blocks, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 69 includes the method of example 68, wherein the second aggregation of physical resource blocks includes one or more edge or central physical resource blocks that are not included in a narrowband and the method further comprises causing a user equipment to puncture transmissions corresponding to the one or more edge or central physical resource blocks in the shared channel transmission to be transmitted in the initial allocation of resources.
  • Example 70 includes the method of example 65, wherein the second aggregation of physical resource blocks includes one or more central or edge physical resource blocks that are not included in a narrowband and the method further comprises causing the UE to leave one or more starting or ending physical resource blocks of the second aggregation of physical resource bloks blank while a number of used physical resource blocks are the same as initial transmission in the repetition of the PUSCH transmission to be transmitted in the subsequent allocation of resources.
  • Example 71 includes the method of any one of examples 58-70, wherein the initial allocation of resources in the first aggregation of physical resource blocks are to be used for a plurality of subframes, including the first subframe, before transmission of the repetition of the shared channel transmission in the second subframe, and the subsequent allocation of resources in the second aggregation of physical resource blocks are to be used for another plurality of subframes, including the second subframe.
  • Example 72 includes the method of any one of examples 58-71, wherein the first aggregation of physical resource blocks are contiguous in frequency and the second aggregation of physical resource blocks are contiguous in frequency.
  • Example 73 includes a method comprising: encoding, based on a frequency hopping pattern, a shared channel transmission using an initial allocation of resources in a first extended narrowband; and encoding, based on the frequency hopping pattern, a repetition of the shared channel transmission using a subsequent allocation of resources in a second extended narrowband, wherein either the first or the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband.
  • Example 74 includes the method of example 73, wherein the first or second extended narrowbands includes a physical resource block that is at a center of an uplink system bandwidth.
  • Example 75 includes the method of example 73 or 74, further comprising configuring a UE to operate in a coverage enhancement mode A.
  • Example 76 includes the method of any one of examples 73-75, wherein the first extended narrowband includes a first plurality of narrowbands, the second extended narrowband includes a second plurality of narrowbands, and either the first or the second extended narrowbands further includes a physical resource block not included in a narrowband.
  • Example 77 includes the method of any one of examples 73-76, wherein the first extended narrowband includes more physical resource blocks than the second extended narrowband.
  • Example 78 includes the method of example 77, wherein the first extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding comprises encoding the repetition of the shared channel transmission in a manner such that a transmission on resource elements with the one or more edge or central physical resource blocks are punctured with respect to the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 79 includes the method of any one of examples 73-78, wherein the encoding comprises applying rate matching independently to the initial allocation of resources and the subsequent allocation of resources.
  • Example 80 includes the method of any one of examples 73-79, wherein the first extended narrowband includes fewer physical resource blocks than the second extended
  • Example 81 includes the method of example 80, wherein the encoding comprises applying rate matching, based on the first extended narrowband, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 82 includes the method of example 80, wherein the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding comprises leaving the one or more edge or central physical resource blocks blank in the repetition of the shared channel transmission.
  • Example 83 includes the method of example 80, wherein the encoding comprises applying rate matching, based on the second extended narrowband, to both the initial allocation of resources and the subsequent allocation of resources.
  • Example 84 includes the method of example 83, wherein the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding comprises puncturing transmissions corresponding to the one or more edge or central physical resource blocks in the shared channel transmission to be transmitted in the initial allocation of resources.
  • Example 85 includes the method of example 84, wherein the second extended narrowband includes one or more edge or central physical resource blocks that are not included in a narrowband and the encoding comprises leaving one or more starting or ending physical resource blocks of the second extended narrowband blank in the repetition of the shared channel transmission to be transmitted in the subsequent allocation of resources.
  • Example 86 includes the method of any one of examples 73-85, wherein the shared channel transmission is a physical downlink shared channel (“PDSCH”) transmission or a physical uplink shared channel (“PUSCH”) transmission.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • Example 87 includes a method comprising: configuring a user equipment (“UE") with frequency hopping information to restrict a number of allocated physical resource blocks before and after frequency hopping to be the same; and enabling frequency hopping based on the frequency hopping information.
  • UE user equipment
  • Example 88 includes the method of example 87, further comprising processing a shared channel transmission based on the frequency hopping information.
  • Example 89 includes the method of example 88, wherein the shared channel transmission is a physical uplink shared channel transmission or a physical downlink shared channel transmission.
  • Example 90 includes the method of any one of examples 87-89, where the frequency hopping information includes a frequency hopping offset.
  • Example 91 includes a method comprising: configuring a user equipment (“UE") with a frequency hopping partem to transmit or receive a shared channel transmission in at least two extended narrowbands; and limiting resource allocation to a same number of physical resource blocks in each of the at least two extended narrowbands.
  • UE user equipment
  • Example 92 includes the method of example 91, further comprising limiting resource allocation to physical resource blocks that are included in respective narrowbands.
  • Example 93 includes the method of example 91 and 92, further comprising processing a shared channel transmission based on frequency hopping information.
  • Example 94 includes the method of example 93, wherein the shared channel transmission is a physical uplink shared channel transmission or a physical downlink shared channel transmission.
  • Example 95 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 58-94, or any other method or process described herein.
  • Example 96 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 58-94, or any other method or process described herein.
  • Example 97 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 58-94, or any other method or process described herein.
  • Example 98 may include a method, technique, or process as described in or related to any of examples 58-94, or portions or parts thereof.
  • Example 99 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 58-94, or portions thereof.
  • Example 100 may include the apparatus of example 99, wherein the apparatus is a category Ml UE.
  • Example 101 may include a system and method of supporting a user equipment that supports larger bandwidth for reception or transmission compared to, for example, Category Ml or Rel-13 low complexity UEs.
  • Example 102 may include the subject matter of example 101 or some other example herein, wherein an ENB is an aggregation of more than 6 PRBs that are located contiguous in frequency.
  • Example 104 may include the subject matter of example 102 or some other example herein, wherein the ENB may include a central PRB or edge PRBs that are not part of any NB.
  • Example 105 may include the subject matter of example 104 or some other example herein, wherein frequency hopping is supported and the number of PRBs within an ENB that includes the initial frequency domain resources and the ENB that includes the frequency domain resources after frequency hopping is different.
  • Example 106 may include the subject matter of example 105 or some other example herein, wherein the initial frequency region including the allocated resources has more PRBs than the frequency region that includes the resources for hopped transmission, and the transmissions on REs within the central PRBs or edge PRBs, which are included in initial allocation but not included in the hopped resources, are punctured in the hopped transmission.
  • Example 107 may include the subject matter of example 105 or some other example herein, wherein the initial frequency region including the allocated resources has more PRBs than the hopped transmission, and the hopped transmission applies rate matching to fewer REs, where the REs within the central PRBs or edge PRBs, which are included in the initial allocation but not included in the hopped resources, are not counted in
  • Example 108 may include the subject matter of example 105 or some other example herein, wherein the initial frequency region including the allocated resources has fewer PRBs than the hopped transmission, and the rate matching in hopped transmission takes into account the additional REs within the central PRBs or edge PRBs, which are not included in initial allocation but included in the hopped resources, for example, rate matching to more REs is applied in hopped transmission.
  • Example 109 may include the subject matter of example 105 or some other example herein, wherein the initial frequency region including the allocated resources has fewer PRBs than the hopped transmission, and same rate matching for initial transmission is applied to hopped transmissions, with RE mapping taking into account the additional REs within the central PRBs or edge PRBs, which are not included in initial allocation but included in the hopped resources.
  • Example 1 10 may include the subject matter of example 109 or some other example herein, wherein rate matching based on the number of available REs in the initial transmission is applied, and thus the first several REs or the last several REs are left blank in the hopped transmissions and the remaining REs carry the transmission with the same rate matching as initial transmission, for example, the number of REs left blank is the same the number of additional REs within the central PRBs or edge PRBs, which are not included in initial allocation but included in the hopped resources.
  • Example 1 11 may include the subject matter of example 109 or some other example herein, wherein rate matching based on the number of available REs in the hopped transmission is applied, and thus the transmissions on REs within the central PRBs or edge PRBs, which are not included in initial allocation but included in the hopped resources, are punctured in initial transmission.
  • Example 1 12 may include the subject matter of example 5 or some other example herein, wherein the initial frequency region including the allocated resources has fewer PRBs than the hopped transmission, and the additional REs within the central PRBs or edge PRBs, which are not included in initial allocation but included in the hopped resources are not counted in RE mapping and are left blank.
  • Example 1 13 may include the subj ect matter of example 112 or some other example herein, wherein the method can be applied to PDSCH when central PRB is left blank, and may not be applied to PUSCH when central PRB is left blank and results in discontiguous frequency domain allocations.
  • Example 1 14 may include the subject matter of example 105 or some other example herein, wherein the resource allocation is limited to ENBs that include the same number of PRBs.
  • Example 1 15 may include the subj ect matter of example 114 or some other example herein, wherein for system BW of 5MHz, the resource allocation is limited to only the ENBs which include 12 PRBs (2 contiguous NBs) on each side of the central PRB.
  • Example 1 16 may include the subj ect matter of example 114 or some other example herein, wherein for system BW of 15MHz, the resource allocation can be limited to either NBs ⁇ 0, 1 , 2, 3, 4, 5 ⁇ or NBs ⁇ 6, 7, 8, 9, 10, 11 ⁇ if maximum UE BW is 20 MHz, or be limited to either NBs ⁇ 0, 1, 2, 3 ⁇ or NBs ⁇ 8, 9, 10, 1 1 ⁇ if maximum UE BW is 5 MHz.
  • Example 1 17 may include the subject matter of example 116 or some other example herein, wherein the method is applied only when FH is enabled, and in cases FH is not configured for the UE via higher layers or disabled via DCI even if configured via higher layers, the ENB containing central or edge PRBs are still included.
  • Example 1 18 may include the subject matter of example 115 or some other example herein, wherein the frequency hopping can be configured to ensure that the number of PRBs in a contiguous frequency region including the allocated resources before and after frequency hopping are the same.
  • Example 1 19 may include the subject matter of example 118 or some other example herein, wherein frequency hopping is disabled explicitly or implicitly, with the explicit enabling/disabling of frequency hopping indicated via the legacy FH field in the DCI for UEs in CEModeA, if the initial allocation is within ENB which has different number of PRBs from other ENBs, e.g. the ENB # 1 in systems with BW of 15MHz, which has ENB #0 and ENB #2 include 24 PRBs, while the ENB # 1 include 25 PRBs (including the central PRB).
  • Example 121 may include a method of communicating in a wireless network as shown and described herein.
  • Example 122 may include a system for providing wireless communication as shown and described herein.
  • Example 123 may include a device for providing wireless communication as shown and described herein.

Landscapes

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

Abstract

Des modes de réalisation de la présente invention concernent des procédés et des appareils pour prendre en charge un saut de fréquence avec un nombre différent de blocs de ressources physiques dans différentes régions de fréquence sautées.
PCT/US2017/052104 2016-09-29 2017-09-18 Support de saut de fréquence avec un nombre différent de blocs de ressources physiques dans différentes régions de fréquence sautées WO2018063845A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112017003821.9T DE112017003821T5 (de) 2016-09-29 2017-09-18 Unterstützung von Frequency-Hopping mit unterschiedlicher Anzahl physikalischer Ressourcenblöcke in unterschiedlichen Frequenzbereichen

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662401538P 2016-09-29 2016-09-29
US62/401,538 2016-09-29

Publications (1)

Publication Number Publication Date
WO2018063845A1 true WO2018063845A1 (fr) 2018-04-05

Family

ID=59969285

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/052104 WO2018063845A1 (fr) 2016-09-29 2017-09-18 Support de saut de fréquence avec un nombre différent de blocs de ressources physiques dans différentes régions de fréquence sautées

Country Status (2)

Country Link
DE (1) DE112017003821T5 (fr)
WO (1) WO2018063845A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018140277A1 (fr) * 2017-01-27 2018-08-02 Qualcomm Incorporated Conception de saut de fréquence pour des attributions de bande passante importantes dans des communications emtc
WO2020051043A1 (fr) * 2018-09-06 2020-03-12 Qualcomm Incorporated Techniques d'attribution souple de ressources
WO2020097905A1 (fr) * 2018-11-16 2020-05-22 Nokia Shanghai Bell Co., Ltd. Commande de transmission de données
CN111954244A (zh) * 2020-08-04 2020-11-17 工业互联网创新中心（上海）有限公司 5g信号仿真方法、装置、电子设备及存储介质
US20210051636A1 (en) * 2019-08-16 2021-02-18 Qualcomm Incorporated Communicating repetitions of multiple transport blocks scheduled by single downlink control information
US10972354B1 (en) 2019-09-16 2021-04-06 Sprint Spectrum L.P. Wireless communication between a wide bandwidth network node and a narrow bandwidth wireless device
US11012112B2 (en) 2018-02-09 2021-05-18 Qualcomm Incorporated Techniques for flexible resource allocation
US20220150003A1 (en) * 2019-02-14 2022-05-12 Ntt Docomo, Inc. User terminal

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160249327A1 (en) * 2015-02-25 2016-08-25 Qualcomm Incorporated Narrowband management for machine type communications

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160249327A1 (en) * 2015-02-25 2016-08-25 Qualcomm Incorporated Narrowband management for machine type communications

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "On retuning time and measurement gaps for MTC UEs", vol. RAN WG1, no. Malmö, Sweden; 20151005 - 20151009, 4 October 2015 (2015-10-04), XP051002240, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20151004] *
INTEL CORPORATION: "Time-frequency relationships for physical channels for MTC", vol. RAN WG1, no. Beijing, China; 20150824 - 20150828, 23 August 2015 (2015-08-23), XP051001402, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20150823] *
ZTE: "Support of larger TBS and larger PDSCH/PUSCH bandwidth for MTC", vol. RAN WG1, no. Gothenburg, Sweden; 20160822 - 20160826, 21 August 2016 (2016-08-21), XP051125838, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20160821] *

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10355743B2 (en) 2017-01-27 2019-07-16 Qualcomm Incorporated Frequency hopping design for large bandwidth allocations in eMTC
WO2018140277A1 (fr) * 2017-01-27 2018-08-02 Qualcomm Incorporated Conception de saut de fréquence pour des attributions de bande passante importantes dans des communications emtc
US11012112B2 (en) 2018-02-09 2021-05-18 Qualcomm Incorporated Techniques for flexible resource allocation
CN112640558A (zh) * 2018-09-06 2021-04-09 高通股份有限公司 用于灵活的资源分配的技术
WO2020051043A1 (fr) * 2018-09-06 2020-03-12 Qualcomm Incorporated Techniques d'attribution souple de ressources
CN112640558B (zh) * 2018-09-06 2023-09-12 高通股份有限公司 用于灵活的资源分配的技术
US11290999B2 (en) 2018-09-06 2022-03-29 Qualcomm Incorporated Techniques for flexible resource allocation
WO2020097905A1 (fr) * 2018-11-16 2020-05-22 Nokia Shanghai Bell Co., Ltd. Commande de transmission de données
US20220150003A1 (en) * 2019-02-14 2022-05-12 Ntt Docomo, Inc. User terminal
US20210051636A1 (en) * 2019-08-16 2021-02-18 Qualcomm Incorporated Communicating repetitions of multiple transport blocks scheduled by single downlink control information
US11553474B2 (en) * 2019-08-16 2023-01-10 Qualcomm Incorporated Communicating repetitions of multiple transport blocks scheduled by single downlink control information
US12010705B2 (en) 2019-08-16 2024-06-11 Qualcomm Incorporated Communicating repetitions of multiple transport blocks scheduled by single downlink control information
US10972354B1 (en) 2019-09-16 2021-04-06 Sprint Spectrum L.P. Wireless communication between a wide bandwidth network node and a narrow bandwidth wireless device
CN111954244A (zh) * 2020-08-04 2020-11-17 工业互联网创新中心（上海）有限公司 5g信号仿真方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
DE112017003821T5 (de) 2019-04-18

Similar Documents

Publication Publication Date Title
US20240032054A1 (en) Enhancement on scheduling and harq-ack feedback for urllc, multiplexing scheme for control/data channel and dm-rs for nr, and activation mechanism, scheduling aspects, and synchronization signal (ss) blocks for new radio (nr) system with multiple bandwidth parts (bwps)
US11575554B2 (en) Scrambling sequence initial seed configuration for reference signals, data, and control channel for new radio
EP3603260B1 (fr) Suivi de signaux de référence pour une nouvelle radio
CN111434165B (zh) 新无线电(nr)频域资源分配技术
US11457510B2 (en) Determining and commuicating control information in wireless telecommunication networks
US20200037314A1 (en) Uplink control information (uci) transmission and hybrid automatic repeat request (harq) process identification for grant-free physical uplink shared channel (pusch)
US20190045529A1 (en) Scheduling request transmission opportunity and resource configuration in new radio
CA2954996C (fr) Equipement d&#39;utilisateur et procedes d&#39;allocation et de signalisation de ressources de temps pour les communications de dispositif a dispositif (d2d)
US12003432B2 (en) Channel state information report on physical uplink shared channel in new radio
WO2018063845A1 (fr) Support de saut de fréquence avec un nombre différent de blocs de ressources physiques dans différentes régions de fréquence sautées
EP3858044A1 (fr) Allocation de ressources du domaine temporel pour transmissions répétées en nouvelle radio
CN112771805B (zh) 新无线电(nr)的基于序列的上行链路(ul)传输取消
WO2020000412A1 (fr) Connexions de couches de transport pour réseaux de communication mobiles
WO2021086499A1 (fr) Systèmes, procédés et dispositifs pour l&#39;activation de cellule secondaire
US12022474B2 (en) Frequency domain resource allocation for downlink (DL) and uplink (UL) in new radio (NR)

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

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17772857

Country of ref document: EP

Kind code of ref document: A1