CN108541359A - System and method for the flexible time-domain resource mapping for NPDCCH and NPDSCH in NB-IOT systems - Google Patents

Abstract

This provides techniques for offering flexible time-domain resource mapping. Information related to discontinuous reception of the Narrowband Physical Downlink Control Channel (NPDCCH) and the corresponding Narrowband Physical Downlink Shared Channel (NPDSCH) can be provided to Narrowband Internet of Things (NB-IoT) User Equipment (UE). Available subframes for the NPDCCH and NPDSCH can be provided to NB-IoT UEs or a group of NB-IoT UEs with similar coverage conditions. Flexible time intervals between the NPDCCH and NPDSCH can also be provided.

Description

Flexible time domain resource mapping for NPDCCH and NPDSCH in NB-IOT system systems and methods

related application

This application claims priority to US Provisional Patent Application Serial No. 62/292,038, filed February 5, 2016, the entire contents of which are hereby incorporated by reference.

technical field

Embodiments herein relate generally to communication between devices in a narrowband wireless communication network.

Background technique

The 3rd Generation Partnership Project (3GPP) is introducing narrowband Internet of Things (NB-IoT) designs into the Release 13 specification of its Long Term Evolution (LTE) wireless mobile communications standard. For NB-IoT devices that may operate under poor coverage conditions, it may be necessary to repeat the transmission to the NB-IoT device. Repeating transmissions to some NB-IoT devices to ensure reception may block transmissions to other NB-IoT devices that do not need repeated transmissions. Accordingly, there may be a need for new techniques to serve NB-IoT devices in poor coverage areas without adversely affecting transmissions to NB-IoT devices in good coverage areas.

Description of drawings

Figure 1 illustrates an exemplary operating environment.

Figure 2 shows an embodiment of a logic flow.

Figure 3 shows an exemplary transmission scheme.

Figure 4 shows a second embodiment of the logic flow.

Figure 5 shows an embodiment of a storage medium.

Figure 6 shows an embodiment of a first device.

Figure 7 shows an embodiment of a second device.

Figure 8 shows an embodiment of a wireless network.

Detailed ways

Various embodiments may generally relate to techniques for providing flexible temporal resource mapping. Information related to discontinuous reception of a narrowband physical downlink control channel (NPDCCH) and a corresponding narrowband physical downlink shared channel (NPDSCH) may be provided to a NB-IoT user equipment (UE). Subframes available for NPDCCH and NPDSCH may be provided to NB-IoT UEs or a group of NB-IoTUEs with similar coverage conditions. A flexible time interval between NPDCCH and NPDSCH may also be provided. Other embodiments are described and claimed.

Various embodiments may include one or more elements. An element may comprise any structure arranged to perform certain operations. Each element can be implemented as hardware, software, or any combination thereof, as desired for a given set of design parameters or performance constraints. Although embodiments may be described as having a limited number of elements in a particular topology by way of example, embodiments may include more or fewer elements in alternative topologies as desired for a given implementation. It is worth noting that any reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrases "in one embodiment," "in some embodiments," and "in various embodiments" in various places in the specification are not necessarily all referring to the same embodiment.

The techniques disclosed herein may involve transferring data over one or more wireless connections using one or more wireless mobile broadband technologies. For example, various embodiments may involve implementations based on one or more 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPP LTE-Advanced (LTE-A) technologies and/or standards (including their Amendments, successors, and variants - including 4G and 5G wireless networks) over one or more wireless connections.

Various embodiments may relate to one or more Narrowband Internet of Things (NB-IoT) technologies and/or standards (for example, the 3GPP NB-IoT design introduced in the Release 13 specification of the LTE wireless mobile communication standard) through one or more transmission over a wireless connection. The 3GPP LTE NB-IoT specification defines a network architecture based on (especially for improved indoor coverage, support for a large number of low-throughput devices, low latency sensitivity, ultra-low device complexity and cost, low device power consumption, and optimized network architecture. The Radio Access Technology (RAT) for the Cellular Internet of Things (CIoT) that is a non-backward compatible variant of the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) standard.

Various embodiments may additionally or alternatively relate to data based on one or more of Global System for Mobile Communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA), and and/or transmission of GSM (GSM/GPRS) technology and/or standards (including their amendments, successors, and variants) with the General Packet Radio Service (GPRS) system.

Examples of wireless mobile broadband technologies and/or standards may also include, but are not limited to, any Institute of Electrical and Electronics Engineers (IEEE) 802.16 wireless broadband standards (e.g., IEEE 802.16m and/or 802.16p), International Mobile Telecommunications Advanced (IMT- ADV), Worldwide Interoperability for Microwave Access (WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 1xRTT, CDMA2000EV-DO, CDMA EV-DV, etc.), High Performance Radio Metropolitan Area Network (HIPERMAN), Wireless Broadband (WiBro), High Speed Downlink Packet Access (HSDPA), High Speed Orthogonal Frequency Division Multiplexing (OFDM) Packet Access (HSOPA), High Speed Uplink Packet Access (HSUPA) technologies and/or Standards, including their amendments, successors and variations.

Some embodiments may additionally or alternatively relate to wireless communications according to other wireless communications technologies and/or standards. Examples of other wireless communication technologies and/or standards that may be used in various embodiments may include, but are not limited to, other IEEE wireless communication standards (e.g., IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11 n, IEEE 802.11u, IEEE 802.11ac, IEEE 802.11ad, IEEE 802.11af, and/or IEEE802.11ah standards), the High Efficiency Wi-Fi standard developed by the IEEE 802.11 High Efficiency WLAN (HEW) Study Group, the Wi-Fi Alliance ( WFA) wireless communication standards (e.g., Wi-Fi, Wi-Fi Direct, Wi-Fi Direct Service, Wireless Gigabit (WiGig), WiGig Display Extensions (WDE), WiGig Bus Extensions (WBE), WiGig Serial Extensions (WSE) standards, and/or standards developed by the WFA Neighbor Awareness Networking (NAN) Task Group), Machine Type Communication (MTC) standards (for example, in 3GPP Technical Report (TR) 23.887, 3GPP Technical Specification (TS) 22.368, and/or those implemented in 3GPP TS 23.682), and/or Near Field Communication (NFC) standards (eg, standards developed by the NFC Forum), including any amendments, successors, and/or variants described above. Embodiments are not limited to these examples.

In addition to transmission over one or more wireless connections, techniques disclosed herein may involve transmission of content over one or more wired connections over one or more wired communication media. Examples of wired communications media may include a wire, cable, metal leads, printed circuit board (PCB), backplane, switch fabric, semiconductor material, twisted-pair wire, co-axial cable, fiber optics, and so forth. The embodiments are not limited in this context.

Conventional techniques may be based on the scheduling window concept to provide a method of supporting discontinuous transmission for NPDCCH and NPDSCH. For scheduling window based approach - define a specific time window that always includes a first set of subframes that can carry NPDCCH and a second set of subframes that can carry NPDSCH, and repeat the pattern.

The disclosed techniques for discontinuous transmission for NPDCCH and NPDSCH provided herein provide enhanced and improved flexibility. The disclosed techniques provided herein allow decoupling the set of subframes used for control and data transmission. The disclosed techniques provided herein also allow flexibility in time-domain multiplexing of different UEs through different configurations of per-UE available downlink (DL) subframes for NB-PDCCH and/or NB-PDSCH.

