WO2019035759A1

WO2019035759A1 - Network node connection control

Info

Publication number: WO2019035759A1
Application number: PCT/SE2018/050834
Authority: WO
Inventors: Anders K ERIKSSON; Chunhui Zhang; Emre YAVUZ; Johan Bergman; Martin Van Der Zee; Tuomas TIRRONEN
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2017-08-18
Filing date: 2018-08-17
Publication date: 2019-02-21

Abstract

A wireless device (12) is configured to control connection to a network node (14). The wireless device (12) is configured to receive network node connection information (18). The network node connection information (18) comprises an indication (18A) of, or comprises information (18B) from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device (12) for connecting to the network node (14). The information (18B) from which the set of zero or more allowed CE levels is derivable may for instance include an indication of zero or more CE levels barred from use by the wireless device (12) for connecting to the network node (14). Regardless, the wireless device (12) is also configured to control connection to the network node (14) based on the received network node connection information (18).

Description

NETWORK NODE CONNECTION CONTROL

BACKGROUND

Coverage enhancement in a wireless network effectively enhances the coverage within which a wireless device is able to connect to the network. A wireless device may use coverage enhancement for instance in the form of transmission repetition. Each transmission may be repeated tens or hundreds of times, depending on the level of coverage enhancement used, to improve the chances of successful reception. In the context of random access, for example, the wireless device may repeat a random access preamble on a random access channel a number of times, e.g., to increase the coverage within which the random access preamble may be received. Coverage enhancement in this way facilitates network connection by devices with challenging coverage conditions, such as utility meter devices installed in basements or other types of enhanced machine-type communication (eMTC) or narrowband internet-of-things (NB-loT) devices.

Although coverage enhancement facilitates network connection in challenging coverage conditions, coverage enhancement also threatens to load system resources (e.g., radio resources), consume device power, and increase system interference. This proves especially true for higher levels of coverage enhancement, e.g., that repeat a transmission a significant number of times.

SUMMARY

Some embodiments herein provide coverage enhancement level based barring, so that a wireless network may bar wireless devices from using certain coverage enhancement levels to connect to the network. This advantageously empowers the network in some embodiments to control the extent to which coverage enhancement contributes to system loading and interference, and/or the extent to which coverage enhancement can be used for certain services (e.g., delay- insensitive services) or by certain class/categories of devices (e.g., eMTC devices, NB-loT devices, or other low-power devices).

More particularly, embodiments herein include a method performed by a wireless device to control connection to a network node. The method comprises receiving network node connection information. The network node connection information in some embodiments comprises an indication of, or comprises information from which is derivable, a set of zero or more coverage enhancement l (CE) levels allowed to be used by the wireless device for connecting to the network node. The method also comprises controlling connection to the network node based on the received network node connection information.

In some embodiments, controlling connection to the network node comprises attempting or not attempting to establish a connection to the network node depending respectively on whether or not a CE level of the wireless device is allowed to be used by the wireless device for connecting to the network node, according to the network node connection information. Alternatively or additionally, controlling connection to the network node in some embodiments comprises selecting one or more physical random access channel resources on which to transmit a random access preamble, from among physical random access resources associated with the set of zero or more CE levels allowed to be used by the wireless device for connecting to the network node.

Embodiments herein also include a method performed by a network node to control access of a wireless device to the network node. The method comprises transmitting to a wireless device network node connection information. The network node connection information in some embodiments comprises an indication of, or comprises information from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device for connecting to the network node.

In any of the embodiments for a method performed by the wireless device or the network node, the network node connection information may comprise information from which is derivable the set of zero or more CE levels allowed to be used by the wireless device for connecting to the network. In one such embodiment, for instance, the information from which is derivable the set of zero or more CE levels allowed to be used by the wireless device for connecting to the network comprises an indication of a set of zero or more CE levels barred from use by the wireless device for connecting to the network node.

Also in any of the embodiments for a method performed by the wireless device or the network node, the network node connection information may be system information and/or be included in a system information block 14 (SIB14).

Alternatively or additionally, the network node connection information may be specific to wireless devices that have one of one or more certain power classes or that belong to one of one or more certain device categories. In some embodiments, specific to wireless devices that have one of one or more certain power classes or that belong to one of one or more certain device categories.

Embodiments herein also include corresponding apparatus, computer programs, and carriers (e.g., non-transitory computer-readable mediums).

For example, embodiments herein further include a wireless device to control connection to a network node. The wireless device is configured to receive network node connection information. The network node connection information in some embodiments comprises an indication of, or comprises information from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device for connecting to the network node. The wireless device is also configured to control connection to the network node based on the received network node connection information.

Embodiments herein further include a network node to control access of a wireless device to the network node. The network node is configured to transmit to a wireless device network node connection information. The network node connection information in some embodiments comprises an indication of, or comprises information from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device for connecting to the network node.

Embodiments also include a computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to perform the device-implemented method as described above.

Embodiments moreover include a computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the network-implemented method described above. Embodiments furthermore include a carrier containing either of the above computer programs. The carrier may be one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a block diagram of a wireless network that includes a wireless device and a network node according to some embodiments.

Figure 2A is a logic flow diagram of a method performed by a network node according to some embodiments. Figure 2B is a logic flow diagram of a method performed by a wireless device according to some embodiments.

Figure 3A is a block diagram of a wireless device according to some embodiments.

Figure 3B is a block diagram of a wireless device according to other embodiments.

Figure 4A is a block diagram of a network node according to some embodiments.

Figure 4B is a block diagram of a network node according to other embodiments.

Figure 5 is a system information block type 14 information element according to some embodiments.

Figure 6 is a system information block type 14 information element according to other embodiments.

Figure 7 is an extended access barring configuration according to some embodiments.

Figure 8 is a block diagram of a wireless communication network according to some embodiments.

Figure 9 is a block diagram of a user equipment according to some embodiments.

Figure 10 is a block diagram of a virtualization environment according to some embodiments.

Figure 1 1 is a block diagram of a communication network with a host computer according to some embodiments.

Figure 12 is a block diagram of a host computer according to some embodiments.

Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. Figure 17 is a method in accordance with some embodiments.

Figure 18 is a block diagram of an apparatus in a wireless network according to some embodiments.

DETAILED DESCRIPTION

Figure 1 shows a wireless network 10 according to some embodiments. The network 10 includes a radio access network 10A and a core network 10B. Wireless device 12 is configured to wirelessly communicate with a network node 14 (e.g., a base station) that in turn connects the wireless device 12 to the core network 10B. The core network 10B may correspondingly provide the wireless device 12 with access to one or more data networks (not shown), such as the Internet.

