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

• US 10,327,207 B2
• Filed: 10/30/2014
• Issued: 06/18/2019
• Est. Priority Date: 05/11/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Jain, Puneet, Bangolae, Sangeetha, Tarradell, Marta Martinez, Fong, Mo-Han
• Primary Examiner(s): Navar, Erica
• Application Number:
  US14/528,747
• Publication Number:
  US 20150056994A1
• Time in Patent Office: 1,692 Days
• Field of Search: 4554351-4353, 455436-444, 455450, 455509, 455512-514
• CPC Class Codes: H04B 1/56 with provision for simultaneous communication in two directions
• CPC Class Codes: H04B 15/00 Suppression or limitation of noise or interference by means associated with receiver H04B1/10
• CPC Class Codes: H04B 7/024 Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0456 Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
• CPC Class Codes: H04B 7/0473 taking constraints in layer or codeword to antenna mapping into account
• CPC Class Codes: H04B 7/0486 taking channel rank into account
• CPC Class Codes: H04B 7/0626 Channel coefficients, e.g. channel state information [CSI]
• CPC Class Codes: H04B 7/063 Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
• CPC Class Codes: H04B 7/0632 Channel quality parameters, e.g. channel quality indicator [CQI]
• CPC Class Codes: H04B 7/0639 Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
• CPC Class Codes: H04B 7/0647 Variable feedback rate
• CPC Class Codes: H04B 7/065 Variable contents, e.g. long-term or short-short
• CPC Class Codes: H04B 7/26 at least one of which is mobile
• CPC Class Codes: H04J 3/00 Time-division multiplex systems H04J14/00 takes precedence; relay systems H04B7/14; selecting techniques H04Q
• CPC Class Codes: H04J 3/1694 Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers Passive Optical Networks H04Q11/0062
• CPC Class Codes: H04J 3/26 in which the information and the address are simultaneously transmitted
• CPC Class Codes: H04L 1/0026 Transmission of channel quality indication
• CPC Class Codes: H04L 1/1803 Stop-and-wait protocols
• CPC Class Codes: H04L 1/1822 involving configuration of automatic repeat request [ARQ] with parallel processes
• CPC Class Codes: H04L 27/2627 : Modulators
• CPC Class Codes: H04L 5/0007 : the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/001 : the frequencies being arranged in component carriers
• CPC Class Codes: H04L 5/0035 : Resource allocation in a cooperative multipoint environment
• CPC Class Codes: H04L 5/0053 : Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0073 : Allocation arrangements that take into account other cell interferences for intercell interference mitigation or co-ordination in orthogonal multiplex systems H04J11/005
• CPC Class Codes: H04L 5/0096 : Indication of changes in allocation
• CPC Class Codes: H04L 5/14 : Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 5/1469 : using time-sharing
• CPC Class Codes: H04L 65/00 : Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 69/324 : in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04W 16/14 : Spectrum sharing arrangements between different networks
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 36/0061 : of neighbour cell information
• CPC Class Codes: H04W 36/0088 : Scheduling hand-off measurements
• CPC Class Codes: H04W 36/0094 : Definition of hand-off measurement parameters
• CPC Class Codes: H04W 36/03 : Reselecting a link using a direct mode connection
• CPC Class Codes: H04W 36/04 : Reselecting a cell layer in multi-layered cells
• CPC Class Codes: H04W 36/16 : Performing reselection for specific purposes
• CPC Class Codes: H04W 36/18 : for allowing seamless reselection, e.g. soft reselection
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 36/32 : by location or mobility data, e.g. speed data
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/023 : using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/06 : Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/90 : Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 48/20 : Selecting an access point
• CPC Class Codes: H04W 52/0209 : in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0225 : using monitoring of external events, e.g. the presence of a signal
• CPC Class Codes: H04W 52/0229 : where the received signal is a wanted signal
• CPC Class Codes: H04W 52/0235 : where the received signal is a power saving command
• CPC Class Codes: H04W 52/0251 : using monitoring of local events, e.g. events related to user activity
• CPC Class Codes: H04W 56/00 : Synchronisation arrangements
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/044 : based on the type of the allocated resource
• CPC Class Codes: H04W 72/12 : Wireless traffic scheduling
• CPC Class Codes: H04W 72/1215 : for collaboration of different radio technologies
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/27 : between access points
• CPC Class Codes: H04W 72/30 : Resource management for broadcast services
• CPC Class Codes: H04W 72/51 : based on terminal or device properties
• CPC Class Codes: H04W 72/54 : based on quality criteria
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 72/542 : using measured or perceived quality
• CPC Class Codes: H04W 72/56 : based on priority criteria
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/18 : Management of setup rejection or failure
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Embodiments are described herein for selective joinder of wireless cells by machine-type communication (“MTC”) user equipment (“UE”). An MTC UE may detect a plurality of wireless cells, each provided by an evolved Node B (“eNB”). The MTC UE may detect eNB categories associated with individual wireless cells of the plurality of wireless cells, and may identify one or more wireless cells of the plurality of detected wireless cells on which MTC traffic is permitted based on the associated eNB categories. The MTC UE may selectively join a wireless cell of the one or more identified wireless cells based on a cell selection criterion. Additionally, an eNB may provide a wireless cell and provide, to an MTC UE, an MTC policy that identifies a circumstance under which the eNB will permit MTC traffic. The eNB may be configured to selectively serve the MTC UE based on the MTC policy.