FIG. 1 illustrates an example operating environment 100 that may, for example, represent some embodiments in which techniques for discontinuous mapping of time-domain resources may be implemented. Operating environment 100 may include mobile device 102 and cellular base station 104 . Operating environment 100 can be considered to be part of a network that enables wireless communication between mobile devices 102 and base stations 104 . The mobile device 102 can communicate with the base station 104 through the wireless communication interface 106 . Mobile device 102 may be any mobile computing device capable of wirelessly communicating with one or more wireless communication networks. As an example, mobile device 102 may be an IoT device capable of communicating wirelessly with cellular base station 104 within a relatively narrowband frequency range. Mobile device 102 may be a user equipment (UE). Base station 104 may be a cellular base station, eg, an evolved Node B (eNB). The wireless communication interface 106 can be, for example, for any wireless network or standard described herein (including, for example, 4G, LTE, or 5G wireless network, or specifically, NB-IoT technology and/or standard (for example, 3GPP LTE NB-IoT standard )) wireless interface. As an example, the mobile device 102 may be a smart meter that may be connected to or incorporated into a larger device for communicating information related to the associated device (the smart meter may thus be considered relative to the larger device equipment is stationary or fixed). Mobile device 102 and base station 104 can implement the techniques described herein for discontinuous mapping of time domain resources.

Operating environment 100 (including its constituent components, including mobile device 102 and base station 104 ) may operate in accordance with the 3GPP LTE NB-IoT standard. Operating environment 100, mobile device 102, and base station 104 may support, for example, three different modes of operation, namely, a standalone mode of operation, a guard-band mode of operation, and an in-band mode of operation. For the stand-alone operation mode and the guard band operation mode, all resources in the NB-IoT carrier can be used for the transmission of NB-IoT signals and channels. A NB-IoT carrier may typically include one legacy LTE physical resource block (PRB) corresponding to a system bandwidth of 180 kHz with a subcarrier spacing of 15 kHz. LTE NB-IoT (or NB-LTE) may be based on Orthogonal Frequency Division Multiple Access (OFDMA) in the downlink (DL) and Single Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL).

The NB-IoT physical layer design that may be used in the operating environment 100 may use a subset of the channels defined for legacy LTE systems. Other channels may not be defined for NB-IoT systems. A NB-IoT UE (eg, mobile device 102) can perform a cell search to identify a suitable cell for connecting to the Internet. In a first step, the NB-IoT UE 102 may attempt to detect a Narrowband Primary Synchronization Signal (NB-PSS). NB-IoT UE 102 may also use NB-PSS to synchronize its clock with the NB-IoT network and detect symbol boundaries of OFDM waveforms. In a second step, the NB-IoT UE 102 may attempt to use the Narrowband Secondary Synchronization Signal (NB-SSS) to obtain the downlink subframe and frame timing as well as the Physical Cell ID (PCI) of the NB-IoT carrier. Based on the cell ID and radio frame synchronization, the UE 102 may proceed to decode the Narrowband Physical Broadcast Channel (NB-PBCH), which may include scheduling information for the transmission of additional system information. Acquiring the NB-IoT system information will enable the NB-IoT UE 102 to initiate a random access (RA) procedure to attach to the NB-IoT network. The network may respond to the random access procedure with a Random Access Response (RAR). The random access procedure allows the network to configure the NB-IoT UE 102 for communication with the network and may include contention resolution procedures. After the connection is established, the network can configure the NB-IoT UE 102 with cell-specific and UE-specific Radio Resource Control (RRC) parameters to control the transmission and reception behavior of the NB-IoT UE 102 .

Communication between NB-IoT UE 102 and the network (via and including base station 104) may be scheduled over a narrowband physical downlink control channel (NPDCCH) (possibly excluding random access channel (RACH)). NPDCCH can carry downlink control information (DCI) from eNodeB 104 to NB-IoT UE 102, which can schedule narrowband physical downlink shared channel (NPDSCH) transmission and/or Narrowband Physical Uplink Shared Channel (NPUSCH) transmission. Other channels may not be required in the NB-LTE system, but they are not excluded.

Demodulation of the narrowband physical broadcast channel (NPBCH), NPDCCH, and/or NPDSCH may be based on a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), or a narrowband reference signal (NB-RS). Furthermore, different channels may be modulated using different reference signals. Finally, several reference signals can be used to demodulate a single channel. For example, NPBCH can be demodulated using NB-RS, and NPDCCH can be demodulated using CRS. In a different example, CRS may be used to demodulate NPDCCH when NB-IoT UE 102 is in good coverage conditions, while other NB-IoT UEs (not shown in FIG. 1 for simplicity) may use CRS and NB-RS to demodulate NPDCCH.

With reference to the NPDCCH (regardless of its detailed physical layer (PHY) design), mechanisms may be needed that allow NB-IoT UEs (eg, mobile device 102 ) to decode the NPDCCH without prior knowledge of the physical resources used to transmit the NPDCCH. Unlike NPDSCH and NPUSCH (the transmission of which is scheduled by DCI, which includes resource allocation for transmission and Adaptive Modulation and Coding (AMC) scheme), NB-IoT UE 102 may need to Down decoding NPDCCH.

Assuming a fixed modulation scheme (e.g., quadrature phase-shift keying (QPSK)) for NPDCCH and a deterministic payload size for DCI, the eNB scheduler can dynamically change the resources in the time-frequency grid allocated to a given NPDCCH The number of elements (RE) is used to adjust the code rate of NPDCCH transmission. The NB-IoT UE 102 when attempting to decode an NPDCCH can typically blindly decode a defined set of physical resources called a search space (SS) for possible NPDCCH transmissions, whereby the cyclic redundancy check (CRC) for NPDCCH candidates passes successfully decoded NPDCCH.

A search space can be considered as a logical concept mapped to physical resources through control channel elements (CCEs). Herein, a Narrowband Control Channel Element (NCCE) may mean a CCE for defining mapping to a physical resource element of an NPDCCH. Specifically, a NB-IoT UE (e.g., mobile device 102) may attempt to decode NPDCCH for different code rate assumptions called aggregation levels (ALs), whereby each AL maps to a different number of transmissions assumed for NPDCCH NCCE. In addition, each group of NCCEs in a subframe can be repeated multiple times according to a repetition level (RL). In other words, NPDCCH candidates are defined in terms of AL, starting NCCE index, and RL(m) for a given NPDCCH candidate.

The number of candidates (ie, blind decoding attempts) for a given AL is known a priori to the UE 102, as defined by the search space. Furthermore, the search space definition may include a hash function for randomizing the CCE indices across subframes to prevent blocking between different NB-IoTUEs. To further address the blocking aspect for both NPDCCH and NPDSCH transmissions, NPDCCH and NPDSCH may be mapped to (eg, temporally) discontinuous sets of subframes, at least for UEs in extended or extreme coverage conditions. In one example, these coverage conditions may map to maximum coupling losses (MCL) of 154dB and 164dB. Furthermore, considering the limited amount of resources available in the frequency domain for each subframe, scheduling flexibility can be further provided by flexibly indicating the time domain resources by flexibly indicating the start subframe of the scheduled NPDSCH.

The techniques described herein facilitate this flexibility by supporting discontinuous transmission for NPDCCH and NPDSCH, and flexible time-domain scheduling for NPDSCH.

As mentioned above, for NB-IoT systems, limited resources can be obtained in the frequency domain (for example, 1 PRB spans 180kHz). As a result, time division multiplexing (TDM) based multiplexing between downlink (DL) transmissions of NPDCCH and NPDSCH for the same or different UEs (eg, mobile device 102 ) may be relied upon for NB-IoT systems. Furthermore, NPDCCH and NPDSCH transmissions may need to be repeated multiple times in order to provide coverage enhancement to UEs in poor channel conditions. A single NPDSCH transport block (TB) may also be mapped to multiple DL subframes for the transmission of moderately sized payloads (eg, ~500 to 1000 bits of information).

The NPDCCH may be sent using one or two NB-CCEs in a subframe, which may be repeated in subsequent subframes to provide the required coverage. While for a UE in good coverage, the NPDCCH transmissions of up to two such UEs can be multiplexed by FDM within a subframe, machine type communication (MTC) enabled user PDCCH signals (M- PDCCH signal) can be multiplexed by TDM.

Furthermore, in order to reduce the number of time-domain repetitions required for UEs to receive NPDSCH, NPDSCH may occupy all available resources in PRB pairs of each subframe - ie, no FDM may be used between NPDCCH and NPDSCH or between two NPDSCH transmissions.