The wireless device 12 supports the use of coverage enhancement (CE) to connect to the network node 14. In fact, in some embodiments, the wireless device 12 supports different possible levels of CE, to provide for coverage in different possible channel conditions. Where the channel conditions are measured in terms of the reference signal received power (RSRP) of a downlink reference signal 16, for instance, the wireless device 12 supports use of or operation in different CE levels that correspond to different ranges of the RSRP, e.g., as defined by RSRP thresholds. The range within which the measured RSRP falls may therefore dictate or govern which CE level the wireless device 12 operates in according to some embodiments. If the measured RSRP falls with a range associated with relatively poor channel conditions, the wireless device 12 may operate in or use a relatively high CE level, whereas if the measured RSRP falls within a range associated with relatively good channel conditions, the wireless device 12 may operate in or use a relatively low CE level or no CE at all (i.e., normal coverage). For instance, where the wireless device 12 repeats a transmission a different number of times when operating in or using different CE levels, the wireless device 12 may repeat a transmission a relatively large number of times when operating in or using a relatively high CE level under relatively poor channel conditions, but repeat a transmission a relatively small number of times when operating in or using a relatively low CE level or no CE level at all under relatively good channel conditions. Accordingly, in these and other embodiments, different CE levels may introduce different levels of interference or channel blocking in the system.

Some embodiments herein provide CE level based barring, so that the wireless network 10 (e.g., via network node 14) may bar wireless devices (including wireless device 12) from using certain CE levels. This advantageously empowers the network 10 in some embodiments to control the extent to which CE contributes to system loading (e.g., in the form of channel blocking) and interference, and/or the extent to which CE can be used for certain services (e.g., delay-insensitive services) or by certain class/categories of devices (e.g., eMTC devices, NB-loT devices, or other low-power devices).

More particularly, the network node 14 in some embodiments is configured to transmit network node connection information 18 to the wireless device 12, e.g., as or within system information. The network node connection information 18 in some embodiments comprises an indication 18A of a set of zero or more coverage enhancement (CE) levels that are allowed to be used by the wireless device 12 for connecting to the network node 14. This set of zero or more CE levels may be referred to for convenience as a set of zero or more allowed CE levels. If the set of zero or more CE levels includes zero CE levels, no CE levels are allowed to be used. In other embodiments, rather than comprising an indication 18A of the set of zero or more allowed CE levels, the network node connection information 18 comprises other information 18B from which the set of zero or more allowed CE levels is derivable. The other information 18B may for example comprise an indication of a set of zero or more CE levels barred from use by the wireless device 12 for connecting to the network node 14. That is, the set of zero or more allowed CE levels may be derived from the set of zero or more barred CE levels. The network node connection information 18 in this way may implicitly indicate the set of zero or more allowed CE levels by specifying which of the CE levels, if any, are not allowed, i.e., which of the CE levels, if any, are barred from use by the wireless device 12. The network node connection 18 may indicate the set of zero or more allowed CE levels in these or other embodiments using flags, a bitmap with one bit per CE level, a combination of bits, or any other encoding method.

Similarly, in some embodiments, the network node connection information 18 may indicate the CE levels, if any, that are included in the set of zero or more allowed CE levels by indicating zero or more RSRP ranges that correspond to the CE levels in the set of zero or more allowed CE levels. Where the RSRP ranges are defined by RSRP thresholds, for instance, the network node connection information 18 may indicate zero or more RSRP thresholds that corresponds to the zero or more CE levels that are allowed to be used.

Note however that, in some embodiments, the network node connection information 18 is specific to (e.g., only applicable to) wireless devices that have one of one or more certain power classes (e.g., low power classes that have for instance a maximum transmit power of 14 dBm). Alternatively or additionally, the network node connection information 18 in some embodiments is specific to (e.g., only applicable to) wireless devices that belong to one of one or more certain device categories. The device categories may be differentiated for instance in terms of device type (e.g., NB-loT devices, eMTC devices, LTE devices, etc.). In this case, then, the network node connection information 18 in some embodiments may for instance be specific to NB-loT devices and/or LTE-M devices, but not LTE devices.

Regardless of how the network node connection information 18 indicates the set of zero or more allowed CE levels, or to which particular devices the information 18 may apply, the wireless device 12 is configured to control connection to the network node 14 based on this received network node connection information 18. In some embodiments, for example, the wireless device 12 may attempt or not attempt to establish a connection to the network node 14 (e.g., via a random access procedure) depending respectively on whether or not a CE level of the wireless device 12 is allowed to be used by the wireless device 12 for connecting to the network node 14, according to the network node connection information 18. That is, the wireless device 12 may be configured to attempt to establish a connection to the network node 14, such as by transmitting a random access preamble 20 on a physical random access channel (PRACH), only if the wireless device 12 is in a CE level that is allowed to be used.

In some embodiments, if the wireless device 12 attempts to establish a connection to the network node 14, based on the wireless device's CE level being allowed (i.e., not barred), the device's CE level may govern how the connection attempt is made. In the context of random access, for example, the wireless device 12 in Figure 1 may for each random access attempt 22 repeat a random access preamble 20 on a random access channel a number N of times (e.g., 2, 4, 8, 16, 32, 64, or 128 times) that corresponds to or otherwise depends on which level of CE the wireless device 12 uses or operates in.

Alternatively or additionally, the wireless device 12 may select one or more physical random access channel resources on which to transmit the random access preamble, from among physical random access resources associated with the set of zero or more allowed CE levels. In these embodiments, for instance, different sets of physical random access resources may be earmarked for use by wireless devices in different respective CE levels. Accordingly, the physical random access resources on which the wireless device 12 may transmit its random access preamble may be limited to those associated with the set of zero or more allowed CE levels.

In view of the above modifications and variations, as well as additional embodiments herein, Figure 2A depicts a method performed by a network node 14 to control access of a wireless device 12 to the network node 14 according to some embodiments. The method includes transmitting to a wireless device 12 network node connection information 18 (Block 1 10). The network node connection information 18 comprises an indication 18A of, or comprises information 18B from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device 12 for connecting to the network node 14.

In some embodiments, the method may also include generating this information 18. This may entail for instance dynamically or semi-statically

determining which CE levels, if any, to allow or to not allow, e.g., based on target interference or channel blocking to allow in the network 10.

In some embodiments, the method further includes receiving or not receiving an attempt to connect to the network node 14 depending on the network node connection information 18. If the network node 14 allows a CE level of the wireless device 12, for instance, the network node 14 may correspondingly receive an attempt to connect to the network node 14.

Figure 2B depicts a corresponding method performed by a wireless device 12 to control connection to the network node 14 according to some embodiments. The method as shown includes receiving network node connection information 18 (Block 200). The network node connection information 18 comprises an indication 18A of, or comprises information 18B from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device 12 for connecting to the network node 14. The method also includes controlling connection to the network node 14 based on the received network node connection information 18 (Block 210). In some embodiments, for example, this entails attempting or not attempting to establish a connection to the network node 14 depending respectively on whether or not a CE level of the wireless device 12 is allowed to be used by the wireless device 12 for connecting to the network node 14, according to the network node connection information 18.

