Selective joinder of machine-type communication user equipment with wireless cell

Summary

The embodiments describe selective connection / connection of wireless cells of user equipment (UE) with machine communication type (MTC). An MTC UE can detect a plurality of wireless cells, each provided by an evolved Node B (eNB). The MTC UE can detect eNB categories associated with individual wireless cells of the plurality of wireless cells, and can identify one or more wireless cells in a plurality of detected wireless cells on which MTC traffic is allowed based on the associated eNB categories. The MTC UE can selectively connect a wireless cell of the identified one or more wireless cells based on a cell selection criterion. In addition, an eNB can provide a wireless cell and provide, to the MTC UE, an MTC policy that identifies a circumstance under which the eNB allows MTC traffic. The eNB may be configured to selectively operate the MTC UE based on the MTC policy.

538 520

SELECTIVE COUPLING OF MACHINE COMMUNICATING USER EQUIPMENT WITH A WIRELESS CELL

Area of ​​technology

The embodiments of the present invention relate generally to the technical field of data processing, and more particularly to the selective connection / interconnection / connection of wireless cells in machine communication type user equipment.

Background

The purpose of the background description herein is to generally present the scope of the invention. The work of the inventors named herein, insofar as it is described in this background section, as well as aspects of the invention which otherwise might not qualify as prior art at the time of filing the application, are neither expressly nor implicitly considered prior art to the present specification. Unless otherwise stated herein, the methods described in this section are not known to the requirements of the present application and are not considered to be known in the art by inclusion in this section. Some User Equipment (UE) may be used primarily or exclusively for communication with other UEs or computer devices, with little or no human intervention. Examples of such UEs may include wireless weather sensors, assembly line sensors, fleet tracking meters, and so on. In many cases, these devices can log on to a wireless network and communicate with a network server, e.g. via the Internet. In connection with 3GPP Long Term Evolution (LTE) Release 10 (March 2011) (the LTE standard), such messages may be called Machine-Type Communication (MTC). In conjunction with the IEEE 802.16 standard, IEEE Std. 802.16-2009, published May 29, 2009 (WiMAX), such messages may be called machine-to-machine (M2M) communication.

538 520

UEs that communicate mainly or exclusively with other computer devices or UEs using MTC can generate very little user traffic. In many cases, that traffic can be treated with low priority. However, as the number of MTC UEs increases, the total volume of communication can still overload a network. Maintaining the connection for such a large number of MTC UEs without affecting other (eg mobile phone) traffic can be difficult.

Summary of the invention

An embodiment of the invention provides a machine communication type (MTC) type user equipment (UE) comprising processing circuits for: detecting a plurality of wireless cells, each provided with an evolved Node B (eNB); detecting eNB categories associated with individual wireless cells of the plurality of wireless cells; identifying one or more wireless cells of a plurality of detected wireless cells on which MTC traffic is allowed based on the associated eNB categories, and selectively connecting a wireless cell of the one or more identified wireless cells based on a cell selection criterion.

An embodiment of the invention ensures that the processing circuit double-checks a list of MTC-dedicated eNBs to which MTC UE is allowed to connect to the identified wireless cells and selectively further connect the wireless cell based on a result of the double-check.

An embodiment of the invention provides that the processing circuit is arranged to obtain the list of MTC-dedicated eNBs from an eNB.

An embodiment of the invention provides that the processing circuit is further arranged to provide the list of MTC-dedicated eNBs using Non-Access Stratum (NAS) signaling.

An embodiment of the invention further provides the processing circuit is arranged to determine that none of the MTC dedicated eNBs on the list can serve MTC UE and identify an eNB serving both MTC and non-MTC traffic, based on an MTC policy for identifying a circumstance. according to which the eNB allows MTC traffic.

One embodiment of the invention provides that the MTC policy is provided by an eNB or configured on the MTC UE using an Open Mobile Alliance Device Management (OMA-DM) configuration.

538 520

An embodiment of the invention provides that the circumstance comprises MTC UE located at or near a predetermined location, within a geographical area (geofence) or a certain type of MTC UE.

An embodiment of the invention provides that the cell selection criterion comprises a signal strength of the identified one or more wireless cells or the expiration of a retries counter.