Claims

1. An evolved Node B (“

eNB”

) comprising;

first circuitry to connect to a plurality of mobility management entities (“

MMEs”

) and obtain communications from individual MMEs of the plurality of MMEs over corresponding S1 interfaces; and

second circuitry, coupled with the first circuitry, to;

determine, based on a first communication of the communications obtained over a first S1 interface of the S1 interfaces, a first MME of the plurality of MMEs that is dedicated to handle Machine-Type Communication (“

MTC”

) network traffic associated with a first priority level, which is lower than a second priority level associated with other network traffic,

determine, based on overload information in the first communication or in another first communication obtained over the first S1 interface, whether the first MME is overloaded, and

select the first MME for a user equipment (“

UE”

) based on an indication that the UE is to generate MTC network traffic when the first MME is not overloaded according to the overload information, or

select a second MME of the plurality of MMEs for the UE when the first MME is overloaded according to the overload information regardless of whether the second MME is dedicated to handle network traffic associated with the first priority level.

2. The eNB of claim 1, wherein the eNB is to receive a communication from the UE that includes the indication.

3. The eNB of claim 1, further comprising:

third circuitry, coupled with the second circuitry, to provide a wireless cell to serve the UE.

4. The eNB of claim 3, wherein the third circuitry is to send, to the UE, a Radio Resource Control (“

RRC”

) message to release the UE based on a determination that the first MME is overloaded.

5. The eNB of claim 3, wherein the third circuitry is to provide, to the UE, an MTC policy that identifies a circumstance under which the eNB is to permit MTC traffic.

6. The eNB of claim 5, wherein the circumstance comprises at least one of the UE being at or near a predefined location, within a geofence, or being a particular type of UE.

7. The eNB of claim 1, further comprising:

a system on chip (“

SoC”

) including;

a processor; and

a communication chip,

wherein the first circuitry and the second circuitry are integrated within at least one of the processor or the communication chip.

8. An evolved Node B (“

eNB”

) comprising;

first circuitry to connect with a plurality of mobility management entities (“

MMEs”

) and obtain communications from individual MMEs of the plurality of MMEs over corresponding interfaces; and

second circuitry, coupled with the first circuitry, to;

determine a first MME of the plurality of MMEs that is dedicated to handle Machine-Type Communication (“

MTC”

) traffic, wherein the second circuitry is to determine the first MME is dedicated to handle MTC traffic based on a first communication of the communications obtained over a first S1 interface of the S1 interfaces,

determine, based on overload information in the first communication or in another first communication obtained over the first S1 interface, whether the first MME is overloaded with MTC traffic, and

select the first MME dedicated to handle MTC traffic for a user equipment (“

UE”

) based on an indication that the UE is to generate MTC traffic and when the first MME is not overloaded according to the overload information, or

select a second MME of the plurality of MMEs for the UE when the first MME is overloaded according to the overload information regardless of whether the second MME is dedicated to handle MTC traffic.

9. The eNB of claim 8, further comprising:

third circuitry, coupled with the second circuitry, to provide a wireless cell to serve the UE.

10. The eNB of claim 9, wherein the third circuitry is to release, using Radio Resource Control (“

RRC”

) signaling, the UE based on the overload information.

11. The eNB of claim 9, wherein the third circuitry is to provide, to the UE, an MTC policy that identifies a circumstance under which the eNB is to permit MTC traffic.

12. The eNB of claim 11, wherein the circumstance comprises at least one of the UE being at or near a predefined location, within a geofence, or being a particular type of UE.

13. The eNB of claim 8, further comprising:

a system on chip (“

SoC”

) including;

a processor; and

a communication chip,

wherein the first circuitry and the second circuitry are integrated within at least one of the processor or the communication chip.

14. One or more non-transitory computer-readable media comprising computing device-executable instructions, wherein the instructions, in response to execution by an evolved Node B (“

eNB”

), cause the eNB to;

obtain a communication over an S1 interface;

determine, based on the communication, a mobility management entity (“

MME”

) from a plurality of MMEs that handles network traffic associated with a Machine-Type Communication (“

MTC”

) communication category;

determine network traffic received from a user equipment (“

UE”

) that is associated with the MTC communication category;

determine, based on overload information in another communication obtained over the S1 interface, whether the MME is overloaded;

release a radio resource control connection with the UE when the other communication indicates that the MME is overloaded;

associate the UE with the MME based on the determination that the MME is associated with the MTC communication category and the MTC traffic from the UE and based on the determination that the MME is not overloaded; and

associate the UE with another MME of the plurality of MMEs based on the determination that the MME is overloaded regardless of whether the other MME handles network traffic associated with the MTC communication category.

15. The one or more non-transitory computer-readable media of claim 14, wherein the instructions further cause the eNB to:

send, to the UE, a Radio Resource Control (“

RRC”

) message to release a request from the UE based on a determination that the MME is overloaded.

16. The one or more non-transitory computer-readable media of claim 14, wherein the instructions further cause the eNB to:

provide, to the UE, an MTC policy that identifies a circumstance under which the eNB is to permit MTC traffic.