Note that the wireless device 12 and network node 14 described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the wireless device 12 and network node 14 may each comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random- access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 3A for example illustrates the wireless device 12 as implemented in accordance with one or more embodiments. In some embodiments wireless device 12 is an NB-loT device or an LTE-M device. Regardless, as shown, the wireless device 12 includes processing circuitry 310 and communication circuitry 320. The communication circuitry 320 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any

communication technology. Such communication may occur via one or more antennas that are either internal or external to the wireless device 12. The processing circuitry 310 is configured to perform processing described above (e.g., in Figure 2B), such as by executing instructions stored in memory 330. The processing circuitry 310 in this regard may implement certain functional means, units, or modules.

Figure 3B illustrates a schematic block diagram of the wireless device 12 in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 8). As shown, the wireless device 12 implements various functional means, units, or modules, e.g., via the processing circuitry 310 in Figure 3A and/or via software code. These functional means, units, or modules, e.g., for implementing the method in Figure 2B herein, include for instance a receiving unit or module 410 for receiving network node connection information 18. The network node connection information 18 comprises an indication 18A of, or comprises information 18B from which is derivable, a set of zero or more coverage

enhancement (CE) levels allowed to be used by the wireless device 12 for connecting to the network node 14. Also included may be a controlling unit or module 420 for controlling connection to the network node 14 based on the received network node connection information 18.

Figure 4A illustrates the network node 14 as implemented in accordance with one or more embodiments. As shown, the network node 14 includes processing circuitry 510 and communication circuitry 520. The communication circuitry 520 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the network node 14. The processing circuitry 510 is configured to perform processing described above (e.g., in Figure 2A), such as by executing instructions stored in memory 530. The processing circuitry 510 in this regard may implement certain functional means, units, or modules.

Figure 4B illustrates a schematic block diagram of the network node 14 in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 8). As shown, the network node 14 implements various functional means, units, or modules, e.g., via the processing circuitry 510 in Figure 4A and/or via software code. These functional means, units, or modules, e.g., for implementing the method in Figure 2A herein, include for instance a transmitting unit or module 610 for transmitting network node connection information 18. The network node connection information 18 comprises an indication 18A of, or comprises information 18B from which is derivable, a set of zero or more coverage

enhancement (CE) levels allowed to be used by the wireless device 12 for connecting to the network node 14

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of a wireless device 12, cause the wireless device 12 to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of a wireless device 12 cause the wireless device 12 to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Furthermore, a computer program comprises instructions which, when executed on at least one processor of a network node 14, cause the network node 14 to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of a network node 14 cause the network node 14 to perform as described above.

Other embodiments contemplated herein will now be described, at times in a context where wireless device 12 may be referred to as a user equipment (UE). Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

A UE in enhanced coverage is a UE that requires the use of enhanced coverage functionality to access the cell. In e.g. 3GPP LTE Rel-14 two enhanced coverage modes (mode A, mode B) are supported.

A UE may access a cell using enhanced coverage functionality only if the master information block (MIB) of the cell indicates that scheduling information for system information block 1 (SIB1) SIB1 specific for bandwidth-reduced low- complexity (BL) UEs is scheduled.

For LTE Rel-15, one of the objectives for enhanced MTC (eMTC) support is to specify new UE power class(es) and signaling support to support lower maximum transmit power.

When introducing UEs with lower power, the current mechanisms for the UE to access the cell are not sufficient for controlling the usage of the physical random access control channel (PRACH) resources.

A set of PRACH resources (e.g. time, frequency, preamble) together with the number of PRACH repetitions and number of maximum preamble transmission attempts per coverage enhancement level is provided in SIB. UEs in the same enhanced coverage level use random access resources associated with the same enhanced coverage level. Time/frequency resources and repetition factor for random access response messages for UEs in enhanced coverage are derived from the used PRACH resources.

The initial cell selection of the UE is described in 3GPP technical specification (TS) 36.304 as follows. The cell selection criterion S in normal coverage is fulfilled when: Srxlev > 0 AND Squal > 0, where Srxlev is the Cell selection RX level value (dB) and Squal is the Cell selection quality value (dB).

Srxlev IS Computed as: Srxlev = Qrxlevmeas - (Qrxlevmin + Qrxlevminoffset) -

Pcompensation - Qoffset_temp. Here, Q ievmeas is the measured cell RX level value (RSRP), Qrxievmin is the minimum required RX level in the cell (dBm), and Qrxlevminoffset is the offset to the signalled Qrxievmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority public land mobile network (PLMN) while camped normally in a visited PLMN (VPLMN). With regard to Pcompensation, if the UE supports the additionalPmax in the NS-PmaxList, if present, in SIB1 , SIB3 and SIB5, Pcompensation is computed as:

max(P_EMAxi -P PowerClass, 0)— (fTlin(PEMAX2, PpowerClass)— ίΤΐίη(ΡΕΜΑΧ1 , PpowerClass)) (dB).

Else, Pcompensation is computed as: max(PEMAxi -P PowerClass, 0) (dB). Here, ΓΕΜΑΧ1 and P_EMAX2 are the maximum TX power level a UE may use when transmitting on the uplink in the cell (dBm) defined as ΡΕΜΑΧ ΙΠ TS 36.101. PEMAXI and PEMAX2 are obtained from the p-Max and the NS-PmaxList respectively in SIB1 , SIB3 and SIB5 as specified in TS 36.331. r PowerClass I s the maximum radio frequency (RF) output power of the UE (dBm) according to the UE power class as defined in TS 36.101.

Squal is computed as: Squal = Q qualmeas^— (Q qualmin + Qqualminoffset) " Qoffsettemp Qquaimeas is the measured cell quality value (RSRQ). Qquaimm is the minimum required quality level in the cell (dB). Qqualminoffset is the offset to the signalled Qquaimm taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN. Qoffsettemp is the offset temporarily applied to a cell as specified TS 36.311 (dB).

The signalled values Qrxievmmoffset and Qqualminoffset are only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLM N while camped normally in a VPLMN. During this periodic search for higher priority PLMN the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN.

If cell selection criterion S in normal coverage is not fulfilled for a cell, UE shall consider itself to be in enhanced coverage if the cell selection criterion S for enhanced coverage is fulfilled, where for Qrxievmm the UE applies coverage specific value Qrxievmin_cE (dBm) and for Qquaimm the UE applies coverage specific value Q_quaimin_cE (dB).

If cell selection criterion S in normal coverage is not fulfilled for a cell and UE does not consider itself in enhanced coverage based on coverage specific values Qrxievmin_cE and Q_quaimin_cE, UE shall consider itself to be in enhanced coverage if UE supports CE Mode B and the cell selection criterion S for enhanced coverage is fulfilled, where for Qrxievmm the UE applies coverage specific value Q_rXievmin_cEi (dBm) and for Qquaimm the UE applies coverage specific value Q_quaimin_cEi (dB). For the UE in enhanced coverage, coverage specific values Qrxievmin_cE and Qquaimin_cE (or Q_rXievmin_cEi and Q_quaimin_cEi) are only applied for the suitability check in enhanced coverage (i.e. not used for measurement and reselection thresholds).

