(19)
(11)EP 3 437 235 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
06.05.2020 Bulletin 2020/19

(21)Application number: 17714713.9

(22)Date of filing:  29.03.2017
(51)Int. Cl.: 
H04L 5/00  (2006.01)
H04W 56/00  (2009.01)
(86)International application number:
PCT/EP2017/057476
(87)International publication number:
WO 2017/167839 (05.10.2017 Gazette  2017/40)

(54)

DYNAMICALLY CONFIGURING NB-IOT CARRIERS

DYNAMISCHE KONFIGURATION VON NB-IOT-TRÄGERN

CONFIGURATION DYNAMIQUE DE PORTEUSES NB-IOT


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 01.04.2016 US 201662316749 P

(43)Date of publication of application:
06.02.2019 Bulletin 2019/06

(73)Proprietor: Telefonaktiebolaget LM Ericsson (PUBL)
164 83 Stockholm (SE)

(72)Inventors:
  • NADER, Ali
    SE-212 42 MALMÖ (SE)
  • LIU, Yuhang
    SE-22474 LUND (SE)
  • HÖGLUND, Andreas
    SE-170 62 SOLNA (SE)
  • RATHONYI, Béla
    SE-234 37 LOMMA (SE)

(74)Representative: Zacco Sweden AB 
Valhallavägen 117 Box 5581
114 85 Stockholm
114 85 Stockholm (SE)


(56)References cited: : 
EP-A1- 2 930 990
US-A1- 2008 267 127
  
  • SONY: "Considerations on NB-PDSCH", 3GPP DRAFT; R1-160176, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. RAN WG1, no. Budapest, HU; 20160118 - 20160120 17 January 2016 (2016-01-17), XP051053495, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/Meetings_3GPP_ SYNC/RAN1/Docs/ [retrieved on 2016-01-17]
  • LENOVO: "Discussion on NB-IoT multi-carrier operation", 3GPP DRAFT; R1-161008, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. RAN WG1, no. St Julian's, Malta; 20160215 - 20160219 6 February 2016 (2016-02-06), XP051064490, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL 1/TSGR1_84/Docs/ [retrieved on 2016-02-06]
  • NTT DOCOMO: "Remaining issues on multiple NB-IoT carrier operations", 3GPP DRAFT; R1-161020 NB-IOT MULTIPLE PRB, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. RAN WG1, no. St Julian's, Malta; 20160215 - 20160219 14 February 2016 (2016-02-14), XP051054324, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/Meetings_3GPP_ SYNC/RAN1/Docs/ [retrieved on 2016-02-14]
  • ERICSSON: "NB-IoT - Support for operation with Multiple PRBs", 3GPP DRAFT; R1-160265 - NB-IOT - SUPPORT FOR OPERATION WITH MULTIPLE PRBS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDE , vol. RAN WG1, no. St Julian's, Malta; 20160215 - 20160219 14 February 2016 (2016-02-14), XP051053605, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/Meetings_3GPP_ SYNC/RAN1/Docs/ [retrieved on 2016-02-14]
  • INTEL CORPORATION: "Remaining details of NB-IoT multi-carrier operation", 3GPP DRAFT; R1-161893 - INTEL MCO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. RAN WG1, no. Sophia Antipolis, FRANCE; 20160322 - 20160324 16 March 2016 (2016-03-16), XP051081010, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL 1/TSGR1_AH/LTE_NB-IoT_1603/Docs/ [retrieved on 2016-03-16]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

[Technical Field]



[0001] The present invention relates generally to networks and more specifically to a network entity, wireless radio device, a method of controlling a network entity and a method of controlling a wireless radio device.

[Background]



[0002] NB-IoT is a narrowband system being developed for cellular Internet of Things by 3GPP. The system is based on existing LTE systems and addresses optimized network architecture and improved indoor coverage for a large number of devices. The system is expected to have the following characteristics:
  • low throughput devices (e.g. 2 kbps)
  • low delay sensitivity (∼10 seconds)
  • ultra-low device cost (below 5 dollars)
  • low device power consumption (battery life of 10 years)


[0003] It is envisioned that each cell (covering an area of approximately 1 km2) in this system will serve thousands of devices (∼50 thousand) such as sensors, meters, actuators, and the like. In order to be able to make use of existing spectrum, e.g. GSM, a fairly narrow bandwidth has been adopted for NB-IoT technology. It is envisaged that a bandwidth of 180 kHz would be used, which is the bandwidth of one LTE Physical Resource Block (PRB).

[0004] For FDD mode of NB-IoT (i.e. the transmitter and the receiver operate at different carrier frequencies) only half-duplex mode needs to be supported in the wireless radio device. In order to achieve improved coverage, data repetition is used both in UL and/or DL. The lower complexity of the devices (e.g. only one transmission/receiver chain) means that some repetition might be needed also in normal coverage.

[0005] Furthermore, to alleviate wireless radio device complexity, the working assumption is to have cross-subframe scheduling. That is, a transmission is first scheduled on a Physical DL Control Channel (NPDCCH) and then the first transmission of the actual data on the Physical DL Shared Channel (NPDSCH) is carried out after the final transmission of the NPDCCH.

[0006] Similarly for uplink (UL) data transmission, information about resources scheduled by the NW and needed by the wireless radio device for UL transmission is first conveyed on the NPDCCH and then the first transmission of the actual data by the wireless radio device on the Physical UL Shared Channel (NPUSCH) is carried out after the final transmission of the NPDCCH.

[0007] Therefore, for both cases above, there is no simultaneous reception of control channel and reception/transmission of data channel from the wireless radio device's perspective.

[0008] Furthermore, not all the subframes are available for dedicated data communication in DL in an NB-IoT carrier. The amount of available subframes in the DL is dependent on one of the three operation modes (namely, Stand-alone, In-band, and Guard-band) NB-IoT is deployed in, as depicted in Figure 1. For all operation modes, a wireless radio device needs to rate-match around the following non-available subframes (or parts of subframe):
  • The NB-IoT primary and secondary synchronization channels (NPSS and NSSS), where NPSS is transmitted every 5th subframe (NSSS transmission cycle is still to be defined in 3GPP)
  • The NB-IoT broadcast channel (NPBCH) containing the Master Information Block (MIB) occupying every 0th subframe.
  • The NB-IoT system information blocks broadcast on NDLSCH (e.g. NSIB1 broadcast in 4th subframe of every other 10ms frame)
  • DL gaps, when configured (however, this is yet to be defined in 3GPP)
  • NB-IoT reference symbols (NRS)


[0009] And, in addition, in the case of in-band operation:
  • LTE reference symbols such as CRS and positioning reference symbols, and LTE MBSFN subframes.


[0010] Further 3GPP requirements are also specified, such as that a NB-IoT carrier may only be deployed on a 100 kHz frequency raster (± 7.5 kHz). In the in-band case, not to overlap with the middle 6 LTE PRBs (because too few subframes are available due to broadcast of LTE synchronization signals and broadcast of LTE MIB), and in the in-band/guard-band operation modes not all LTE PRBs are possible to configure as NB-IoT carriers, as depicted in Figures 2a, 2b and 2c.

[0011] Due to the nature of NB-IoT with half-duplex communication, cross-scheduling, low bandwidth, the available amount of subframes, the 100 kHz raster requirement for carriers (known as an NB-IoT Anchor carrier in 3GPP) deployment, and the amount of wireless radio devices to be served, it becomes evident that (as with all other communication devices) NB-IoT will benefit from utilizing more spectrum for efficient operation, especially if such spectrum is already available (e.g. in an in-band operation mode during low traffic hours when LTE carrier is not fully used).

[0012] Figure 3 depicts a currently envisaged operation of NB-IoT networks. NB-IoT multi-carrier operation has been adopted where the wireless radio device 303 operating in a carrier 301 is configured through higher layer signaling (Layer 3 RRC) to operate in an NB-IoT non-anchor carrier 302 (which does not have the requirement to be deployed on the 100kHz raster, i.e. any LTE in-band PRB can be used) during connected mode operation. At the end of connected mode operation, the wireless radio device 303 autonomously returns back to the carrier 301.

