JP7079552B2 - Simultaneous deployment of narrowband carriers and wideband carriers - Google Patents

Description

Various embodiments include resources within the first spectrum between at least one access node and the first terminal of the wireless network on at least one narrowband carrier operating according to the first wireless access technique. Regarding communicating with. In particular, various embodiments are scenarios in which the first spectrum is at least partially located within a second spectrum in which communication between at least one access node and the second terminal is performed on a broadband carrier. Regarding.

Mobile communication over cellular networks is an integral part of modern life. An example of a cellular network is 3GPP (Third Generation Partnership Project) LTE (Long Term Evolution) technology. The conventional LTE technology uses a radio access technology (RAT) called E-UTRA (evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access). The E-UTRA RAT uses a bandwidth of 1.4 to 20 MHz.

Within the 3GPP framework, further RATs are being studied that aim to meet target criteria such as low cost, low complexity and low power consumption.

One RAT studied is machine-based communication (MTC). MTC is a variant of 3GPP LTE communication, using a reduced bandwidth of 1.4 MHz. The data rate is limited to a maximum of 1 MBps. See, for example, 3GPP Technical Report (TR) 36.888 V12.0.0 (2013-6). The MTC RAT may be based on the E-UTRA RAT.

A further RAT studied is the NB-IoT (Narrow Band Internet of Things). The development goal is a bandwidth of 180 kHz and a data rate of about 100 kbps. See 3GPP RP-151621 "New Work Item: NowBand IOT (NB-IOT)". As can be seen, NB-IoT uses narrowband carriers when compared to both LTE and MTC. NB-IoT RAT may be based on E-UTRA RAT.

Communication techniques for NB-IoT RAT face some limitations and drawbacks. For example, within the existing framework of NB-IoT, the data rate is fixed at a relatively low value. Moreover, the data rates are statically fixed and dynamic adaptation of the data rates is not possible or possible to a limited extent.

Therefore, advanced communication techniques related to NB-IoT RAT are required. In particular, there is a need for techniques to add flexibility regarding the data rate of communications relating to NB-IoT RAT.

This need is met by the characteristics of independent claims. Dependent claims define an embodiment.

According to various embodiments, methods are provided. This method involves communicating on multiple narrowband carriers. The communication takes place between at least one access node of the wireless network and a first terminal connected to the wireless network. The plurality of narrowband carriers include resources in the first spectrum. The plurality of narrowband carriers operate according to the first RAT. The first spectrum is at least partially located within the second spectrum. On the second spectrum, communication between at least one access node and the second terminal is performed on the broadband carrier. Broadband carriers include resources within the second spectrum.

The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT.

According to various embodiments, computer program products are provided. Computer program products include program code executed by at least one processor. By executing the program code, at least one processor executes the method. This method involves communicating on multiple narrowband carriers. The communication takes place between at least one access node of the wireless network and a first terminal connected to the wireless network. The plurality of narrowband carriers include resources in the first spectrum. The plurality of narrowband carriers operate according to the first RAT. The first spectrum is at least partially located within the second spectrum. On the second spectrum, communication between at least one access node and the second terminal is performed on the broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT.

According to various embodiments, methods are provided. This method involves communicating on at least one narrowband carrier. The communication takes place between at least one wireless access node and a first terminal connected to a wireless network. At least one narrowband carrier comprises resources in the first spectrum. At least one narrowband carrier operates according to the first RAT. The first spectrum is at least partially located within the second spectrum in which communication between the at least one access node and the second terminal is performed on the broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT. Both the first spectrum and the second spectrum include a shared spectrum.

According to various embodiments, computer program products are provided. Computer program products include program code executed by at least one processor. By executing the program code, at least one processor executes the method. This method involves communicating on at least one narrowband carrier. The communication takes place between at least one wireless access node and a first terminal connected to a wireless network. At least one narrowband carrier comprises resources in the first spectrum. At least one narrowband carrier operates according to the first RAT. The first spectrum is at least partially located within the second spectrum in which communication between the at least one access node and the second terminal is performed on the broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT. Both the first spectrum and the second spectrum include a shared spectrum.

According to various embodiments, access nodes for wireless networks are provided. The access node comprises an interface configured to send and receive wirelessly over a wireless link. The access node further comprises at least one processor configured to communicate with the terminal via an interface. The terminal is connected to a wireless network. The communication is performed on a plurality of narrow band carriers. The plurality of narrowband carriers include resources in the first spectrum and operate according to the first RAT. The first spectrum is at least partially located within the second spectrum in which communication between the at least one access node and the second terminal is performed on the broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT.

According to various embodiments, access nodes for wireless networks are provided. The access node comprises an interface configured to send and receive wirelessly over a wireless link. The access node comprises at least one processor configured to communicate with the terminal via an interface. The terminal is connected to a wireless network. The communication takes place on at least one narrowband carrier. At least one narrowband carrier comprises resources in the first spectrum. At least one narrowband carrier operates according to the first RAT. The first spectrum is at least partially located within the second spectrum. On the second spectrum, communication between at least one access node and the second terminal is performed on the broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT. Both the first spectrum and the second spectrum include a shared spectrum.

According to various embodiments, methods are provided. This method involves communicating on multiple narrowband carriers. The communication takes place between at least one access node of the wireless network and a first terminal connected to the wireless network. The plurality of narrowband carriers include resources in the first spectrum. The plurality of narrowband carriers operate according to the first RAT. The first spectrum is at least partially located within the second spectrum. The method further comprises communicating between the at least one access node and the second terminal on a broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT.

According to various embodiments, methods are provided. This method involves communicating on at least one narrowband carrier. The communication takes place between at least one access node of the wireless network and a first terminal connected to the wireless network. At least one narrowband carrier comprises resources in the first spectrum. At least one narrowband carrier operates according to the first RAT. The first spectrum is at least partially located within the second spectrum. The method further comprises communicating between the at least one access node and the second terminal on a broadband carrier. Broadband carriers include resources within the second spectrum. The broadband carrier operates according to the second RAT. The second RAT is different from the first RAT. Both the first spectrum and the second spectrum include a shared spectrum.

It should be appreciated that the features described above and the features described below may be used not only in each of the combinations shown, but also in other combinations or alone without departing from the scope of the invention.

It is a schematic diagram of the communication between the 1st access node and the 1st terminal which concerns on a 1st RAT, and the communication between a 2nd access node and a 2nd terminal which concerns on a 2nd RAT. The access node is configured to communicate with the first terminal according to the first RAT and with the second terminal according to the second RAT, the first RAT corresponds to NB-IoT, and the second RAT. Is a schematic diagram of a cellular network relating to the 3GPP LTE and NB-IoT frameworks of E-UTRA. FIG. 6 shows resources on a radio link schematically illustrating a scenario in which the first spectrum of a narrowband NB-IoT carrier is located within the second spectrum of a wideband LTE carrier. Various embodiments illustrating a scenario in which the first spectrum of a plurality of narrowband NB-IoT carriers is located within a second spectrum of a broadband LTE carrier and schematically an intraband discontinuous deployment scenario. It is a figure which shows the resource on the wireless link which concerns on. In various embodiments, the first spectrum of the plurality of narrowband NB-IoT carriers is schematically shown in the second spectrum of the wideband LTE carrier, and the in-band continuous deployment scenario is shown roughly. It is a figure which shows the resource on the said wireless link. A scenario in which the first spectrum of a plurality of narrowband NB-IoT carriers is partially arranged in the second spectrum of a wideband LTE carrier is shown schematically, and a discontinuous deployment scenario in which the in-band / protection band is mixed is shown. It is a figure which shows the resource on the wireless link which concerns on the various embodiments shown. It is a diagram schematically showing a bundled transmission set of messages communicated at subsequent transmission intervals, each of which contains data encoded according to a given redundancy version. It is a diagram schematically showing a message containing data encoded according to different redundant versions. It is a figure which shows the asymmetric distribution of the control message and the control signal among a plurality of narrow band NB-IoT carriers which relate to various embodiments. It is a figure which shows schematic the asymmetric transmission power of a plurality of narrow band NB-IoT carriers which concerns on various embodiments. The aggregation of messages communicated on a plurality of narrowband carriers in the media access layer of the communication protocol stack of the NB-IoT RAT in which the plurality of narrowband NB-IoT carriers according to the various embodiments are outlined. It is a figure which shows. Shown are resources on radio links according to various embodiments that illustrate scenarios in which both the first spectrum of at least one narrowband NB-IoT carrier and the second spectrum of a wideband LTE carrier comprise a shared spectrum. It is a figure. Various embodiments schematically illustrating a scenario in which the first spectrum of the at least one narrowband NB-IoT carrier, the second spectrum of the wideband LTE carrier, and the third spectrum of the wideband MTC carrier all include a shared spectrum. It is a figure which shows the resource on the wireless link which concerns on. It is a schematic diagram of the terminal which concerns on various embodiments. It is a schematic diagram of the access node which concerns on various embodiments. It is a flowchart of the method which concerns on various embodiments.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be understood that the following description of the embodiments shall not be construed in a limited sense. The scope of the invention is not limited to the drawings merely exemplary or the embodiments described below.