The PRACH procedure is described in 3GPP TS 36.321 (Medium Access Control, MAC, protocol specification). For initial CE level selection, the Random Access procedure shall be performed as follows.

The procedure includes flushing the Msg3 buffer and setting the

PREAMBLE_TRANSMISSION_COUNTER to 1.

If the UE is an NB-loT UE, a BL UE or a UE in enhanced coverage, the procedure includes the following. The

PREAMBLE_TRANSMISSION_COUNTER_CE is to be set to 1. If the starting enhanced coverage level, or for NB-loT the starting number of NPRACH repetitions, has been indicated in the PDCCH order which initiated the Random Access procedure, or if the starting enhanced coverage level has been provided by upper layers, the MAC entity considers itself to be in that enhanced coverage level regardless of the measured RSRP. Else: (i) if the RSRP threshold of enhanced coverage level 3 is configured by upper layers in rsrp-ThresholdsPrachlnfoList and the measured RSRP is less than the RSRP threshold of enhanced coverage level 3 and the UE is capable of enhanced coverage level 3, then the MAC entity considers to be in enhanced coverage level 3; (ii) else if the RSRP threshold of enhanced coverage level 2 configured by upper layers in rsrp-ThresholdsPrachlnfoList and the measured RSRP is less than the RSRP threshold of enhanced coverage level 2 and the UE is capable of enhanced coverage level 2, then the MAC entity considers to be in enhanced coverage level 2; (iii) else if the measured RSRP is less than the RSRP threshold of enhanced coverage level 1 as configured by upper layers in rsrp- ThresholdsPrachlnfoList, then the MAC entity considers to be in enhanced coverage level 1 ; (iv) else the MAC entity considers to be in enhanced coverage level 0.

No matter whether the UE is an NB-loT UE, a BL UE, or a UE in enhanced coverage, the procedure then includes: set the backoff parameter value to 0 ms; for the RN, suspend any RN subframe configuration; and proceed to the selection of the Random Access Resource.

Regarding CE level ramping, if no Random Access Response or, for BL UEs or UEs in enhanced coverage for mode B operation, no PDCCH scheduling Random Access Response is received within the RA Response window, or if none of all received Random Access Responses contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble, the Random Access Response reception is considered not successful and the MAC entity shall perform the following if the UE is an NB-loT UE, a BL UE or a UE in enhanced coverage. The PREAMBLE_TRANSMISSION_COUNTER_CE is to be incremented by 1. Then, if PREAMBLE_TRANSMISSION_COUNTER_CE =

maxNumPreambleAttemptCE for the corresponding enhanced coverage level + 1 , reset PREAMBLE_TRANSMISSION_COUNTER_CE and consider to be in the next enhanced coverage level, if it is supported by the Serving Cell and the UE, otherwise stay in the current enhanced coverage level. Moreover, if the UE is an NB-loT UE: if the Random Access Procedure was initiated by a PDCCH order, select the PRACH resource in the list of UL carriers providing a PRACH resource for the selected enhanced coverage level for which the carrier index is equal to ((Carrier Index from the PDCCH order) modulo (Number of PRACH resources in the selected enhanced coverage)), and consider the selected PRACH resource as explicitly signalled. Then, proceed to the selection of a Random Access Resource.

The thresholds in the above procedure may be compensated for the lower UE power (as e.g. performed for NB-loT devices), but it may be difficult to exactly control the mechanisms for the usage of the resources with only modifying the thresholds for the lower UE power class.

There currently exist certain challenge(s), such as the following. The UE needs to estimate the RSRP and compare this estimation with the system configurated threshold to determine the CE level. The UE could end up with higher CE level than expected, for example in the following situations: (i) unreliable /inaccurate RSRP Measurement (The measurements may be unreliable, potentially 10 dB off or more); or (ii) high interference and no random access response thus ramping up CE level.

In situations such as the above or others, the UE may consume more system resources than is necessary and this is not preferred from the system perspective. It could also be beneficial from UE power saving perspective and in delay insensitive use cases if such a high CE level is not allowed to be used in such situations.

The highest PRACH CE levels, and CE mode B, are typically intended for stationary, delay-tolerant and low-load use cases. Current solutions cannot just enable high CE level UE with desired use case. Hence a solution to more flexibly configure the UE with different CE level is preferred. The new power class for LTE-MTC is intended to enable new use cases which are likely to be very mobile, e.g. wearables, and it may be desirable that these UEs do not start trying to access far-away base stations using hundreds of repetitions.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. A way to alleviate some, all or none of the above noted problems is to block some PRACH CE levels (or an equivalent mechanism), so that the lower power UEs would not be able to use the highest levels. One way to achieve such blocking can be configured by the network, such as in system information, for example by flags or combination of bits per UE power class and CE level. The network can change the blocking configuration by changing network information, e.g. system information.

One objective of certain embodiments according to the present disclosure is to be able to prevent a group of UEs, (in one particular case lower power UEs) to attempt establish a connection to the network when in certain CE level(s), e.g. avoid too many repetitions that would be required to transmit when in high CE levels such as CE Mode B, if maximum transmission power is lower. Such prevention could be indicated by the network via network information, such as system information, such as using flags or combination of bits per UE power class and CE level, or barring bitmap.

There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

In one embodiment, a method performed by a wireless device (e.g. user equipment) to control connection to a network node is provided. The method comprises: receiving a network node connection information, said network node connection information being associated with an indication of a set of CE levels allowed to be used by the wireless device, wherein the set of CE levels may have no elements, one element or more elements; and controlling connection to the network node based on the received network node connection information. Optionally, the network node connection information is system information, such as SIB. Optionally, the method further comprises processing sub-information within the network node information, wherein the sub-information may comprise a wireless device power class information. The method may further comprise providing user data; and forwarding the user data to a host computer via the transmission to the network node.

In another embodiment, a method performed by a network node (e.g. base station) to control access of a wireless device to the network node is provided. The method comprises transmitting to a wireless device a network node connection information, said network node connection information being associated with an indication of a set of CE levels allowed to be used by the wireless device, wherein the set of CE levels may have no elements, one element or more elements. The network node connected information may comprise sub-information, wherein the sub-information may comprise a wireless device power class information. The method may further comprise obtaining user data and forwarding the user data to a host computer or a wireless device.

Associated units, devices, and/or computer programs configured to implement the above methods are also provided.

Certain embodiments may provide one or more of the following technical advantage(s): Giving the network the possibility to configure various control mechanisms for network access (such as PRACH) with respect to CE levels.