[0013] Therefore, existing solutions/agreements in 3GPP are built around the idea that a NB-IoT non-anchor carrier is not a carrier, i.e. synchronization signals (NSS/PSS) and system information are not provided in such a carrier. At present, even if the NB-IoT non-anchor carrier would be fully operational, the wireless radio device need not receive nor perform rate-matching around NSS/PSS, and PBCH.

[0014] As a result of the wireless radio device not rate-matching around non-available subframes a number of drawbacks will result, namely:
  • NW resource scheduling becomes very complex since the NW needs to constantly make sure that no collision takes place between dedicated/unicast data aimed for the wireless radio device and non-available subframes (or parts of subframe) in the carrier.
  • Even if the NW succeeds in such scheduling, there will be need for much more control information (NPDCCH) for avoiding overlap with unavailable subframes than it would be necessary leading to waste of wireless radio device battery power.
  • NW may not be able to reconfigure wireless radio devices in less than optimal coverage to such NB-IoT non-anchor carrier since other wireless radio devices are in need of many repetitions which imply overlapping the non-available subframes.
  • In case the NW just lets the wireless radio device receive data in the non-available subframes rather than complex scheduling, there would be waste of wireless radio device power and also a risk for false data detection.


[0015] The present invention aims to provide an apparatus and method for a network entity and an apparatus and method for a wireless radio device which exhibits improved NW resource scheduling, performs rate-matching, uses less device power consumption and provides better synchronization.

[0016] US 2008/0267127 A1 describes a handover procedure in a wireless communication system comprising a source base station, a target base station, and a mobile station. The source base station sends a handover indication to the mobile station for switching the connection for the mobile station from the source base station to the target base station.

[0017] SONY: "Considerations on NB-PDSCH," vol. RAN WG1, no. Budapest, HU, dated 17 January 2016, describes an approach for load balancing in multiple inband NB-IoT carriers by transferring UEs between NB-IoT carriers via RRC signalling.

[0018] Lenovo: "Discussion on NB-IoT multi-carrier operation", vol. RAN WG1, no. St. Julian's, Malta, dated 6th February 2016, addresses the support of multiple PRBs/carrier operation for NB-IoT and clear benefits to support anchor carrier for NB-IoT.

[Summary]



[0019] The invention is defined by the independent claims. Furthermore, the embodiments of the invention are those defined by the claims. Moreover, examples, embodiments and descriptions, which are not covered by the claims are presented not as embodiments of the invention, but as background art or examples useful for understanding the invention.

[0020] The present invention provides a network entity operative to control a first carrier arranged to serve at least a first group of wireless radio devices and a second carrier arranged to serve at least a second group of wireless radio devices.

[0021] The first carrier is further arranged, when a wireless radio device belonging to a first group of wireless radio devices connects to the first carrier, to transfer the wireless radio device to the second carrier. The network entity is arranged, when the wireless radio device is transferred, to indicate to the wireless radio device that the second carrier is configured to serve as a carrier for other wireless radio devices.

[0022] The present invention also provides a wireless radio device belonging to a first group of wireless radio devices. The wireless radio device is arranged to connect to a first carrier arranged to serve at least the first group of wireless radio devices and arranged to transfer the connected wireless radio device to a second carrier arranged to serve at least the second group of wireless radio devices and receive an indication that the second carrier is configured to serve as a carrier for other wireless radio devices.

[0023] The present invention also provides a method of controlling a network entity. The method comprises transferring a connected wireless radio device belonging to a first group of wireless radio devices from a first carrier arranged to serve at least a first group of wireless radio devices to a second carrier arranged to serve at least a second group of wireless radio devices and indicating to the transferred wireless radio device that the second carrier is configured to serve as a carrier for other wireless radio devices.

[0024] The present invention also provides a method of controlling a wireless radio device belonging to a first group of wireless radio devices. The method comprises connecting to a first carrier arranged to serve at least the first group of wireless radio devices and arranged to transfer the connected wireless radio device to a second carrier arranged to serve at least a second group of wireless radio devices and receiving an indication that a second carrier is configured to serve as a carrier for other wireless radio devices.

[Brief Description of the Drawings]



[0025] Embodiments of the invention will now be described by way of example only with reference to the accompanying drawings, in which like reference numbers designate the same or corresponding parts, and in which:

Figure 1 shows the three operation modes of an NB-IoT carrier: stand-alone, LTE guard-band and LTE in-band.

Figure 2a shows possible NB-IoT carriers for a carrier deployment in LTE in-band mode.

Figure 2b shows possible NB-IoT carriers for a carrier deployment in LTE guard mode.

Figure 2c shows agreed LTE in-band PRBs possible for a carrier deployment.

Figure 3 shows exemplary scenarios where a wireless radio device is transferred from a carrier (known as an NB-IoT anchor carrier in 3GPP) to a non-anchor carrier.

Figure 4 shows a scenario where a wireless radio device is transferred from a first carrier (known as an NB-IoT anchor carrier in 3GPP) to a second carrier, according to a first embodiment of the present invention.

Figure 5 shows a method of operating a network entity according to a first embodiment of the present invention.

Figure 6 shows a method of operating a wireless radio device according to a first embodiment of the present invention.


[Detailed Description of Embodiments]


[First Embodiment]



[0026] A first embodiment of the present invention will be described with reference to Figure 4, which schematically shows a network entity 400 and a wireless radio device 403.

[0027] In one example, the network entity 400 is a NB-IoT network entity 400 but other network entities are envisaged.

[0028] The network entity 400 is operable to control a first carrier 401 and a second carrier 402.

[0029] A carrier in NB-IoT 3GPP is known as an NB-IoT Anchor Carrier. To simplify the understanding, it is known as a "carrier" throughout the present description. A carrier can have many functions. For example, the carrier may be a carrier that is on the raster that a wireless radio device will initially search for and provide all necessary information such as synchronization signals, reference signals, paging information and broadcast information and can be used for dedicated communication. In one specific non-limiting example the carrier may provide synchronization signals and system information to at least the wireless radio devices it is configured serve.

[0030] In the first embodiment more than one carrier is configured in a particular area, so as to be able to serve a large number of wireless radio devices in Idle mode e.g. for distributing paging load or NW access among thousands of wireless radio devices and therefore it should be possible to configure wireless radio devices among such carriers based on load situation in connected mode. Therefore, two carriers are provided in one coverage area.

[0031] In this way, a large number of wireless radio devices can be spread across many carriers.

[0032] Therefore, the first carrier 401 is arranged to serve at least a first group of wireless radio devices and the second carrier 402 is arranged to serve at least a second group of wireless radio devices.

[0033] In one non-limiting example, the first carrier may be arranged to provide synchronization signals and system information to at least the first group of wireless radio devices and the second carrier may be arranged to provide synchronization signals and system information to at least the second group of wireless radio devices.

[0034] In this non-limiting example, the first group of wireless radio devices is different from the second group of wireless radio devices, with each group comprising wireless radio devices that are different from the wireless radio devices in any other group. The groups are provided so that each carrier serves only a part of the total devices which the network entity as a whole serves. In this way a large number of wireless radio devices can be served with the paging load and NW access being shared amongst the carriers.

[0035] As explained previously each carrier may operate in one of three modes, as depicted in Figure 1. Namely, they may operate in an LTE in-band mode, an LTE guard-band mode or an NB-IoT stand-alone mode. Each carrier may operate in any of the three modes without limitation. In Figure 4 the first and second carriers 401, 402 are shown operating in the LTE in-band mode. However, other examples are possible. For example, the first carrier 401 may operate in in-band mode whilst the second carrier 402 may operate in LTE guard-band mode. Alternatively, the first carrier 401 may operate in NB-IoT stand-alone mode whilst the second carrier 402 may operate in LTE guard-band mode.

[0036] In the first embodiment, the wireless radio device 403 belongs to the first group of wireless radio devices and is arranged to connect to the first carrier 401.

[0037] When the wireless radio device 403 connects to the first carrier 401, the first carrier 401 is arranged to transfer the wireless radio device 403 to the second carrier 402. One way to achieve this is by configuring the wireless radio device 403 to the second carrier 402 which serves as a carrier for other wireless radio devices. For example, the second carrier 402 may be configured to serve as a carrier for at least the second group of wireless radio devices.