Drawings are considered schematic and the elements shown in the drawings are not necessarily shown to scale. Rather, the various elements are manifested to those skilled in the art in their function and general purpose. Any connection or connection between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be by indirect connection or connection. Can be implemented. Coupling between the components may be established via a wireless connection.

Functional blocks can be implemented in hardware, firmware, software, or a combination thereof.

In the following, on the one hand, the communication on at least one narrowband carrier that contains the resources in the first spectrum and operates according to the first RAT, and on the other hand, the resources in the second spectrum that contain the resources in the second spectrum and the second RAT. Techniques for simultaneous deployment of communications on wideband carriers that operate according to are disclosed.

Simultaneous deployment can refer to allowing communication via first and second RATs at least in overlapping geographic areas where interference between narrowband and wideband carriers exists. Simultaneous deployment can include controlled interference mitigation to avoid interference between communications on the first and second RATs. Therefore, simultaneous deployment may correspond to communicating via the first and second RATs in a coordinated manner. For example, centralized adjustment may be applied, at least during rollouts. For example, simultaneous deployment may accommodate one or more network operators coordinating the deployment of first and second RATs.

The RAT may correspond to a physical connection technique for communicating over a wireless link. Therefore, the RAT may specify a set of rules that allow communication over the wireless link. RAT is a modulation and coding scheme (MCS) such as frequency band bandwidth of the spectrum associated with the carrier of RAT, duration of transmission time interval (TTI), eg turbocode, convolution coding, interleaving, etc. Elements selected from groups may be specified that include modulation such as orthogonal frequency division multiplexing (OFDM), binary phase shift keying (BPSK), Gaussian minimum shift keying (GMSK). Different RATs can be different with respect to at least one such rule.

The RAT can be implemented on the carrier. The carrier specifies a particular set of resources that can implement communication for a given RAT. Thus, each carrier may include one spectrum and implement one or more logical channels for communication on the spectrum. Carriers that include a spectrum with one or more frequency bands with a relatively large total bandwidth are typically referred to as wideband carriers, which are typically referred to as narrowband carriers, which are relatively small total bands. This is in contrast to carriers that contain spectra with one or more frequency bands of width. Here, narrowband carriers and wideband carriers can be defined relative to each other in a simultaneous deployment scenario.

Both the first and second spectra of the narrowband carrier and the wideband carrier may both include one or more frequency bands. The frequency bands of the spectrum do not need to be arranged continuously. In some examples, the first and second spectra may not overlap, i.e., there may be no shared spectrum contained by both the first and second spectra. In a further example, the first and second spectra include a shared spectrum, which can define overlap in the frequency domain.

In particular, the following discloses techniques for narrowband carrier in-band scenarios for wideband carriers. The in-band arrangement may correspond to the first spectrum being at least partially located within the second spectrum. For example, in an in-band deployment scenario, one or more frequency bands in the first spectrum may be placed adjacent to one or more frequency bands in the second spectrum, eg, without guard bands. ..

In this context, the following discloses examples that allow flexible adjustment of resource allocation to at least one narrowband carrier and wideband carrier, respectively. For example, in a scenario where communication on at least one narrowband carrier requires a higher data rate, additional resources may be allocated to at least one narrowband carrier, here for at least one narrowband carrier. Additional resources may be removed from the bandwidth carrier.

In the first example, communication on a plurality of narrow band carriers can be implemented. Communication on multiple narrowband carriers may be implemented by narrowband carrier aggregation (CA) in some scenarios. For each of the plurality of narrowband carriers, the CA implements a separated or largely separated lower end of the physical layer of each communication protocol stack of the first RAT to provide the communication protocol stack, eg, the media access layer. Alternatively, it may correspond to bonding to a certain point above the physical layer at the lower end, such as a sublayer above the physical layer. CA corresponds to communicating with a single terminal via multiple carriers. By using a plurality of narrowband carriers, the amount of resources available in the first spectrum can be increased, thereby increasing the data rate for communication with respect to the first RAT.

In the second example, both the first spectrum of the first RAT in which at least one narrowband carrier operates accordingly and the second spectrum of the second RAT in which the wideband carrier operates accordingly are shared spectra. including. Resources within the shared spectrum can be flexibly allocated to either at least one narrowband carrier or wideband carrier, depending on, for example, the required data rate, traffic throughput, etc. of at least one narrowband carrier. Therefore, centralized scheduling across the first and second RATs can be implemented. For example, the scheduling scheme may allocate resources within a shared spectrum in a time division multiplexing (TDM) scheme between at least one narrowband carrier and a wideband carrier.

The various examples disclosed herein can be found to be specific applications of NB-IoT co-deployment scenarios for LTE and / or MTC. In particular, a single carrier of NB-IoT is typically associated with a bandwidth of, for example, 180 kHz, whereas a single carrier of LTE has a bandwidth in the range of 1.4 MHz to 20 MHz. Also, a single carrier of the MTC has a bandwidth of, for example, 1.4 MHz. Therefore, the NB-IoT carrier implements a narrow band carrier (narrow band NB-IoT carrier) with respect to the wide band carrier mounted by the LTE carrier (broad band LTE carrier) and / or the MTC carrier (broad band MTC carrier). Can be done.

Thus, although various scenarios are described in the context of at least one narrowband NB-IoT carrier and wideband LTE or wideband MTC carrier, the techniques disclosed herein are other types of wideband carriers and / or narrow. It can be easily applied to band carriers. For example, for broadband carriers, similar techniques are used for GSM (Global Systems for Mobile Communications), WCDMA (Wideband Code Division Multiplex), GPRS (General Packet Radio Service), EDGE (Enhanced Data Rates for GSM Evolution), and EGPRS (Enhanced). It can be easily applied to various types of 3GPP designated RATs such as GPRS), UMTS (Universal Mobile Telecommunications System), and HSPA (High Speed Packet Access), as well as the corresponding architectures of related cellular networks. For example, for narrowband carriers, similar techniques can be readily applied to various types of other RATs such as LTE-M (LTE-Machine to Machine).

FIG. 1 schematically illustrates an aspect of a simultaneous deployment scenario of NB-IoT LAT191 and E-UTRA LAT192 relating to LTE technology. In the example of FIG. 1, the first access node 112-1 is the first terminal 130-1 on the narrow band NB-IoT carrier mounted on the wireless link 101 (indicated as a user device and UE in FIG. 1). Communicate with. The narrowband NB-IoT carrier operates according to the NB-IoT RAT. The second access node 112-2 communicates with the second terminal 130-2 on the broadband LTE carrier mounted on the wireless link 101. Broadband LTE carriers operate according to the E-UTRA RAT.