In view of this, as mentioned above, in order to provide sufficient scheduling flexibility and avoid blocking NPDCCH or NPDSCH transmissions to UEs that may require a large number of repetitions/subframes, the discontinuous mapping of time domain resources at subframe level can Used for both NPDCCH and NPDSCH transmissions. Additional flexibility may be further provided by allowing a flexible time interval (rather than a fixed time interval) between the NB-PDCCH and the scheduled (associated) NB-PDSCH.

Accordingly, techniques are provided herein for providing discontinuous time-domain resource mapping for NPDCCH and NPDSCH. In various embodiments, a bitmap based mechanism may be used. However, the embodiments and techniques described herein are not limited in this regard. Furthermore, techniques are provided herein for providing flexible time-domain resource allocation (with flexible spacing between NPDCCH and NPDSCH).

In various embodiments, techniques are provided for providing sufficient scheduling flexibility and avoiding NPDCCH or NPDSCH transmissions to a UE that require a large number of repetitions/subframes from blocking NPDCCH or NPDSCH transmissions to other UEs.

In various embodiments, to achieve discontinuous resource allocation in the time domain, a UE-specific or UE-group-specific bitmap-based configuration of subframes available for NPDCCH and NPDSCH may be utilized. For UE group-specific options, a common configuration may be provided to all UEs in a cell or UEs with similar coverage classes.

FIG. 2 illustrates an example of a logic flow 200 that may represent an implementation of one or more disclosed techniques for providing discontinuous resource allocation. For example, logic flow 200 may represent operations that may be performed by mobile device 102 (eg, UE) and/or base station 104 in operating environment 100 of FIG. 1 in some embodiments. In general, the logic flow can represent operations performed between a mobile device (eg, mobile device 102 ) and a base station (eg, base station 104 ) to facilitate discontinuous resource mapping for NB-IoT devices.

At 202, a mobile device and a base station can establish a wireless communication link. The wireless communication link may be a narrowband wireless communication link. The wireless communication link may be the wireless link 106 described with respect to FIG. 1 . A mobile device may be a NB-IoT device. A mobile device may be a mobile device located at or in a relatively poor coverage area. That is, a mobile device may be a mobile device that may be sent with a relatively large number of transmission repetitions (e.g., repeated subframes) for the mobile device to correctly receive and handle transfers.

At 204, an indication of discontinuous time domain resource mapping for NPDCCH and/or NPDSCH can be provided. An indication may be provided by a base station. An indication can be received by a mobile device. The mobile device can decode and process the received indications. The indication may be provided over a control channel or as part of the control information. The indication may be provided as part of downlink control information (DCI).

At 206, an indication of subframes available for NPDCCH and/or NPDSCH can be provided. An indication may be provided by a base station. An indication can be received by a mobile device. The mobile device can decode and process the received indications. The indication may be provided over a control channel or as part of the control information. The indication may be provided as part of downlink control information (DCI).

In various embodiments, a bitmap based configuration may be used to indicate available subframes for NPDCCH and NPDSCH. In various other embodiments, available subframes for NPDCCH and NPDSCH may be indicated by other signaling techniques as described herein. In various embodiments, the available subframes for NPDCCH and NPDSCH may be indicated specifically for each mobile device (eg, on a UE-specific basis). In various other embodiments, available subframes for NPDCCH and NPDSCH may be indicated for groups of mobile devices (eg, on a UE group-specific basis). In various embodiments, a combination of UE-specific indications and UE group-specific indications may be used. In various embodiments, for options specific to a group of UEs, a common configuration may be provided to all UEs in a cell or UEs with similar coverage classes.

As an example, UEs in robust coverage (corresponding to maximum coupling loss (MCL) values up to 144dB, 154dB, 164dB, respectively), extended coverage, and extreme coverage may be grouped in order to multiplex to UEs belonging to different coverage classes NPDCCH and NPDSCH. In various embodiments (e.g., for UE group-specific configuration), control information related to subframes available for NPDCCH and NPDSCH may be passed through a common radio resource control (RRC) RRC (e.g., system information block (SIB) signaling) or through dedicated RRC signaling.

In general, signaling provided to UEs on a UE-specific basis may also be used to provide signaling to UEs on a UE group-specific basis.

In various embodiments, the eNodeB may signal a common configuration of UE-specific available subframes for all downlink (DL) unicast channels (eg, both NPDCCH and NPDSCH). In various embodiments, the eNodeB may signal separate configurations of UE-specific available subframes for NPDCCH and NPDSCH. In various embodiments, the configuration (eg, via bitmap based signaling) may relate to absolute radio frame and/or subframe indices.

In various embodiments, signaling (e.g., by constructing a bitmap) may indicate available subframes or valid DL subframes within a larger set of all DL subframes (or a set of available contiguous valid subframes) (e.g., 10 or 20 effective subframes). In various embodiments, instructions (eg, patterns) may be repeated in time.

As noted above, the techniques described herein provide flexible temporal resource allocation. As described herein, flexible time-domain resource allocation may be provided by supporting non-contiguous time-domain resource mapping (eg, at the subframe level). Scheduling flexibility may be further enhanced by supporting flexible time intervals between scheduled assignments carried by NPDCCHs and scheduled (eg, associated) NPDSCHs.

In various embodiments, the eNodeB may configure or indicate the value k_PDSCH for NPDSCH scheduling with a flexible time interval from the last subframe of the corresponding NPDCCH. The value k_PDSCH may be used such that the first subframe of the scheduled NPDSCH is the first UE-specific available subframe after an interval of k_PDSCH-1 subframes from the last subframe of the scheduled NPDCCH.

In various embodiments, the value of k_PDSCH may be at least two. In various embodiments, the lower bound may be further increased to allow additional time budget for decoding the NPDCCH, enabling a low complexity UE implementation (with reduced peak processing load requirements). In various embodiments, the value of k_PDSCH may be signaled by higher layers (eg, dedicated RRC) or using DCI that schedules NPDSCH. In various embodiments, for indicating k_PDSCH using DCI signaling, multiple bits (eg, 1 or 2 bits) may be used to indicate the k_PDSCH value.

FIG. 3 shows an exemplary subframe structure 300 for providing flexible time intervals between scheduled assignments carried by NPDCCHs and scheduled (eg, associated or corresponding) NPDSCHs. Indicator 302 shows an indication of the relative timing relationship. As shown in FIG. 3 , subframe 304 may represent the last subframe in which the NPDCCH is scheduled. Subframe 306 may represent a first subframe of a scheduled NPDSCH (eg, scheduled by NPDCCH). A gap 308 may be provided between subframes 304 and 306 . In various embodiments, interval 308 may be a flexible time interval 308 . Interval 308 may indicate a first UE-specific available subframe for NPDSCH 306 . Interval 308 may indicate the beginning of NPDSCH 306 relative to the end of NPDCCH 304 . In various embodiments, interval 308 may be configured or indicated using the value k_PDSCH described above.

FIG. 4 shows an example of a logic flow 400 that may represent one or more mechanisms for providing a flexible time interval between a scheduled assignment carried by an NPDCCH and a scheduled (e.g., associated or corresponding) NPDSCH. implementation of the disclosed technology. For example, logic flow 400 may represent operations that may be performed by mobile device 102 (eg, UE) and/or base station 104 in operating environment 100 of FIG. 1 in some embodiments. In general, the logic flow can represent the steps (e.g., correlation) performed between a mobile device (e.g., mobile device 102) and a base station (e.g., base station 104) to facilitate scheduling allocation and scheduling carried by NPDCCH for NB-IoT devices. Operations that provide flexible time intervals between connected or corresponding) NPDSCHs.

At 402, a mobile device and a base station can establish a wireless communication link. The wireless communication link may be a narrowband wireless communication link. The wireless communication link may be the wireless link 106 described with respect to FIG. 1 . A mobile device may be a NB-IoT device. A mobile device may be a mobile device located at or in a relatively poor coverage area. That is, a mobile device may be a mobile device that may be sent with a relatively large number of transmission repetitions (e.g., repeated subframes) for the mobile device to correctly receive and handle transfers.