[0038] Once the transfer occurs, the network entity 400 is arranged to indicate to the wireless radio device 403 that the second carrier 402 is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices). Therefore, the wireless radio device 403 is arranged to receive an indication that the second carrier 402 is configured to serve as a carrier for other wireless radio devices.

[0039] In a non-limiting example, the network entity 400 may be further arranged to provide, to the wireless radio device 403, synchronization signals and system information. The wireless radio device 403, having received synchronization signals and system information and the indication that the second carrier 402 is configured to serve as a carrier for other wireless radio devices, knows which subframes (or parts thereof) are available for unicast transmission.

[0040] In the first embodiment, by way of non-limiting example, the same subframes are available in both the first carrier 401 and the second carrier 402, for simplicity.

[0041] In another non-limiting example, the network entity 400 may be further arranged to indicate to the wireless radio device that rate-matching is allowed around non-available subframes.

[0042] In a further non-limiting example, the wireless radio device 403 may be arranged to perform rate-matching around non-available subframes. In this manner, the wireless radio device 403 can avoid unavailable subframes without constant interaction from the network.

[0043] Additionally, in a further non-limiting example, the wireless radio device 403 may optionally perform further functions. In particular, the wireless radio device 403 may turn off its receiver/transmitter chain during non-available subframes.

[0044] Alternatively or in addition the wireless radio device 403 may optionally utilize the target carrier NPSS/NSSS. In this way, the wireless radio device 403 may utilize the synchronization signals, provided by the second carrier 402, for better synchronization.

[0045] Figure 5 shows a method for controlling a network entity according to the first embodiment.

[0046] Referring to Figure 5, at step S501, a connected wireless radio device belonging to a first group of wireless radio devices is transferred from a first carrier to a second carrier arranged to serve at least a second group of wireless radio devices. One way to achieve this is by configuring the wireless radio device to the second carrier which serves as a carrier for other wireless radio devices. For example, the second carrier may be configured to serve as a carrier for at least the second group of wireless radio devices.

[0047] At step S502, an indication is made to the transferred wireless radio device that the second carrier is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices).

[0048] In a non-limiting example, the method may further comprise providing, to the wireless radio device, synchronization signals and system information.

[0049] In another non-limiting example, the method may further comprise indicating to the wireless radio device that rate-matching is allowed around non-available subframes.

[0050] Figure 6 shows a method for controlling a wireless radio device belonging to first group of wireless radio devices.

[0051] Referring to Figure 6, at step S601, the wireless radio device is connected to a first carrier arranged to serve at least the first group of wireless radio devices. The first carrier is further arranged to transfer the wireless radio device to a second carrier arranged to serve at least a second group of wireless radio devices.

[0052] At step S602, the wireless radio device receives an indication that the second carrier is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices).

[0053] In a non-limiting example, the method may further comprise receiving synchronization signals and system information. The wireless radio device, having received synchronization signals and system information and the indication that the second carrier is configured to serve as a carrier for other wireless radio devices, knows which subframes (or parts thereof) are available for unicast transmission.

[0054] In a further non-limiting example, the method may further comprise performing rate-matching around non-available subframes. In this manner, the wireless radio device 403 can avoid unavailable subframes without constant interaction from the network.

[0055] Additionally, in a further non-limiting example, the method may optionally provide further steps. In particular, the method may further comprise, the wireless radio device turning off its receiver/transmitter chain during non-available subframes.

[0056] Alternatively or in addition the method may further comprise the wireless radio device utilizing the target carrier NPSS/NSSS. In this way, the wireless radio device may utilize the synchronization signals for better synchronization.

[0057] The first embodiment also encompasses a first computer program. The first computer program may be provided on a computer-readable medium.

[0058] When the first computer program is run on a network entity, the program performs the function of the network entity which is operable to control a first carrier and a second carrier.

[0059] The first carrier is arranged to serve at least a first group of wireless radio devices and the second carrier is arranged to serve at least a second group of wireless radio devices.

[0060] In one non-limiting example, the first carrier may be arranged to provide synchronization signals and system information to at least the first group of wireless radio devices and the second carrier may be arranged to provide synchronization signals and system information to at least the second group of wireless radio devices.

[0061] The present embodiment also encompasses a second computer program. The second computer program may be provided on a computer-readable medium.

[0062] The second computer program, when run on a wireless radio device, performs the function of the wireless radio device which belongs to the first group of wireless radio devices and is arranged to connect to the first carrier.

[0063] When the wireless radio device connects to the first carrier, the first carrier is arranged to transfer the wireless radio device to the second carrier. One way to achieve this is by configuring the wireless radio device to the second carrier which serves as a carrier for other wireless radio devices. For example, the second carrier 402 may be configured to serve as a carrier for at least the second group of wireless radio devices.

[0064] Once the transfer occurs, the network entity is arranged to indicate to the wireless radio device that the second carrier is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices). Therefore, the wireless radio device 403 is arranged to receive an indication that the second carrier 402 is configured to serve as a carrier for other wireless radio devices.

[0065] In a non-limiting example, the network entity may be further arranged to provide, to the wireless radio device, synchronization signals and system information. The wireless radio device, having received synchronization signals and system information and the indication that the second carrier is configured to serve as a carrier for other wireless radio devices, knows which subframes (or parts thereof) are available for unicast transmission.

[0066] In the first embodiment, by way of non-limiting example, the same subframes are available in both the first carrier and the second carrier, for simplicity.

[0067] In another non-limiting example, the network entity may be further arranged to indicate to the wireless radio device that rate-matching is allowed around non-available subframes.

[0068] In a further non-limiting example, the wireless radio device may be arranged to perform rate-matching around non-available subframes. In this manner, the wireless radio device can avoid unavailable subframes without constant interaction from the network.

[0069] Additionally, in a further non-limiting example, the wireless radio device may optionally perform further functions. In particular, the wireless radio device may turn off its receiver/transmitter chain during non-available subframes.

[0070] Alternatively or in addition the wireless radio device may optionally utilize the target carrier NPSS/NSSS. In this way, the wireless radio device may utilize the synchronization signals, provided by the second carrier 402, for better synchronization.

[0071] The first embodiment also provides modules for performing the function of the network entity.

[0072] In particular, the present embodiment provides a module for transferring a connected wireless radio device belonging to a first group of wireless radio devices from a first carrier to a second carrier arranged to serve at least a second group of wireless radio devices. One way to achieve this is by configuring the wireless radio device to the second carrier which serves as a carrier for other wireless radio devices.

[0073] For example, the second carrier may be configured to serve as a carrier for at least the second group of wireless radio devices.

[0074] The present embodiment also provides a module for indicating to the transferred wireless radio device that the second carrier is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices).

[0075] In a non-limiting example, there may also comprise a module for providing, to the wireless radio device, synchronization signals and system information.

[0076] In another non-limiting example, there may also comprise a module for indicating to the wireless radio device that rate-matching is allowed around non-available subframes.

[0077] The wireless radio device may also be provided by modules.

[0078] In particular, the present embodiment provides a module for connecting the wireless radio device to a first carrier arranged to serve at least the first group of wireless radio devices. The first carrier is further arranged to transfer the wireless radio device to a second carrier arranged to serve at least a second group of wireless radio devices.

[0079] The present embodiment also provides a module for receiving an indication that the second carrier is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices).

[0080] In a non-limiting example, the present embodiment may further comprise a module for receiving synchronization signals and system information. The wireless radio device, having received synchronization signals and system information and the indication that the second carrier is configured to serve as a carrier for other wireless radio devices, knows which subframes (or parts thereof) are available for unicast transmission.

[0081] In a further non-limiting example, the present embodiment may further comprise a module for performing rate-matching around non-available subframes. In this manner, the wireless radio device 403 can avoid unavailable subframes without constant interaction from the network.

[0082] Additionally, in a further non-limiting example, the present embodiment may further comprise a module for turning off the wireless radio device's receiver/transmitter chain during non-available subframes.

[0083] Alternatively or in addition the method may further comprise present embodiment may further comprise a module for utilizing the target carrier NPSS/NSSS. In this way, the wireless radio device may utilize the synchronization signals for better synchronization.

[Second Embodiment]



[0084] The second embodiment of the present invention has the same components as the first embodiment but differs in manner of operation.