In the example of FIG. 1, the first terminal 130-1 and the second terminal 130-2 are located in a given geographical area, and therefore, in principle, communication on the narrowband NB-IoT carrier is wideband LTE. It may interfere with communication on the carrier. Therefore, in the example of FIG. 1, control signaling is implemented to facilitate interference mitigation between the first access node 112-1 and the second access node 112-2. In some examples, the first access node 112-1 and the second access node 112-2 may be co-located and implemented by a single access node. .. Such a scenario is shown in FIG.

FIG. 2 shows the architecture of a cellular network 100 according to some exemplary implementations. In particular, the cellular network 100 according to the example of FIG. 2 implements a 3GPP LTE architecture, sometimes referred to as an advanced packet system (EPS). EPS has been extended to support NB-IoT.

The second terminal 130-2 is connected to the access node 112 of the cellular network 100 via the wireless link 101. The access node 112 and the terminal 130-2 implement the E-UTRA RAT, and therefore the access point node 112 is an eNB 112. For example, the second terminal 130-2 may be selected from a group including smartphones, mobile phones, tables, notebooks, computers, smart TVs and the like.

The first terminal 130-1 is connected to the eNB 112 via the wireless link 101. However, the first terminals 130-1 and eNB 112 communicate according to the NB-IoT RAT. For example, the first terminal 130-1 may be an IoT device.

IoT devices are typically devices that have lower demands on data traffic and less latency requirements than, for example, LTE or MTC devices. In addition, communications using IoT devices should achieve low complexity and low cost. In particular, radio frequency (RF) modems should have low complexity. In addition, the energy consumption of IoT devices should be relatively low to allow battery-powered devices to function over a relatively long duration. Battery life should be long enough to provide communication capabilities, for example up to 10 years.

The eNB 112 is connected to a gateway node implemented by the serving gateway (SGW) 117. The SGW 117 can route and transfer payload data and act as a mobility anchor during handover of terminals 130-1 and 130-2.

The SGW 117 is connected to a gateway node implemented by the Packet Data Network Gateway (PGW) 118. The PGW 118 serves as an exit point and an entry point for the cellular network 110 for data destined for the packet data network (PDN, not shown in FIG. 2), for which the PGW 118 serves as an access point node 121 for the packet data network. Connected to. The access point node 121 is uniquely identified by an access point name (APN). The APN is used by terminals 130-1 and 130-2 to seek access to the packet data network.

The PGW 118 can be an endpoint for an end-to-end connection (not shown in FIG. 2) for packetized payload data of terminals 130-1 and 130-2. End-to-end connections can be used to communicate data for a particular service. Different services may use different end-to-end connections, or at least partially share an end-to-end connection. The end-to-end connection can be implemented by one or more bearers used to communicate service-specific data. An EPS bearer characterized by a set of quality of service parameters, indicated by a QoS class identifier (QCI).

FIG. 3 shows a mode of communication on the wireless link 101 in the simultaneous deployment scenario according to the reference implementation. FIG. 3 shows the distribution of resources 308 between the wideband LTE carrier 312 and the narrowband NB-IoT carrier 311. FIG. 3 shows a time frequency resource grid.

In FIG. 3, the specific resource 308 is highlighted and is a downlink (DL) for communication of a DL payload message including a data packet 350 between the eNB 112 and the terminal 130-1 according to the NB-IoT RAT191. Identified by scheduling allocation (following the same graphical notation in the figure below).

In the example of FIG. 3, each of the resources 308 carries a data packet 350 encoded according to a given redundant version, and in the example of FIG. 3, the data packet 350 is repeatedly transmitted. In another example, it is possible, for example, for each HARQ retransmission that only a single iteration of the data packet 350 be transmitted.

Although FIG. 3 illustrates DL communication of data packet 350, each technique can also be readily applied to uplink (UL) scheduling grants. Here, a particular resource 308 is identified for UL communication.

Each resource 308 can specify, for example, a time frequency resource block capable of communicating a certain number of bits on the wireless link 101. Depending on the MCS, the number of bits per resource 308 can vary. Resource 308 has a well-defined duration in the time domain (vertical axis in FIG. 3). The duration of resource 308 corresponds to the duration of TTI, sometimes referred to as subframe 309. During a given duration, a certain number of symbols may subsequently be communicated. Similarly, resource 308 has a well-defined width in the frequency domain (horizontal axis of FIG. 3). For example, the width can be 180 kHz. Typically, each resource 308 contains a plurality of subcarriers whose symbols are quadrature modulated.

As can be seen, the broadband LTE carrier 312 includes the resource 308 in the second spectrum 302. The second spectrum 302 includes two discontinuously arranged frequency bands. Within the range of the second spectrum 302, the resource 308 of the first spectrum 301 of the narrowband NB-IoT carrier 311 is arranged. The first spectrum 301 includes only a single frequency band in the example of FIG. For example, the single frequency band of the first spectrum 301 may have a bandwidth of 180 kHz, which may correspond to the frequency width of a single resource 308. The single frequency band of the first spectrum 301 is arranged adjacent to the two frequency bands of the second spectrum 302.

The first and second spectra 301 and 302 in the example of FIG. 3 do not overlap in the frequency domain, so that between communicating on the narrowband NB-IoT carrier 311 and communicating on the wideband LTE carrier 312. Interference is mitigated.

Both the narrowband NB-IoT carrier 311 and the wideband LTE carrier 312 may implement, for example, one or more payload channels for communicating payload messages carrying data packets containing user data in the upper layers of an application. .. In particular, the payload channel may facilitate UL and DL communications. For example, in the case of the broadband LTE carrier 312, the DL payload channel is sometimes referred to as the physical downlink shared channel (PDSCH). For example, in the case of the broadband LTE carrier 312, the UL payload channel is sometimes referred to as the physical uplink shared channel (PUSCH). Similar notations may be used in some scenarios for the narrowband NB-IoT carrier 311.

Both the narrowband NB-IoT carrier 311 and the wideband LTE carrier 312 may implement one or more control channels for communicating control messages carrying control information for configuring communication according to their respective RAT191,192. .. For example, in the case of the broadband LTE carrier 312, the particular DL control channel is a physical downlink control channel (PDCCH) used for communication such as scheduling control messages, power control messages, radio resource control (RRC) control signaling and the like. Further examples of control channels are PCFICH (Physical Control Format Indicator Channel), PHICH (Physical Hybrid-) for communicating acknowledgment messages of the Automatic Repeat Request (ARQ) protocol, which protects the communication of data by controlling retransmissions. There are ARQ Indicator Channel) and PBCH (Physical Broadcast Channel). The PBCH can carry system information for terminals requesting access to the network. System information may include a master information block (MIB) control message or a system information block (SIB) control message. Control channels similar to those disclosed above for the wideband LTE carrier 312 may also be implemented for the narrowband NB-IOT carrier 311.

In the example of FIG. 3, the bandwidth of the frequency band of the first spectrum 301 available for communication of the message relating to the NB-IoT RAT191 on the narrowband NB-IoT carrier 311 is limited to 180 kHz. Therefore, the data rate is also limited.

Further, in the example of FIG. 3, the communication latency is relatively long. This is because four subsequent subframes 309 are required to communicate the data packet 350. Specifically, according to the reference implementation as shown in FIG. 3, a certain number of iterative transmissions of the same redundant version of encoded data (in the example of FIG. 3, four transmissions of the same redundant version are the communications of the data packet 350. Used for). Therefore, each redundant version of the coded data in the ARQ protocol is repeated a certain number of times. Here, message iterations that carry the same redundant version are typically implemented by a bundled transmission set 351 of messages communicated in successive / subsequent subframes 309 of channels implemented on the wireless link. For example, 3GPP Technical Report (TR) 45.820 V13.0.0 (2015-08), Section 6.2.1.3 or 3GPP TR 36.888 V12.0.0 (2013). Please refer to -6). By using the bundled transmission set 351 it is possible to increase the probability of successful transmission even in a scenario where the conditions for communicating on the wireless link are poor. Thereby, even in the case of the low transmission power assumed within the MTC and NB-IoT domains, the coverage of the cellular network can be significantly enhanced. This is sometimes referred to as coverage enhancement (CE).