At 404, an indication of a flexible time interval between the scheduled assignment carried by the NPDCCH and the scheduled (eg, associated or corresponding) NPDSCH can be provided. An indication may be provided by a base station. An indication can be received by a mobile device. The mobile device can decode and process the received indications. The indication may be provided over a control channel or as part of the control information. The indication may be provided as part of downlink control information (DCI).

At 406, an indication of a value (eg, or length or duration) of the flexible time interval can be provided. In various embodiments, the value k_PDSCH may be used to indicate this value. The value k_PDSCH may be used to indicate that the first subframe of the scheduled NPDSCH may be the first UE-specific available subframe after an interval of k_PDSCH-1 subframes from the last subframe of the scheduled NPDCCH. In this way, a flexible time interval between the NPDCCH and the scheduled associated NPDSCH can be provided.

As described by the techniques described herein, the NB-IoT UE (e.g., UE 102) may decode an indication included in the received downlink information, based on the indication determine a discontinuous time domain resource mapping for NPDCCH and NPDSCH, And the available subframes for NPDCCH and NPDSCH can be decoded based on the determined discontinuous time domain resource mapping. Available subframes for NPDCCH and NPDSCH may be provided or indicated in the determined discontinuous time domain resource mapping. The indication provided to the NB-IoT UE 102 may only/uniquely correspond to the NB-IoT UE. The base station 104 may provide indications related to discontinuous time-domain resource mapping for each NB-IoT UE in the cell individually, or may provide similar time-domain resource mapping for multiple NB-IoT UEs. For example, base station 104 may provide the same discontinuous time domain resource mapping to a group of NB-IoT UEs. That is, discontinuous time-domain resource mapping can be provided to a group of NB-IoT UEs. As an example, the group of NB-IoT UEs operate within the same cell. As another example, the group of NB-IoT UEs operate within the same coverage class. That is, the set of NB-IoT UEs may operate under similar reception quality and/or coverage conditions (eg, and may require a similar number of repetitions to ensure adequate reception).

Discontinuous time domain resource mapping may specify available subframes for NPDCCH and/or available subframes for NPDSCH. Discontinuous time domain resource mapping may specify available subframes based on reference subframe indices and/or based on reference absolute radio frames. The decoded indication may include a further indication of the flexible time interval between NPDCCH and NPDSCH. Alternatively, a separate or independent indication of the flexible time interval may be provided and decoded. The downlink information received by the NB-IoT UE may be received through DCI or dedicated RRC.

FIG. 5 shows an embodiment of a storage medium 500 . Storage medium 500 may include any non-transitory computer-readable or machine-readable storage medium, such as optical, magnetic, or semiconductor storage media. In various embodiments, storage medium 500 may comprise an article of manufacture. In some embodiments, the storage medium 500 may store computer-executable instructions, eg, computer-executable instructions for implementing the logic flow 200 of FIG. 2 and/or the logic flow 400 of FIG. 4 . Examples of computer-readable or machine-readable storage media can include any tangible medium capable of storing electronic data, including volatile or nonvolatile memory, removable or non-removable, erasable or non-removable Erasable memory, writable or rewritable memory, etc. Examples of computer-executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The embodiments are not limited in this context.

As used herein, the term "circuitry" may refer to, may be part of, or may include the following: an Application Specific Integrated Circuit (ASIC), an electronic circuit, a (shared , dedicated, or group) processor and/or memory (shared, dedicated, or group), combinational logic, and/or other suitable hardware components that provide the described functionality. In some embodiments, a circuit may be implemented in one or more software or firmware modules, or functionality associated with a circuit may be implemented by one or more software or firmware modules. In some embodiments, circuitry may include logic at least partially operable in hardware. The embodiments described herein may be implemented as a system using any suitably configured hardware and/or software.

FIG. 6 shows an example of a mobile device 600 that may represent a mobile device (eg, UE) implementing one or more disclosed techniques in various embodiments. For example, mobile device 600 may represent mobile device 102 according to some embodiments. In some embodiments, mobile 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 coupled together at least as shown 610.

Application circuitry 602 may include one or more application processors. For example, application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general and special purpose processors (eg, graphics processors, application processors, etc.). The processor may be coupled to and/or include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

Baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 604 may include one or more baseband processors and/or control logic to process baseband signals received from the receive signal path of RF circuitry 606 and generate baseband signals for the transmit signal path of RF circuitry 606 . Baseband processing circuitry 604 may interface with application circuitry 602 for generating and processing baseband signals and for controlling the operation of RF circuitry 606 . For example, in some embodiments, baseband circuitry 604 may include a second generation (2G) baseband processor 604a, a third generation (3G) baseband processor 604b, a fourth generation (4G) baseband processor 604c, and/or Other baseband processor(s) 604d in other existing generations, generations in development, or generations to be developed in the future (eg, fifth generation (5G), 6G, etc.). Baseband circuitry 604 (eg, one or more of baseband processors 604 a - d ) may handle various radio control functions that support communication with one or more radio networks via RF circuitry 606 . Radio control functions may include, but are not limited to: signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 604 may include Fast Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of baseband circuitry 604 may include convolutional, tailbiting convolutional, turbo, Viterbi, and/or low density parity check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples, and other suitable functionality may be included in other embodiments.

In some embodiments, baseband circuitry 604 may include elements of a protocol stack, for example, elements of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example: physical (PHY), medium access control (MAC), radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and/or Radio Resource Control (RRC) elements. A central processing unit (CPU) 604e of baseband circuitry 604 may be configured to run elements of a protocol stack for signaling at the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processors (DSPs) 604f. Audio DSP(s) 604f may include elements for compression and/or decompression and/or echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, the components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or suitably arranged on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuitry 604 and application circuitry 602 may be implemented together, eg, on a system-on-chip (SOC).

In some embodiments, baseband circuitry 604 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 604 may support communication with Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN) communication. Embodiments in which baseband circuitry 604 is configured to support radio communications for multiple wireless protocols may be referred to as multi-mode baseband circuitry.

RF circuitry 606 may support communication with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate communication with wireless networks. RF circuitry 606 may include a receive signal path, which may include circuitry to downconvert RF signals received from FEM circuitry 608 and provide baseband signals to baseband circuitry 604 . RF circuitry 606 may also include a transmit signal path, which may include circuitry to upconvert the baseband signal provided by baseband circuitry 604 and provide the RF output signal to FEM circuitry 608 for transmission.

In some embodiments, RF circuitry 606 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuit 606 may include a mixer circuit 606a, an amplifier circuit 606b, and a filter circuit 606c. The transmit signal path of the RF circuit 606 may include a filter circuit 606c and a mixer circuit 606a. The RF circuit 606 may also include a combiner circuit 606d for combining frequency spectra for use by the mixer circuit 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 606a of the receive signal path may be configured to downconvert the RF signal received from the FEM circuit 608 based on the synthesized frequency provided by the synthesizer circuit 606d. Amplifier circuit 606b may be configured to amplify the down-converted signal, and filter circuit 606c may be a low-pass filter (LPF) or filter circuit 606c configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. Band Pass Filter (BPF). The output baseband signal may be provided to baseband circuitry 604 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 606a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuit 606a of the transmit signal path may be configured to upconvert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 606d to generate an RF output signal for the FEM circuit 608 . The baseband signal may be provided by baseband circuitry 604 and may be filtered by filter circuitry 606c. Filter circuit 606c may include a low pass filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may comprise two or more mixers and may be arranged for quadrature down-conversion and/or Or upconvert. In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may comprise two or more mixers and may be arranged for image suppression (e.g., Hartley image inhibition). In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 604 may include a digital baseband interface in communication with RF circuitry 606 .

In some dual-mode embodiments, separate radio integrated circuit (IC) circuits may be provided to process signals for one or more frequency spectrums, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuit 606d may be a fractional N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

The synthesizer circuit 606d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 606a of the RF circuit 606 . In some embodiments, the combiner circuit 606d may be a fractional N/N+1 combiner.