An embodiment of the invention provides that the processing circuit is further arranged to: transmit the MTC UE from a connected state to a standby state, and while in the idle state, periodically detecting another plurality of wireless cells, each provided with an eNB, detecting eBB categories associated with individual wireless cells of another plurality of wireless cells; identifying one or more wireless cells of another plurality of detected wireless cells on which MTC traffic is allowed based on the associated eNB categories, and selectively initiating handoff from the wireless cell to which MTC UE previously selectively interconnected another wireless cell of the identified one or several wireless cells by another plurality of detected wireless cells based on the cell selection criterion.

An embodiment of the invention further provides that the processing circuit is arranged to retrieve, from the eNB upon detection of a network congestion, an instruction to switch from a connected mode to a standby mode or disconnect a connection to the eNB and redirect subsequent communications through another eNB.

An embodiment of the invention provides a developed Node B (eNB) comprising processing circuits for: providing a wireless cell, and providing, to a machine type communication (UTC) user equipment (MTC) detecting the wireless cell, an MTC policy identifying a circumstance according to which the eNB allows MTC traffic, and selectively earns MTC UE based on the MTC policy.

An embodiment of the invention provides that the processing circuit is further arranged to provide the MTC policy to the MTC UE using Non-Access Stratum (NAS) signaling and / or Radio Resource Control (RRC) signaling.

An embodiment of the invention provides that the processing circuit is further arranged to release MTC UE in response to a determination that a part of a network to which eNB is connected

538 520 to is overloaded, includes releasing the MTC UE including transitioning the MTC UE to a standby mode or a disconnected mode, or redirecting to a new eNB.

An embodiment of the invention provides that the part of the network is the wireless cell provided by the eNB.

An embodiment of the invention provides that the circumstance comprises that the MTC UE is located at or near a predetermined location.

An embodiment of the invention provides that the circumstance comprises that the MTC UE is within a geographical area.

An embodiment of the invention provides that the circumstance comprises that MTC UE is a particular type of MTC UE.

An embodiment of the invention further comprises that the processing circuit is arranged to: detect a plurality of entities Mobility Management Entities (MME); detect the MME categories associated with individual MMEs of the plurality of MMEs, identify one or more MMEs of the plurality of detected MMEs dedicated MTC traffic based on the associated MME categories, and select an MME of one or more identified MMEs based on an MME selection criterion.

An embodiment of the invention provides that the MME categories are detected via one or more SI interfaces.

An embodiment of the invention provides a computer readable medium comprising instructions which, in response to the execution of the instructions with a machine communication type user equipment (UE), enable the MTC UE to identify evolved Node B (eNB) categories associated with eNBs providing individual wires. cells of a plurality of wireless cells and selecting, from this plurality of wireless cells, a wireless cell for the MTC UE to unite to transmit or receive MTC traffic, based on the identified MTC categories and a cell selection criterion comprising one or more of a relative signal strength of the eNB that gives the selected wireless cell or the expiration of a retry counter.

An embodiment of the invention provides that the selection is further based on an MTC policy obtained from the selected eNB, wherein the MTC policy identifies a circumstance under which the eNB will allow MTC traffic.

538 520

An embodiment of the invention provides that the circumstance comprises that the MTC UE is located at or near a certain location.

An embodiment of the invention provides that the circumstance includes MTC UE is within a geographical area.

An embodiment of the invention provides that the circumstance comprises that the MTC UE is a particular type of UE.

One embodiment of the invention provides that the MTC categories or MTC policies are obtained using None-Access Stratum (NAS) signaling.

Brief description of the drawings

The various embodiments will be readily understood from the following detailed description with reference to the accompanying drawings. To facilitate this description, like reference numerals denote like structural elements. The embodiments are illustrated by means of examples which are not to be construed as limitations in the figures of the accompanying drawings.

Fig. 1 schematically illustrates various network devices configured according to the applicable parts of the present description to facilitate selective connection of user equipment (UE), of machine communication type (MTC), with suitable wireless cells, in accordance with the various embodiments in the present description.