In the following, various techniques that allow flexible adjustment of the total bandwidth available for communication according to NB-IoT RAT191 are disclosed, thereby flexibly adjusting the data rate of communication according to NB-IoT RAT191. It can be possible to reduce transmission latency as an alternative or addition, eg, by coordinating the transmission of the same redundant version of the data.

The techniques disclosed below show that the complexity of the limited RF modems of terminals 130-1 that implement IoT devices is typically due solely to the radio bandwidth and peak data rates utilized, or primarily to them. Motivated by knowing that it is not determined by. In particular, some other parameters, such as the RF subsystem or the analog front end of the RF modem, define size and cost, and thus complexity. As a result, some RF modem vendors may reuse hardware component designs for both MTC and NB-IoT RF modems, for example to benefit from economies of scale. Thus, an NB-IoT RF modem can be hardware that supports a single narrowband NB-IoT carrier (see FIG. 3) and is capable of utilizing bandwidths and data rates greater than, for example, 180 kHz. This encourages an increase in the bandwidth available for communication according to the NB-IoT RAT191, as hardware capabilities may support such an increase in bandwidth.

FIG. 4 is a first example of the distribution of resources 308 using a larger total bandwidth for communications according to NB-IoT RAT191. From the comparison of FIGS. 3 and 4, it can be seen that the communication according to the NB-IoT RAT191 of the example of FIG. 4 uses a plurality of narrowband NB-IoT carriers 311-1 and 311-2. In the example of FIG. 4, the two narrowband NB-IoT carriers 311-1 and 311-2 are arranged in an in-band discontinuous deployment scenario. The total bandwidth of the frequency band of the first spectrum 301 is doubled. Thereby, the total data rate can also be increased.

FIG. 5 is a second example of the distribution of resources 308 using a larger total bandwidth for communications according to NB-IoT RAT191. From the comparison of FIGS. 3 and 5, it can be seen that the communication according to the NB-IoT RAT191 of the example of FIG. 5 uses a plurality of narrowband NB-IoT carriers 311-1, 311-2, 311-3. In the example of FIG. 5, the three narrowband NB-IoT carriers 311-1, 311-2, 311-3 are arranged in an in-band continuous deployment scenario. The total bandwidth of the frequency band of the first spectrum 301 is tripled. Thereby, the total data rate can also be increased.

FIG. 6 is a third example of the distribution of resources 308 using a larger total bandwidth for communications according to NB-IoT RAT191. From the comparison of FIGS. 3 and 6, it can be seen that the communication according to the NB-IoT RAT191 of the example of FIG. 6 uses a plurality of NB-IoT carriers 311-1 and 311-2. In the example of FIG. 6, the two narrowband NB-IoT carriers 311-1 and 311-2 are arranged in a discontinuous deployment scenario in which the in-band / protection band is mixed. The total bandwidth of the frequency band of the first spectrum 301 is doubled. Thereby, the total data rate can also be increased.

In the scenarios of FIGS. 4-6, the total bandwidth of the NB-IoT RAT191 is increased as compared to the reference implementation of FIG. Therefore, the capabilities of the terminal 130-1 communicating with the extended bandwidth of the additional narrowband NB-IoT carriers 311-1, 311-2, 311-3, such as the hardware and / or software capabilities, are ensured. May be desirable. Therefore, the capability control message can be communicated on the control channel of the narrow band NB-IoT carrier 311-1, 311-2, 311-3, and the capability control message is the first terminal 130-1. Includes an indicator indicating the capabilities of communication in the first spectrum 301 of.

Therefore, in the scenario according to FIGS. 4-6, a plurality of narrowband carriers 311-1, 311-2, 311-3 are used, and the first spectrum 301 is at least a portion within the range of the second spectrum 302. Is arranged. For example, referring to FIG. 6, the in-band frequency band of the first spectrum 301 is adjacent to the frequency band of the second spectrum 302, and the protected band frequency band of the first spectrum 301 is that of the second spectrum 302. Not adjacent to the frequency band.

4 to 6 disclose examples in which two or three NB-IoT carriers, 311-1, 311-2, 311-3 are used, but in other examples, a larger number. NB-IoT carriers such as 4, 5, 5 and up to 10 NB-IoT carriers can be used. The specific time-frequency allocation schemes of FIGS. 4-6 are provided for illustration purposes only. The examples shown in FIGS. 4 to 6 can be combined with each other.

FIG. 6A shows an aspect of the bundling policy. The bundling policy corresponds to communicating a message containing data encoded according to a given redundant version as a bundled transmission set 351. These techniques can be used for UL and DL. The bundling policy specifies how the same data packet encoded according to a given redundant version is communicated using multiple iterations. Applying a bundling policy is optional. Although various examples to which bundling policies apply are disclosed, bundling policies are not closely related to the techniques disclosed herein and are not closely related to different narrowband NBs, such as CA scenarios. -The techniques that use communication on IoT carriers are not closely related. For example, within each HARQ retransmission, only a single iteration of a given redundant version 371-373 can be communicated.

FIG. 6A shows a payload message communicated over the payload channel under a bundling policy. The payload message includes a data packet 350 encoded according to the first redundant version 371 (indicated as RV0 in FIG. 6A). As can be seen from FIG. 6A, the messages are communicated continuously in subsequent subframes 309, thereby implementing the bundled transmission set 351. For example, the bundled transmit set 351 may contain a number of payload messages greater than 20, greater than 50, or greater than 100, all carrying redundant iterations of the data packet 350.

Subsequent subframes 309 carrying the data packet 350 are distributed across different narrowband NB-IoT carriers 311-1 and 311-2. In some examples, the temporal arrangement and / or number of subframes 309 of the bundled transmit set 351 may be symmetrically distributed across different narrowband NB-IoT carriers 311-1 and 311-2. (As shown in FIG. 6A). In a further example, the temporal arrangement and / or number of subframes 309 of the bundled transmit set 351 is asymmetrically distributed across different narrowband NB-IoT carriers 311-1, 311-2, 311-3. It may be (not shown in FIG. 6A).

The specific time frequency arrangement of the message shown in FIG. 6A is only an example. Other examples are possible.

Although FIG. 6A shows a scenario in which a payload message is communicated, similar techniques can be readily applied to other types and types of messages, such as control messages.

FIG. 6B shows an embodiment of encoding the data packet 350 according to different redundant versions 371-373. As can be seen from FIG. 6B, the data packet 350 includes a series of bits. For example, the data packet 350 can be at least part of a MAC layer service data unit (SDU). The data packet 350 can also correspond to RRC commands or other control data such as ACK, NACK, UL authorization, or DL allocation.

Encoding the data packet 350 may correspond to adding a checksum 412 to the data packet 350. Various coding techniques can be used, such as Reed-Solomon coding, turbo convolutional coding, and convolutional coding. The provision of a checksum 412 can facilitate the reconstruction of corrupted bits in the corresponding message according to the coding scheme. Typically, the longer (shorter) the checksum 412, the stronger (less) the communication of the corresponding message for noise and channel imperfections, and thus the successful reception of the data packet 350. The probability can be adjusted by the length of the checksum. Encoding the data, as an alternative or addition, may correspond to applying an interleave in which the bits of the data packet 350 are shuffled (not shown in FIG. 6B).

Typically, the different redundant versions 371-373 correspond to checksums 412 of different lengths (as illustrated in FIG. 6B). In another example, the different redundant versions 371-373 can also use checksums 412 of the same length, but encoded according to different coding schemes. As an alternative or addition, different redundant versions may use different interleaving schemes.