In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The frequency divider control input may be provided by the baseband circuit 604 or the application processor 602, depending on the desired output frequency. In some embodiments, the frequency divider control input (eg, N) may be determined from a lookup table based on the channel indicated by the application processor 602 .

The combiner circuit 606d of the RF circuit 606 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (eg, based on implementation) to provide a fractional division ratio. In some example embodiments, a DLL may include a cascaded set of tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to break up the VCO cycle into at most Nd equal phase groupings, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 606d may be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, quadruple), and can be used in conjunction with quadrature generator and frequency divider circuits to generate multiple signals at the carrier frequency with multiple phases different from each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 606 may include IQ and/or polarity switches.

FEM circuitry 608 may include a receive signal path that may include RF signals configured to manipulate received RF signals from one or more antennas 610, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 606 for circuit for further processing. FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 606 for transmission by one or more of one or more antennas 610 .

In some embodiments, FEM circuit 608 may include a TX/RX switch to switch between transmit mode and receive mode operation. FEM circuitry 608 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 608 may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (eg, to RF circuit 606 ). The transmit signal path of FEM circuitry 608 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuitry 606), and may include one or more filters to generate or multiple antennas 610) for RF signals.

In some embodiments, mobile device 600 may include additional elements such as memory/storage, display, camera, sensors, and/or input/output (I/O) interfaces.

FIG. 7 illustrates an embodiment of a communications device 700 that may implement one or more of mobile device 102 , base station 104 , logic flow 200 , logic flow 400 , storage medium 500 , and mobile device 600 . In various embodiments, device 700 may include logic circuitry 728 . Logic circuitry 728 may include physical circuitry for performing operations such as described for one or more of mobile device 102 , base station 104 , logic flow 200 , logic flow 400 , storage medium 500 , and mobile device 600 . As shown in FIG. 7, device 700 may include radio interface 710, baseband circuitry 720, and computing platform 730, but embodiments are not limited to this configuration.

Device 700 can implement one of logic circuits 728 for mobile device 102, base station 104, logic flow 200, logic flow 400, storage medium 500, mobile device 600, and a single computing entity (e.g., entirely within a single device entity) Some or all of the structures and/or operations of one or more items. Alternatively, appliance 700 may use a distributed system architecture (e.g., client-server architecture, 3-tier architecture, N-tier architecture, tightly coupled or clustered architecture, peer-to-peer architecture, master-slave architecture, shared database architecture, and other types of distributed system) to distribute the structure and /or parts of the operation. The embodiments are not limited in this context.

In one embodiment, the radio interface 710 may include components suitable for transmitting and/or receiving single-carrier or multi-carrier modulated signals (including, for example, complementary code keying (CCK), orthogonal frequency division multiplexing (OFDM), and/or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols), but embodiments are not limited to any particular air interface or modulation scheme. Radio interface 710 may include, for example, a receiver 712 , a frequency synthesizer 714 , and/or a transmitter 716 . The radio interface 710 may include a bias control, a crystal oscillator, and/or one or more antennas 718-f. In another embodiment, the radio interface 710 may use external voltage controlled oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters, and/or RF filters as desired. Due to the variety of potential RF interface designs, an extensive description thereof is omitted.

Baseband circuitry 720 may be in communication with radio interface 710 to process receive and/or transmit signals, and may include, for example, mixers for downconverting received RF signals, analog-to-digital conversion for converting analog signals to digital form A converter 722, a digital-to-analog converter 724 for converting the digital signal to analog form, and a mixer for up-converting the signal for transmission. Additionally, baseband circuitry 720 may include baseband or PHY processing circuitry 726 for physical layer (PHY) link layer processing of corresponding receive/transmit signals. Baseband circuitry 720 may include, for example, Media Access Control (MAC) processing circuitry 727 for MAC/data link layer processing. Baseband circuitry 720 may include memory controller 732 for communicating with MAC processing circuitry 727 and/or computing platform 730 , eg, via one or more interfaces 734 .

In some embodiments, PHY processing circuitry 726 may include frame building and/or detection modules in combination with additional circuitry, such as buffer memory, to build or deconstruct communication frames. Alternatively or additionally, MAC processing circuitry 727 may share processing for some of these functions, or perform these processes independently of PHY processing circuitry 726 . In some embodiments, MAC and PHY processing may be integrated into a single circuit.

Computing platform 730 may provide computing functionality for device 700 . As shown, computing platform 730 may include a processing component 740 . In addition to or instead of baseband circuitry 720, device 700 may employ processing component 740 to perform processing operations on one or more of mobile device 102, base station 104, logic flow 200, storage medium 500, and mobile device 800 OR logic and logic circuit 728 . Processing component 740 (and/or PHY 726 and/or MAC 727) may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application-specific integrated circuits ( ASIC), programmable logic device (PLD), digital signal processor (DSP), field programmable gate array (FPGA), memory unit, logic gate, register, semiconductor device, chip, microchip, chipset, etc. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, A method, procedure, software interface, application programming interface (API), instruction set, computational code, computer code, code segment, computer code segment, word, value, symbol, or any combination thereof. Determining the use of hardware elements and/or software elements to implement an embodiment may vary depending on any number of factors, for example, desired computational rates, power levels, thermal tolerance, processing cycle budget, input data, as desired for a given implementation rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

Computing platform 730 may also include other platform components 750 . Other platform components 750 include common computing elements such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components (eg, digital displays), power supplies, etc. Examples of memory units may include, but are not limited to, various types of computer-readable and machine-readable storage media in the form of one or more higher-speed memory units, such as read-only memory (ROM), random-access memory ( RAM), Dynamic RAM (DRAM), Double Data Rate DRAM (DDRAM), Synchronous DRAM (SDRAM), Static RAM (SRAM), Programmable ROM (PROM), Erasable Programmable ROM (EPROM), Electrically Erasable In addition to programmable ROM (EEPROM), flash memory, polymer memory (for example, ferroelectric polymer memory, Ovonic memory, phase change or ferroelectric memory, silicon oxide nitrogen oxide silicon (SONOS) memory), magnetic Or optical cards, arrays of devices such as redundant array of independent disks (RAID) drives, solid state memory devices (eg USB memory, solid state drives (SSD)), and any other type of storage medium suitable for storing information.

Device 700 may be, for example, an ultra-mobile device, mobile device, stationary device, machine-to-machine (M2M) device, personal digital assistant (PDA), mobile computing device, smart phone, telephone, digital phone, cellular phone, user equipment, e-book Reader, cell phone, one-way pager, two-way pager, messaging device, computer, personal computer (PC), desktop computer, laptop computer, notebook computer, netbook computer, handheld computer, tablet computer, server, server array or server farm, web server, network server, internet server, workstation, minicomputer, mainframe computer, supercomputer, network device, web appliance, distributed computing system, multiprocessor system, processor-based system, consumer electronics, programmable consumer Electronics, gaming equipment, monitors, televisions, digital televisions, set-top boxes, wireless access points, base stations, Node Bs, subscriber stations, mobile subscriber centers, radio network controllers, routers, hubs, gateways, bridges, switches, machines, or its combination. Accordingly, functionality and/or specific configurations of device 700 described herein may be included or omitted in various embodiments of device 700 as suitably desired.

Embodiments of device 700 may be implemented using a single-input single-output (SISO) architecture. However, certain implementations may include multiple antennas (e.g., antenna 718) for transmitting and/or receiving using adaptive antenna techniques for beamforming or space division multiple access (SDMA) and/or using MIMO communication techniques. -f).

The components and features of device 700 may be implemented using any combination of discrete circuits, application specific integrated circuits (ASICs), logic gates, and/or a single chip architecture. Additionally, features of device 700 may be implemented using microcontrollers, programmable logic arrays, and/or microprocessors, or any combination of the foregoing, where appropriate. Note that hardware, firmware, and/or software elements may be referred to herein collectively or individually as "logic" or "circuitry."