Fig. 2 shows an example of exchange of communication that can be implemented between an MTC UE and an evolved Node B (eNB), in accordance with various embodiments.

Fig. 3 shows another example of an exchange of communication that can be implemented between an MTC UE and an eNB, in accordance with various embodiments.

Fig. 4 shows an example of a method that can be implemented by an MTC UE, in accordance with various embodiments.

Fig. 5 shows an example of a method that can be implemented by an eNB, in accordance with various embodiments.

Fig. 6 shows another example of a method that can be implemented by an eNB, in accordance

538 520 with various embodiments.

Fig. 7 schematically shows an example of a computer unit on which the described methods and computer-readable media can be implemented, in accordance with various exemplary embodiments.

Detailed description

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof and in which like reference numerals throughout denote like parts, and in which are shown by way of illustration the embodiments which may be practiced. It is to be understood that other embodiments may be used and that structural or logical changes may be made without departing from the scope of the present description. Therefore, the following detailed description is not to be considered in a limiting sense, but the scope of the embodiments is defined by the appended claims and their equivalents.

Different operations can in turn be described as several separate measures or operations, in a way that is most useful for understanding what is being applied for. However, the order in the description should not be interpreted as meaning that these operations are necessarily order dependent. In particular, these operations do not need to be performed in order. The described operations can be performed in a different order than the one described. Various further operations can be performed and / or described operations can be omitted in further embodiments.

For the purposes of the present specification, the terms A or B and A and / or B mean (A), (B) or (A and B). For the purposes of the present specification, the terms A, B and / or C mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).

In the description, the phrases are used in an exemplary embodiment or in exemplary embodiments, each of which may comprise one or more of the same or different exemplary embodiments. Furthermore, the terms including, including, having, and the like, as used with respect to the embodiments of the present specification, are synonymous.

As used herein, the terms module and / or logic may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and / or memory (shared , dedicated, or group) that executes one or more software programs or hardware programs (firmware), a combination logic circuit, and / or other suitable components that provide the described functionality.

538 520

Devices that can facilitate selective association of wireless cells using a machine type communicating (MTC) user equipment (UE) are shown in Figure 1. Although examples described herein provide repeated references to UE and other LTE-centric terminology, this is not intended to be limiting. ; Techniques described herein can be used in other wireless networks, such as GPS, EDGE, GPRS, CDMA, WiMAX, Ev-DO and others.

The MTC UE 100 may be configured to detect a plurality of wireless cells 102.1. In different embodiments, each wireless cell 102 may be provided by an evolved Node B (ENB). In various embodiments, the MTC UE 100 may be configured to detect eNB categories associated with individual wireless cells 102 of the plurality of wireless cells 102. The term eNB category as used herein may denote a type of service provided or not provided by an eNB. For example, some eNBs, e.g. a first eNB 104 and a second eNB 106 in Figure 1, are configured to prevent MTC traffic. An eNB can be configured in this way for a variety of reasons, such as reserving the eNB's bandwidth for traffic that is considered to have higher priority than MTC traffic.

Some eNBs, such as a third eNB 108 in Figure 1, may be provided that preliminarily or exclusively handle MTC traffic. This can conserve resources for regular eNBs such as a first eNB 104 and a second eNB 106 for other traffic. In various embodiments, an MTC-dedicated eNB may be a low cost eNB, e.g. for use in a factory or other environment with a large number of MTC UEs. This may reduce Capital Expenditure (CAPEX) as new MTC services are rolled out. In various embodiments, an MTC-dedicated eNB may send an indication, for example, as part of an MTC node ID, that it is dedicated to MTC traffic.

Still other eNBs, such as a fourth eNB 110 in Figure 1, can be configured to support regular (eg non-MTC) traffic, but also to support MTC traffic, either without qualification or in special circumstances (examples of such will to be described below). Such an eNB 110 may be referred to herein as a hybrid eNB. In various embodiments, hybrid eNB 110 may transmit an indication, e.g. as part of an MTC node ID, that it accepts MTC traffic in any or all circumstances.

In various embodiments, eNBs can be configured to transmit or otherwise make available their categories and other information that can be used to connect cells that they