In the following, exemplary implementations are given to build different redundant versions.

Step 1: Build a Different Redundant Version 1: A block of information bits, i.e., a data packet 350 to be transmitted, is encoded. Here, additional redundant bits are generated, i.e., in addition to the data packet 350. Assuming that N is the number of information bits, for example, in the case of E-UTRA RAT, the total number of encoded bits (that is, the total of information bits and redundant bits) can reach 3N. A decoder that receives all 3N bits can typically decode the information bits even if there are a large number of bit errors in the received bits due to the high BER.

Step 2: Build a Different Redundant Version: Therefore, only a portion of the redundant bits is selected to avoid excessive transmission overhead. The information bits and the selected redundant bits form the first redundant version 371. Therefore, the amount of coding bits for the first redundant version is 371, somewhere between N and 3N using the above example. The process of removing redundant bits by selecting a portion is sometimes referred to as puncturing. This first redundant version 371 may then be transmitted to the receiver.

Step 3: Build Different Redundant Versions: If retransmissions are requested according to the HARQ protocol, new redundant versions 372,373 are transmitted. Higher-order redundant versions 372, 373 include additional redundant bits from those pre-punctured in step 2, typically again containing the same information bits. In this way, after several iterations, the entire 3N bit is transmitted at least once.

It is possible to implement a bundled transmission set 351 using redundant transmissions or iterations of messages containing data encoded according to given redundant versions 371-373 for payload messages and control messages.

If the receiver receives multiple iterations of the data packet 350, decoding can be based on a combination of received signals from the multiple iterations. Thereby, the possibility of successful decryption can be increased. Instead of boosting the transmit power to facilitate successful transmission, or in addition, it can be implemented to implement multiple iterations.

From the comparison between FIGS. 4 to 6 and FIG. 3, it can be seen that the duration of the bundled transmission set 351 for communicating a given data packet can be significantly reduced. Therefore, the latency can be shortened. This is achieved by communicating the same redundant version of the data packet 350 on different narrowband NB-IoT carriers 311-1, 311-2, 311-3. That is, the first message containing the data packet 350 encoded according to the given redundant versions 371-373 is communicated on the first narrowband NB-IoT carrier 311-1, 311-2, 311-3. , The second message containing the data packet 350 encoded according to the same given redundant version 371-373 is different from the first narrowband NB-IoT carrier 311-1, 311-2, 311-3. It is possible to communicate on the narrow band NB-IoT carrier 311-1, 311-2, 311-3 of 2. That is, the first plurality of iterations of the data packet 350 encoded according to a given redundant version 371, 372, 373 are communicated on the primary carrier 311-1 and the same given redundant version 371, 372. , A second plurality of iterations of the data packet encoded according to 373 can be communicated on the secondary carrier 311-2.

For example, even if the first and second iterations of the data packet 350 encoded according to the same given redundant versions 371, 372, 373 are at least partially communicated in overlapping TTIs, such as subframe 309. good. The first and second iterations may be communicated at least partially in parallel.

For example, the number of first plurality of iterations may be equal to the number of second plurality of iterations. Also, an asymmetry between the number of first plurality of iterations and the number of second plurality of iterations can be implemented.

In the example of FIGS. 4-6, the various redundant versions of the data packet 350 are different narrowband NB-IoT carriers 311-1, 311 as part of the bundled transmit set 351 for example in subsequent subframes 309. It is communicated via -2, 311-3. In another example, multiple iterations of the data packet 350 encoded according to the same given redundant versions 371-373 may be communicated in discontinuously arranged subframes 309.

In the examples of FIGS. 4-6, 6A, 6B, the increase in available data rates has already been made by increasing the total bandwidth of the first spectrum 301 available for communication according to NB-IoT RAT191. Can be achieved. Below are further disclosure scenarios that allow for even greater data rates available. Further scenarios can further increase the available data rate, which simplifies the implementation and reduces the control signaling overhead for a given available total bandwidth of the first spectrum 301. Can be achieved. Further scenarios are based on at least one asymmetric distribution of control messages and control signals and transmit power among multiple narrowband carriers 311-1, 311-2, 311-3.

FIG. 7 shows an embodiment in which control messages and control signals are asymmetrically distributed among a plurality of narrowband carriers 311-1, 311-2, and 311-3. Referring to FIG. 7, for an example relying on three narrowband carriers 311-1, 311-2, 311-3, the concept of asymmetrically distributing control messages and control signaling is shown, but each concept is , Can be easily applied for any number of narrowband carriers.

In the example of FIG. 7, the primary carrier 311-1 is defined, and two secondary carriers 311-2 and 311-3 are further defined. The primary carrier 311-1 may host control functions with respect to the secondary carriers 311-2 and 311-3.

Specifically, the control messages and signals are asymmetrically distributed between the primary carriers 311-1 on the one hand and the secondary carriers 311-2 and 311-3 on the other. In particular, in the asymmetric distribution, the control signaling overhead is transferred from the secondary carriers 311-2, 311-3 to the primary carriers 311-1, with the secondary carriers 311-2 and 311-3 controlling messages and /. Or do not include control signals, or include a smaller number of control messages and / or control signals. In this regard, the control messages and control signals communicated on the primary channel 311-1 may include information targeting the secondary carriers 311-2 and 311-3. For this reason, the secondary carriers 311-2 and 311-3 can provide more resources for the payload channel (not shown in FIG. 7) and may be referred to as a "clean channel". Since the overhead can be reduced, the overall data rate of the communication according to the NB-IoT RAT191 can be further increased.

Specifically, as shown in FIG. 7, the primary carrier 311-1 includes the control channel 403 and the secondary carriers 311-2 and 311-3 do not include the control channel 403. For example, the control channel 403 according to the NB-IoT RAT191 may correspond to the PDCCH or PUCCH or PHICH (all not shown in FIG. 2) according to the E-UTRA RAT192. The control channel 403 can include control messages associated with communication on both the primary carrier 311-1 and the secondary carriers 311-2 and 311-3. For example, the control message communicated on the control channel 403 identifies the DL scheduling allocation that identifies the resource 308 in the first spectrum 301 in DL communication, the resource 308 in the first spectrum 301 in UL communication. ARQ acknowledgment message, such as a positive response message or a negative response message, of a payload message communicated on one of the payload channels of the UL scheduling permission, primary carrier 311-1 or secondary carrier 311-2, 311-3. And may be selected from a group containing RRC control messages. The control channel 403 may be a unicast channel, i.e., specifically targeted at terminal 130-1.

Further, as shown in FIG. 7, the primary carrier 311-1 includes a broadcast control channel 401 that does not target a specific terminal, and the secondary carriers 311-2 and 311-3 do not include a broadcast control channel 401. .. For example, the broadcast control channel 401 of the NB-IoT RAT191 may correspond to the PBCH of the E-UTRA RAT192 (not shown in FIG. 2). The broadcast control channel 401 can include control messages associated with communication on both the primary carrier 311-1 and the secondary carriers 311-2 and 311-3. For example, the control message communicated on the broadcast control channel 401 may correspond to a carrier access system information control message for accessing the cellular network 100 via the NB-IoT RAT191. Such control messages may correspond to an E-UTRA RAT MIB or SIB. Illustrative information includes frame numbering, carrier-specific information, and scheduling allocation for random access.

As described above for control channels 401, 403, the information contained in a given control message communicated on control channels 401, 403 on primary carriers 311-1 is secondary carriers 311-2, 311-3. It is possible to target one of them. That is, a given control message may be associated with communicating on a plurality of narrowband NB-IoT carriers 311-1, 311-2, 311-1 primary carriers 311-1 and / or. It may be associated with communication with one or more of the secondary carriers 311-2 and 311-3. Each indicator can be used to facilitate identification of the particular carrier 311-1, 311-2, 311-3 to which a given control message communicated on control channels 401, 403 is directed. .. On the receiver side, this identification can be used for processing information. For example, the control message may include an indicator indicating one of the primary carriers 311-1 or the secondary carriers 311-2, 311-3. These can be explicit or implied indicators. For example, a number of 3 bits may be used. For example, if the control message corresponds to the E-UTRA RAT192 MIB, 3GPP Technical Specialization (TS) 36.331 Rel. 12, The reserved bit according to Section 6.2.2 can be used to indicate one of the primary carrier 311-1 or the secondary carrier 311-2, 311-3.