It should be appreciated that the exemplary device 700 shown in the block diagram of FIG. 7 may represent one functionally descriptive example of many potential implementations. Accordingly, the division, omission, or inclusion of block functions depicted in the figures cannot infer that hardware components, circuits, software, and/or elements for implementing these functions will necessarily be divided, omitted, or included in the embodiments.

FIG. 8 shows an embodiment of a broadband wireless access system 800 . As shown in FIG. 8 , the broadband wireless access system 800 may be an Internet Protocol (IP) type network, including an Internet 810 type network capable of supporting mobile wireless access and/or fixed wireless access to the Internet 810 . In one or more embodiments, the broadband wireless access system 800 may include any type of Orthogonal Frequency Division Multiple Access (OFDMA) based or Single Carrier Frequency Division Multiple Access (SC-FDMA) based wireless network, for example, with One or more of the 3GPP LTE specifications and/or the IEEE 802.16 standard are compatible systems, and the scope of claimed subject matter is not limited in these respects.

In the exemplary broadband wireless access system 800, radio access networks (RAN) 812 and 818 can be coupled with evolved Node Bs or base stations (eNBs) 814 and 820, respectively, to provide one or more fixed devices 816 and the Internet 810 and/or wireless communication between one or more mobile devices 822 and the Internet 810. One example of a stationary device 816 comprising a stationary version of device 700 and a mobile device 822 comprising a mobile version of device 700 is device 700 of FIG. 7 . RANs 812 and 818 may implement profiles that define the mapping of network functions to one or more physical entities on broadband radio access system 800 . eNBs 814 and 820 may include radios to provide RF communications with fixed devices 816 and/or mobile devices 822 (such as described with reference to device 700), and may include PHYs and MACs compatible with, for example, 3GPP LTE specifications or IEEE 802.16 standards layer device. Base stations or eNBs 814 and 820 may also include IP backplanes to couple to Internet 810 via RANs 812 and 818, respectively, although the scope of claimed subject matter is not limited in these respects.

The broadband wireless access system 800 may also include a visiting core network (CN) 824 and/or a home CN 826, each of which may be capable of providing one or more network functions, including but not limited to proxy and/or relay type functions, For example, Authentication, Authorization, and Accounting (AAA) functions, Dynamic Host Configuration Protocol (DHCP) functions, or domain name service control, etc., domain gateways such as Public Switched Telephone Network (PSTN) gateways or Voice over Internet Protocol (VoIP) gateways , and/or Internet Protocol (IP) type server functions, etc. However, these are merely examples of the types of functionality that visiting CN 824 and/or home CN 826 can provide, and the scope of claimed subject matter is not limited in these respects. In cases where the visiting CN 824 is not part of the regular service provider for the fixed device 816 or mobile device 822 (e.g., where the fixed device 816 or mobile device 822 is moving away from its corresponding home CN 826), or in broadband wireless Where the access system 800 is part of a regular service provider for the fixed device 816 or mobile device 822, but the broadband wireless access system 800 may be in another location or state that is not the primary or home location for the fixed device 816 or mobile device 822 Hereinafter, visiting CN 824 may be referred to as visiting CN. The embodiments are not limited in this context.

The fixed device 816 may be located anywhere within range of one or both of the eNBs 814 and 820, for example, in or near a home or business, to provide Home or business customer bandwidth access to Internet 810 attributed to CN 826 . It is worth noting that although the fixture 816 is typically placed in a static location, it can be moved to a different location as desired. For example, mobile device 822 may be utilized at one or more locations if mobile device 822 is within range of one or both of base stations or eNBs 814 and 820 . According to one or more embodiments, an Operational Support System (OSS) 828 may be part of the broadband wireless access system 800 to provide management functions for the broadband wireless access system 800 and to provide communication between functional entities of the broadband wireless access system 800 Interface. Broadband wireless access system 800 of FIG. 8 is merely one type of wireless network illustrating a number of components of broadband wireless access system 800 and the scope of claimed subject matter is not limited in these respects.

Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), Digital Signal Processors (DSP), Field Programmable Gate Arrays (FPGA), Logic Gates, Registers, Semiconductor Devices, Chips, Microchips, Chipsets, etc. Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interface, application program interface (API), instruction set, computational code, computer code, code segment, computer code segment, word, value, symbol, or any combination thereof. Determining the use of hardware elements and/or software elements to implement an embodiment may vary depending on any number of factors, for example, desired computational rate, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed and other design or performance constraints.

One or more aspects of at least one embodiment can be implemented by representative instructions stored on a machine-readable medium representing various logic within a processor, which, when read by a machine, cause the machine to fabricate logic to perform the functions described herein. Technology. Such representations (referred to as "IP cores") may be stored on a tangible, machine-readable medium and provided to various customers or manufacturing facilities to be loaded into the manufacturing machines that actually manufacture the logic or processors. Some embodiments may be implemented, for example, using a machine-readable medium or article that can store instructions or a set of instructions that, if executed by a machine, cause the machine to perform methods and/or operations according to the embodiments. Such a machine may comprise, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware and/or software. A machine-readable medium or article may include, for example, any suitable type of storage unit, storage device, storage item, storage medium, storage device, storage item, storage medium, and/or storage unit, e.g., memory, removable or non-removable media, removable or non-removable media, writable or rewritable media, digital or analog media, hard disks, floppy disks, compact disc read-only memory (CD-ROM), compact disc-recordable (CD-R), Compact discs rewritable (CD-RW), optical discs, magnetic media, magneto-optical media, removable memory cards or discs, various types of digital versatile discs (DVD), magnetic tape, cassettes, and the like. Instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc.

The following examples relate to further examples:

Example 1 is a narrowband Internet of Things (NB-IoT) user equipment (UE) comprising a memory; and baseband circuitry coupled to the memory, the baseband circuitry configured to: decode an indication included in the received downlink information ; determining discontinuous time domain resource mapping for the narrowband physical downlink control channel (NPDCCH) and narrowband physical downlink shared channel (NPDSCH) based on the indication; and decoding the discontinuous time domain resource mapping for the NPDCCH and Available subframes for NPDSCH.

Example 2 is an extension of Example 1 or any other example disclosed herein, and the indication only corresponds to NB-IoT UE.

Example 3 is an extension of Example 1 or any other example disclosed herein, and the indication corresponds to a group of NB-IoT UEs.

Example 4 is an extension of example 3 or any other example disclosed herein, the group of NB-IoT UEs operate within the same cell.

Example 5 is an extension of Example 3 or any other example disclosed herein, the group of NB-IoT UEs operating within the same coverage class.

Example 6 is an extension of Example 1 or any other example disclosed herein, the discontinuous time domain resource mapping is used to specify the available subframes for NPDCCH.

Example 7 is an extension of Example 1 or any other example disclosed herein, the discontinuous time domain resource mapping is used to specify the available subframes for NPDSCH.

Example 8 is an extension of Example 1 or any other example disclosed herein, the discontinuous time-domain resource mapping is used to specify available subframes based on reference subframe indices.

Example 9 is an extension of Example 1, or any other example disclosed herein, that a discontinuous time-domain resource mapping is used to specify available subframes based on referencing an absolute radio frame.

Example 10 is an extension of Example 1 or any other example disclosed herein, and the indication is also used to indicate a flexible time interval between NPDCCH and NPDSCH.

Example 11 is an extension of Example 10 or any other example disclosed herein, the flexible time interval is used to specify the first frame of the NPDSCH relative to the last frame of the NPDCCH.

Example 12 is an extension of Example 11 or any other example disclosed herein, the value of k_PDSCH is used to indicate the flexible time interval.

Example 13 is an extension of Example 12 or any other example disclosed herein, k_PDSCH-1 is used to indicate the number of subframes away from the last subframe for scheduling NB-PDCCH.

Example 14 is an extension of Example 12 or any other example disclosed herein, the value of k_PDSCH includes an integer.

Example 15 is an extension of Example 12 or any other example disclosed herein, and the value of k_PDSCH includes an integer of 2 or more.