[0085] More particularly, according to the second embodiment, unlike the first embodiment, the first carrier 401 and the second carrier 402 have different subframe configurations.

[0086] The present inventors overcame this by arranging the network entity 400 to convey information indicative of the subframe configuration of the second carrier 402 to the wireless radio device 403.

[0087] The network entity 400 may convey the information in a number of ways. The present inventors found that fully conveying the entire subframe configuration of the second carrier 402 to the wireless radio device 403 was particularly effective.

[0088] Alternatively, only conveying the changes of the subframe configuration of the second carrier 402 relative to the first carrier 401 was found to minimize the amount of information that needed to be conveyed.

[0089] The wireless radio device 403 may therefore be arranged to receive the information indicative of the subframe configuration of the second carrier 402.

[0090] The method of controlling a network entity depicted in Figure 5 also comprises the further step of conveying to the wireless radio device information indicative of the subframe configuration of the second carrier.

[0091] Similarly, the method of controlling a wireless radio device in Figure 6 also comprises the step of receiving the information indicative of the subframe configuration of the second carrier.

[0092] The first computer program mentioned in the first embodiment would therefore include the further function of conveying to the wireless radio device information indicative of the subframe configuration of the second carrier.

[0093] The second computer program mentioned in the first embodiment would therefore include the further function of receiving the information indicative of the subframe configuration of the second carrier.

[0094] The modules provided in the first embodiment for performing the function of the network entity further comprise a module for conveying to the wireless radio device information indicative of the subframe configuration of the second carrier.

[0095] The modules provided in the first embodiment for performing the function of the wireless radio device further comprise a module for receiving the information indicative of the subframe configuration of the second carrier.

[Third Embodiment]



[0096] The third embodiment of the present invention pertains to the 3GPP contribution made by the present inventors. In this embodiment the wireless radio device is referred to as user equipment, UE.

[0097] In particular, in RAN2#93 it was agreed as per R2-161888, RAN1#84 NB-IoT Adhoc, 15-19 February 2016, to add support for multiple PRB operations. In the agreement, it was decided to include configuration of a non-anchor PRB in the IE radioResourceConfigDedicated.

[0098] In this embodiment further details about UE reconfiguration to a non-anchor carrier are provided.

[0099] 36.331 Running CR to capture agreements on NB-IoT specifications related to multi-PRB support the following is captured under 5.3.10.6 Physical channel reconfiguration:
For NB-IoT, the UE shall:
  1. 1> if the carrierInfo [FFS] is included and specifies a carrier that the UE shall use for future receptions and transmissions:
    2> the UE shall start to use the new carrier immediately after the last transport block carrying the RRC message has been acknowledged by the MAC layer, and any subsequent RRC response message sent for the current RRC procedure is therefore sent on the new carrier;


[0100] The details of the configuration of a non-anchor carrier and related actions are FFS
  1. 1> reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated-NB.


[0101] The contents of physicalConfigDedicated-NB needed for configuring the UE to a non-anchor carrier is further explained below.

[0102] In physicalConfigDedicated-NB, a NB-IoT UE is optionally provided with a set of parameters related to the non-anchor carrier(s). The set of parameters are scenario-dependent (e.g. from/to in-band/guard-band/standalone) and relate to downlink and/or uplink non-anchor carriers as presented below in the ASN.1 structure. -- ASN1START Carrier-ConfigDedicated-NB-r13 ::= SEQUENCE { dl-nonAnchorCarrierFreq-NB-r13 DL- NonAnchorCarrierFreq-NB-r13 OPTIONAL, ul-nonAnchorCarrierFreq-NB-r13 UL- NonAnchorCarrierFreq-NB-r13 OPTIONAL, } -- ASN1STOP

[0103] Therefore, the following proposal is made:
Proposal 1 Carrier-ConfigDedicated-NB-r13 with the preceding ASN.1 format is introduced in physicalConfigDedicated-NB to specify the UL and/or DL non-anchor carrier(s) structure.

[0104] As pointed out in R4-157639, On channel arrangement for NB-IOT, 3GPP RAN WG4 Meeting #77, Anaheim, US, 16 - 20 November, 2015, the actual NB-IoT channel center frequency in the case of in-band/guard-band operations will have a frequency offset to the 100 kHz raster ranging from 2.5 kHz to 47.5 kHz. Hence, in order to be able to configure the UE to a non-anchor carrier, it is proposed to convey the carrier frequency information in terms of eARFCN and an optional offset needed for guard-band/in-band operation as follows in ASN.1 format: -- ASN1START CarrierFreq-NB-r13 ::= SEQUENCE { carrierFreq-NB-r13 ARFCN-ValueEUTRA-r9, carrierFreqOffset-NB-r13 INTEGER (0..19) OPTIONAL, -- Need ON } -- ASN1STOP

[0105] The following proposal is also made:
Proposal 2 The non-anchor carrier frequency is configured in terms of eARFCN and an optional offset needed for guard-band/in-band operation according to the preceding ASN.1 format.

[0106] As agreed in RAN1#84, the UE is not expected to receive NPBCH, and NPSS/NSSS and any transmissions other than unicast transmissions in the non-anchor PRB. As a result, the PCI of the non-anchor carriers needs to be communicated to the UEs by either SI broadcast in the anchor carrier or through reconfiguration signaling unless the same PCI is used for the non-anchor carrier as for the anchor carrier. For Rel-13 no benefit is achieved of assigning different PCIs to non-anchor carriers other than the one of the associated anchor carrier.

[0107] The following proposal is also made:
Proposal 3 The PCI of a non-anchor NB-IoT carrier is always the same as its associated anchor carrier.

[0108] For carrier reconfiguration to a DL non-anchor in-band PRB, apart from the carrier information mentioned above, the number of LTE CRS antenna ports, number of LTE PDCCH symbols (or NB-IoT start symbol), the PRB offset to LTE middle PRB and the knowledge about whether LTE uses same PCI as NB-IoT (in able to be able to use LTE CRS), and number of NRS antenna ports need to be known by the UE prior to the reconfiguration procedure. For carrier reconfiguration to a DL non-anchor PRB, the number of NB-RS antenna ports needs to be known by the UE during the reconfiguration procedure. These configuration parameters can either be broadcasted on the anchor carrier in a newly defined SIB or optionally sent to the UE in dedicated message in case not broadcasted. Further, in the RAN1#2 Ad-Hoc is was agreed that:
On PRBs different than the NB-IoT carrier on which the UE has received NB-PSS/SSS, NB-PBCH and SIB transmissions, the NB-IoT UE does not rate match around NB-PBCH and NB-PSS/SSS, i.e., the mapping of NB-PDCCH/PDSCH symbols to REs occurs without consideration of NB-PSS/SSS/PBCH.

[0109] However, just including an indication that the carrier which the UE is reconfigured to, does in fact contain NPSS/NSSS and NPBCH would allow for reconfiguring and distributing UEs between several anchor carriers. Since the benefits can be rather large for a minor cost such an indication is included here.

[0110] The configurations mentioned above are outlined in ASN.1 format below: -- ASN1START DL-NonAnchorCarrierFreq-NB-r13 ::= SEQUENCE { carrierFreq-NB-r13 CarrierFreq-NB-r13, nbRsPortsCount-NB-r13 ENUMERATED {n1, n2} OPTIONAL, -- Need ON servesAsAnchorForOthers BOOLEAN OPTIONAL, -- Need ON inbandNonAnchorCarrierInfo InbandNonAnchorCarrierInfo OPTIONAL, -- Cond SIconfig ...} -- ASN1STOP , where -- ASN1START InbandNonAnchorCarrierInfo ::= SEQUENCE { offsetToLteMiddlePrb-NB-r13 INTEGER (-50..49) OPTIONAL, -- Cond samePCI startSymbol-NB-r13 INTEGER (1..4) OPTIONAL, sameLtePCI-Indicator-NB-r13 BOOLEAN OPTIONAL, lteCrsPortsCount-NB-r13 ENUMERATED {an1, an2, an4, spare1} OPTIONAL, } -- ASN1STOP