Further, as shown in FIG. 7, the time density (number per hour) of the reference signal 402 is larger in the primary carrier 311-1 as compared with the secondary carrier 311-2. Similarly, the time density of the reference signal 402 is greater in the secondary carrier 311-2 as compared to the secondary carrier 311-3. The reference signal facilitates demodulation (demodulation reference signal, DMRS) and / or provides a power reference for communication (sounding reference signal, SRS) or provides cell-specific information for beamforming. Alternatively, it can support channel estimation (cell-specific reference signal, RS). Further, as shown in FIG. 7, the synchronization signal 404 is communicated only on the primary carrier 311-1 and not on the secondary carriers 311-2 and 311-3. Such a synchronization signal 404 can facilitate the temporary acquisition of the timing reference of eNB 112, 112-1, 112-2 by the terminal 130-2.

Therefore, in general, the primary carrier 311-1 is associated with the first number of control signals 402, 404 per hour, and the secondary carriers 311-2, 311-3 control the second number per hour. Can be associated with signals 402, 404. The first number may be larger than the second number by, for example, 1.2 times, 1.5 times, 2 times, 10 times, 50 times, or a larger magnification. In some scenarios, the control signals 402, 404 may even be communicated only on the primary carrier 311-1. By using the asymmetry with respect to the control signals 402, 404, the amount of overhead can be reduced. This increases the data rate available for communication according to the NB-IoT RAT191.

Therefore, as can be seen from FIG. 7, in different examples, different implementations of the asymmetric distribution of control messages and / or control signals between the primary carriers 311-1 and the secondary carriers 311-2, 311-3 are conceivable. Will be. Further asymmetry between the primary carriers 311-1 and the secondary carriers 311-2, 311-3 may be implemented in terms of transmit power.

FIG. 8A shows an aspect relating to the transmission power 870. For example, the transmit power of FIG. 8A may indicate power spectral density (PSD). For example, the primary carrier 311-1 has a coefficient of at least 2 dB, preferably at least 6 dB, more preferably at least 10 dB only, as compared to the second transmit power 872 of the secondary carriers 311-2 and 311-3. It can be configured to implement a boosted first transmit power 871.

By implementing asymmetric transmission power, the chances of successful transmission of control messages and / or control signals communicated on the primary carrier 311-1 can be increased, thereby the primary carrier 311-. If the control message and / or control signal communicated on 1 is also associated with communicating on the secondary carriers 311-2, 311-3, all carriers 311, 311-1, 311-2, 311-. The overall communication reliability of the NB-IoT RAT191 over three can be increased.

In a further example, the primary carrier 311-1 is such to implement a boosted first transmit power 871 compared to, for example, the average transmit power of all resources 308 of the NB-IoT RAT191 and / or the E-UTRA RAT192. It may be configured in.

Above are examples of transmit power and asymmetry with respect to at least one of the control message and control signal. Further asymmetry, which may be implemented as an alternative or addition, may be associated with a bundled transmission set 351 containing multiple iterations of the same redundant version of the data. For example, the temporal arrangement and / or number of subframes of the bundled transmission set 351 may be asymmetrically distributed across different narrowband NB-IoT carriers 311-1, 311-2, 311-3. For example, the primary carrier 311-1 can carry more iterations of the bundled transmit set 351 when compared to the secondary carriers 311-2, 311-3 (see FIG. 6). For example, the primary carrier 311-1 may initiate iterative communication of the bundled transmit set 351 earlier than the secondary carrier 311-2, 311-3 (see FIG. 6).

For example, an implementation of such asymmetry with respect to transmit power and / or at least one of the control message and / or control signal, and / or bundled transmit set 351 is the narrowband NB- of NB-IoT RAT191. Due to the relatively small total bandwidth of the first spectrum 301 of the IoT carriers 301, 301-1, 301-2, 301-3 and / or the narrow band NB-IoT carriers 301, 301-1, 301-2, 301 It can be facilitated by the relatively small bandwidth of each of -3. For example, the distance in the frequency space between the primary carriers 311-1 and the secondary carriers 311-2, 311-3 is relatively small (small bands of each individual carrier 311-1, 311-2, 311-3). The reference signal communicated on the primary carrier 311-1 can be important for the secondary carriers 311-2 and 311-3). This is particularly applicable to in-band continuous deployment scenarios (see Figure 4). Also, if the bandwidth of each individual carrier 311-1, 311-2, 311-3 is small, the number of reference signals required per carrier may be relatively small. Further, if the individual secondary carriers 311-2, 311-3 cannot operate independently, i.e., without the accompanying primary carrier 311-1, synchronous control only on the primary carrier 311-1. It is possible to communicate the signal 404, and in such scenarios the TTI is synchronized between the primary carrier 311-1 and the secondary carriers 311-2, 311-3, for example frame or subframe. It is possible. Cross-carrier scheduling is facilitated by using the control channel 403, including scheduling control messages only on the primary carrier 311-1. Frequency hopping can be used.

FIG. 8B shows the communication protocol stack 800 of the NB-IoT RAT191. In particular, FIG. 8B shows aspects of the CA scenario. As can be seen, in the CA scenario of FIG. 8B, a separate physical layer 803 of the communication protocol stack 800 is implemented for each of the plurality of narrowband NB-IoT carriers 311-1 and 311-2. That is, when a larger (smaller) number of NB-IoT carriers are used, a larger (smaller) number of coexisting instances of physical layer 803 are implemented.

Aggregation of payload messages communicated on the payload channels of each carrier 311-1 and 311-2 is implemented at the top of the media access layer (MAC) 802 of the communication protocol stack 800. Further, the upper layer includes a radio link control (RLC) layer, a PDCP (Packet Data Convergence Protocol) layer, and an RRC layer.

In other CA scenarios, aggregation may be implemented at other levels of the communication protocol stack 800, for example somewhere within physical layer 803 or near the bottom edge of MAC layer 802. In particular, in the scenario of FIG. 8B, the hybrid ARQ (HARQ) protocol, including the ARQ protocol function and the forward error correction (FEC) function, independently corresponds to each carrier 311-1 and 311-2, respectively. Implemented by 852-2, in other examples the CA may be implemented using only a single HARQ instance.

FIG. 8B further shows aspects of the physical layer 803 transport block (TB) sublayers 853-1, 853-2. The TB sublayers 853-1 and 853-2 assemble the data packet of the upper layer, for example, the MAC packet data unit (PDU) into the TB mapped to the subframe 309. Here, different numbers of bits can be included in each TB (bit loading) depending on the MCS.

In some examples, the sublayers 853-1 and 853-2 of the two carriers 311-1 and 311-2 can operate independently of each other. Bit loading may then be independently selected for the TB of each carrier 311-1 and 311-2.

In another example (shown by a horizontal dashed line in FIG. 8B), there may be adjustments between the sublayers 853-1 and 853-2 of the two carriers 311-1 and 311-2. For example, such an adjustment may use TBs of different carriers 311-1 and 311-2 with the same size, ie, the same number of bits, for time-overlapping subframes 309 of different carriers 311-1 and 311-2. Can be implemented. For example, if the TTIs of different carriers 311-1 and 311-2 are synchronized, TBs of the same size may be used across different carriers 311-1 and 311-2 at the same moment. Therefore, bit loading can be synchronized across the narrowband NB-IoT carriers 311-1 and 311-2. For example, if TBs of the same size are used, it may be preferable to include additional adjustments between the HARQ processes 852-1, 852-2 (shown by the horizontal dashed line in FIG. 8B). In some examples, the same HARQ process may be used for all carriers 311-1 and 311-2, or the bonding may be below the HARQ process.