Example 16 is an extension of example 1 or any other example disclosed herein, the received downlink information includes dedicated radio resource control (RRC).

Example 17 is an extension of example 1 or any other example disclosed herein, the received downlink information includes downlink control information (DCI).

Example 18 is an extension of Example 1, or any other example disclosed herein, the apparatus comprising at least one radio frequency (RF) transceiver and at least one RF antenna.

Example 19 is a method of wireless communication, comprising: decoding an indication included in received downlink information; ) for discontinuous time domain resource mapping; and decoding available subframes for NPDCCH and NPDSCH based on the determined discontinuous time domain resource mapping.

Example 20 is an extension of Example 19 or any other example, the indication corresponds to only one NB-IoTUE.

Example 21 is an extension of Example 19 or any other example, and the indication corresponds to a group of NB-IoTUEs.

Example 22 is an extension of example 21 or any other example, the group of NB-IoT UEs operate within the same cell.

Example 23 is an extension of example 21 or any other example, the group of NB-IoT UEs operate within the same coverage class.

Example 24 is an extension of example 19 or any other example, the discontinuous time domain resource mapping specifies available subframes for NPDCCH.

Example 25 is an extension of example 19 or any other example, the discontinuous time domain resource mapping specifies available subframes for NPDSCH.

Example 26 is an extension of example 19 or any other example, the discontinuous time domain resource mapping specifies available subframes based on reference subframe indices.

Example 27 is an extension of example 19 or any other example, the discontinuous time domain resource mapping is based on specifying available subframes by reference to absolute radio frames.

Example 28 is an extension of example 19, or any other example, indicating that the flexible time interval between NPDCCH and NPDSCH is also indicated.

Example 29 is an extension of example 28 or any other example, the flexible time interval specifies the first frame of the NPDSCH relative to the last frame of the NPDCCH.

Example 30 is an extension of example 29 or any other example, the value of k_PDSCH indicates a flexible time interval.

Example 31 is an extension of Example 30 or any other example, k_PDSCH-1 indicates the number of subframes away from the last subframe where the NB-PDCCH is scheduled.

Example 32 is an extension of Example 30 or any other example, the value of k_PDSCH includes an integer.

Example 33 is an extension of Example 30 or any other example, the value of k_PDSCH includes an integer of 2 or more.

Example 34 is an extension of example 19, or any other example, the received downlink information includes dedicated radio resource control (RRC).

Example 35 is an extension of example 19, or any other example, the received downlink information includes downlink control information (DCI).

Example 36 is at least one computer-readable storage medium comprising a set of instructions responsive to being executed on a computing device, causing the computing device to perform wireless communication according to any of Examples 19-35 or any other example disclosed herein method.

Example 37 is a user equipment (UE) comprising means for performing the wireless communication method according to any of Examples 19 to 35 or any other example disclosed herein.

Example 38 is at least one computer-readable storage medium comprising a set of wireless communication instructions that, in response to being executed on a computing device, cause the computing device to: decode the indication; determining discontinuous time-domain resource mapping for the narrowband physical downlink control channel (NPDCCH) and narrowband physical downlink shared channel (NPDSCH) based on the indication; decoding for the NPDCCH and Available subframes for NPDSCH.

Example 39 is an extension of Example 38, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to determine a discontinuous time domain resource map to designate available subframes for the NPDCCH .

Example 40 is an extension of Example 38, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to determine a discontinuous time domain resource map to designate available subframes for the NPDSCH .

Example 41 is an extension of Example 38, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to determine a discrete time-domain resource map to specify based on the referenced subframe index Available subframes.

Example 42 is an extension of Example 38, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to determine a discrete time-domain resource map to specify based on reference to an absolute radio frame Available subframes.

Example 43 is an extension of Example 38, or any other example disclosed herein, comprising wireless communication instructions responsive to execution on the computing device, causing the computing device to determine a flexible time interval between the NPDCCH and the NPDSCH based on the indication.

Example 44 is an extension of Example 43, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to determine a flexible time interval to specify the NPDSCH relative to the last frame of the NPDCCH the first frame of .

Example 45 is an extension of Example 44, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to determine a value of k_PDSCH to indicate the flexible time interval.

Example 46 is an extension of Example 45, or any other example disclosed herein, that includes wireless communication instructions that, in response to being executed on the computing device, cause the computing device to determine k_PDSCH-1 to indicate the distance from the last subclass of the NB-PDCCH The number of subframes of the frame.

Example 47 is an extension of Example 45, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to decode a downlink received from a dedicated radio resource control (RRC). information.

Example 48 is an extension of Example 45, or any other example disclosed herein, comprising wireless communication instructions, responsive to execution on the computing device, causing the computing device to decode downlink received from downlink control information (DCI). road information.

Example 49 is a narrowband Internet of Things (NB-IoT) user equipment (UE) comprising memory; radio frequency (RF) circuitry for receiving downlink control; and baseband circuitry coupled to the memory and to To the RF circuit, the baseband circuit is used to: decode the indication included in the received downlink information, determine based on the indication which is different for the narrowband physical downlink control channel (NPDCCH) and the narrowband physical downlink shared channel (NPDSCH) Continuous time-domain resource mapping, and decoding available subframes for NPDCCH and NPDSCH based on the determined discontinuous time-domain resource mapping; the RF circuit is used for: receiving available subframes for NPDCCH and NPDSCH.

Example 50 is an extension of Example 49 or any other example disclosed herein, the indication is also used to indicate a flexible time interval between NPDCCH and NPDSCH.

Example 51 is an apparatus comprising a memory; and baseband circuitry coupled to the memory, the baseband circuitry configured to: determine a group of user equipment (UE) devices of the same coverage class; The discontinuous time domain resource mapping of channel control channel (NPDCCH) and narrowband physical downlink shared channel (NPDSCH); An indication of a subframe.

Example 52 is an extension of example 51, or any other example disclosed herein, the group of UE devices are configured to operate within the same cell.

Example 53 is an extension of Example 51 or any other example disclosed herein, the discontinuous time domain resource mapping is used to specify available subframes based on reference subframe indices.

Example 54 is an extension of Example 51, or any other example disclosed herein, that a discontinuous time domain resource mapping is used to specify available subframes based on referencing an absolute radio frame.

Example 55 is an extension of Example 51 or any other example disclosed herein, indicating that the flexible time interval between NPDCCH and NPDSCH is also indicated.

Example 56 is an extension of Example 55 or any other example disclosed herein, the flexible time interval is used to specify the first frame of the NPDSCH relative to the last frame of the NPDCCH.

Example 57 is an extension of Example 56 or any other example disclosed herein, the value of k_PDSCH is used to indicate the flexible time interval.

Example 58 is an extension of any of Examples 51-57, or any other example disclosed herein, to include at least one radio frequency (RF) transceiver and at least one RF antenna.

Example 59 is at least one computer-readable storage medium comprising a set of wireless communication instructions responsive to being executed on a computing device, causing the computing device to: determine a group of user equipment (UE) of the same coverage class equipment; determining discontinuous time domain resource mapping for the narrowband physical downlink control channel (NPDCCH) and narrowband physical downlink shared channel (NPDSCH) for the group of UE devices; and based on the determined discontinuous time domain resources for the determined group of UE devices mapping to encode the indication of available subframes for NPDCCH and NPDSCH.

Example 60 is an extension of example 59, or any other example disclosed herein, comprising a set of wireless communication instructions responsive to execution on the computing device, causing the computing device to determine that the set of UE devices are operating within the same cell.

Example 61 is an extension of Example 59, or any other example disclosed herein, comprising a set of wireless communication instructions responsive to being executed on the computing device, causing the computing device to determine a discrete time-domain resource map based on the referenced subframe Index to specify available subframes.

Example 62 is an extension of Example 59, or any other example disclosed herein, comprising a set of wireless communication instructions responsive to being executed on the computing device, causing the computing device to determine a discrete time-domain resource map based on reference absolute radio frame to specify available subframes.