[0111] As noted in R1-161820, NB-IoT - Remaining issues for NPBCH and MIB, Ericsson, RAN1#2 NB-IoT Ad-Hoc Meeting Sophia Antipolis, 22nd - 24th March 2016, there is no need to include the bandwidth of the LTE carrier but it is sufficient to indicate the offset, which in this case is relative to the central frequency of the LTE carrier.

[0112] The following proposal is also made:
Proposal 4 For NB-IoT DL non-anchor carrier configuration, the information outlined in preceding ASN.1 is provided to the UE in physicalConfigDedicated-NB.

[0113] For carrier reconfiguration to an UL non-anchor carrier, the UE needs to know the UL carrier information. This information can either be explicitly configured via CarrierFreq-NB-r13 mentioned above or alternately in case DL PRB non-anchor is also configured, the same duplex distance as for anchor DL-UL can be indicated to the UE. Furthermore the UE needs to know whether the target UL PRB serves as an anchor carrier for other UEs, i.e. whether the non-anchor is used for random access by others. For simplicity, the same random access configuration shall in such case apply to the target PRB as in source PRB. These configurations are outlined in the ASN.1 format below: -- ASN1START UL-NonAnchorCarrierFreq-NB-r13 ::= SEQUENCE { ulFreqInfo CHOICE { carrierFreq-NB-r13 CarrierFreq-NB- r13, sameDuplexDistanceAsAnchor NULL -- Cond }, servesAsAnchorForOthers BOOLEAN OPTIONAL, -- Need ON ...} -- ASN1STOP

[0114] The following proposals are also made:
Proposal 5 For NB-IoT UL non-anchor carrier configuration, the information outlined in preceding ASN.1 is provided to the UE.

[0115] Proposal 6 In case the parameter "servesAsAnAnchorForOthers" is set to "true" in the configuration to non-anchor carrier above for UL and/or DL, the UE shall assume the same available subframes as in its anchor carrier.

[0116] As mentioned above, another way to convey many of the parameters above related to non-anchor carrier is through system information on the anchor carrier. This could be beneficial in case an operator often configures UEs to non-anchor carriers with same configuration rather than repeatedly sending the same configuration parameters to different UEs. Hence, it is suggested to define a new SIB that is optionally broadcasted and contains non-anchor configuration parameters. However, in case configuration parameters are provided in physicalConfigDedicated-NB, they override the parameters broadcasted in anchor carrier.

[0117] The following proposals are also made:
Proposal 7 In the anchor carrier, it is possible to optionally broadcast NB-IoT DL/UL non-anchor carrier configuration.

[0118] Proposal 8 Parameters provided to the UE in physicalConfigDedicated-NB override the non-anchor configuration parameters broadcasted in anchor carrier.

[0119] With the above proposals the ASN.1 structure for the new SIB with some of the required IEs is given below.

[0120] In particular, the proposed structure for the system information block containing the information about the LTE carrier in the case the non-anchor carrier is in-band. -- ASN1START SystemInformationBlockTypeX-r13 ::= SEQUENCE { InbandNonAnchorCarrierInfo ::= SEQUENCE { offsetToLteMiddlePrb-NB-r13 INTEGER (-50..49) OPTIONAL, -- Cond samePCI startSymbol-NB-r13 INTEGER (1..4) OPTIONAL, sameLtePCI-Indicator-NB-r13 BOOLEAN OPTIONAL, lteCrsPortsCount-NB-r13 ENUMERATED {an1, an2, an4, spare1} OPTIONAL, ... } } -- ASN1STOP

[0121] The InbandNonAnchorCarrierInfo field descriptions are:
offsetToLteMiddlePrb-NB-r13

[0122] This parameter gives the PRB index relative to the middle PRB in order for the UE to determine the legacy CRS. The sign of the PRB index is positive for PRBs higher in frequency than the central PRB and negative for PRBs lower in frequency. For an LTE carrier with an even (odd) number of PRBs, the central six (seven) PRBs are not valid as NB-IoT non-anchor carriers. The PRB index relative to middle PRB is converted to LTE PRB index.
startSymbol-NB-r13

[0123] This parameter specifies the PDCCH region of the LTE carrier.
sameLtePCI-Indicator-NB-r13

[0124] This parameter specifies whether the non-anchor carrier reuses the same PCI as the LTE carrier.
lteCrsPortsCount-NB-r13

[0125] This parameter specifies the number of antenna ports used by the legacy carrier in the in-band case.

[0126] samePCI The field is mandatory present if the sameLtePCI-Indicator-NB-r13 is present and set to TRUE. Otherwise the field is not present.

[0127] Below follows a summary of the ASN.1 structure. Based on the following structure currently suggested in R2-162070, 36.331 Running CR to capture agreements on NB-IoT, version 13.0.0. -- ASN1START PhysicalConfigDedicated-NB ::= SEQUENCE { Carrier-ConfigDedicated-NB-r13 Carrier- ConfigDedicated-NB-r13 OPTIONAL, -- Need ON pdsch-ConfigDedicated-NB-r13 PDSCH-ConfigDedicated- NB-r13 OPTIONAL, -- Need ON pusch-ConfigDedicated-NB-r13 PUSCH-ConfigDedicated- NB-r13 OPTIONAL, -- Need ON uplinkPowerControlDedicated-NB-r13 UplinkPowerControlDedicated-NB-r13 OPTIONAL, -- Need ON tpc-PDCCH-ConfigPUSCH TPC-PDCCH-Config OPTIONAL, -- Need ON cqi-ReportConfig-NB-r13 CQI-ReportConfig- NB-r13 OPTIONAL, -- Need ON soundingRS-UL-ConfigDedicated-NB-r13 SoundingRS-UL- ConfigDedicated-NB-r13 OPTIONAL, -- Need ON ... } -- ASN1STOP

[0128] The following are physicalConfigDedicated-NB field descriptions:
Carrier-ConfigDedicated-NB-r13

[0129] This parameter contains the non-anchor carrier frequency positions dl-nonAnchorCarrierFreq-NB-r13 and/or ul-nonAnchorCarrierFreq-NB-r13.

[0130] The following structure has been proposed for Carrier-ConfigDedicated-NB-r13: -- ASN1START Carrier-ConfigDedicated-NB-r13 ::= SEQUENCE { dl-nonAnchorCarrierFreq-NB-r13 DL- NonAnchorCarrierFreq-NB-r13 OPTIONAL, ul-nonAnchorCarrierFreq-NB-r13 UL- NonAnchorCarrierFreq-NB-r13 OPTIONAL, } -- ASN1STOP

[0131] The following are Carrier-ConfigDedicated-NB-r13 field descriptions:
dl-nonAnchorCarrierFreq-NB-r13

[0132] This parameter specifies the frequency for the downlink carrier plus some additional information. If this parameter as absent the UE shall continue to use the anchor downlink carrier.
ul-nonAnchorCarrierFreq-NB-r13

[0133] This parameter specifies the frequency for the uplink carrier plus some additional information. If this parameter as absent the UE shall continue to use the anchor uplink carrier. -- ASN1START DL-NonAnchorCarrierFreq-NB-r13 ::= SEQUENCE { carrierFreq-NB-r13 CarrierFreq-NB-r13, nbRsPortsCount-NB-r13 ENUMERATED {n1, n2} OPTIONAL, -- Need ON servesAsAnchorForOthers BOOLEAN OPTIONAL, -- Need ON inbandNonAnchorCarrierInfo InbandNonAnchorCarrierInfo OPTIONAL, -- Cond SIconfig ...} -- ASN1STOP

[0134] The following are DL-NonAnchorCarrierFreq-NB-r13 field descriptions:
nbRsPortsCount-NB-r13

[0135] This parameter specifies whether the eNB uses one antenna port (n1) or two (n2). If this parameter is not present, the UE shall assume the same number of antenna ports as configured for the anchor carrier.
servesAsAnchorForOthers

[0136] If this parameter is set to True the non-anchor carrier contains NPSS/NSSS, NPBCH and System Information.
inbandNonAnchorCarrierInfo

[0137] This parameter gives the configuration for the downlink non-anchor carrier. This configuration will override any previous configured by system information broadcast in the anchor carrier.