538 520 provides. In Fig. 2, for example, MTC-dedicated eNB 108 is displayed when it broadcasts its category (MTC-dedicated). The MTC UE 100 can receive this broadcast category, along with categories broadcast by other eNBs (eg 104,106,110, not shown in Fig. 2).

In various embodiments, upon detection of the plurality of wireless cells and their categories, the MTC UE 100 may be configured to identify one or more wireless cells in the plurality of detected wireless cells 102 on which MTC traffic is allowed. In other embodiments, this identification may be based on the detected eNB categories associated with each wireless cell. connect. In other embodiments, the list of MTC-dedicated eNBs may be obtained from an eNB, e.g. using NAS signaling.

In other embodiments, a list of MTC-dedicated eNBs to which the MTC UE 100 is allowed to connect can be maintained, e.g. through different devices in different places. In some embodiments, the list may be maintained by the MTC UE 100. In addition, or alternatively, the list may be maintained through network devices and made available via Non-Access Stratum (NAS) signaling. In various embodiments, the list may contain MTC-dedicated eNBs belonging to a particular Public Land Mobile Network (PLMN) identity. For example, the list may be a Closed Subscriber Group (CSG) whitelist. The MTC UE 100 can select the most suitable detected cell that is also on this list, e.g. based on a cell selection criterion.

Once the MTC UE 100 has matched identified wireless cells 102 of the detected cells to allowed MTC dedicated cells on the list, in various embodiments, the MTC UE 100 may selectively combine one of the matching wireless cells 102, e.g. based on a cell selection criterion. An example of this is shown in Fig. 2.1 different embodiments can, after a successful connection, MTC UE be configured to store connection information to facilitate future connections and wireless cell choices.

Cell selection criteria may be useful, e.g. through MTC UE 100, to choose from a plurality of wireless candidate cells, and can come in various forms. In various embodiments, a cell selection criterion may be a signal strength of one or more of the identified wireless cells 102. For example, the MTC UE 100 may determine that the third eNB 108 has a stronger signal.

538 520 than a cell from another MTC-dedicated eNB (not shown), and can selectively connect the wireless cell 102 provided by the third eNB 108, on that basis. Other cell selection criteria may include, but are not limited to, available cell bandwidth, number of attempts to count outputs, connection type, ping return time, available eNB resources, and so on.

Situations may arise where no identified MTC-dedicated eNBs are included in the list, or where no MTC-dedicated eNBs meet one or more cell selection criteria. In such cases, the MTC UE 100 may identify one or more wireless cells 102 that both MTC and non-MTC traffic are allowed (e.g., provided by hybrid ENB 110). For example, in Figure 3, hybrid ENB 110 may provide, e.g. to MTC UE 100 individually or as part of a broadcast, MTC policy dictating circumstances under which MTC traffic is and is not allowed on a wireless cell 102 is provided by hybrid ENB 110. Based on this policy and similar MTC policies in conjunction with other hybrid eNBs MTC UE can identify which of these hybrid eNBs, if any, the MTC UE 100 would be allowed to go given its current circumstances.

In various embodiments, the MTC policy may be provided by the hybrid eNB 110 using a dedicated UE signaling (eg NAS). In various embodiments, this MTC policy may be included in the transmitted eNB category information depicted in Figure 2. An MTC policy may be provided to the MTC UE in other ways as well. For example, in some embodiments, Open Mobile Alliance Device Management (OMA-DM) protocols may be used to configure the MTC UE 100 with one or more MTC policies.

The MTC policy may indicate circumstances under which MTC traffic is permitted for a wireless cell 102 provided from the hybrid eNB 110. For example, MTC UE at or near a particular location, e.g. within a geographical area may be served, while MTC UEs located elsewhere may not be served. As another example, MTC UEs of a certain type can be operated, while MTC UEs of another type cannot be operated. As shown in Figure 3, the MTC UE 100 can use this policy, along with various MTE UE attributes such as its location (eg based on Global Positioning System, or GPS coordinates) or type, to determine whether hybrid eNB 110 will allow MTC traffic to / from the MTC UE 100 on the wireless cell 102. Then the MTC UE 100 can select and merge a specific eNB, based on cell selection criteria.