More particularly, some embodiments herein are elaborated more fully below. In one embodiment, SIB2 indicates with 1 boolean bit per configured PRACH CE level whether the PRACH CE level is allowed or not for low-power-class UEs in the cell. In another embodiment, SIB2 indicates with 2 bits what's the highest PRACH CE level (in the range 0 to 3) that a low-power-class UE is allowed to access in the cell. In yet another embodiment, the ramping to the next CE level may be conditional on that the measured RSRP is above the RSRP threshold (optionally plus an offset value) for initial selection of the CE level. In another embodiment, the ramping to next CE level also depend on RSRQ. In another embodiment, offset values for lower power UEs are introduced in the cell selection criterion.

Consider now embodiments that utilize configuration in SIB14. In one embodiment, the configuration per CE level and UE power class is given in SIB14 (or SIB14-BR or SIB14-NB). The benefit of using SIB14 is that changing the contents of SIB14 does not trigger system information change notification, thus the UEs not using EAB don't need to reacquire system information. Figure 5 shows one example of how the allowed CE levels may be configured in

SystemlnformationBlockType14 in some embodiments.

The field name "14dBmAllowedCELevels" in Figure 5 is an example and refers to maximum transmit power which could be 14 dBm. In this example, there is one bit per CE level {0,1 ,2,3}, where indicates the corresponding CE level is blocked. In another example the allowed levels are listed instead. In another example the highest allowed CE level for lower power class UEs is given using two bits (i.e. range 0-3).

In another embodiment the barring per CE level is done per UE category and Access Class with existing extended access barring (EAB) parameters. In this embodiment only part of the UEs would not be able to use all of the available CE levels, depending on what Access Classes are indicated as not barred in SIB14. Figure 6 shows one example of such an embodiment.

In an alternative of this embodiment, as shown in Figure 7, there is a separate parameter in EAB-config indicating which CE levels are barred. In this case there is no need for separate field in SystemlnformationBlockType14-r15 or the like.

In another embodiment, a specific Access Class is allocated to the low power class UEs, and this Access Class is further combined with parameter indicating the allowed/barred or maximum CE level. EAB is used to indicate when the eNB wants to block certain CE levels for low power UEs. This embodiment may further require introduction of new Access Classes or categories to extend the number of currently available classes.

Additional details of some embodiments herein will now be described. The wireless device referred to in the below embodiments of Figures 8-16 may correspond to the wireless device 12 described above. Similarly, a network node referred to in the below embodiments of Figures 8-16 may correspond to the network node 14 described above.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 8. For simplicity, the wireless network of Figure 8 only depicts network 806, network nodes 860 and 860b, and WDs 810, 810b, and 810c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 860 and wireless device (WD) 810 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile

Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the

Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 806 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 860 and WD 810 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, and evolved Node Bs (eNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi- standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 8, network node 860 includes processing circuitry 870, device readable medium 880, interface 890, auxiliary equipment 884, power source 886, power circuitry 887, and antenna 862. Although network node 860 illustrated in the example wireless network of Figure 8 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 860 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 880 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 860 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 860 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 860 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 880 for the different RATs) and some components may be reused (e.g., the same antenna 862 may be shared by the RATs). Network node 860 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 860, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 860.

Processing circuitry 870 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 870 may include processing information obtained by processing circuitry 870 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 870 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 860 components, such as device readable medium 880, network node 860 functionality. For example, processing circuitry 870 may execute instructions stored in device readable medium 880 or in memory within processing circuitry 870. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 870 may include a system on a chip (SOC).

In some embodiments, processing circuitry 870 may include one or more of radio frequency (RF) transceiver circuitry 872 and baseband processing circuitry 874. In some embodiments, radio frequency (RF) transceiver circuitry 872 and baseband processing circuitry 874 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 872 and baseband processing circuitry 874 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 870 executing instructions stored on device readable medium 880 or memory within processing circuitry 870. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 870 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 870 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 870 alone or to other components of network node 860, but are enjoyed by network node 860 as a whole, and/or by end users and the wireless network generally.

Device readable medium 880 may comprise any form of volatile or nonvolatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or nonvolatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 870. Device readable medium 880 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 870 and, utilized by network node 860. Device readable medium 880 may be used to store any calculations made by processing circuitry 870 and/or any data received via interface 890. In some embodiments, processing circuitry 870 and device readable medium 880 may be considered to be integrated.

Interface 890 is used in the wired or wireless communication of signalling and/or data between network node 860, network 806, and/or WDs 810. As illustrated, interface 890 comprises port(s)/terminal(s) 894 to send and receive data, for example to and from network 806 over a wired connection. Interface 890 also includes radio front end circuitry 892 that may be coupled to, or in certain embodiments a part of, antenna 862. Radio front end circuitry 892 comprises filters 898 and amplifiers 896. Radio front end circuitry 892 may be connected to antenna 862 and processing circuitry 870. Radio front end circuitry may be configured to condition signals communicated between antenna 862 and processing circuitry 870. Radio front end circuitry 892 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 892 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 898 and/or amplifiers 896. The radio signal may then be transmitted via antenna 862. Similarly, when receiving data, antenna 862 may collect radio signals which are then converted into digital data by radio front end circuitry 892. The digital data may be passed to processing circuitry 870. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 860 may not include separate radio front end circuitry 892, instead, processing circuitry 870 may comprise radio front end circuitry and may be connected to antenna 862 without separate radio front end circuitry 892. Similarly, in some embodiments, all or some of RF transceiver circuitry 872 may be considered a part of interface 890. In still other embodiments, interface 890 may include one or more ports or terminals 894, radio front end circuitry 892, and RF transceiver circuitry 872, as part of a radio unit (not shown), and interface 890 may communicate with baseband processing circuitry 874, which is part of a digital unit (not shown). Antenna 862 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 862 may be coupled to radio front end circuitry 890 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 862 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as Ml MO. In certain embodiments, antenna 862 may be separate from network node 860 and may be connectable to network node 860 through an interface or port.

Antenna 862, interface 890, and/or processing circuitry 870 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 862, interface 890, and/or processing circuitry 870 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 887 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 860 with power for performing the functionality described herein. Power circuitry 887 may receive power from power source 886. Power source 886 and/or power circuitry 887 may be configured to provide power to the various components of network node 860 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 886 may either be included in, or external to, power circuitry 887 and/or network node 860. For example, network node 860 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 887. As a further example, power source 886 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 887. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 860 may include additional components beyond those shown in Figure 8 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 860 may include user interface equipment to allow input of information into network node 860 and to allow output of information from network node 860. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 860.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop- embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 810 includes antenna 81 1 , interface 814, processing circuitry 820, device readable medium 830, user interface equipment 832, auxiliary equipment 834, power source 836 and power circuitry 837. WD 810 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 810, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 810.

Antenna 811 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 814. In certain alternative embodiments, antenna 81 1 may be separate from WD 810 and be connectable to WD 810 through an interface or port. Antenna 81 1 , interface 814, and/or processing circuitry 820 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 81 1 may be considered an interface.