In some examples, bit loading may be optimized across all carriers 311-1, 311-2, 311-3 of the NB-IoT RAT191. In a further example, bit loading may be selectively optimized for the primary carrier 311-1. In particular, the number of bits in the TB can be based on a frequency-selective measurement 360 (see FIGS. 4-6) indicating the quality of communication on the primary carrier 311-1.

Such measurements have been associated with some acknowledgment messages of the HARQ protocol associated with payload messages communicated on primary carrier 311-1 and payload messages communicated over primary carrier 311-1. It may include some negative response messages of the HARQ protocol, elements selected from the group including the channel quality indicator (CQI) of communication on the primary carrier 311-1.

Due to the small overall bandwidth of the first spectrum 301 of the NB-IoT RAT191, the measurements 360 made for the primary carrier 311-1 are also for communication on the secondary carriers 311-2 and 311-3. Can be important. By reusing the measurements 360 made for the primary carrier 311-1 for the secondary carriers 311-2 and 311-3, the complexity of the system can be reduced and further the secondary carriers 311-2, The need for control signaling on 311-3, eg CQI reporting, can be reduced. Control signaling overhead can be reduced, thereby increasing the data rate.

Regarding FIGS. 4 to 8B described above, there is an example in which the first spectrum 301 of the narrowband NB-IoT carrier 311, 311-1, 311-2, 311-3 does not overlap with the second spectrum 302 of the broadband LTE carrier 312. It has been disclosed. Therefore, the first spectrum 301 may be dedicated to the NB-IoT carriers 311, 311-1, 311-2, 311-3, and the first spectrum 301 and the second spectrum 302 may not include the shared spectrum. There is sex. Here, the increase in available data rates is rather achieved, for example, by using a plurality of narrowband NB-IoT carriers 311-1, 311-2, 311-3 according to the implementation of CA. The additional resource 308 is dedicated to the narrowband NB-IoT carriers 311-1, 311-2, 311-3.

Dedicating resource 308 to such a narrowband NB-IoT RAT191 can be relatively fixed. Therefore, it may not be possible, or only to a limited extent, possible to fine-tune the distribution of resources 308 between RAT191, 192 during operation, for example on a short time scale. Such fine-tuning is desirable, for example, when the traffic of data communicated according to NB-IoT RAT191 changes. Hereinafter, a technique that enables fine adjustment of the distribution of the resource 308 between RAT191 and 192 will be disclosed. These techniques rely on the use of shared spectra. Such techniques can be combined with the techniques disclosed above, relying on multiple narrowband NB-IoT carriers.

FIG. 9 shows an embodiment relating to the use of the shared spectrum 305. As can be seen from FIG. 9, both the first spectrum 301 of the narrowband NB-IoT carrier 311 and the second spectrum 302 of the wideband LTE carrier 312 include a shared spectrum 305. The shared spectrum 305 is located adjacent to the dedicated spectrum 306, which is occupied only by the narrowband NB-IoT carrier 311.

The resource 308 of the shared spectrum 305 is allocated to either the communication according to NB-IoT RAT192 or the communication according to E-UTRA RAT312, if necessary. For example, as can be seen in FIG. 9, the first resource 308 in the shared spectrum is allocated to the narrowband NB-IoT carrier 311 and the second resource 308 in the shared spectrum 305 is allocated to the broadband LTE carrier 312. .. This allocation is performed in a TDM manner such that the first and second resources 308 allocated to different carriers 311 and 312 are orthogonal to each other, thereby interfering between the NB-IoT RAT191 and the E-UTRA RAT192. Can be alleviated.

A centralized scheduling process common to RAT191 and 192 may be implemented. The centralized scheduling process may facilitate interference mitigation in the shared spectrum 305 by implementing TDM scheduling. This may include control signaling between non-colocated access nodes 112-1 and 112-2 (see Figure 1).

The scheduling control message including the indicator indicating the first resource 308 can be communicated on the control channel of the narrowband NB-IoT carrier 311 (not shown in FIG. 9). For example, RRC control signaling may be used. This informs terminal 130-1 about the resource 308 that can be used on the shared spectrum 305. Further scheduling control messages, including an indicator indicating a second resource 308, can be communicated over the control channel of the broadband LTE carrier 312 (not shown in FIG. 9). For example, PDCCH can be used. RRC control signaling can be used. This informs terminal 130-2 about the resource 308 that can be used on the shared spectrum 305.

Since the shared spectrum 305 extends beyond the dedicated spectrum 306 of the first spectrum 301, which is not shared with the second spectrum 302, the first terminal 130-1 needs to support communication in a wider frequency band. be. Capability control messages can be communicated on the control channel of at least one NB-IOT carrier 311 to ensure that the first terminal 130-1 can communicate on the frequency of the shared spectrum 305. The capability control message includes an indicator indicating the capability of communication in the shared spectrum 305 of the first terminal 130-1 (capability control message is not shown in FIG. 9).

As disclosed above with respect to FIG. 8B, when determining the MCS of the resource 308 located in the shared spectrum 305, it is possible to rely on the measurement 360 indicating the quality of communication on the narrowband carrier 311 in the dedicated spectrum 306. be. Therefore, all TBs communicated in the shared spectrum 305 and the dedicated spectrum 306 in the time overlap subframe 309 may contain the same number of bits. The technique disclosed above for the example of FIG. 8B can also be applied to scenarios that rely on the shared spectrum 305.

The concepts described above for the co-deployment scenarios of NB-IoT RAT191 and E-UTRA RAT192 can be applied alternative or additionally to co-deployment scenarios involving other RATs. Another example of RAT is MTC RAT.

FIG. 10 shows an embodiment relating to the use of the shared spectrum 305. Here, the shared spectrum 305 is a part of the first spectrum 301 of the narrowband NB-IoT carrier 311 and is a further part of the second spectrum 302 of the wideband LTE carrier 312 and is the second of the wideband MTC carrier 313. It is also a further part of spectrum 303 of 3.

Scenarios using the shared spectrum 305 as shown above for FIGS. 9 and 10 include a plurality of narrowband NB-IoT carriers 311-1, 311-2, as shown above for FIGS. 4-8B. It can be easily combined with scenarios that use 311-3.

FIG. 11 schematically shows terminals 130-1, 130-2, for example, an IoT device. The terminal comprises a processor 131-1 such as a single core or multi-core processor. Distributed processing may be used. Processor 131-1 is coupled to memory 131-2, for example, non-volatile memory. Memory 131-2 may store program code that can be executed by processor 131-1. By executing the program code, the processor 131-1 may, for example, have one or more narrowband NB-IoT carriers 311, 311-1, 311-2, 311-2 and / or one or more wideband LTE carriers 312. Alternatively, the techniques disclosed herein are performed with respect to communicating on a broadband MTC carrier 313. Interface 131-3 may include an analog front end and / or a digital front end. Interface 131-3 may implement, for example, the communication protocol stack 800 according to 3GPP E-UTRA RAT191 and / or 3GPP NB-IoT RAT191. The communication protocol stack 800 may include a physical layer, a MAC layer, and the like.

FIG. 12 schematically shows eNB 112, 112-1, 112-2. The eNB 112, 112-1, 112-2 include a processor 113-1 such as a single-core or multi-core processor. Distributed processing may be used. Processor 113-1 is coupled to memory 113-2, eg, non-volatile memory. Memory 113-2 may store program code that can be executed by processor 113-1. By executing the program code, the processor 113-1 communicates, for example, on one or more narrowband NB-IoT carriers 311, 311-1, 311-2, 311-2, and / or one. Communicating on the above wideband LTE carrier 312 or wideband MTC carrier 313, narrowband NB-IoT carriers 311, 311-1, 311-2, 311-2, or one or more widebands of resources in the shared spectrum 305. The techniques disclosed herein can be performed with respect to allocation to LTE carriers 312 or wideband MTC carriers 313. The eNB 112, 11121, 112-2 also include an interface 113-3 configured to communicate with terminals 130-1, 130-2 on the wireless link 101. Interface 113-3 may include an analog front end and / or a digital front end. Interface 113-3 may implement, for example, the communication protocol stack 800 according to 3GPP E-UTRA RAT191 and / or 3GPP NB-IoT RAT191. The communication protocol stack 800 may include a physical layer, a MAC layer, and the like.