538 520

A UE may experience periods of downtime where it does not send or receive communications. In some cases, for example when a UE switches to a standby mode, e.g. to save energy and / or computer or network resources. However, a UE can move around while in standby mode. To maintain a sufficiently good wireless connection, a standard UE (eg a mobile phone) in standby mode, e.g. in accordance with the Third Generation Partnership Project (3GPP) Technical Specification (TS) 36,304, regularly search for permitted cells to which it can connect in the event that the wireless cell that last served it is no longer the best option. For example, in standby mode, a UE may use a CSG whitelist that identifies cells to which the UE is allowed to connect (for example, cells provided by a particular wireless carrier or belonging to a particular PLMN identity).

Similar to standard UEs, in standby mode, MTC UEs can regularly search for authorized cells that support or are provided by MTC-dedicated eNBs. If more than one allowed cell provided by an MTC-dedicated eNB is found, then the UE can rank the cells by the cell selection criteria. If no allowed cells, provided by MTC-dedicated eNBs, are found (or that meet the cell selection criteria), then the UE in standby mode can switch to a camp in any cell mode in which it searches more broadly for allowed cells (eg by a CSG) provided by hybrid eNBs that allow MTC traffic along with other traffic.

For example, the MTC UE 100, in various embodiments, and when in Radio Resource Control (RRC) standby mode, may be configured to periodically detect another plurality of wireless cells 102, e.g. which may differ from a plurality of wireless cells 102 detected when the MTC UE 100 was last connected to a wireless cell 102. Similar to when it was first connected to a wireless cell 102, the MTC UE 100 can be configured to detect eNB categories associated with individual wireless cells in another plurality of wireless cells, and to identify one or more wireless cells of another plurality of detected cells. wireless cells on which MTC traffic is allowed based on the associated eNB categories. In various embodiments, the MTC UE 100 may be configured to selectively initiate handoff from a wireless cell 102 to which the MTC UE is already connected to another wireless cell 102 by the one or more identified wireless cells based on a cell selection criterion.

Referring to Figure 4, an example of a method 400 that may be implemented by an MTC UE such as an MTC UE 100 is shown in Figure 1, in accordance with various embodiments. At block 402, the MTC UE can detect a plurality of wireless cells (e.g., 102 in Fig. 1), each provided

538 520 of an eNB (eg 104 to 110 in Fig. 1). At block 404, the MTC UE can detect eNB categories associated with the individual wireless cells in the plurality of wireless cells.

At block 406, the MTC UE can identify one or more wireless cells of the plurality of detected wireless cells on which MTC traffic is allowed, e.g. based on the associated eNB categories. At block 408, the MTC UE can double-check one or more identified wireless cells against a list of MTC-dedicated eNBs to which the MTC UE is permitted to connect (eg, a CSG stored in the memory of the MTC UE 100 or maintained on the NAS). If, at block 408, one or more matching wireless cells are found, at block 410 the MTC UE will be able to selectively connect the most suitable matching wireless cell provided by an MTC-dedicated eNB based on a cell selection criterion.

However, if in block 408 no matching wireless cells are found in the list, then in block 412 MTC UE can selectively connect a wireless cell from via a hybrid eENB (eg 110 in Fig. 1) which allows both MTC and non-MTC traffic, e.g. based on cell selection criteria. In various embodiments, this selective connection may be based on an MTC policy of the hybrid eNB that identifies a circumstance according to which the hybrid eNB allows MTC traffic. As mentioned above, a hybrid eNB can make the MTC policy available in various ways, for example via NAS signaling (in some cases with the eNB categories).

Referring now to Fig. 5, there is shown an example of a method 500 that may be implemented by an eNB (eg, 104-110), in accordance with various embodiments. Different operations in method 500 can be added or removed depending on whether the eNB-implemented method 500 is an MTC-dedicated eNB (eg 108), a hybrid eNB (eg 110) or an eNB that is not allows MTC traffic (eg 104, 106).