As illustrated, interface 814 comprises radio front end circuitry 812 and antenna 81 1. Radio front end circuitry 812 comprise one or more filters 818 and amplifiers 816. Radio front end circuitry 814 is connected to antenna 81 1 and processing circuitry 820, and is configured to condition signals communicated between antenna 81 1 and processing circuitry 820. Radio front end circuitry 812 may be coupled to or a part of antenna 81 1. In some embodiments, WD 810 may not include separate radio front end circuitry 812; rather, processing circuitry 820 may comprise radio front end circuitry and may be connected to antenna 81 1.

Similarly, in some embodiments, some or all of RF transceiver circuitry 822 may be considered a part of interface 814. Radio front end circuitry 812 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 812 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 818 and/or amplifiers 816. The radio signal may then be transmitted via antenna 81 1. Similarly, when receiving data, antenna 81 1 may collect radio signals which are then converted into digital data by radio front end circuitry 812. The digital data may be passed to processing circuitry 820. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 820 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 810 components, such as device readable medium 830, WD 810 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 820 may execute instructions stored in device readable medium 830 or in memory within processing circuitry 820 to provide the functionality disclosed herein.

As illustrated, processing circuitry 820 includes one or more of RF transceiver circuitry 822, baseband processing circuitry 824, and application processing circuitry 826. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 820 of WD 810 may comprise a SOC. In some embodiments, RF transceiver circuitry 822, baseband processing circuitry 824, and application processing circuitry 826 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 824 and application processing circuitry 826 may be combined into one chip or set of chips, and RF transceiver circuitry 822 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 822 and baseband processing circuitry 824 may be on the same chip or set of chips, and application processing circuitry 826 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 822, baseband processing circuitry 824, and application processing circuitry 826 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 822 may be a part of interface 814. RF transceiver circuitry 822 may condition RF signals for processing circuitry 820.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 820 executing instructions stored on device readable medium 830, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 820 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 820 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 820 alone or to other components of WD 810, but are enjoyed by WD 810 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 820 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 820, may include processing information obtained by processing circuitry 820 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 810, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 830 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 820. Device readable medium 830 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 820. In some embodiments, processing circuitry 820 and device readable medium 830 may be considered to be integrated.

User interface equipment 832 may provide components that allow for a human user to interact with WD 810. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 832 may be operable to produce output to the user and to allow the user to provide input to WD 810. The type of interaction may vary depending on the type of user interface equipment 832 installed in WD 810. For example, if WD 810 is a smart phone, the interaction may be via a touch screen; if WD 810 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 832 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 832 is configured to allow input of information into WD 810, and is connected to processing circuitry 820 to allow processing circuitry 820 to process the input information. User interface equipment 832 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 832 is also configured to allow output of information from WD 810, and to allow processing circuitry 820 to output information from WD 810. User interface equipment 832 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 832, WD 810 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment 834 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 834 may vary depending on the embodiment and/or scenario. Power source 836 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 810 may further comprise power circuitry 837 for delivering power from power source 836 to the various parts of WD 810 which need power from power source

836 to carry out any functionality described or indicated herein. Power circuitry 837 may in certain embodiments comprise power management circuitry. Power circuitry

837 may additionally or alternatively be operable to receive power from an external power source; in which case WD 810 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 837 may also in certain embodiments be operable to deliver power from an external power source to power source 836. This may be, for example, for the charging of power source 836. Power circuitry 837 may perform any formatting, converting, or other modification to the power from power source 836 to make the power suitable for the respective components of WD 810 to which power is supplied.

Figure 9 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user. A UE may also comprise any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-loT UE that is not intended for sale to, or operation by, a human user. UE 900, as illustrated in Figure 9, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable.

Accordingly, although Figure 9 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 9, UE 900 includes processing circuitry 901 that is operatively coupled to input/output interface 905, radio frequency (RF) interface 909, network connection interface 911 , memory 915 including random access memory (RAM) 917, read-only memory (ROM) 919, and storage medium 921 or the like, communication subsystem 931 , power source 933, and/or any other component, or any combination thereof. Storage medium 921 includes operating system 923, application program 925, and data 927. In other embodiments, storage medium 921 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 9, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 9, processing circuitry 901 may be configured to process computer instructions and data. Processing circuitry 901 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 901 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 905 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 900 may be configured to use an output device via input/output interface 905. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 900. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 900 may be configured to use an input device via input/output interface 905 to allow a user to capture information into UE 900. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 9, RF interface 909 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.

Network connection interface 91 1 may be configured to provide a communication interface to network 943a. Network 943a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 943a may comprise a Wi-Fi network. Network connection interface 911 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 91 1 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 917 may be configured to interface via bus 902 to processing circuitry 901 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 919 may be configured to provide computer instructions or data to processing circuitry 901. For example, ROM 919 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 921 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 921 may be configured to include operating system 923, application program 925 such as a web browser application, a widget or gadget engine or another application, and data file 927. Storage medium 921 may store, for use by UE 900, any of a variety of various operating systems or combinations of operating systems. Storage medium 921 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 921 may allow UE 900 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 921 , which may comprise a device readable medium.

In Figure 9, processing circuitry 901 may be configured to communicate with network 943b using communication subsystem 931. Network 943a and network 943b may be the same network or networks or different network or networks.

Communication subsystem 931 may be configured to include one or more transceivers used to communicate with network 943b. For example, communication subsystem 931 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.9, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 933 and/or receiver 935 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 933 and receiver 935 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of

communication subsystem 931 may include data communication, voice

communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 931 may include cellular communication, Wi-Fi communication,

Bluetooth communication, and GPS communication. Network 943b may

encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a

telecommunications network, another like network or any combination thereof. For example, network 943b may be a cellular network, a W-Fi network, and/or a near- field network. Power source 913 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 900.

The features, benefits and/or functions described herein may be

implemented in one of the components of UE 900 or partitioned across multiple components of UE 900. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 931 may be configured to include any of the components described herein. Further, processing circuitry 901 may be configured to communicate with any of such components over bus 902. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 901 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 901 and communication subsystem 931. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

Figure 10 is a schematic block diagram illustrating a virtualization

environment 1000 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes 1030. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 1020 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1020 are run in virtualization environment 1000 which provides hardware 1030 comprising processing circuitry 1060 and memory 1090. Memory 1090 contains instructions 1095 executable by processing circuitry 1060 whereby application 1020 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1000, comprises general-purpose or special- purpose network hardware devices 1030 comprising a set of one or more

processors or processing circuitry 1060, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware

components or special purpose processors. Each hardware device may comprise memory 1090-1 which may be non-persistent memory for temporarily storing instructions 1095 or software executed by processing circuitry 1060. Each hardware device may comprise one or more network interface controllers (NICs) 1070, also known as network interface cards, which include physical network interface 1080. Each hardware device may also include non-transitory, persistent, machine- readable storage media 1090-2 having stored therein software 1095 and/or instructions executable by processing circuitry 1060. Software 1095 may include any type of software including software for instantiating one or more virtualization layers 1050 (also referred to as hypervisors), software to execute virtual machines 1040 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 1040, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1050 or hypervisor. Different embodiments of the instance of virtual appliance 1020 may be implemented on one or more of virtual machines 1040, and the implementations may be made in different ways.