[0138] The SIconfig field is mandatory present if the UE is reconfigured to an in-band carrier and InbandNonAnchorCarrierInfo is not provided in SI. Otherwise the field is optional present, and any configuration given will override the corresponding one in SI. -- ASN1START InbandNonAnchorCarrierInfo ::= SEQUENCE { offsetToLteMiddlePrb-NB-r13 INTEGER (-50..49) OPTIONAL, -- Cond samePCI startSymbol-NB-r13 INTEGER (1..4) OPTIONAL, sameLtePCI-Indicator-NB-r13 BOOLEAN OPTIONAL, lteCrsPortsCount-NB-r13 ENUMERATED {an1, an2, an4, spare1} OPTIONAL, } -- ASN1STOP

[0139] The following are InbandNonAnchorCarrierInfo field descriptions
offsetToLteMiddlePrb-NB-r13

[0140] This parameter gives the PRB index relative to the middle PRB in order for the UE to determine the legacy CRS. The sign of the PRB index is positive for PRBs higher in frequency than the central PRB and negative for PRBs lower in frequency. For an LTE carrier with an even number of PRBs the central six PRBs ({-3, 2}) are not valid as NB-IoT non-anchor carriers, and for odd numbers of PRBs the central seven PRBs ({-3, 3}) are not valid. The PRB index relative to middle PRB is converted to LTE PRB index.
startSymbol-NB-r13

[0141] This parameter specifies the PDCCH region of the LTE carrier.
sameLtePCI-Indicator-NB-r13

[0142] This parameter specifies whether the non-anchor carrier reuses the same PCI as the LTE carrier.
lteCrsPortsCount-NB-r13

[0143] This parameter specifies the number of antenna ports used by the legacy carrier in the in-band case.

[0144] The samePCI field is mandatory present if the sameLtePCI-Indicator-NB-r13 is present and set to TRUE. Otherwise the field is not present. -- ASN1START UL-NonAnchorCarrierFreq-NB-r13 ::= SEQUENCE { ulFreqInfo CHOICE { carrierFreq-NB-r13 CarrierFreq-NB- r13, sameDuplexDistanceAsAnchor NULL -- Cond }, servesAsAnchorForOthers BOOLEAN OPTIONAL, -- Need ON ...} -- ASN1STOP

[0145] The following are UL-NonAnchorCarrierFreq-NB-r13 field descriptions
ulFreqInfo

[0146] This parameter specifies whether the frequency for the uplink carrier explicitly included or implicit from reusing the same duplex distance as for the anchor carrier.
sameDuplexDistanceAsAnchor

[0147] If the downlink non-anchor carrier is specified by DL-NonAnchorCarrierFreq-NB-r13, this parameter can be specified to reuse the same duplex distance as for the anchor carrier and hence the uplink carrier frequency is not specified.
servesAsAnchorForOthers

[0148] If this parameter is set to True the non-anchor carrier contains NPSS/NSSS, NPBCH and System Information. -- ASN1START CarrierFreq-NB-r13 ::= SEQUENCE { carrierFreq-NB-r13 ARFCN-ValueEUTRA-r9, carrierFreqOffset-NB-r13 INTEGER (0..19) OPTIONAL, -- Need ON } -- ASN1STOP

[0149] The following are CarrierFreq-NB-r13 field descriptions carrierFreq-NB-r13

[0150] This parameter specifies the central frequency for the carrier in terms on ARFCN.
carrierFreqOffset-NB-r13

[0151] The frequency offset of the carrier relative to the central frequency is given as ((carrierFreqOffset-NB-r13 - 10) 2 + 1) 2.5) kHz for downlink, and ((carrierFreqOffset-NB-r13-10) 2) 2.5) kHz for uplink. If this optional parameter is omitted the UE shall apply a zero offset according to 'Need ON'.

[Modifications and Variations]



[0152] The present description has been given with DL configuration as an example. However, UL configuration is envisaged by the present inventors using a similar apparatus. In this case the wireless radio device 403 would need to avoid UL transmission colliding with PRACH resources that might be used by wireless radio devices having the second carrier 402 as their carrier. Parts of the UL subframe may operate on single-tones or multi-tones. These "tones" refer to sub-carriers in the UL (either 3.75 kHz or 15 kHz). Therefore, not all of the 180 kHz UL is necessarily used by one wireless radio device in UL.

[0153] In this regard, the network entity 400 is arranged to indicate for each of UL and DL respectively that the second carrier 402 is configured to serve as a carrier for other wireless radio devices (e.g. the second group of wireless radio devices). An indicator is provided for each of UL and DL respectively, as the wireless radio device 403 might only be configured to operate only in UL or DL on a NB-IoT non-anchor carrier.

[Abbreviations]



[0154] 
CRS
Cell Reference Symbols
FDD
Frequency Division Duplex
LTE
Long Term Evolution
MBSFN
Multimedia Broadcast Single Frequency network
MIB
Master Information Block
NB
Narrowband
NB-IoT
NB Internet of Things
NDLSCH
NB Downlink Shared Channel
NPBCH
NB Physical Broadcast Channel
NPRACH
NB Physical Random Access Channel
NPSS
NB Primary Synchronization Signal
NRS
NB Reference Symbols
NSSS
NB Secondary Synchronization Signal
NW
Network
SI
System Information
SIB
System Information Block
UE
User Equipment



Claims

1. A network entity (400) operative to control:

a first Narrow Band - Internet of Things, NB-IoT, carrier (401) arranged to serve at least a first group of wireless radio devices; and

a second NB-IoT carrier (402) arranged to serve at least a second group of wireless radio devices,

wherein:

the first NB-IoT carrier (401) is further arranged, when a wireless radio device (403) belonging to a first group of wireless radio devices connects to the first NB-IoT carrier (401), to transfer the wireless radio device (403) to the second NB-IoT carrier (402), and

the network entity (400) is arranged, when the wireless radio device (403) is transferred, to indicate to the wireless radio device (403) that the second NB-IoT carrier (402) is configured to serve as a carrier for other wireless radio devices, and

wherein the network entity (400) is further arranged to indicate to the wireless radio device (403) that rate-matching is allowed around non-available subframes.


 
2. The network entity (400) according to Claim 1, wherein the network entity (400) is further arranged to provide, to the wireless radio device (403), synchronization signals and system information.
 
3. The network entity (400) according to any preceding claim, wherein the first NB-IoT carrier (401) is arranged to provide synchronization signals and system information to at least the first group of wireless radio devices and the second NB-IoT carrier (402) is arranged to provide synchronization signals and system information to at least the second group of wireless radio devices.
 
4. The network entity (400) according to any preceding claim, wherein the first NB-IoT carrier (401) and second NB-IoT carrier (402) may each be arranged to operate in one of: LTE in-band mode, LTE guard-band mode or NB-IoT stand alone mode.
 
5. The network entity (400) according to any preceding claim, wherein the first NB-IoT carrier (401) and the second NB-IoT carrier (402) have different subframe configurations and the network entity (400) is further arranged to convey information indicative of the subframe configuration of the second carrier NB-IoT (402) to the wireless radio device (403).
 
6. A wireless radio device (403) belonging to a first group of wireless radio devices, wherein the wireless radio device (403) is arranged to:

connect to a first Narrow Band - Internet of Things, NB-IoT, carrier (401) arranged to serve at least the first group of wireless radio devices and arranged to transfer the connected wireless radio device (403) to a second NB-IoT carrier (402) arranged to serve at least a second group of wireless radio devices, and

receive an indication that the second NB-IoT carrier (402) is configured to serve as a carrier for other wireless radio devices, wherein the wireless radio device (403) is further arranged to perform rate-matching around non-available subframes.


 
7. The wireless radio device (403) according to -Claim 6, wherein the wireless radio device (403) is further arranged to perform at least one of:

turn off its receiver/transmitter chain during non-available subframes, and

utilise the target carrier NPSS/NSSS.


 
8. A method of controlling a network entity (400), the method comprising:

transferring (S501) a connected wireless radio device (403) belonging to a first group of wireless radio devices from a first Narrow Band - Internet of Things, NB-IoT, carrier (401) arranged to serve at least a first group of wireless radio devices to a second NB-IoT carrier (402) arranged to serve at least a second group of wireless radio devices; and

indicating (S502) to the transferred wireless radio device that the second NB-IoT carrier (402) is configured to serve as a carrier for other wireless radio devices, wherein the method further comprises indicating, by the network entity (400), to the wireless radio device (403) that rate-matching is allowed around non-available subframes.


 
9. The method according to Claim 8, further comprising:
providing, to the wireless radio device, synchronization signals and system information.
 