At block 502, the eNB may provide a wireless cell, such as one of the wireless cells 102 depicted in Fig. 1. At block 504, the eNB may provide, e.g. to MTC UE 100 (which may have detected the wireless cell 102 provided by the eNB), an MTC category that generally indicates whether MTC traffic is allowed on the wireless cell provided by the eNB. If the eNB is a member of an MTC category that prohibits MTC traffic (e.g. 104,106), MTC UE 100 can not communicate with eNB further and method 500 can be terminated. If the nNB is an MTC-dedicated eNB (eg 108), then the MTC UE 100 can connect to the wireless cell

538 520 provided by the eNB, or other wireless cell from another MTC-dedicated eNB, based on the cell selection criteria of the MTC UE 500.

If the eNB is a hybrid eNB (eg 110), in block 506, the eNB may provide, e.g. to MTC UE 100, an MTC policy that identifies a circumstance under which the eNB allows MTC traffic. As mentioned above, the MTC policy may indicate that the eNB will serve MTC UEs located at or near a particular location, e.g. within a geographical area, or that it will serve MTC UE of a particular type. In various embodiments, the MTC category and / or MTC policy can be provided to the MTC UE 100 using NAS signaling. At block 508, the eNB can selectively operate the MTC UE 100 based on the MTC policy.

In various embodiments, at block 510, the eNB may be configured to determine that a portion of a network to which the eNB is connected is overloaded. For example, the eNB may determine that its wireless cell is overloaded with network traffic, e.g. due to its traffic density if it exceeds a predetermined threshold value. In such cases, at block 512, the eNB may be configured to deliver one or more MTC UEs, for example, by using an RRCConnectionRelease message with a specific RRC Release Indicator. In various embodiments, the RRC Release Indicator may cause one or more MTCs to switch to a state / mode in which the MTC UE is disconnected from the network without re-registration. In various embodiments, the RRC Release Indicator may cause one or more MTC UEs to enter a standby / standby mode. In various embodiments, the RRC Release Indicator may redirect MTC UEs to another eNB.

In other embodiments, other components of a network besides eNBs may be dedicated to MTC communication, e.g. to include MTC traffic and conserve network resources for non-MTC components for non-MTC traffic. An example of such a device that can come in MTC-dedicated form is a Mobility Management Entity (MME).

For example, in Figure 1, there are two common MMEs 112 that are not particularly dedicated to MTC traffic and an MTC-dedicated MME 114. The MTC-dedicated eNB 108 and the hybrid eNB 110 can be configured to select the MTC-dedicated MME 114 for use. whenever possible, but may also use the non-MTC dedicated MME 112 if necessary (for example, if the MTC dedicated MME 114 is disabled or overloaded). In various embodiments, similar to the MTC-dedicated eNB 108, the MTC-dedicated

538 520

MME 114 be a low cost MME, such as. can be set up in a factory or in another environment with a large number of MTC UEs. This may further reduce CAPEX as new MTC services are rolled out. It is to be understood that the configuration of MMEs and eNBs shown in Figure 1 is for illustration only, and that any other configuration or arrangement of MMEs and eNBs is conceivable.

Fig. 6 shows an example of a method 600 that can be implemented by different eNBs such as MTC-dedicated eNBs 108 and hybrid-eNBs 110, to utilize an MTC-dedicated MME. At block 602, the eNB can detect multiple Mobility Management Entities (MMEs). At block 604, the eNB can detect MME categories associated with individual MMEs by the plurality of MMEs. For example, MMEs can provide their individual MME categories via an SL interface.

At block 606, the eNB can identify one or more MMEs of the plurality of detected MMEs dedicated to MTC traffic based on the associated MME categories. For example, the hybrid eNB 110 in Figure 1 may identify MTC-dedicated MME 114. At block 608, the eNB may select an MME from the one or more MMEs identified at block 606, based on an MME selection criterion. If there was only one MTC-MME identified in block 606, the eNB could simply use that MME.

Fig. 7 illustrates an example of a computer unit 700, in accordance with various embodiments.