During operation, processing circuitry 1060 executes software 1095 to instantiate the hypervisor or virtualization layer 1050, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1050 may present a virtual operating platform that appears like networking hardware to virtual machine 1040.

As shown in Figure 10, hardware 1030 may be a standalone network node with generic or specific components. Hardware 1030 may comprise antenna 10225 and may implement some functions via virtualization. Alternatively, hardware 1030 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 10100, which, among others, oversees lifecycle management of applications 1020.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 1040 may be a software

implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 1040, and that part of hardware 1030 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1040, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1040 on top of hardware networking infrastructure 1030 and corresponds to application 1020 in Figure 10.

In some embodiments, one or more radio units 10200 that each include one or more transmitters 10220 and one or more receivers 10210 may be coupled to one or more antennas 10225. Radio units 10200 may communicate directly with hardware nodes 1030 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system 10230 which may alternatively be used for communication between the hardware nodes 1030 and radio units 10200.

With reference to Figure 11 , in accordance with an embodiment, a

communication system includes telecommunication network 1 110, such as a 3GPP-type cellular network, which comprises access network 11 11 , such as a radio access network, and core network 1 114. Access network 11 11 comprises a plurality of base stations 1 112a, 1 112b, 11 12c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 11 13a, 1 113b, 1 113c. Each base station 11 12a, 1 112b, 1 112c is connectable to core network 1 114 over a wired or wireless connection 11 15. A first UE 1 191 located in coverage area 11 13c is configured to wirelessly connect to, or be paged by, the corresponding base station 1 112c. A second UE 1192 in coverage area 11 13a is wirelessly connectable to the corresponding base station 1112a. While a plurality of UEs 1 191 , 1192 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1 112.

Telecommunication network 11 10 is itself connected to host computer 1 130, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1 130 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1121 and 1 122 between telecommunication network 1 110 and host computer 1 130 may extend directly from core network 11 14 to host computer 1 130 or may go via an optional intermediate network 1 120. Intermediate network 1120 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1 120, if any, may be a backbone network or the Internet; in particular, intermediate network 1 120 may comprise two or more sub-networks (not shown).

The communication system of Figure 11 as a whole enables connectivity between the connected UEs 1 191 , 1192 and host computer 1 130. The connectivity may be described as an over-the-top (OTT) connection 1 150. Host computer 1130 and the connected UEs 1191 , 1 192 are configured to communicate data and/or signaling via OTT connection 1 150, using access network 11 1 1 , core network 1 114, any intermediate network 1 120 and possible further infrastructure (not shown) as intermediaries. OTT connection 1 150 may be transparent in the sense that the participating communication devices through which OTT connection 1 150 passes are unaware of routing of uplink and downlink communications. For example, base station 1 112 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1 130 to be forwarded (e.g., handed over) to a connected UE 1 191. Similarly, base station 1 112 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1191 towards the host computer 1130.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 12. In communication system 1200, host computer 1210 comprises hardware 1215 including communication interface 1216 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1200. Host computer 1210 further comprises processing circuitry 1218, which may have storage and/or processing capabilities. In particular, processing circuitry 1218 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1210 further comprises software 1211 , which is stored in or accessible by host computer 1210 and executable by processing circuitry 1218. Software 121 1 includes host application 1212. Host application 1212 may be operable to provide a service to a remote user, such as UE 1230 connecting via OTT connection 1250 terminating at UE 1230 and host computer 1210. In providing the service to the remote user, host application 1212 may provide user data which is transmitted using OTT connection 1250.

Communication system 1200 further includes base station 1220 provided in a telecommunication system and comprising hardware 1225 enabling it to communicate with host computer 1210 and with UE 1230. Hardware 1225 may include communication interface 1226 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1200, as well as radio interface 1227 for setting up and maintaining at least wireless connection 1270 with UE 1230 located in a coverage area (not shown in Figure 12) served by base station 1220. Communication interface 1226 may be configured to facilitate connection 1260 to host computer 1210. Connection 1260 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1225 of base station 1220 further includes processing circuitry 1228, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1220 further has software 1221 stored internally or accessible via an external connection.

Communication system 1200 further includes UE 1230 already referred to. Its hardware 1235 may include radio interface 1237 configured to set up and maintain wireless connection 1270 with a base station serving a coverage area in which UE 1230 is currently located. Hardware 1235 of UE 1230 further includes processing circuitry 1238, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1230 further comprises software 1231 , which is stored in or accessible by UE 1230 and executable by processing circuitry 1238. Software 1231 includes client application 1232. Client application 1232 may be operable to provide a service to a human or non-human user via UE 1230, with the support of host computer 1210. In host computer 1210, an executing host application 1212 may communicate with the executing client application 1232 via OTT connection 1250 terminating at UE 1230 and host computer 1210. In providing the service to the user, client application 1232 may receive request data from host application 1212 and provide user data in response to the request data. OTT connection 1250 may transfer both the request data and the user data. Client application 1232 may interact with the user to generate the user data that it provides.

It is noted that host computer 1210, base station 1220 and UE 1230 illustrated in Figure 12 may be similar or identical to host computer 1130, one of base stations 1 112a, 1 112b, 1 112c and one of UEs 1 191 , 1192 of Figure 11 , respectively. This is to say, the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 1 1.

In Figure 12, OTT connection 1250 has been drawn abstractly to illustrate the communication between host computer 1210 and UE 1230 via base station 1220, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 1230 or from the service provider operating host computer 1210, or both. While OTT connection 1250 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 1270 between UE 1230 and base station 1220 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1230 using OTT connection 1250, in which wireless connection 1270 forms the last segment. More precisely, the teachings of these embodiments may improve one or more of usage of system resources, power consumption, delay sensitivity, and thereby provide benefits such as better system management, power consumption, etc.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 1250 between host computer 1210 and UE 1230, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1250 may be implemented in software 121 1 and hardware 1215 of host computer 1210 or in software 1231 and hardware 1235 of UE 1230, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1250 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 121 1 , 1231 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1250 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1220, and it may be unknown or imperceptible to base station 1220. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1210's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1211 and 1231 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 1250 while it monitors propagation times, errors etc.

Figure 13 is a flowchart illustrating a method implemented in a

communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step 1310, the host computer provides user data. In substep 1311 (which may be optional) of step 1310, the host computer provides the user data by executing a host application. In step 1320, the host computer initiates a transmission carrying the user data to the UE. In step 1330 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1340 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 14 is a flowchart illustrating a method implemented in a

communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step 1410 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1420, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1430 (which may be optional), the UE receives the user data carried in the transmission.

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1510 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1520, the UE provides user data. In substep 1521 (which may be optional) of step 1520, the UE provides the user data by executing a client application. In substep 151 1 (which may be optional) of step 1510, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1530 (which may be optional), transmission of the user data to the host computer. In step 1540 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 16 is a flowchart illustrating a method implemented in a

communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1610 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1620 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1630 (which may be optional), the host computer receives the user data carried in the

transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Figure 17 depicts a method in accordance with particular embodiments, the method begins at step 1702 with receiving a network node connection information, said network node connection information being associated with an indication of a set of CE levels allowed to be used by the wireless device, wherein the set of CE levels may have no elements, one element or more elements. "Associated" means that the network node connection information may comprise said indication or it may comprise other information related to said indication, and, e.g. from which set indication may be derived etc. This meaning of the term "associated" may be understood throughout other parts of the disclosure describing similar aspects. The method continues at step 1704 which includes controlling connection to the network node based on the received network node connection information.

Figure 18 illustrates a schematic block diagram of an apparatus 1800 in a wireless network (for example, the wireless network shown in Figure 8). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 810 or network node 860 shown in Figure 8). Apparatus 1800 is operable to carry out the example method described with reference to Figure 17 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 17 is not necessarily carried out solely by apparatus 1800. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1800 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some

implementations, the processing circuitry may be used to cause receiver unit 1802 and control unit 1804, and any other suitable units of apparatus 1800 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Figure 18, apparatus 1800 includes receiver unit 1802, control unit 1804, and receiver unit 1802 is configured to receive a network node connection information, said network node connection information being associated with an indication of a set of CE levels allowed to be used by the wireless device, wherein the set of CE levels may have no elements, one element or more elements; control unit 1804 is configured controlling connection to the network node based on the received network node connection information.

Embodiments herein may generally include those enumerated below. A first embodiment includes a method performed by a wireless device (e.g. user equipment) to control connection to a network node, the method comprising:

receiving a network node connection information, said network node connection information being associated with an indication of a set of CE levels allowed to be used by the wireless device, wherein the set of CE levels may have no elements, one element or more elements; and controlling connection to the network node based on the received network node connection information.

A second embodiment includes the method of embodiment 1 wherein, optionally, the network node connection information is system information, such as SIB, and, optionally, the method further comprises processing sub-information within the network node information, wherein the sub-information may comprises a wireless device power class information.

A third embodiment includes the method of any of the previous

embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

A fourth embodiment includes a method performed by a network node (e.g. base station) to control access of a wireless device to the network node, the method comprising: transmitting to a wireless device a network node connection information, said network node connection information being associated with an indication of a set of CE levels allowed to be used by the wireless device, wherein the set of CE levels may have no elements, one element or more elements.

A fifth embodiments includes the method of embodiment 4, wherein the network node connected information comprises sub-information, wherein the sub- information may comprises a wireless device power class information.

A sixth embodiment includes the method of any of the previous

embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

A seventh embodiment includes a wireless device to allow connection to a base station, the wireless device comprising: processing circuitry configured to perform any of the steps of any of embodiments 1-3; and power supply circuitry configured to supply power to the wireless device.

An eighth embodiment includes a base station to allow connection to a wireless device, the base station comprising: processing circuitry configured to perform any of the steps of any of embodiments 4-6; power supply circuitry configured to supply power to the wireless device.

A ninth embodiment includes a user equipment (UE) to allow connection to a base station, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of embodiments 1-3; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

Claims

CLAIMS What is claimed is:

1. A method performed by a wireless device (12) to control connection to a network node (14), the method comprising:

receiving (200) network node connection information (18), wherein the

network node (14) connection information comprises an indication (18A) of, or comprises information (18B) from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device (12) for connecting to the network node (14); and

controlling (210) connection to the network node (14) based on the received network node connection information (18).

2. The method of claim 1 , wherein controlling connection to the network node (14) comprises attempting or not attempting to establish a connection to the network node (14) depending respectively on whether or not a CE level of the wireless device (12) is allowed to be used by the wireless device (12) for connecting to the network node (14), according to the network node connection information (18).

3. The method of any of claims 1-2, wherein controlling connection to the network node (14) comprises selecting one or more physical random access channel resources on which to transmit a random access preamble, from among physical random access resources associated with the set of zero or more CE levels allowed to be used by the wireless device (12) for connecting to the network node (14).

4. A method performed by a network node (14) to control access of a wireless device (12) to the network node (14), the method comprising:

transmitting (110) to a wireless device (12) network node connection

information (18), wherein the network node connection information (18) comprises an indication (18A) of, or comprises information (18B) from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device (12) for connecting to the network node (14).

5. The method of any of claims 1-4, wherein the network node connection information (18) comprises information (18B) from which is derivable the set of zero or more CE levels allowed to be used by the wireless device (12) for connecting to the network.

6. The method of claim 5, wherein the information (18B) from which is derivable the set of zero or more CE levels allowed to be used by the wireless device (12) for connecting to the network comprises an indication of a set of zero or more CE levels barred from use by the wireless device (12) for connecting to the network node (14).

7. The method of any of claims 1-6, wherein the network node connection information (18) is system information.

8. The method of any of claims 1-7, wherein the network node connection information (18) is included in a system information block 14 (SIB14).

9. The method of any of claims 1-8, wherein different CE levels correspond to different respective ranges of reference signal received power, RSRP.

10. The method of any of clams 1-9, wherein the network node connection information (18) is specific to wireless devices that have one of one or more certain power classes or that belong to one of one or more certain device categories.

1 1. A wireless device (12) to control connection to a network node (14), the wireless device (12) configured to:

receive network node connection information (18), wherein the network node connection information (18) comprises an indication (18A) of, or comprises information (18B) from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device (12) for connecting to the network node (14); and control connection to the network node (14) based on the received network node connection information (18).

12. The wireless device of claim 10, configured to perform the method of any of claims 2-3 and 5-10.

13. A network node (14) to control access of a wireless device (12) to the network node (14), the network node (14) configured to:

transmit to a wireless device (12) network node connection information (18), wherein the network node connection information (18) comprises an indication (18A) of, or comprises information (18B) from which is derivable, a set of zero or more coverage enhancement (CE) levels allowed to be used by the wireless device (12) for connecting to the network node (14).

14. The network node of claim 13, configured to perform the method of any of claims 5-10.

15. A computer program comprising instructions which, when executed by at least one processor of a wireless device (12), causes the wireless device (12) to perform the method of any of claims 1-3 and 5-10.

16. A computer program comprising instructions which, when executed by at least one processor of a network node (14), causes the network node (14) to perform the method of any of claims 4-10.

17. A carrier containing the computer program of any of claims 15-16, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

18. A wireless device (12) to control connection to a network node (14), the wireless device (12) comprising communication circuitry (320) and processing circuitry (310) wherein the wireless device (12) is configured to:

19. The wireless device of claim 18, configured to perform the method of any of claims 2-3 and 5-10.

20. A network node (14) to control access of a wireless device (12) to the network node (14), the network node (14) comprising communication circuitry (520) and processing circuitry (510) wherein the network node (14) configured to:

21. The network node of claim 20, configured to perform the method of any of claims 5-10.