FIG. 13 is a flowchart of the method according to various embodiments. First, in 2001, communication is performed on at least one narrowband carrier such as NB-IoT carrier 311, 311-1, 311-2, 311-3. For example, 2001 may be executed by terminals 130-1 and / or access nodes 112, 112-1. Communication may include transmission and / or reception.

Communication may be performed on multiple narrowband carriers, for example using CA. Therefore, this method may further include aggregating payload messages communicated on the payload channels of multiple narrowband carriers in MAC layer 802. In another example, aggregation may occur at different locations within the communication protocol stack 800, eg, at the top of physical layer 803. The aggregation may accommodate bonding of various narrowband carriers.

The at least one narrowband carrier comprises the resource 308 in the first spectrum 301 and operates according to the first RAT, eg, NB-IoT RAT191. The first spectrum 301 is at least partially located within the range of the second spectrum 302.

Optionally, at 2002, communication is performed on a broadband carrier such as the broadband LTE carrier 312 and / or the broadband MTC carrier 313. Broadband carriers include resources 308 within the second spectrum 302.

In some examples, both the first and second spectra 301, 302 include a shared spectrum 305. In such cases, the method optionally allocates the first resource 308 in the shared spectrum 305 to at least one narrowband carrier and the second resource 308 in the shared spectrum 305 to the broadband carrier. Further inclusions are possible. Here, centralized scheduling can be implemented across both RATs associated with narrowband carriers and wideband carriers. Each scheduling control message may be communicated as part of a method of indicating a first resource and / or a second resource.

In some examples, communication in 2001 and 2002 may be done in a coordinated manner, i.e. in a simultaneous deployment scenario. For this purpose, control signaling between each access node can be implemented, and each access node can be statically configured to achieve coordination for a concurrent deployment scenario.

In summary, the above techniques of flexible resource allocation when communicating on one narrowband carrier or multiple narrowband carriers are exemplified. This technique relies on communicating on multiple narrowband carriers and / or on a shared spectrum shared between at least one narrowband carrier and one or more broadband carriers.

The techniques disclosed above allow the flexibility to increase or adjust the data rate of communications associated with the RAT associated with at least one narrowband carrier.

In addition, the techniques disclosed above can reduce the latency of data transmissions, for example, in scenarios where bundled transmission sets that carry the same redundant version of coded data are used in subsequent TTIs. ..

In particular, in some examples, the techniques disclosed herein may be applied to communications relating to NB-IoT RAT. By flexibly increasing the data rate achievable by NB-IoT RAT, the gap between MTC RAT and NB-IoT technology can be closed. Allows flexible resource allocation for operators targeting NB-IoT deployments and supporting use case flexibility between NB-IoT RAT on the one hand and MTC RAT or E-UTRA RAT on the other. Become.

Although the present invention has been illustrated and described with respect to some preferred embodiments, reading and understanding herein will bring to those skilled in the art the equivalents and modifications. The present invention includes all such equivalents and modifications and is limited only by the appended claims.

For example, in the above, an example is mainly given regarding the simultaneous deployment scenario of NB-IoT RAT and E-UTRA RAT, but in another example, other RATs such as NB-IoT RAT and MTC RAT are simultaneously deployed. can do. Further, a larger number of RATs such as NB-IoT RAT, MTC RAT, and E-UTRA RAT may be deployed at the same time.

For example, the above examples relying primarily on multiple narrowband carriers or shared spectra are primarily disclosed, but in other examples the concept of using multiple narrowband carriers is easy with the concept of using shared spectra. Can be combined with.

For example, the various examples described above are predominantly given with respect to communicating on at least one narrowband carrier according to the first RAT, but in other examples one or more of the second RATs. Communication on the bandwidth carrier can follow embodiments.

For example, the various examples described above are given for DL communication between a terminal and a cellular network, but in other examples, each technique can be easily applied to UL communication.

For example, the various examples described above are disclosed in the context of using a bundled transmit set in which multiple iterations of a data packet encoded according to a given redundant version are communicated over at least one narrowband carrier. However, in other examples, such iterative communication of the same redundant version does not need to be implemented to communicate on at least one narrowband carrier. For example, in a further example, the transmit power can be increased instead of communicating multiple iterations.

Claims (8)

On at least one narrowband carrier, at least one access node (112, 112-1, 112-2) of the wireless network (100) and a first terminal (130-1) connected to the wireless network (100). ), Including communicating with
The at least one narrowband carrier comprises a resource (308) within the first spectrum (301) and operates according to the first radio access technique (191).
In the first spectrum (301), communication between the at least one access node (112, 112-1, 112-2) and the second terminal (130-2) is a broadband carrier (312, 313). At least partially located within the range of the second spectrum (302) performed above,
The broadband carrier (312, 313) includes a resource (308) in the second spectrum (302) and operates according to a second radio access technique (192) that is different from the first radio access technique (191). death,
Both the first spectrum (301) and the second spectrum (302) include a shared spectrum (305).
Resources within the shared spectrum are flexibly allocated to either the at least one narrow region carrier or the broadband carrier using centralized scheduling across the first radio access technique and the second radio access technique.
Method. The duration of the resource corresponds to the transmission time interval of the first radio access technique and the second radio access technique.
The method according to claim 1 . The centralized scheduling allocates resources in the shared spectrum between the at least one narrowband carrier and the wideband carrier in a time division multiplexing manner.
The method according to claim 1 or 2 . Allocating the first resource (308) in the shared spectrum (305) to the at least one narrowband carrier
Claiming that the first resource (308) is orthogonal to the second resource, further comprising allocating the second resource (308) in the shared spectrum (305) to the broadband carrier (312, 313). Item 1. The method according to Item 1. Further comprising communicating scheduling control messages on the control channels (401, 403) of the at least one narrowband carrier.
The method of claim 4 , wherein the scheduling control message comprises an indicator indicating the first resource (308). The broadband carrier includes an additional control channel for communicating additional scheduling control messages, including an indicator indicating the second resource.
The additional control channel is different from the control channel of the at least one narrowband carrier.
The method according to claim 5 . Further comprising communicating capability control messages over the control channels (401, 403) of the at least one narrowband carrier.
The method according to any one of claims 1 to 6 , wherein the capability control message includes an indicator indicating the capability of communication in the shared spectrum (305) of the first terminal (130-1). Access nodes (112, 112-1, 112-2) of the wireless network (100).
An interface configured to send and receive wirelessly over a wireless link,
Includes a terminal connected to the wireless network (100) on at least one narrowband carrier and at least one processor configured to communicate over the interface.
The at least one narrowband carrier comprises a resource (308) within the first spectrum (301) and operates according to the first radio access technique (191).
In the first spectrum (301), communication between the at least one access node (112, 112-1, 112-2) and the second terminal (130-2) is a broadband carrier (312, 313). The broadband carrier (312, 313) comprises a resource (308) within the second spectrum (302), at least partially located within the range of the second spectrum (302) performed above, said. It operates according to a second wireless access technique (192) that is different from the first wireless access technique (191).
Both the first spectrum (301) and the second spectrum (302) include a shared spectrum (305).
Resources within the shared spectrum are flexibly allocated to either the at least one narrow region carrier or the broadband carrier using centralized scheduling across the first radio access technique and the second radio access technique.
Access nodes (112, 112-1, 112-2).

Images