10. The method according to Claim 8 or Claim 9, wherein the first NB-IoT carrier is arranged to provide synchronization signals and system information to at least the first group of wireless radio devices and the second NB-IoT carrier is arranged to provide synchronization signals and system information to at least the second group of wireless radio devices.
 
11. The method according to any of Claims 8 - 10, wherein the first NB-IoT carrier and the second NB-IoT carrier have different subframe configurations and the method further comprises conveying information indicative of the subframe configuration of the second NB-IoT carrier to the wireless radio device.
 
12. A method of controlling a wireless radio device (403) belonging to a first group of wireless radio devices, the method comprising:

connecting (S601) to a first Narrow Band - Internet of Things, NB-IoT, carrier (401) arranged to serve at least the first group of wireless radio devices and arranged to transfer the connected wireless radio device to a second NB-IoT carrier (402) arranged to serve at least a second group of wireless radio devices; and

receiving (S602) an indication that the second NB-IoT carrier is configured to serve as a carrier for other wireless radio devices, wherein the method further comprises performing, by the wireless radio device (403), rate-matching around non-available subframes.


 
13. The method according to Claim 12, further comprising:
receiving synchronization signals and system information.
 
14. The method of any of Claims 12 - 13, wherein the wireless radio device is further arranged to perform at least one of:

turn off its receiver chain and/or transmitter chain during non-available subframes, and

utilise the target carrier NPSS/NSSS.


 


Ansprüche

1. Netzwerkeinheit (400), die betriebsfähig ist zum Steuern:

eines ersten Narrow-Band-Internet-of-Things-Trägers, NB-IoT-Trägers (401), der angeordnet ist, mindestens eine erste Gruppe von drahtlosen Funkvorrichtungen zu bedienen; und

eines zweiten NB-IoT-Trägers (402), der angeordnet ist, mindestens eine zweite Gruppe von drahtlosen Funkvorrichtungen zu bedienen,

wobei:

der erste NB-IoT-Träger (401) ferner angeordnet ist, wenn eine zu einer ersten Gruppe drahtloser Funkvorrichtungen gehörende drahtlose Funkvorrichtung (403) sich mit dem ersten NB-IoT-Träger (401) verbindet, die drahtlose Funkvorrichtung (403) zu dem zweiten NB-IoT-Träger (402) zu übertragen, und

die Netzwerkeinheit (400) angeordnet ist, wenn die drahtlose Funkvorrichtung (403) übertragen ist, der drahtlosen Funkvorrichtung (403) anzugeben, dass der zweite NB-IoT-Träger (402) dazu konfiguriert ist, als Träger für andere drahtlose Funkvorrichtungen zu dienen, und

wobei die Netzwerkeinheit (400) ferner angeordnet ist, der drahtlosen Funkvorrichtung (403) anzugeben, dass Ratenabgleich um nicht verfügbare Unterrahmen erlaubt ist.


 
2. Netzwerkeinheit (400) nach Anspruch 1, wobei die Netzwerkeinheit (400) ferner angeordnet ist, der drahtlosen Funkvorrichtung (403) Synchronisationssignale und Systeminformationen bereitzustellen.
 
3. Netzwerkeinheit (400) nach einem der vorstehenden Ansprüche, wobei der erste NB-IoT-Träger (401) angeordnet ist, mindestens der ersten Gruppe von drahtlosen Funkvorrichtungen Synchronisationssignale und Systeminformationen bereitzustellen, und der zweite NB-IoT-Träger (402) angeordnet ist, mindestens der zweiten Gruppe von drahtlosen Funkvorrichtungen Synchronisationssignale und Systeminformationen bereitzustellen.
 
4. Netzwerkeinheit (400) nach einem der vorstehenden Ansprüche, wobei der erste NB-IoT-Träger (401) und der zweite NB-IoT-Träger (402) jeweils angeordnet sein können, in einem von: LTE-In-Band-Modus, LTE-Schutzband-Modus oder NB-IoT-Standalone-Modus betrieben zu werden.
 
5. Netzwerkeinheit (400) nach einem der vorstehenden Ansprüche, wobei der erste NB-IoT-Träger (401) und der zweite NB-IoT-Träger (402) unterschiedliche Unterrahmenkonfigurationen aufweisen und die Netzwerkeinheit (400) ferner angeordnet ist, Informationen, die auf die Unterrahmenkonfiguration des zweiten Träger-NB-IoT (402) hinweisen, an die drahtlose Funkvorrichtung (403) zu übermitteln.
 
6. Drahtlose Funkvorrichtung (403), die zu einer ersten Gruppe von drahtlosen Funkvorrichtungen gehört, wobei die drahtlose Funkvorrichtung (403) angeordnet ist zum:

Verbinden mit einem ersten Narrow-Band-Internet-of-Things-Träger, NB-IoT-Träger (401), der angeordnet ist, mindestens die erste Gruppe von drahtlosen Funkvorrichtungen zu bedienen und angeordnet ist, die verbundene drahtlose Funkvorrichtung (403) zu einem zweiten NB-IoT-Träger (402) zu übertragen, der angeordnet ist, mindestens eine zweite Gruppe von drahtlosen Funkvorrichtungen zu bedienen, und

Empfangen einer Angabe, dass der zweite NB-IoT-Träger (402) konfiguriert ist, als ein Träger für andere drahtlose Funkvorrichtungen zu dienen, wobei die drahtlose Funkvorrichtung (403) ferner angeordnet ist, einen Ratenabgleich um nicht verfügbare Unterrahmen durchzuführen.


 
7. Drahtlose Funkvorrichtung (403) nach Anspruch 6, wobei die drahtlose Funkvorrichtung (403) ferner angeordnet ist zum Durchführen von mindestens einem von:

Ausschalten ihrer Empfänger/Sender-Kette während nicht verfügbarer Unterrahmen, und

Verwenden des Zielträger-NPSS/NSSS.


 
8. Verfahren zum Steuern einer Netzwerkeinheit (400), das Verfahren umfassend:

Übertragen (S501) einer verbundenen drahtlosen Funkvorrichtung (403), die zu einer ersten Gruppe von drahtlosen Funkvorrichtungen gehört, von einem ersten Narrow-Band-Internet-of-Things-Träger, NB-IoT-Träger (401), der angeordnet ist, mindestens die erste Gruppe von drahtlosen Funkvorrichtungen zu bedienen, zu einem zweiten NB-IoT-Träger (402), der angeordnet ist, mindestens eine zweite Gruppe von drahtlosen Funkvorrichtungen zu bedienen; und

Angeben (S502) an die übertragene drahtlose Funkvorrichtung, dass der zweite NB-IoT-Träger (402) konfiguriert ist, als ein Träger für andere drahtlose Funkvorrichtungen zu dienen, wobei das Verfahren ferner das Angeben, durch die Netzwerkeinheit (400), an die drahtlose Funkvorrichtung (403), dass Ratenabgleich um nicht verfügbare Unterrahmen erlaubt ist, umfasst.


 
9. Verfahren nach Anspruch 8, ferner umfassend:
Bereitstellen, an die drahtlose Funkvorrichtung, von Synchronisationssignalen und Systeminformationen.
 
10. Verfahren nach Anspruch 8 oder Anspruch 9, wobei der erste NB-IoT-Träger angeordnet ist, mindestens der ersten Gruppe von drahtlosen Funkvorrichtungen Synchronisationssignale und Systeminformationen bereitzustellen, und der zweite NB-IoT-Träger angeordnet ist, mindestens der zweiten Gruppe von drahtlosen Funkvorrichtungen Synchronisationssignale und Systeminformationen bereitzustellen.
 
11. Verfahren nach einem der Ansprüche 8 bis 10, wobei der erste NB-IoT-Träger und der zweite NB-IoT-Träger unterschiedliche Unterrahmenkonfigurationen aufweisen und das Verfahren ferner das Übermitteln von Informationen, die auf die Unterrahmenkonfiguration des zweiten NB-IoT-Trägers hinweisen, an die drahtlose Funkvorrichtung umfasst.
 