Example 63 is an extension of Example 59, or any other example disclosed herein, comprising a set of wireless communication instructions responsive to execution on the computing device such that the computing device encodes an indication to further indicate flexibility between NPDCCH and NPDSCH time interval.

Example 64 is an extension of Example 63, or any other example disclosed herein, comprising a set of wireless communication instructions responsive to execution on the computing device such that the computing device encodes a flexible time interval to specify a last time relative to the NPDCCH The first frame of the NPDSCH frame.

Example 65 is an extension of Example 64, or any other example disclosed herein, comprising a set of wireless communication instructions responsive to execution on the computing device, causing the computing device to encode a value of k_PDSCH to indicate a flexible time interval.

Numerous specific details have been set forth herein to provide a thorough understanding of the embodiments. However, it will be understood by those skilled in the art that the embodiments may be practiced without these specific details. In other instances, well-known operations, components, and circuits have not been described in detail so as not to obscure the embodiments. It can be appreciated that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.

Some embodiments may be described using the expressions "coupled" and "connected," along with their derivatives. These terms are not intended as synonyms for each other. For example, some embodiments may be described using the terms "connected" and/or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

Unless expressly stated otherwise, it is understood that terms such as "process", "calculate", "estimate", "determine", etc. refer to the actions of a computer or computing system, or similar electronic computing device and/or or processing, the computer or computing system, or similar electronic computing device, manipulates and/or converts data of a physical quantity (e.g., electrons) within registers and/or memories denoted computing system into similarly denoted computing system memory, registers or other such information storage, transmission or display of other data in physical quantities within the device. The embodiments are not limited in this context.

It should be noted that the methods described herein do not have to be performed in the order described, or in any particular order. Furthermore, various activities described with respect to the methods identified herein may be performed in serial or parallel fashion.

Although specific embodiments have been shown and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiment shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. It will be understood that the foregoing description has been made in an illustrative manner and not in a restrictive manner. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. Accordingly, the scope of various embodiments includes any other applications in which the combinations, structures, and methods described above are used.

It is emphasized that the Abstract of the Disclosure is provided to comply with 37 C.F.R Part 1.72(b) requirement that the abstract will allow the reader to quickly ascertain the nature of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms "comprising" and "wherein" are used as the simplified English equivalents of the respective terms "comprising" and "wherein", respectively. Furthermore, the terms "first", "second", and "third", etc. are used only as labels and are not intended to impose numbering requirements on their objects.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (25)

1. a kind of device, including：

Memory；And

Baseband circuit, the baseband circuit are coupled to the memory, and the baseband circuit is used for：

Decoding is included in the instruction in the downlink information received；

It is determined for narrowband physical downlink control channel (NPDCCH) and narrowband physical down link based on the instruction The discontinuous time-domain resource mapping of shared channel (NPDSCH)；

And

It is mapped based on determining discontinuous time-domain resource to decode the subframe for the NPDCCH and the NPDSCH.

2. the apparatus according to claim 1, the instruction corresponds to one group of narrowband Internet of Things (NB-IoT) user equipment (UE) equipment.

3. the apparatus of claim 2, this group of NB-IoT UE equipment is operated in same cells.

4. device according to claim 2 or 3, this group of NB-IoT UE equipment is operated in identical covering classification.

5. the apparatus according to claim 1, the discontinuous time-domain resource mapping is specified for the available of the NPDCCH Subframe.

6. the apparatus according to claim 1, the discontinuous time-domain resource mapping is specified for the available of the NPDSCH Subframe.

7. device according to claim 5 or 6, the discontinuous time-domain resource mapping is specified based on reference subframe index Subframe can be used.

8. device according to claim 5 or 6, the discontinuous time-domain resource mapping based on quote Absolute Radio frame come Specified available subframe.

9. the apparatus according to claim 1, the instruction also indicates flexible between the NPDCCH and the NPDSCH Time interval.

10. device according to claim 9, the flexible time interval is for specified relative to the last of the NPDCCH The first frame of the NPDSCH of one frame.

11. the value of device according to claim 10, k_PDSCH is used to indicate the flexible time interval.

12. at least one computer readable storage medium, including one group of wireless communication instruction, one group of wireless communication instruction are rung Ying Yu is executed on the computing device so that the computing device executes following operation：

Decoding is included in the instruction in the downlink information received；

It is determined for narrowband physical downlink control channel (NPDCCH) and narrowband physical down link based on the instruction The discontinuous time-domain resource mapping of shared channel (NPDSCH)；

It is mapped based on determining discontinuous time-domain resource to decode the subframe for the NPDCCH and the NPDSCH.

13. at least one computer readable storage medium according to claim 12, including wireless communication instruction, the nothing Line communication instruction is in response to executing on said computing device so that the computing device determines that the discontinuous time-domain resource is reflected It penetrates with the specified available subframe for the NPDCCH.

14. at least one computer readable storage medium according to claim 12, including wireless communication instruction, the nothing Line communication instruction is in response to executing on said computing device so that the computing device determines that the discontinuous time-domain resource is reflected It penetrates with the specified available subframe for the NPDSCH.

15. at least one computer readable storage medium according to claim 13 or 14, including wireless communication instruction, institute Wireless communication instruction is stated in response to being executed on said computing device so that the computing device determines that the discontinuous time domain provides Source mapping come specified based on reference subframe index can be used subframe.

16. at least one computer readable storage medium according to claim 13 or 14, including wireless communication instruction, institute Wireless communication instruction is stated in response to being executed on said computing device so that the computing device determines that the discontinuous time domain provides Source mapping come specified based on reference Absolute Radio frame can be used subframe.

17. at least one computer readable storage medium according to claim 12, including wireless communication instruction, the nothing Line communication instruction is in response to executing on said computing device so that the computing device is determined based on described in the instruction Flexible time interval between NPDCCH and the NPDSCH.

18. at least one computer readable storage medium according to claim 17, including wireless communication instruction, the nothing Line communication instruction is in response to executing on said computing device so that the computing device determines the flexible time interval to refer to The first frame of the NPDSCH of the fixed last frame relative to the NPDCCH.

19. a kind of device, including：

Memory；And

Baseband circuit, the baseband circuit are coupled to the memory, and the baseband circuit is used for：

Determine one group of user equipment (UE) equipment of identical covering classification；

It is determined for this group of UE equipment and is directed to narrowband physical downlink control channel (NPDCCH) and narrowband physical down link The discontinuous time-domain resource mapping of shared channel (NPDSCH)；And

It is mapped based on determining discontinuous time-domain resource to encode for NPDCCH and NPDSCH for this group of determining UE equipment Available subframe instruction.

20. device according to claim 19, this group of UE equipment is operated in same cells.

21. the device according to claim 19 or 20, the instruction is additionally operable to indicate the NPDCCH and the NPDSCH Between flexible time interval.

22. device according to claim 21, the flexible time interval is for specifying relative to the NPDCCH most The first frame of the NPDSCH of a later frame.

23. at least one computer readable storage medium, including one group of wireless communication instruction, one group of wireless communication instruction are rung Ying Yu is executed on the computing device so that the computing device executes following operation：

Determine one group of user equipment (UE) equipment of identical covering classification；

It is determined for this group of UE equipment and is directed to narrowband physical downlink control channel (NPDCCH) and narrowband physical down link The discontinuous time-domain resource mapping of shared channel (NPDSCH)；

It is mapped based on determining discontinuous time-domain resource to encode for NPDCCH and NPDSCH for this group of determining UE equipment Available subframe instruction.

24. at least one computer readable storage medium according to claim 23, including wireless communication instruction, described one The instruction of group wireless communication is in response to executing on said computing device so that the instruction of computing device coding is with further Indicate the flexible time interval between the NPDCCH and the NPDCCH.

25. at least one computer readable storage medium according to claim 24, including wireless communication instruction, described one The instruction of group wireless communication is in response to executing on said computing device so that the computing device encodes the flexible time interval With the first frame of the NPDSCH of the specified last frame relative to the NPDCCH.