The MTC UE 100 or any of the eNBs (e.g., 104-110) described herein may be implemented on a computer unit such as the computer unit 700. The computer unit 700 may include a number of components, one or more processors 704, and at least one communication chip 706.1. these processors 704 each be a processor core. In different embodiments, at least one communication chip 706 may also be physically and electrically connected to the one or more processors 704.1. Additional implementations, the communication chip 706 may be part of one or more processors 704.1 In different embodiments, the computer unit 700 may include a printed circuit board (PCB) 702. For these embodiments, one or more processors 704 and communication chips 706 may be provided thereon. In alternative embodiments, the various components may be connected without the use of PCB 702.

Depending on its applications, the computer unit 700 may include other components which may or may not be physically and electrically connected to the PCB 702. These other components

538 520 includes, but is not limited to, volatile memories (such as Dynamic Random Access Memory 708, also known as DRAM), non-volatile memories (such as Read Only Memory 710, also known as ROM), flash memory 712, an input / output controller 714, a digital signal processor (not shown), a crypto processor (not shown), a graphics processor 716, one or more antennas 718, a display (not shown) shown), a touch screen 720, a touch screen 722, a battery 724, an audio codec (not shown), a video codec (not shown), a global positioning system (GPS) 728, a compass 730, an accelerometer (not shown) , a gyroscope (not shown), a speaker 732, a camera 734, one or more other sensors 736 (eg a barometer, Geiger counter, thermometer, viscometer, Rheometer, altimeter or other sensors, eg that can be found in different manufacturing environments or used in other applications), or more a mass storage device ( such as a hard disk, an SSD, a CD (CD), a Digital Versatile Disk (DVD) (not shown), and so on. In various embodiments, the processor 704 may be integrated on the same array as other components to form a System on Chip (SoC).

In other embodiments, volatile memories (e.g., DRAM 708), non-volatile memories (e.g. ROM 710), flash memory 712, and mass storage devices include programming instructions configured to enable the computer device 700, in response to execution in one or more processors 704, to practice all or selected aspects of the data exchange shown in Figures 2. and 3, or in methods such as 400, 500 or 600, depending on which computer unit 700 is used for the implementation. More specifically, one or more of the memory devices such as the volatile memories (e.g. DRAM 708), non-volatile memories (eg ROM 710), flash memories 712 and the mass storage device include temporal and / or durable copies of instructions which, when executed by one or more processors 704, enable the computer unit 700 operating one or more modules 738 to practice all or selected aspects of the data exchange shown in Figures 2 or 3, or the methods 400, 500 or 600, depending on which computer unit 700 is used for the implementation.

The communication chip 706 may enable wired and / or wireless communication for the transmission of data to and from the computer unit 700. The term wireless and its variants may be used to describe circuits, devices, systems, methods, techniques, communication channels, etc. which may communicate data using modulated electromagnetic radiation through a non-solid medium. The term does not mean that the associated devices do not contain any cables, but in some embodiments they may not.

538 520

The communication chip 706 may implement any of a number of wireless standards or protocols, including but not limited to IEEE 702.20, General Packet Radio Service (GPRS), Evolution Data Optimized (Ev-DO), Evolved High Speed ​​Packet Access (HSPA +), Evolved High Speed Downlink Packet Access (HSDPA +), Evolved High Speed ​​Uplink Packet Access (HSUPA +), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Digital Enhanced Cordless Telecommunications (DECT), Bluetooth, derivatives thereof, as well as all other wireless protocols identified as 3G, 4G, 5G, and the like. The computer unit 700 may include a plurality of communication chips 706. For example, a first communication chip 706 may be dedicated to wireless communications over shorter distances such as Wi-Fi and Bluetooth and a second communication chip 706 may be intended for wireless communication over longer distances such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, Ev-DO and similar.

In various implementations, the computer unit 700 may be a Laptop, a Netbook, a Notebook, an Ultrabook, a Smartphone, a Tablet, a Personal Digital Assistant (PDA), an ultraportable computer, a mobile phone, a desktop computer, a server, a printer, a scanner, a monitor, a set-top box, an entertainment controller (such as a game console), a digital camera, a portable music player, or a digital video camera. In further implementations, the computer unit 700 may be any other electronic device that processes the data.

Embodiments of devices, packages, computer-implemented methods, systems, devices, and computer-readable media (volatile and durable) are described herein for selective connection of MTC UE wireless cells. In various embodiments, a plurality of wireless cells can be detected, each provided with an eNB. In various embodiments, eNB categories associated with the individual wireless cells of the plurality of wireless cells can be detected. In various embodiments, one or more wireless cells of the plurality of detected wireless cells on which MTC traffic is allowed can be identified based on the associated eNB categories. In various embodiments, an MTC UE may selectively connect a wireless cell of the identified one or more wireless cells based on a cell selection criterion.

In various embodiments, the MTC UE may receive, for example, from the eNB upon detection of a network congestion, an instruction to switch from a connected mode to a standby mode.

538 520 or a disconnected mode, and / resolve a connection to the eNB and redirect subsequent communication through another eNB.

In various embodiments, a list of MTC-dedicated eNBs that MTC UE is allowed to connect to can be double-checked against the identified wireless cells. In various embodiments, the MTC UE can be selectively associated with the wireless cell also based on a result of the dual control. In various embodiments, the list of MTC-dedicated eNBs can be obtained from an eNB and / or via NAS signaling.

In various embodiments, it can be determined that none of the MTC-dedicated eNBs on the list can serve MTC UE. In various embodiments, an eNB that serves both MTC and non-MTC traffic can be identified, for example, based on an MTC policy for the eNB that identifies a circumstance under which the eNB allows MTC traffic. In various embodiments, the MTC policy may be provided by an eNB or configured on the MTC UE using an OMA-DM configuration. In various embodiments, the circumstance included in the MTC policy may include the MTC UE located at or near a predetermined location, within a geographic area or a particular type of MTC UE.

In various embodiments, the cell selection criterion may include a signal strength of the identified wireless cells or the output of a retry counter. In various embodiments, the MTC UE may be transmitted from a connected mode to a sleep mode. In various embodiments, the MTC UE, while in sleep mode, may periodically detect a different plurality of wireless cells, each provided by an eNB. In various embodiments, the eNB categories associated with individual wireless cells of the second plurality of wireless cells can be detected. In other embodiments, one or more wireless cells of another plurality of detected wireless cells on which MTC traffic is allowed may be identified from the associated eNB categories. In various embodiments, handoff from the wireless cell to which MTC UE previously selectively connected to another wireless cell of the identified one or more wireless cells of the second plurality of detected wireless cells may be selectively initiated based on the cell selection criterion.

In various embodiments, an eNB may be configured to provide a wireless cell. In various embodiments, the eNB may be configured to provide, to an MTC UE that detects the wireless cell, an MTC policy that identifies a circumstance under which

538 520 eNB will allow MTC traffic. In various embodiments, the eNB can be configured to selectively operate the MTC UE based on the MTC policy. In other embodiments, the eNB may be configured to provide the MTC policy to the MTC UE using dedicated UE signaling.

In various embodiments, the eNB may be configured to release the MTC UE in the event that a portion of a network to which the eNB is connected is overloaded. In various embodiments, the release may include the transition of the MTC UE to an inactive or disconnected position, and / or redirection to a new eNB. In various embodiments, the portion of the network may be the wireless cell provided by the eNB.

In other embodiments, the eNB may be configured to detect a plurality of MMEs. In various embodiments, the eNB may be configured to detect MME categories associated with individual MMEs by the plurality of MMEs. In various embodiments, the eNB may be configured to identify one or more MMEs of the plurality of detected MMEs dedicated to MTC traffic based on the associated MME categories. In various embodiments, the eNB may be configured to select an MME from the identified one or more MMEs based on an MME selection criterion. In various embodiments, the MME categories can be detected over one or more Sl interfaces.

Although certain embodiments have been illustrated and described herein to clarify the invention, this application is intended to cover all adaptations or variations of the embodiments discussed herein. The intent of the embodiments described herein is limited only by the claims.

Where the description refers to one or a first element or the like, such reference refers to one or more such elements, without requiring or excluding two or more such elements. In addition, ordinal number indicators are used (e.g. first, second or third) for identified parts to distinguish the elements, but this does not indicate or imply a required or limited number of such elements, nor do they indicate a particular position or order of such elements unless otherwise specified.