12. Verfahren zum Steuern einer drahtlosen Funkvorrichtung (403), die zu einer ersten Gruppe von drahtlosen Funkvorrichtungen gehört, das Verfahren umfassend:

Verbinden (S601) mit einem ersten Narrow-Band-Internet-of-Things-Träger, NB-IoT-Träger (401), der angeordnet ist, mindestens die erste Gruppe von drahtlosen Funkvorrichtungen zu bedienen, und angeordnet ist, die verbundene drahtlose Funkvorrichtung zu einem zweiten NB-IoT-Träger (402) zu übertragen, der angeordnet ist, mindestens eine zweite Gruppe von drahtlosen Funkvorrichtungen zu bedienen; und

Empfangen (S602) einer Angabe, dass der zweite NB-IoT-Träger konfiguriert ist, als ein Träger für andere drahtlose Funkvorrichtungen zu dienen, wobei das Verfahren ferner das Durchführen, durch die drahtlose Funkvorrichtung (403), eines Ratenabgleichs um nicht verfügbare Unterrahmen umfasst.


 
13. Verfahren nach Anspruch 12, ferner umfassend:
Empfangen von Synchronisationssignalen und Systeminformationen.
 
14. Verfahren nach einem der Ansprüche 12 bis 13, wobei die drahtlose Funkvorrichtung ferner angeordnet ist zum Durchführen von mindestens einem von:

Ausschalten ihrer Empfängerkette und/oder Senderkette während nicht verfügbaren Unterrahmen, und

Verwenden des Zielträger-NPSS/NSSS.


 


Revendications

1. Entité réseau (400) opérationnelle pour commander :

une première porteuse Internet des objets en bande étroite, NB-IoT (401) agencée pour servir au moins un premier groupe de dispositifs radio sans fil ; et

une deuxième porteuse NB-IoT (402) agencée pour servir au moins un deuxième groupe de dispositifs radio sans fil,

dans laquelle :

la première porteuse NB-IoT (401) est agencée en outre, lorsqu'un dispositif radio sans fil (403) appartenant à un premier groupe de dispositifs radio sans fil se connecte à la première porteuse NB-IoT (401), pour transférer le dispositif radio sans fil (403) vers la deuxième porteuse NB-IoT (402), et

l'entité réseau (400) est agencée, lorsque le dispositif radio sans fil (403) est transféré, pour indiquer au dispositif radio sans fil (403) que la deuxième porteuse NB-IoT (402) est configurée pour servir de porteuse pour d'autres dispositifs radio sans fil, et

dans laquelle l'entité réseau (400) en outre agencée pour indiquer au dispositif radio sans fil (403) qu'une adaptation de débit est autorisée autour de sous-trames non disponibles.


 
2. Entité réseau (400) selon la revendication 1, dans laquelle l'entité réseau (400) est en outre agencée pour fournir, au dispositif radio sans fil (403), des signaux de synchronisation et des informations système.
 
3. Entité réseau (400) selon l'une quelconque des revendications précédentes, dans laquelle la première porteuse NB-IoT (401) est agencée pour fournir des signaux de synchronisation et des informations système au moins au premier groupe de dispositifs radio sans fil et la deuxième porteuse NB-IoT (402) est agencée pour fournir des signaux de synchronisation et des informations système au moins au deuxième groupe de dispositifs radio sans fil.
 
4. Entité réseau (400) selon l'une quelconque des revendications précédentes, dans laquelle la première porteuse NB-IoT (401) et la deuxième porteuse NB-IoT (402) peuvent chacune être agencées pour fonctionner dans l'un parmi : un mode intrabande LTE, un mode de bande de garde LTE ou un mode autonome NB-IoT.
 
5. Entité réseau (400) selon l'une quelconque des revendications précédentes, dans laquelle la première porteuse NB-IoT (401) et la deuxième porteuse NB-IoT (402) ont des configurations de sous-trame différentes et l'entité réseau (400) est en outre agencée pour transporter des informations indicatives de la configuration de sous-trame de la deuxième porteuse NB-IoT (402) au dispositif radio sans fil (403).
 
6. Dispositif radio sans fil (403) appartenant à un premier groupe de dispositifs radio sans fil, dans lequel le dispositif radio sans fil (403) est agencé pour :

se connecter à une première porteuse Internet des objets en bande étroite, NB-IoT (401) agencée pour servir au moins le premier groupe de dispositifs radio sans fil et agencée pour transférer le dispositif radio sans fil connecté (403) à une deuxième porteuse NB-IoT (402) agencée pour servir au moins un deuxième groupe de dispositifs radio sans fil, et

recevoir une indication indiquant que la deuxième porteuse NB-IoT (402) est configurée pour servir de porteuse pour d'autres dispositifs radio sans fil, dans lequel le dispositif radio sans fil (403) est en outre agencé pour mettre en œuvre une adaptation de débit autour de sous-trames non disponibles.


 
7. Dispositif radio sans fil (403) selon la revendication 6, dans lequel le dispositif radio sans fil (403) est en outre agencé pour mettre en œuvre au moins l'un parmi :

désactiver sa chaîne de réception/transmission pendant des sous-trames non disponibles, et

utiliser la porteuse cible NPSS/NSSS.


 
8. Procédé de commande d'une entité réseau (400), le procédé comprenant :

le transfert (S501) d'un dispositif radio sans fil connecté (403) appartenant à un premier groupe de dispositifs radio sans fil depuis une première porteuse Internet des objets en bande étroite, NB-IoT (401) agencée pour servir au moins un premier groupe de dispositifs radio sans fil vers une deuxième porteuse NB-IoT (402) agencée pour servir au moins un deuxième groupe de dispositifs radio sans fil ; et

l'indication (S502) au dispositif radio sans fil transféré que la deuxième porteuse NB-IoT (402) est configurée pour servir de porteuse pour d'autres dispositifs radio sans fil, dans lequel le procédé comprend en outre l'indication, par l'entité réseau (400), au dispositif radio sans fil (403) qu'une adaptation de débit est autorisée autour de sous-trames non disponibles.


 
9. Procédé selon la revendication 8, comprenant en outre :
la fourniture, au dispositif radio sans fil, de signaux de synchronisation et d'informations système.
 
10. Procédé selon la revendication 8 ou la revendication 9, dans lequel la première porteuse NB-IoT est agencée pour fournir des signaux de synchronisation et des informations système au moins au premier groupe de dispositifs radio sans fil et la deuxième porteuse NB-IoT est agencée pour fournir des signaux de synchronisation et des informations système au moins au deuxième groupe de dispositifs radio sans fil.
 
11. Procédé selon l'une quelconque des revendications 8 à 10, dans lequel la première porteuse NB-IoT et la deuxième porteuse NB-IoT ont des configurations de sous-trame différentes et le procédé comprend en outre le transport d'informations indicatives de la configuration de sous-trame de la deuxième porteuse NB-IoT au dispositif radio sans fil.
 
12. Procédé de commande d'un dispositif radio sans fil (403) appartenant à un premier groupe de dispositifs radio sans fil, le procédé comprenant :

la connexion (S601) à une première porteuse Internet des objets en bande étroite, NB-IoT (401) agencée pour servir au moins le premier groupe de dispositifs radio sans fil et agencée pour transférer le dispositif radio sans fil connecté vers une deuxième porteuse NB-IoT (402) agencée pour servir au moins un deuxième groupe de dispositifs radio sans fil ; et

la réception (S602) d'une indication indiquant que la deuxième porteuse NB-IoT est configurée pour servir de porteuse pour d'autres dispositifs radio sans fil, dans lequel le procédé comprend en outre la mise en œuvre, par le dispositif radio sans fil (403), d'une adaptation de débit autour de sous-trames non disponibles.


 
13. Procédé selon la revendication 12, comprenant en outre :
la réception de signaux de synchronisation et d'informations système.
 
14. Procédé selon l'une quelconque des revendications 12 ou 13, dans lequel le dispositif radio sans fil est en outre agencé pour mettre en œuvre au moins l'un parmi :
désactiver sa chaîne de réception et/ou chaîne de transmission pendant des sous-trames non disponibles, et utiliser la porteuse cible NPSS/NSSS.
 




Drawing



























REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description




Non-patent literature cited in the description