JP2016529792A - Managing wireless connections based on movement - Google Patents

Abstract

Methods, systems, and apparatus for avoiding temporary wireless connections are described. In one method, a first connection with a first access point may be used for data transmission. The motion state of the mobile device can be determined based on sensor data from at least one sensor in the mobile device. A second access point can be identified. A determination may be made to use the second access point for data transmission based at least in part on the motion state of the mobile device.

Description

Cross-reference This patent application is filed on Aug. 7, 2013 and assigned to the assignee of this application by US Patent Application No. 13 / 961,078, entitled "Managing Wireless Connections Based on Motion" by Schlatter et al. Claim priority.

  Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. Wireless communication systems typically include macrocell access points for providing coverage over a large area. Small cell access points are increasingly being deployed in wireless communication systems to increase the capacity and / or improve coverage of wireless communication systems.

  A small cell access point can provide coverage in a smaller area than a macro cell access point. Therefore, the mobile station can enter and exit the small cell coverage within a short time. As a result, the connection may be temporary and reconnection may be frequent. In some cases, this may result in a signaling storm to the access point, mobile station disconnection, and / or higher power consumption of the mobile station.

  The described features generally relate to one or more improved methods, systems and / or devices for avoiding wireless connectivity failures.

  In one configuration, the mobile station can use a first connection with a first access point for data transmission. The mobile station can determine its motion state based on sensor data from at least one sensor in the mobile device. In a scan for available access points, a second access point can be identified. The second access point may be a small cell access point. The mobile station may decide to use the second access point based at least in part on the motion state of the mobile station.

  In some embodiments, determining the motion state of the mobile device may include determining the motion state based on acceleration of movement of the mobile device.

  In some embodiments, determining the motion state of the mobile device may include determining the motion state based on the angular rotation speed of the mobile device.

  In some embodiments, the movement state of the second access point may be determined.

  In some embodiments, determining whether to use a second access point for data transmission includes determining the mobile device's determined motion state and the second access point's determined motion. And determining whether to use the second access point based on the status.

  In some embodiments, determining whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point is Determining to use the second access point when the determined motion state of the mobile device and the motion state of the second access point are the same.

  In some embodiments, determining whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point is Deciding to use the second access point when the relative difference between the determined motion state of the mobile device and the determined motion state of the second access point is within a threshold Can include.

  In some embodiments, determining the movement state of the second access point learns the movement state of the second access point based at least in part on a previous connection with the second access point. Can include.

  In some embodiments, determining the motion state of the second access point may include crowdsourcing information about the second access point. The information may include a movement state of the second access point.

  In some embodiments, determining whether to use a second access point for data transmission may include determining whether a backoff timer has been met.

  In some embodiments, the duration of the backoff timer may be adjusted based at least in part on a previous connection with the second access point.

  In some embodiments, the duration of the backoff timer may be access point specific.

  In some embodiments, determining whether to use a second access point may include determining whether to establish a connection with the second access point.

  In some embodiments, determining whether to use the second access point determines whether to switch data transmission to an established connection with the second access point. Can be included.

  In some embodiments, the determined motion state may be associated with the identified second access point. Information about the identified second access point and its associated motion state may be stored.

  In some embodiments, the first access point may be a macro cell access point and the second access point may be a small cell access point.

  In some embodiments, the at least one sensor may include an accelerometer and / or a gyroscope.

  An apparatus for managing data transmission is also described. In one configuration, the apparatus uses the mobile device based on the means for using the first connection with the first access point for data transmission and sensor data from at least one sensor in the mobile device. Means for determining a motion state of the mobile device, means for identifying a second access point, and a second access point for data transmission based at least in part on the determined motion state of the mobile device Means for determining whether or not to use.

  Another apparatus for managing data transmission is also described. The apparatus can include a processor, memory in electronic communication with the processor, and instructions embodied in the memory. The instructions determine the motion state of the mobile device based on sensor data from at least one sensor in the mobile device, using the first connection with the first access point for data transmission by the processor Determining whether to use the second access point for data transmission based at least in part on the determined motion state of the mobile device and identifying the second access point May be feasible to do.

  A computer program product for managing data transmission is also described. The computer program product may include a non-transitory computer readable medium storing instructions, the instructions using the first connection with the first access point for data transmission by the processor, in the mobile device Based on sensor data from at least one sensor, determining a motion state of the mobile device, identifying a second access point, and based at least in part on the determined motion state of the mobile device, It can be performed to determine whether to use the second access point for data transmission.

  In addition, a method for managing connections will be described. In one configuration, a request for connection may be received from a mobile device. At the access point, a determination can be made as to whether the mobile device is blacklisted. A mobile device may be blacklisted when the number of previous connections associated with the mobile device exceeds a threshold. If the mobile device is determined to be blacklisted, the request for connection from the mobile device may be denied.

  In some embodiments, the previous connection may include a connection with a duration that fails to meet the time threshold.

  In some embodiments, the previous connection may include a connection in which the mobile device is disconnected to leave the access point's coverage area.

  In some embodiments, a mobile device can be blacklisted when the number of previous connections within a time period exceeds a threshold.

  In some embodiments, determining that the mobile device is not blacklisted may establish a connection with the mobile device.

  In some embodiments, a mobile device can be identified. The duration of the connection with the mobile device can also be determined. A connection may be identified as a previous connection when the duration of the connection fails to meet the threshold. In some cases, the time of the previous connection can be identified. In some embodiments, the previous connection may be associated with the identified mobile device.

  In some embodiments, the access point may be a small cell access point.

  An apparatus for managing connections is also described. In one configuration, the apparatus includes a means for receiving a request for a connection from a mobile device, a means for determining whether the mobile device is blacklisted at the access point, and the mobile device Determining that it is blacklisted may include means for rejecting requests for connections from mobile devices. A mobile device may be blacklisted when the number of previous connections associated with the mobile device exceeds a threshold.

  Another device for managing connections is also described. The apparatus can include a processor, memory in electronic communication with the processor, and instructions embodied in the memory. The instructions receive by the processor a request for connection from the mobile device, determine at the access point whether the mobile device is blacklisted, and the mobile device is blacklisted. If so, it may be feasible to do the rejection of the request for connection from the mobile device. A mobile device may be blacklisted when the number of previous connections associated with the mobile device exceeds a threshold.

  A computer program product for managing connections is also described. The computer program product may include a non-transitory computer readable medium storing instructions, wherein the instructions receive a request for a connection from the mobile device by the processor, at the access point, the mobile device is blacklisted. Determining whether or not and determining that the mobile device is blacklisted can be performed to deny a request for connection from the mobile device. A mobile device may be blacklisted when the number of previous connections associated with the mobile device exceeds a threshold.

  Further scope of the applicability of the described method and apparatus will become apparent from the following detailed description, claims, and drawings. Since various changes and modifications within the spirit and scope of the description will become apparent to those skilled in the art, the modes for carrying out the invention and specific examples are given by way of illustration only.

  A further understanding of the nature and advantages of the present invention may be realized by reference to the following drawings. In the accompanying drawings, similar components or features may have the same reference label. Further, various components of the same type can be distinguished by placing a reference label followed by a dash and a second label that distinguishes multiple similar components. Where only the first reference label is used within this specification, the description will be any one of the similar components having the same first reference label, regardless of the second reference label. It is applicable to.

1 is a block diagram of a wireless communication system. FIG. 6 is a block diagram of a mobile station capable of managing routing of data transmissions according to various embodiments. FIG. 6 is a block diagram of another mobile station capable of managing the routing of data transmissions according to various embodiments. FIG. 6 is a block diagram of yet another mobile station capable of managing routing of data transmissions according to various embodiments. FIG. 6 is a block diagram of an access point that can avoid poor wireless connectivity according to various embodiments. FIG. 6 is a block diagram of another access point that can avoid poor wireless connectivity in accordance with various embodiments. FIG. 4 is a message flow diagram illustrating one embodiment of wireless communication between a mobile station and a first access point and a second access point, according to various embodiments. FIG. 6 is a message flow diagram illustrating another embodiment of wireless communication between a mobile station and a first access point and a second access point, according to various embodiments. FIG. 6 is a message flow diagram illustrating yet another embodiment of wireless communication between a mobile station and a first access point and a second access point, according to various embodiments. FIG. 6 is a message flow diagram illustrating one embodiment of wireless communication between a mobile station and an access point, according to various embodiments. FIG. 6 is a message flow diagram illustrating another embodiment of wireless communication between a mobile station and an access point, according to various embodiments. FIG. 6 is a message flow diagram illustrating one embodiment of network management wireless communication between a mobile station and a first access point and a second access point, according to various embodiments. 1 is a block diagram of a MIMO communication system according to various embodiments. FIG. 2 is a flowchart of a method for avoiding poor wireless connectivity, according to various embodiments. 2 is a flowchart of a method for avoiding poor wireless connectivity, according to various embodiments. 2 is a flowchart of a method for avoiding poor wireless connectivity, according to various embodiments. 2 is a flowchart of a method for avoiding poor wireless connectivity, according to various embodiments. 2 is a flowchart of a method for avoiding poor wireless connectivity, according to various embodiments.

  The following generally relates to switching between macrocell access points and small cell access points. In some cases this may correspond to a switch between a cellular network and a Wi-Fi network. Specifically, the following relates to avoiding wireless connection failures (eg, temporary connections).

  Cellular operators are increasingly using Wi-Fi and other small cell technologies to expand network capacity and coverage. In general, the use of these smaller cells (eg, Wi-Fi) is cheaper for operators and energy efficient for mobile devices. Thus, operators can automatically connect to available small cell access points (e.g., Wi-Fi access points) and use cellular connections for data transmission, and therefore for data transmission. The mobile device may be configured to switch to using a small cell access point. However, the mobile device may be within the coverage of the small cell access point only for a short time. For example, the mobile device may be in a vehicle that is driving near a stationary small cell access point. In another example, the mobile device may be stationary and a small cell access point on the bus may pass near the stationary mobile device. In these types of situations, the mobile device connects to a small cell access point, switches data transmission to the small cell access point, and eventually establishes a cellular connection when the mobile device is no longer within range of the small cell access point. You may need to resume and return to the cellular connection. These temporary connections may result in multiple reconnections with the cellular network (resulting in higher power consumption), signaling storms to the access points, and application disconnection (eg, user experience interruption).

  The following description provides examples and is not intended to limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and configuration of the elements discussed without departing from the spirit and scope of this disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than the described order, and various steps may be added, omitted, or combined. Also, features described in connection with some embodiments may be combined with other embodiments.

  Referring first to FIG. 1, the figure shows an example of a wireless communication system 100. System 100 includes a base station (or cell) 105, a communication device 115, and a core network 130. Base station 105 may communicate with communication device 115 under control of a base station controller (not shown), which may be part of core network 130 or base station 105 in various embodiments. Base station 105 can communicate control information and / or user data with core network 130 via backhaul link 132. In an embodiment, the base stations 105 can communicate with each other directly or indirectly via a backhaul link 134, which can be a wired or wireless communication link. The system 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can simultaneously transmit modulated signals on a plurality of carriers. For example, each communication link 125 may be a multi-carrier signal modulated by the various radio technologies described above. Each modulated signal may be sent on a different carrier and may carry control information (eg, reference signal, control channel, etc.), overhead information, data, etc.

  Base station 105 may communicate wirelessly with device 115 via one or more base station antennas. Each of the base station 105 sites may provide communication coverage for a respective geographic area 110. In some embodiments, the base station 105 is a transceiver base station, a radio base station, an access point, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a Node B, an eNode B (eNB), It may be referred to as home node B, home e-node B, or some other appropriate terminology. The coverage area 110 of the base station may be divided into sectors (not shown) that constitute only a part of the coverage area. System 100 may include different types of base stations 105 (eg, macro base stations, micro base stations, femto base stations, and / or pico base stations). Micro base stations, femto base stations, and pico base stations may be examples of small cells. Different technology coverage areas may overlap. For example, the small cell 105-a may be a Wi-Fi base station in the coverage area of the LTE / LTE-A base station.

  In some embodiments, system 100 is an LTE / LTE-A network. In LTE / LTE-A networks, the terms evolved Node B (eNB) and user equipment (UE) may generally be used to describe the base station 105 and the device 115, respectively. As used herein, base station 105 is commonly referred to as an access point (AP) and device 115 is commonly referred to as a mobile station (MS). System 100 may be a heterogeneous LTE / LTE-A network in which different types of APs provide coverage for various geographic regions. For example, each AP 105 may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. Macrocells typically cover a relatively large geographic area (eg, a few kilometers in radius) and can allow unrestricted access by the MS through service contracts with network providers. A picocell will typically cover a relatively small geographic area, and a service contract with a network provider may allow unrestricted access by the MS. Femtocells will also typically cover a relatively small geographic area (e.g., residential) and, in addition to unrestricted access, an MS (e.g., in a limited subscriber group (CSG)) that has an association with a femtocell. Limited access by MS, MS for users in homes, etc. can also be provided. An AP for a macro cell may be referred to as a macro AP. An AP for a pico cell may be referred to as a pico AP. An AP for a femto cell may also be referred to as a femto AP or a home AP. An AP may support one or multiple (eg, two, three, four, etc.) cells.

  The core network 130 can communicate with the AP 105 via the backhaul 132 (eg, S1). APs 105 may also communicate with each other directly, for example, via backhaul link 134 (e.g., X2) and / or via backhaul link 132 (e.g., through core network 130). it can. The wireless network 100 can support synchronous or asynchronous operation. In synchronous operation, APs can have similar frame timing, and transmissions from different APs can be approximately time aligned. In asynchronous operation, APs can have different frame timings, and transmissions from different APs may not be time aligned. The techniques described herein may be used for either synchronous or asynchronous operations.

  The MSs 115 are distributed throughout the wireless network 100, and each MS may be stationary or mobile. MS115 is also available by those skilled in the art to user equipment, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile It may also be referred to as a terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology. The MS 115 may be a mobile phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, tablet computer, laptop computer, cordless phone, wireless local loop (WLL) station, etc. The MS may be able to communicate with macro eNBs, pico eNBs, femto eNBs, relays, and the like.

  The transmission link 125 shown in the network 100 may include an uplink (UL) transmission from the mobile device 115 to the base station 105 and / or a downlink (DL) transmission from the base station 105 to the mobile device 115. Downlink transmissions can also be referred to as forward link transmissions, while uplink transmissions can also be referred to as reverse link transmissions.

  In some embodiments, the MS 115-a may be in the coverage area of multiple APs. For example, MS 115-a may be in the coverage area of LTE / LTE-A access point 105 and the coverage area of small cell Wi-Fi access point 105-a. In some cases, it may be beneficial for the MS to use a small cell access point 105-a (e.g., a Wi-Fi access point) instead of using a macro cell 105 (e.g., LTE / LTE-A access point). obtain. For example, a small cell can enable efficient resource usage (eg, reducing user power consumption, improving spectral efficiency, etc.) by bringing the network closer to the user. Small cells are often used to increase network capacity. For example, capacity may be increased by offloading traffic (eg, data traffic) from a macro cell to a small cell when available. This can be particularly beneficial in urban environments where small cells can provide better coverage and / or increased bandwidth than macro cells.

  However, offloading traffic from a macro cell to a small cell may not always be beneficial. For example, since the small cell coverage area is typically small, a moving MS 115-a enters the coverage area of the small cell access point 105-a and eventually, after a short time, the coverage of the small cell access point 105-a. Can leave the area. Without the systems and methods described herein, MS 115- connected to macro cell 105 (eg, via first transmission link 125-a) and operating near stationary small cell 105-a. a connects to the second transmission link 125-b for traffic and tries to use it, eventually leaving the coverage area of the small cell 105-a after a short time and the first for traffic It may be necessary to switch back to using transmit link 125-a. As a result, considerable resources may be spent with little or no benefit to MS 115-a. In addition to consuming unnecessary resources, causing poor connections (for example, connections with a duration that is below a threshold) can disrupt traffic flow (for example, disrupt the user experience) .

  In some embodiments, the MS 115-a can determine its motion state and can determine whether to use the small cell 105-a based on the motion state of the MS 115-a. For example, if MS 115-a determines that it is moving quickly (e.g., driving), MS 115-a avoids using small cell 105-a, or Until it is determined that a connection with small cell 105-a (e.g., transmission link 125-b) is likely to be a good connection (e.g., a connection with a duration longer than the threshold), small cell 105-a You can decide to delay using -a. As used herein, a connection may include network address association, authentication, and allocation.

  In some cases, MS 115-a is based on the movement state of MS 115-a (eg, stationary, walking, driving) relative to the movement state of the access point (eg, stationary, moving). , It can be determined whether to connect to an access point (eg, a small cell access point). In other cases (for example, when the MS 115-a automatically connects to an available small cell access point), the MS 115-a may change the MS 115-a motion state relative to the small cell access point motion state. Based on this, it can be determined whether the connection with the small cell access point should be used for data transmission. If the MS115-a motion state is stationary and the small cell access point motion state is stationary, the MS115-a switches and uses the connection with the small cell access point for data transmission can do. However, if the MS 115-a is moving and the small cell access point is stationary, the MS 115-a may not use a connection with the small cell access point to send / receive data traffic. Instead, the MS 115-a can continue to use the connection with the cellular access point for data transmission. Thus, the MS 115-a can avoid establishing and using a wireless connection failure (eg, a temporary connection). In some cases, such a mechanism can be used to improve connection control so that temporary connections are removed in lower layers. By avoiding poor connections, the signaling load encountered by the access point can be eliminated, which can be desirable for network operators.

  The MS 115-a can use various sensors (eg, accelerometer, gyroscope, compass, etc.) to determine the motion state of the MS 115-a. In some cases, sensor data may be evaluated over one or more time periods to identify a motion state associated with the sensor data (eg, stationary, walking, driving, etc.). In some cases, the motion state may be determined based on the detected movement acceleration and / or angular rotation speed of MS-115a.

  In some cases, the MS 115-a can learn the movement state of the access point based on the duration of the connection with the access point (eg, a small cell access point). If the connection duration is longer than a threshold (eg, 60 seconds), the access point motion state may be categorized to be the same as the MS 115-a motion state. However, if the connection duration is shorter than the threshold, the movement state of the access point can be determined based on the movement state of the MS 115-a. For example, if MS 115-a is stationary and the connection is lost, the access point may be determined to be mobile (access point motion state = mobile). When MS 115-a moves, the movement state of the access point may be unknown. In some cases, the movement state of the access point can be obtained based on information from the cloud source or can be indicated by the access point.

  In some cases, the MS 115-a can immediately determine whether to connect to and / or use an access point for data transmission. In other cases, the MS 115-a may wait until the backoff timer expires before deciding whether to connect to and / or use the access point for data transmission. it can. This may be particularly beneficial when the MS 115-a with a driving motion state becomes stationary (eg, stops at a red light) for a period of time. In some cases, the mobile device may quickly move away from a stationary access point (eg, the signal turns blue, runs away). In these situations (away situations), the motion state of MS 115-a may remain in operation. In some cases, the MS 115-a can learn to set the back-off timer to a value that exceeds the typical rest time before leaving. This allows the MS115-a to avoid using the connection until there is a greater probability that the connection with the access point will be a good connection (for example, a connection that lasts longer than 60 seconds). obtain. In other cases, the MS 115-a may remain stationary (e.g., switch to a stationary motion state) or transition to use walking movement (e.g., walking motion state). May be switched). In that case, when the back-off timer expires, the MS 115-a can analyze the movement state of the MS 115-a with respect to the movement state of the access point and determine whether to connect to a stationary access point. For example, when the back-off timer expires, the MS 115-a can determine that the motion state of the MS 115-a and the motion state of the access point are the same. In another example, upon expiration of the backoff timer, MS 115-a may determine that the relative difference between the MS 115-a motion state and the access point motion state is within a threshold.

  Because there are varying degrees and circumstances of movement, the decision to connect to a small cell access point (e.g. Wi-Fi access point) for data transmission and to use the connection with the small cell access point is , Based on some combination of MS115-a motion state and access point motion state. For example, if MS 115-a is in a moving motion state while walking and is likely to be in the coverage of a stationary access point for a sufficient duration, MS 115-a may use a small cell access point for data transmission. You can decide to use a connection with. However, if the MS115-a is in a more accelerated motion state and the access point is stationary, the MS115-a should ignore (not use) the connection with the small cell access point for data transmission Or decide not to connect with it. The MS 115-a associates a motion state with each unique access point as may be defined by a WLAN MAC address or ECGI (E-UTRAN cell global identifier).

  In some embodiments, the small cell 105-a identifies the MS 115-a attempting to connect to the small cell 105-a and determines the number of poor connections associated with the identified MS 115-a. Thus, connection failure can be avoided. Small cell 105-a can blacklist MS 115-a with the number of poor connections exceeding the threshold. In some cases, the threshold may be static (eg, the number of poor connections within a given time period). In other cases, the threshold may be dynamic (eg, the relative number of connections with other APs, the highest percentage of MSs associated with the largest number of bad connections, etc.). These blacklisted MSs 115-a may be blocked from connecting with the small cell 105-a. For example, if MS 115-a is in the coverage area of small cell 105-a and sends a request for connection, but MS 115-a is blacklisted on small cell 105-a, then small cell 105 -a can reject the request for connection and block the MS 115-a from connecting to the small cell 105-a. In some cases, blacklisting MS115-a associated with the number of poor connections exceeding the threshold will cause a signaling storm (e.g., temporary connection with multiple reconnections) in small cell 105-a. Can be prevented.

  Referring now to FIG. 2, a block diagram 200 illustrates an MS 115-b that can manage the routing of data transmissions according to various embodiments. MS 115-b may be an example of one or more aspects of one of MS 115 described with reference to FIG. MS115-b can also be a processor. MS 115-b may include MS receiver module 205, MS connection management module 210, and / or MS transmitter module 215. Each of these components may be in communication with each other.

  MS115-b components are implemented individually or collectively by one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware Can be done. Alternatively, those functions may be performed on one or more integrated circuits by one or more other processing units (or cores). In other embodiments, other types of integrated circuits (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), and other semi-customs that can be programmed in any manner known in the art. IC) can be used. The functions of each unit may also be implemented in whole or in part by instructions embodied in memory formatted to be executed by one or more general purpose or application specific processors.

  The MS receiver module 205 may include any number or type of receivers, and in some cases may include two or more wireless receivers, such as a cellular receiver and a wireless local area network (WLAN) receiver. . In some cases, the cellular receiver may be or include an LTE / LTE-A receiver. The MS receiver module 205 may transmit various types of data and / or control signals (ie, transmissions) on one or more communication channels of a wireless communication system, such as the wireless communication system 100 described with reference to FIG. Can be used to receive

  The MS transmitter module 215 may include any number or type of transmitters, and in some cases may include two or more wireless transmitters, such as a cellular transmitter and a WLAN transmitter. In some cases, the cellular transmitter may be or include an LTE / LTE-A transmitter. MS transmitter module 215 may be used to transmit various types of data and / or control signals over one or more communication channels of a wireless communication system, such as wireless communication system 100.

  The MS connection management module 210 can perform various functions. In some embodiments, the MS connection management module 210 can manage connections made via the MS receiver module 205 and the MS transmitter module 215. For example, the MS connection management module 210 can determine whether to connect to the access point based on the motion state of the MS 115-b. In another example (e.g., when MS 115-b automatically connects to an available access point), MS connection management module 210 may use the first access point based on the MS 115-b motion status. From using the first connection to the second access point, it can be determined whether to switch traffic. If the MS connection management module 210 decides not to use the second access point, the MS 115-b can continue to use the first connection with the first access point for data transmission.

  In some embodiments, the MS connection management module 210 can use the first connection with the first access point for data transmission. The MS connection management module 210 can determine and / or monitor the movement status of the MS 115-b. Upon detecting the second access point, the MS connection management module 210 can identify the movement state of the second access point. The MS connection management module 210 may determine whether to use the second access point for data transmission based on the motion state of the MS 115-b relative to the motion state of the second access point. In one example, this determination may be based on the difference between the MS115-b motion state and the second access point motion state being below a threshold. In one embodiment, the first access point may be a macro cell (eg, LTE / LTE-A access point) and the second access point is a small cell (eg, Wi-Fi access point). Good.

  Referring now to FIG. 3, a block diagram 300 illustrates an MS 115-c that can manage the routing of data transmissions according to various embodiments. MS 115-c may be an example of one or more aspects of one of MS 115 described with reference to FIG. MS115-c can also be a processor. The MS 115-c may include an MS receiver module 205, an MS connection management module 210-a, and / or an MS transmitter module 215. Each of these components may be in communication with each other.

  MS115-c components are implemented individually or collectively by one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware Can be done. Alternatively, those functions may be performed on one or more integrated circuits by one or more other processing units (or cores). In other embodiments, other types of integrated circuits (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), and other semi-customs that can be programmed in any manner known in the art. IC) can be used. The functions of each unit may also be implemented in whole or in part by instructions embodied in memory formatted to be executed by one or more general purpose or application specific processors.

  MS receiver module 205 and MS transmitter module 215 may be configured similarly to those described with respect to FIG. The MS connection management module 210-a may be an example of one or more aspects of the MS connection management module 210 described with reference to FIG. 2 and includes a motion state determination module 305 and / or a connection usage module 310. obtain.

  The motion state determination module 305 can monitor the motion of the MS 115-c and determine the motion state for the MS 115-c. In some cases, the motion state determination module 305 may generate an MS 115 based on sensor data from one or more sensors (e.g., accelerometer, compass, gyroscope, magnetometer, global positioning system, triangulation system, etc.). The movement state of -c can be determined. For example, the motion state determination module 305 can determine a walking motion state based on acceleration of movement associated with walking and / or angular rotation speed measurements. In another example, the motion state determination module 305 can determine a driving motion state based on accelerations of travel associated with driving and / or angular rotation speed measurements. In some embodiments, one or more sensors may be included in MS115-c.

  The motion state determination module 305 can monitor the motion of the MS 115-c by analyzing sensor data periodically or continuously and determining the motion state based on the analysis of the sensor data. In one example, the motion state determination module 305 can determine whether the MS 115-c is stationary or moving. In some cases, the motion state determination module 305 can distinguish between various types of motion (eg, walking, running, driving, etc.). For example, the motion state determination module 305 can analyze sensor data over a period of time, for example, the level of movement, the percentage of the time period during which that level of movement is performed, the location of the movement, and the trend of movement over that time period. The motion state may be determined based on a recent motion or a motion predicted based on a history of previous motion. For example, the motion state determination module 305 can determine that the MS 115-c has moved previously but is now stationary. As an example, a user of MS 115-c may have been driving or riding a vehicle. The MS 115-c may currently be stationary (eg, stopped at a traffic signal). However, MS115-c will transition back to motion when the traffic light turns blue. In some cases, the motion state determination module 305 can maintain a history or log of motion types associated with various locations and can predict future motion states of the MS 115-c based on the history or log.

  In some embodiments, the motion state determination module 305 can identify the motion state of the access point. For example, the motion state determination module 305 can determine whether the access point is stationary or mobile. In one example, the motion state determination module 305 can determine the motion state of the access point based on the previous connection with the access point and the motion state of the MS 115-c during the previous connection. In another example, the motion state determination module 305 can determine the motion state of the access point based on the acquired information (eg, cloud source information, stored database, etc.).

  Based on the motion state determined by the motion state determination module 305, the connection usage module 310 can determine whether the connection should be used for data transmission. In some embodiments, the connection usage module 310 interacts with the MS receiver module 205 and the MS transmitter module 215 to make a connection with an access point and / or have traffic (eg, data transmission). You can switch to a connection. In some cases, the connection usage module 310 can maintain multiple connections while using only one or a subset of the multiple connections for traffic. In other cases, the connection usage module 310 performs a handoff between the first connection with the first access point and the second connection with the second access point (second access If the traffic handoff to the point is successful, the first connection can be dropped).

  Referring now to FIG. 4, a block diagram 400 illustrates an MS 115-d that can manage the routing of data transmissions according to various embodiments. MS 115-d may be an example of one or more aspects of one of MS 115 described with reference to FIG. 1, FIG. 2, and / or FIG. MS115-d can also be a processor. The MS 115-d may include an MS receiver module 205, an MS connection management module 210-b, and / or an MS transmitter module 215. Each of these components may be in communication with each other.

  MS115-d components are implemented individually or collectively by one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware Can be done. Alternatively, those functions may be performed on one or more integrated circuits by one or more other processing units (or cores). In other embodiments, other types of integrated circuits (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), and other semi-customs that can be programmed in any manner known in the art. IC) can be used. The functions of each unit may also be implemented in whole or in part by instructions embodied in memory formatted to be executed by one or more general purpose or application specific processors.

  MS receiver module 205 and MS transmitter module 215 may be configured similarly to those described with respect to FIG. 2 and / or FIG. The MS connection management module 210-b may be an example of one or more aspects of the MS connection management module 210 described with reference to FIGS. 2 and / or 3, and the motion state determination module 305-a and / or Or it may include a connection usage module 310-a. The motion state determination module 305-a and the connection usage module 310-a may be examples of one or more aspects of the respective motion state determination module 305 and connection usage module 310 described with reference to FIG.

  The motion state determination module 305-a can determine the motion state of the MS 115-d. In some cases, the motion state determination module 305-a can determine the motion state of the AP. In this regard, the motion state determination module 305-a may include a motion detection submodule 405, a crowdsourcing submodule 410, and / or a learning submodule 415.

  The motion detection sub-module 405 can obtain sensor data from one or more sensors and can determine the motion state of the MS 115-d based on the sensor data. In various embodiments, the motion detection sub-module 405 can analyze the sensor data to determine the motion state of the MS 115-d. In some cases, motion detection submodule 405 may determine the motion state of MS 115-d based on a single time instance. For example, the motion detection sub-module 405 can obtain sensor data over a single time instance and determine the motion state of the MS 115-d by analyzing the sensor data in that single time instance. be able to. In other cases, motion detection sub-module 405 may determine the motion state of MS 115-d based on a certain time period. For example, the motion detection sub-module 405 can monitor sensor data over a period of time and can analyze the sensor data over that period of time. In one example, the motion detection submodule 405 can average the sensor data over that time period. In another example, the motion detection sub-module 405 can analyze the percentage of different types of instantaneous motion states over that time period. In some cases, motion detection sub-module 405 selects a time period for determining MS115-d motion state based on recent motion state information, MS115-d location, and / or learned behavior pattern. can do.

  The crowdsourcing sub-module 410 can obtain the movement state of the access point based on the cloud source information about the base station. In some cases, crowdsourcing sub-module 410 may receive communications from one or more nearby MSs that indicate AP motion status. For example, the MS 115-d may receive cloud source information about the AP, including motion state information about the AP (eg, when the MS 115-d approaches the AP). In other cases, the crowdsourcing sub-module 410 can obtain the AP's motion state based on a database that is updated via crowdsourcing information (eg, hosted on a server).

  The learning sub-module 415 learns the AP's motion state by monitoring the connection with the AP and by monitoring the motion state of the MS 115-d (eg, via the motion detection sub-module 405) Can do. For example, the learning sub-module 415 can learn the AP movement state by analyzing the strength of the connection with the AP with respect to the movement state of the MS 115-d. Accordingly, the learning sub-module 415 may include a connection monitoring sub-module 420. The connection monitoring submodule 420 can monitor the connection with the AP. For example, the connection monitoring sub-module 420 can monitor the signal strength between the AP and the MS 115-d and can monitor whether the connection has been broken. In addition, the connection monitoring submodule 420 can monitor the duration of the connection with the AP.

  In one example, the learning sub-module 415 can determine whether the connection between the MS 115-d and the AP is a good connection based on the duration of the connection with the AP. If the duration of the connection is longer than a threshold (eg, 60 seconds), the AP motion state is determined to be the same as the MS 115-d motion state. If the duration of the connection is less than the threshold, the AP motion state may be determined based on the MS 115-d motion state when the connection with the AP is broken. For example, if the motion state of MS 115-d is stationary and the connection is broken, the AP motion state may be determined to be mobile. Connection is established when MS115-d is stationary (e.g., stopped at traffic signal) but lost when MS115-d moves (e.g., continues driving away from traffic signal) If so, the movement state of the AP can be determined to be stationary. In this example, the learning sub-module 415 can learn the time that is typically in stationary motion before the MS 115-d moves and sets a backoff timer over the learned time to It can be avoided.

  The connection usage module 310-a may determine whether to use the connection based on the MS115-d motion state and / or the AP motion state. To use the connection, the connection usage module 310-a can connect to the access point and / or switch traffic so that data traffic uses the connection with the access point. In this regard, the connection usage module 310-a may include a connection establishment submodule 425, a traffic switching submodule 430, and / or a backoff submodule 435.

  The connection establishment submodule 425 can establish a connection with one or more APs. In some cases, the connection establishment submodule 425 may decide to connect to the AP. For example, the connection establishment sub-module 425 may decide to connect to the AP based on the MS115-d motion state and / or the AP motion state. In other cases, the connection establishment sub-module 425 can automatically connect to the AP when the MS 115-d is in the AP's coverage area. In any case, the connection establishment submodule 425 can establish a connection that can be used for data traffic. In one example, the connection establishment submodule 425 can establish a connection with a first connection with a first access point (eg, a macrocell access point). Upon entering the coverage area of a second access point (e.g., a small cell access point), the connection establishment sub-module 425 may determine whether the second access point (e.g., small cell access point) You can automatically connect to the access point or decide to connect.

  The traffic switching sub-module 430 can switch traffic (eg, data traffic) from the first connection to the second connection based on the MS115-d motion state and / or the AP motion state. If the connection establishment submodule 425 automatically connects to the second AP, the traffic switching submodule 430 may not immediately switch the traffic to the connection with the second AP. Alternatively, the traffic switching sub-module 430 may decide to switch traffic to a connection with the second AP based on the MS115-d motion state and / or the second AP motion state. If the connection establishment submodule 425 decides to connect to the second AP based on the MS115-d movement status and / or the second AP movement status, the traffic switching submodule 430 Can be automatically switched to the connection with the second AP.

  Backoff submodule 435 delays connection establishment submodule 425 from connecting to the second AP and / or traffic switching submodule 430 switches traffic to the second AP until the backoff timer expires Can be delayed. In some cases, the connection usage module 310-a can re-comparison the MS115-d movement state with the AP movement state after the backoff timer expires, and connect based on the updated comparison. And / or whether or not a connection should be used. In some cases, the duration of the backoff timer may be learned by the learning submodule 415. The back-off submodule can delay the use of the AP and improve the likelihood that a connection with the AP can be a beneficial connection. For example, if an MS115-d user is driving or riding a car but is stationary in a traffic signal, the back-off timer may indicate that the MS115-d The MS 115-d can be delayed from using the second connection until it becomes detached. In some cases, the backoff submodule 435 can learn the duration of the backoff time for a particular access point based on at least one previous connection with the access point.

  Referring now to FIG. 5, a block diagram 500 illustrates an AP 105-b that can avoid poor wireless connectivity, according to various embodiments. AP 105-b may be an example of one or more aspects of one of APs 105 described with reference to FIG. AP105-b can also be a processor. The AP 105-b may include an AP receiver module 505, an AP connection management module 510, and / or an AP transmitter module 515. Each of these components may be in communication with each other.

  AP105-b components are implemented individually or collectively by one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Can be done. Alternatively, those functions may be performed on one or more integrated circuits by one or more other processing units (or cores). In other embodiments, other types of integrated circuits (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), and other semi-customs that can be programmed in any manner known in the art. IC) can be used. The functions of each unit may also be implemented in whole or in part by instructions embodied in memory formatted to be executed by one or more general purpose or application specific processors.

  The AP receiver module 505 may include any number or type of receivers, and in some cases may include two or more wireless receivers, such as a cellular receiver and a wireless local area network (WLAN) receiver. . In some cases, the cellular receiver may be or include an LTE / LTE-A receiver. The AP receiver module 505 may transmit various types of data and / or control signals (ie, transmissions) on one or more communication channels of a wireless communication system, such as the wireless communication system 100 described with reference to FIG. Can be used to receive

  The AP transmitter module 515 may include any number or type of transmitters, and in some cases may include two or more wireless transmitters, such as a cellular transmitter and a WLAN transmitter. In some cases, the cellular transmitter may be or include an LTE / LTE-A transmitter. The AP transmitter module 515 may be used to transmit various types of data and / or control signals over one or more communication channels of a wireless communication system, such as the wireless communication system 100.

  The AP connection management module 510 can perform various functions. In some embodiments, the AP connection management module 510 can manage connections made via the AP receiver module 505 and the AP transmitter module 515. For example, the AP connection management module 510 can manage the connection by refusing to connect with a blacklisted mobile device. The AP connection management module 510 can identify each mobile device attempting to connect to the AP or connecting to the AP. If the connection with the mobile device is poorly connected (for example, the connection is terminated because the duration is below the threshold and / or the mobile device has left the AP coverage area), the AP Defects can be associated with identified APs. When the identified mobile device is associated with several poor connections over a given time period that exceeds the threshold, the AP can blacklist the identified mobile device. As a result, the AP connection management module 510 can refuse to connect with the identified (blacklisted) mobile device. Since the identified mobile device is blacklisted, the AP will block the identified mobile device from connecting with the AP. As a result, the number of poor connections associated with the identified mobile device may be below a threshold in time. Thus, the identified mobile device can have an opportunity to have a good connection with the AP.

  Referring now to FIG. 6, a block diagram 600 illustrates an AP 105-c that can avoid poor wireless connectivity, according to various embodiments. AP 105-c may be an example of one or more aspects of one of APs 105 described with reference to FIG. AP 105-c can also be a processor. The AP 105-c may include an AP receiver module 505, an AP connection management module 510-a, and / or an AP transmitter module 515. Each of these components may be in communication with each other.

  AP105-c components are implemented individually or collectively by one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware Can be done. Alternatively, those functions may be performed on one or more integrated circuits by one or more other processing units (or cores). In other embodiments, other types of integrated circuits (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), and other semi-customs that can be programmed in any manner known in the art. IC) can be used. The functions of each unit may also be implemented in whole or in part by instructions embodied in memory formatted to be executed by one or more general purpose or application specific processors.

  AP receiver module 505 and AP transmitter module 515 may be configured similarly to those described with respect to FIG. AP connection management module 510-a may be an example of one or more aspects of AP connection management module 510 described with reference to FIG. 5, including AP connection monitoring module 605, black listing module 610, and / or A blocking module 615 may be included.

  The AP connection monitoring module 605 can monitor the connection with the identified MS (eg, MS 115-a). In some cases, the AP connection monitoring module 605 can monitor the connection to determine whether the duration of the connection meets a threshold (eg, 60 seconds). If the duration of the connection is longer than the threshold, the connection can be determined to be a good connection. However, if the duration of the connection is less than the threshold, the connection can be determined to be bad. In other cases, the AP connection monitoring module 605 monitors the connection to determine whether the connection duration meets a threshold and if the connection duration is less than the threshold, the connection Can be determined to be the result of the MS leaving the AP coverage area. In these cases, the AP connection monitoring module 605 has a connection duration less than the threshold and the MS has left the AP coverage area (or, for example, the coverage area has left the MS). When both the connection is terminated, the connection failure can be associated with the identified MS.

  The black listing module 610 can blacklist the identified MS when the number of poor connections associated with the identified MS exceeds a threshold. In some cases, the threshold may be the number of poor connections (eg, 4) within a specified time period (eg, 96 hours). As a result, MSs with a number of connection failures greater than the threshold within a specified time period can be blacklisted. In other cases, the threshold may be the highest percentage (eg, 5%) of MSs ranked based on the largest number of poor connections. As a result, the highest percentage of MSs with the greatest number of bad connections can be blacklisted. In one example, the black listing module 610 can maintain an at least partial list of MSs associated with a number greater than a certain number of poor connections. For example, the black listing module 610 can rank the at least partial list of MSs according to the number of poor connections within a specified time period.

  Blocking module 615 can block connections from blacklisted MSs. In one example, the blocking module 615 can identify the MS associated with the connection request and can determine whether the identified MS is blacklisted. If the identified MS is blacklisted, the blocking module 615 can deny a request for a connection from the identified MS. If the identified MS is not blacklisted, blocking module 615 may allow AP 105-c to connect with the identified MS.

  In some embodiments, the AP connection monitoring module 605, the black listing module 610, and / or the blocking module 615 may be implemented using the AP 105-c's connection manager, modem, and / or operating system.

  FIG. 7 is a message illustrating an embodiment of wireless communication between MS 115-e and first AP 105-d-1 and wireless communication between MS 115-e and second AP 105-d-2. FIG. In one example, the first AP 105-d-1 may be a macro cell AP, and the second AP 105-d-2 may be a small cell AP. MS 115-e may be an example of one or more aspects of MS 115 described with reference to FIG. 1, FIG. 2, FIG. 3, and / or FIG. AP105-d-1 and / or AP105-d-2 may be an example of one or more aspects of AP105 described with reference to FIG. 1, FIG. 5, and / or FIG.

  In one configuration, the MS 115-e can use the first connection with the first AP 105-d-1 for data transmission. For example, the MS 115-e may have previously established a connection 705 with the first AP 105-d-1 in order to engage in wireless communication with the first AP 105-d-1. In one example, MS 115-e may be using connection 705 with first AP 105-d-1 for data traffic.

  At block 710, MS 115-e may determine the motion state of MS 115-e. For example, the MS 115-e can continuously monitor the movement state of the MS 115-e. In some embodiments, the motion state of the MS 115-e is determined by the MS connection management module 210 described with reference to FIGS. 2, 3, and / or 4, and / or FIG. 3 and / or FIG. It can be determined using the motion state determination module 305 described with reference.

  At block 715, the MS 115-e may scan for available APs. In some cases, MS 115-e can periodically scan for available APs. Scanning for available APs, the MS 115-e can receive the broadcast 720 from the second AP 105-d-2. In some cases, the broadcast 720 may include information that may be used to identify the second AP 105-d-2. For example, the broadcast 720 may include a service set identifier (SSID). In various situations, the MS 115-e can enter the coverage area of the second AP 105-d-2, but within the coverage area of the second AP 105-d-2 until the scan for the AP at block 715. It may not be recognized that there is. At block 725, the MS 115-e may identify the second AP 105-d-2 based at least in part on the received broadcast 720.

  At block 730, the MS 115-e may determine the movement state of the second AP 105-d-2. In some cases, the MS 115-e can determine the motion state of the second AP 105-d-2 based on information obtained for the second AP 105-d-2. For example, the MS 115-e can obtain cloud source information about the movement state of the second AP 105-d-2. In another example, the MS 115-e may have previously learned the motion state of the second AP 105-d-2, and from the information stored for the second AP 105-d-2, the second AP 105-d-2 The d-2 motion state can be acquired. In some cases, the MS 115-e learns or re-learns the movement state of the second AP 105-d-2 and monitors each established connection with the second AP 105-d-2. The information stored for the AP105-d-2 can be updated. Although not shown, the MS 115-e can learn or relearn the movement state of the second AP 105-d-2 based on the connection 740 with the second AP 105-d-2.

  At block 735, the MS 115-e sends to the second AP 105-d-2 when the difference between the movement state of the MS 115-e and the movement state of the second AP 105-d-2 is less than a threshold. You can decide to connect and use it. For example, when the movement of the MS 115-e relative to the movement of the second AP 105-d-2 is within a threshold. For example, the MS 115-e may have a second AP 105-d-2 when the second AP 105-d-2 is stationary and the MS 115-e is stationary or slowly moving around (eg, walking). You can decide to connect to d-2 and use it. However, MS115-e has a second AP105-d-2 stationary and MS115-e is moving quickly (eg, driving) or MS115-e is stationary, When the second AP 105-d-2 is moving quickly, it may not decide to connect to and / or use the second AP 105-d-2.

  When connecting to the second AP and deciding to use it, the MS 115-e can establish a connection 740 with the second AP 105-d-2 and with the first AP 105-d-1. The data traffic 745 can be switched from the connection 705 to the connection 740 with the second AP 105-d-2. When the data traffic 745 is switched, the MS 115-e can maintain the connection 705 with the first AP 105-d-1. For example, the MS 115-e can maintain an active (eg, active) connection 705 with the first AP 105-d-1. In another example, the MS 115-e can maintain an idle (eg, idle) connection 705 with the first AP 105-d-1. Alternatively, the MS 115-e may not maintain the connection 705 with the first AP 105-d-1 (eg, disconnect and drop). In some cases, the MS 115-e can continue to monitor the motion state of the MS 115-e and can monitor the connection 740 to learn or relearn the motion state of the second AP 105-d-2. . Although FIG. 7 shows various blocks in a particular order, it should be understood that the blocks can be rearranged in various ways. For example, one possible order may proceed from block 715 to broadcast 720 and from broadcast 720 to block 710, where connection establishment may be performed last, as shown.

  FIG. 8 illustrates another embodiment of wireless communication between the MS 115-e and the first AP 105-d-1 and wireless communication between the MS 115-e and the second AP 105-d-2. FIG. The embodiment shown in message flow diagram 800 may be similar to the embodiment shown in message flow diagram 700. However, in this embodiment, the MS 115-e can automatically connect to an available AP.

  As previously described, the MS 115-e can use the first connection 805 with the first AP 105-d-1 for data transmission. At block 810, the MS 115-e can scan for APs. When scanning for APs, the MS 115-e can receive the broadcast 820 and can establish a connection 825 with the second AP 105-d-2. MS115-e has established connection 825 with the second AP105-d-2, but MS115-e uses connection 805 with the first AP105-d-1 for data traffic. You can continue.

  At block 830, MS 115-e may determine the motion state of MS 115-e. At block 835, the MS 115-e can identify the second AP 105-d-2. At block 840, the MS 115-e may determine the movement state of the second AP 105-d-2.

  At block 845, the MS 115-e sends the second AP 105 for data transmission when the difference between the MS 115-e motion state and the second AP 105-d-2 motion state is less than a threshold. It can be decided to use connection 825 with -d-2. For example, when the movement of the MS 115-e relative to the movement of the second AP 105-d-2 is within a threshold. For example, MS115-e switches traffic 850 when the second AP105-d-2 is stationary and MS115-e is stationary or slowly moving around (eg walking) , It can be decided to use the connection 825 with the second AP 105-d-2. However, MS115-e has a second AP105-d-2 stationary and MS115-e is moving quickly (eg, driving) or MS115-e is stationary, When the second AP 105-d-2 is moving quickly, it may not decide to switch traffic and use the connection with the second AP 105-d-2. When MS115-e decides to switch traffic 850, MS115-e decides to keep connection 805 active, keep connection 805 idle, or not keep connection 805 Can do.

  FIG. 9 illustrates another embodiment of wireless communication between the MS 115-e and the first AP 105-d-1 and wireless communication between the MS 115-e and the second AP 105-d-2. FIG. 9 is a message flow diagram 900. FIG. The embodiment shown in message flow diagram 900 may be similar to the embodiment shown in message flow diagram 700 and may be similarly adapted to be used in the embodiment shown in message flow diagram 800. However, in this embodiment, the MS 115-e connects to the second AP 105-d-2 and / or uses the connection to the second AP 105-d-2 until the backoff timer expires. Can be delayed.

  As previously described, the MS 115-e can use the first connection 905 with the first AP 105-d-1 for data transmission. At block 910, MS 115-e may determine the motion state of MS 115-e.

  At block 915, the MS 115-e may determine whether the motion state of the MS 115-e exceeds a threshold value. If the MS115-e motion state exceeds a threshold, a backoff timer may be started. In some cases, the back-off timer may be initiated based on changes in MS 115-e movement and / or movement state. In other cases, the backoff timer may be started based on detection of an available AP. If an AP-specific back-off timer (eg, back-off time) has been acquired (eg, learned), the MS 115-e can use the acquired AP-specific back-off timer. If an AP-specific backoff timer for the AP has not been obtained, a default backoff timer (which is a default time, eg, 60 seconds) may be used. In one example, a backoff timer may be started (eg, based on a default time), and an AP specific time may be used instead of the default time when identifying the AP.

  At block 920, the MS 115-e may scan for APs. When scanning for APs, the MS 115-e can receive the broadcast 925. At block 930, the MS 115-e may identify the second AP 105-d-2 based on the broadcast 925. At block 935, the MS 115-e may determine the movement state of the second AP 105-d-2.

  At block 940, the MS 115-e determines the first time when the back-off timer expires and when the difference between the motion state of the MS 115-e and the second AP 105-d-2 meets the threshold. You can decide to connect to and / or use two AP105-d-2. For example, when the back-off timer expires, the MS 115-e can determine whether the motion state of the MS 115-e with respect to the motion state of the second AP 105-d-2 satisfies a threshold value. As a result, the MS 115-e can only detect the second AP 105 after the back-off timer expires and only when the relative movement between the MS 115-e and the second AP 105-d-2 meets the threshold. -d-2 can be connected and / or decided to use it.

  Upon determining to connect to and / or use the second AP, the MS 115-e can establish a connection 945 with the second AP 105-d-2, and the first AP 105-d Data traffic 955 can be switched from connection 905 to -1 to connection 945 to the second AP 105-d-2. In some cases, the MS 115-e can continue to monitor the motion state of the MS 115-e and can monitor the connection 945 to learn or update the motion state of the second AP 105-d-2. Additionally or alternatively, the MS 115-e can monitor the movement status of the MS 115-e and can monitor the connection 945 to learn or adjust the duration of the backoff timer. For example, if the duration of the connection 945 established with the second AP 105-d-2 is less than the threshold at the expiration of the backoff timer, the MS 115-e will (with the second AP 105-d-2 Can be determined to increase the duration of the backoff timer (for subsequent connections). In another example, if the duration of the connection 945 established with the second AP 105-d-2 is longer than the threshold when the back-off timer expires, based on the MS115-e motion state analysis, The MS 115-e can reduce the duration of the backoff timer (for subsequent connections with the second AP 105-d-2). In some cases, the MS 115-e may generate a unique (eg, AP specific) backoff timer for each AP with which the backoff timer is used. In some embodiments, the back-off timer can be triggered at any time when the motion state of MS 115-e exceeds a threshold.

  FIG. 10 is a message flow diagram 1000 illustrating one embodiment of wireless communication between an MS 115-f and an AP 105-e. AP 105-e may be an example of one or more aspects of access point 105 described with reference to FIG. In one example, AP 105-e may be a small cell AP. MS115-f may be an example of one or more aspects of MS115 described with reference to FIGS. 1, 2, 3, 4, 7, 7, and / or 9. AP 105-e may be an example of one or more aspects of AP 105 described with reference to FIGS. 1, 5, 6, 7, 8, and / or 9.

  In one configuration, the AP 105-e can receive a connection request 1005 from the MS 115-f. In one example, the MS 115-f may attempt to connect to the AP 105-e and send a connection request 1005.

  At block 1010, the AP 105-e can identify the MS 115-f. For example, the AP 105-e can identify the MS 115-f based on the received connection request 1005. At block 1015, AP 105-e may determine whether MS 115-f is blacklisted. Upon determining that MS 115-f is not blacklisted, AP 105-e can send a response to the connection request and establish a connection 1020 with the identified MS 115-f.

  At block 1025, AP 105-e may start a timer upon establishing connection 1020 with MS 115-f. In some cases, AP 105-e can monitor connection 1020 with MS 115-f. For example, the AP 105-e can monitor the connection 1020 and detect a disconnection 1030 of the connection 1020. At block 1035, the AP 105-e may stop the timer upon detecting the disconnect 1030 of the connection 1020. As a result of starting the timer at connection 1020 and stopping the timer at the end of the connection (eg, disconnection 1030), the duration of the timer may correspond to the duration of connection 1020. In some cases, the AP 105-e has a connection 1020 that is a good connection (e.g., the timer duration is longer than a threshold) or a poor connection (e.g., based on the duration of the timer) Whether the timer duration is less than the threshold).

  At block 1040, a connection failure may be associated with the identified MS 115-f when the duration of the timer is less than the threshold. In some cases, the AP 105-e can maintain a list of MSs along with the number of poor connections associated with each MS.

  At block 1045, the AP 105-e may blacklist the MS 115-f if the number of poor connections associated with the MS 115-f is greater than the black listing threshold. In some cases, the black listing threshold may be time limited. For example, the black listing threshold may correspond to the number of poor connections within the last time period (eg, 48 hours). Since the blacklisted MS is blocked from connecting with the AP 105-e, if the MS is blacklisted, the number of poor connections associated with the MS may not be increased. As a result, blacklisted MSs can be removed from the blacklist over time as the number of poor connections in the last time period decreases with time. Therefore, the blacklisted MS may be removed from the blacklist at a later point in time and can reconnect to the AP 105-e. In this way, a previously blacklisted MS can have an opportunity to establish a good connection with AP 105-e. In some cases, the black listing threshold may be dynamic. For example, the black listing threshold may be the highest percentage MS with the highest number of bad connections (eg, within a given time period). As a result, MSs can be blacklisted or unblackened based on the number of poor connections associated with other MSs. For example, if other MSs accumulate more connection failures, one MS may no longer be within the highest percentage of MSs with connection failures. Similarly, if the number of misconnections of other MSs is decreasing (e.g. due to the passage of time), one MS will fall within the highest percentage of MSs with connectivity failures, and therefore , Can become blacklisted. As a result, the MS can be blacklisted or removed from the blacklist without any interaction with the AP.

  FIG. 11 is a message flow diagram 1100 illustrating another embodiment of wireless communication between the MS 115-f and the AP 105-e. The embodiment shown in message flow diagram 1100 may be similar to the embodiment shown in message flow diagram 1000. However, in this embodiment, MS115-f can be blacklisted.

  As previously described, the AP 105-e can receive the connection request 1105 from the MS 115-f. At block 1110, the AP 105-e can identify the MS 115-f. For example, the AP 105-e can identify the MS 115-f based on the received connection request 1105. At block 1115, AP 105-e may determine that MS 115-f is blacklisted.

  If block 1120 determines that MS 115-f is blacklisted, AP 105-e may deny the request 1105 for connection from MS 115-f. In some cases, the AP 105-e can ignore the connection request 1105. For example, the AP 105-e can determine not to respond to the connection request 1105. In other cases (not shown), AP 105-e may send a response to MS 115-f indicating that AP 105-e refuses to connect with MS 115-f.

  FIG. 12 illustrates one implementation of network management wireless communication between the MS 115-g and the first AP 105-f-1 and network management wireless communication between the MS 115-g and the second AP 105-f-2. FIG. 12 is a message flow diagram 1200 showing a form. APs 105-f-1, 105-f-2 may be examples of one or more aspects of the access point 105 described with reference to FIG. In one example, the first AP 105-f-1 may be a macro cell AP and the second AP 105-f-2 may be a small cell AP. MS115-g is an example of one or more aspects of MS115 described with reference to FIGS. 1, 2, 3, 4, 7, 7, 9, 10, and / or 11. It can be. AP105-f-1 and / or AP105-f-2 is one of AP105 described with reference to FIGS. 1, 5, 6, 7, 8, 9, 10, and / or 11. It may be an example of one or more aspects.

  In one configuration, the MS 115-g may use the first connection 1205 with the first AP 105-f-1 for data transmission. For example, the MS 115-g may have previously established a connection 1205 with the first AP 105-f-1 to engage in wireless communication with the first AP 105-f-1. In one example, MS 115-g may be using connection 1205 with first AP 105-f-1 for data traffic. At block 1210, MS 115-g may determine the motion state of MS 115-g.

  Having determined the motion state of MS 115-g, MS 115-g may generate a measurement report at 1215 that includes motion state information for MS 115-g. The MS 115-g may send a measurement report including motion state information to the first AP 105-f-1 (eg, serving cell). The MS 115-g may receive a response 1220 regarding a measurement report that includes motion state information. In some cases, where the network determines not to instruct MS 115-g to connect to another AP, MS 115-g may receive an instruction based on motion state information. For example, an instruction based on motion state information may be an acknowledgment (ACK) for measurement report 1215 without an instruction to connect to another AP. The network decides to instruct the MS 115-g to connect to another AP (eg, the second AP 105-f-2). In other cases, the MS 115-g acknowledges the measurement report 1215. A response (ACK) can be received as well as a command to connect to another AP (eg, a second AP 105-f-2).

  At block 1225, the MS 115-g may determine whether to connect to the second AP 105-f-2 based on the instructions 1220. If the instruction 1220 determines that it contains instructions to connect to the second AP105-f-2, the MS115-g decides to connect to the second AP105-f-2 based on those instructions can do. Upon determining to connect to the second AP 105-f-2, the MS 115-g can establish a connection 1230 with the second AP 105-f-2. In some cases, the MS 115-g may switch traffic to use the established connection 1230 with the second AP 105-f-2.

  FIG. 13 is a block diagram of a MIMO communication system 1300 including an AP 105-g and an MS 115-h. This system 1300 may represent an embodiment of the system 100 of FIG. The AP 105-g can be equipped with antennas 1334-a through 1334-x, and the MS 115-h can be equipped with antennas 1352-a through 1352-n. In system 1300, AP 105-g may be able to send data on multiple communication links simultaneously. Each communication link can be referred to as a “layer”, and the “rank” of the communication link can indicate the number of layers used for communication. For example, in a 2 × 2 MIMO system in which AP 105-g transmits two “layers”, the rank of the communication link between AP 105-g and MS 115-h is 2.

  At the AP 105-g, the transmit processor 1320 can receive data from the data source. The transmit processor 1320 can process the data. Transmit processor 1320 may also generate reference symbols and cell specific reference signals. A transmit (TX) MIMO processor 1330 may perform spatial processing (eg, precoding) on data symbols, control symbols, and / or reference symbols, if applicable, and transmit modulators 1332-a through 1332- An output symbol stream can be supplied to x. Each modulator 1332 may process a respective output symbol stream (eg, for OFDM) to obtain an output sample stream. Each modulator 1332 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink (DL) signal. In one example, DL signals from modulators 1332-a through 1332-x may be transmitted via antennas 1334-a through 1334-x, respectively.

  In the MS 115-h, the MS antennas 1352-a to 1352-n can receive DL signals from the AP 105-g, and can supply the received signals to the demodulators 1354-a to 1354-n, respectively. Each demodulator 1354 may adjust (eg, filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 1354 may further process input samples (eg, for example, OFDM) to obtain received symbols. MIMO detector 1356 can obtain received symbols from all demodulators 1354-a to 1354-n, perform MIMO detection on the received symbols where applicable, and provide detected symbols . Receive processor 1358 processes (eg, demodulates, deinterleaves, and decodes) the detected symbols, provides decoded data for MS 115-h to the data output, and provides decoded control information to processor 1380 or The memory 1382 can be supplied.

  The processor 1380 may execute stored instructions to instantiate the MS connection management module 210-c in some cases. In some embodiments, the MS connection management module 210-c may be an example of one or more aspects of the MS connection management module 210 described with reference to FIG. 2, FIG. 3, and / or FIG. . In some embodiments, the MS connection management module 210-c may determine whether to connect to and / or use the AP 105-g based on the motion state of the MS 115-h. . In other cases, the MS connection management module 210-c should connect to and / or use the AP105-g based on the MS115-h motion state and the AP105-g motion state. Can be determined. In one example, the MS 115-h may be connected to a first AP 105-g (e.g., macro cell AP) and determines whether to connect to a second AP 105-g (e.g., small cell AP). Can do. In some cases, MS 115-h includes antennas 1352-a through 1352-n, modulator / demodulators 1354-a through 1354-n, MIMO detector 1356, receive processor 1358, transmit processor 1364, and / or MIMO processor 1366. One or more of these may be used to communicate with the first AP 105-g and / or the second AP 105-g.

  On the uplink (UL), in MS 115-h, transmit processor 1364 may receive and process data from the data source. Transmit processor 1364 may also generate reference symbols for the reference signal. The symbols from transmit processor 1364 are precoded by transmit MIMO processor 1366 where applicable, and further processed by demodulators 1354-a through 1354 -n (e.g., for SC-FDMA, etc.) and AP105-g May be transmitted to the AP 105-g according to the transmission parameters received from. At AP 105-g, the UL signal from MS 115-h may be received by antenna 1334, processed by demodulator 1332, detected by MIMO detector 1336 when applicable, and further processed by receive processor 1338. Receiving processor 1338 may provide the decoded data to the data output and processor 1340.

  The processor 1340 may execute stored instructions for instantiating the AP connection management module 510-b in some cases. In some embodiments, the AP connection management module 510-b may be an example of one or more aspects of the AP connection management module 510 described with reference to FIG. 5 and / or FIG. In some embodiments, the AP connection management module 510-b can determine whether the MS should be blacklisted and can refuse to connect to the blacklisted MS. . For example, the AP connection management module 510-b can receive a connection request from the MS 115-h and determine whether the MS 115-h is blacklisted. If the MS 115-h is blacklisted, the AP connection management module 510-b can reject the request for connection. However, if the MS115-h is not blacklisted, the AP connection management module 510-b can connect to the MS115-h, monitor the connection with the MS115-h, and connect to the MS115-h. It can be determined whether the connection has a duration longer than a threshold. If the connection duration is less than the threshold, a connection failure may be associated with MS 115-h. AP connection management module 510-b blacklists MS115-h if the number of bad connections associated with MS115-h exceeds a threshold (for example, the number of connections in the last predetermined period) be able to.

  MS115-h components are implemented individually or collectively by one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware Can be done. Each of the mentioned modules may be a means for performing one or more functions related to the operation of the system 1300. Similarly, AP105-g components can be individually or assembled by one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Can be implemented. Each of the mentioned components may be a means for performing one or more functions related to the operation of system 1300.

  A communication network that can accommodate some of the various disclosed embodiments can be a packet-based network that operates according to a layered protocol stack. For example, communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. A radio link control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. The medium access control (MAC) layer can perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also use hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency. At the physical layer, transport channels can be mapped to physical channels.

  FIG. 14 is a flowchart illustrating a method 1400 for avoiding a connection failure. Of the MS 115 described with reference to FIGS. 1, 2, 3, 4, 7, 7, 8, 9, 10, 11, 12, and / or 13 for clarity. The method 1400 is described below with reference to one of these. In one implementation, the MS connection management module 210 described with reference to FIGS. 2, 3, 4, and / or 13 includes one or more sets of code for controlling the functional elements of the MS 115. Once executed, the functions described below can be implemented.

  At block 1405, the first connection with the first AP may be used for data transmission.

  At block 1410, the motion state of the MS may be determined. For example, the motion state of the MS can be determined based on sensor data for at least one sensor in the MS. In one example, the sensor data may include sensor data from a magnetometer (eg, acceleration of MS movement). In addition or alternatively, the sensor data may include sensor data (eg, angular rotation speed) from the gyroscope. In some embodiments, the motion state of the MS may be determined using the motion state determination module 305 described with reference to FIG. 3 and / or FIG.

  At block 1415, a second AP may be identified. For example, the second AP may be detected during a scan for available APs and may be identified based on a broadcast signal from that AP. In some embodiments, the operations in block 1415 may be performed by the connection usage module 310 described with reference to FIGS. 3 and / or 4.

  At block 1420, a determination may be made as to whether to use the second AP for data transmission based at least in part on the MS motion state. In some embodiments, the first AP may be a macrocell AP and the second AP may be a small cell AP. In these embodiments, the MS motion state is in the coverage area of the second AP for a sufficient time that it may be beneficial to connect to and / or use the second AP. It can be predicted whether or not.

  Accordingly, method 1400 can be used to avoid poor connectivity with an AP (eg, a small cell AP). Note that the method 1400 is only one implementation and the operation of the method 1400 may be reordered or possibly modified as other implementations are possible.

  FIG. 15 is a flowchart illustrating another method 1500 for avoiding poor connection. Of the MS 115 described with reference to FIGS. 1, 2, 3, 4, 7, 7, 8, 9, 10, 11, 12, and / or 13 for clarity. The method 1500 is described below with reference to one of these. In one implementation, the MS connection management module 210 described with reference to FIGS. 2, 3, 4, and / or 13 includes one or more sets of code for controlling the functional elements of the MS 115. Once executed, the functions described below can be implemented.

  At block 1505, the first connection with the first AP may be used for data transmission.

  At block 1510, the motion state of the MS can be determined.

  At block 1515, a second AP may be identified.

  At block 1520, the motion state of the second AP may be determined. In some cases, the motion state of the second AP may be learned based on at least one previous connection with the second AP. For example, the AP motion state may be learned based on the duration of the previous connection with the AP and the MS motion state over the previous connection with the AP. In some embodiments, the motion state of the second AP may be determined using the motion state determination module 305 described with reference to FIG. 3 and / or FIG.

  At block 1525, a determination may be made as to whether the difference between the MS motion state and the second AP motion state meets a threshold. In one example, the threshold may require the MS motion state to be the same as the AP motion state. In another example, the threshold may be a relative difference between the MS motion state and the AP motion state. If the difference between the MS motion state and the AP motion state meets a threshold, then at block 1530, the second AP may be used for data transmission. However, if the difference between the MS motion state and the AP motion state does not meet the threshold, then at block 1535, the second AP may not be used for data transmission. In some embodiments, the operations in blocks 1525, 1530, and 1535 may be performed by the connection usage module 310 described with reference to FIGS. 3 and / or 4.

  Thus, method 1500 can be used to avoid poor connections. Note that the method 1500 is only one implementation and the operation of the method 1500 may be reordered or possibly modified as other implementations are possible.

  FIG. 16 is a flowchart illustrating yet another method 1600 for avoiding poor connections. Of the MS 115 described with reference to FIGS. 1, 2, 3, 4, 7, 7, 8, 9, 10, 11, 12, and / or 13 for clarity. The method 1600 is described below with reference to one of the following. In one implementation, the MS connection management module 210 described with reference to FIGS. 2, 3, 4, and / or 13 includes one or more sets of code for controlling the functional elements of the MS 115. Once executed, the functions described below can be implemented.

  At block 1605, the first connection with the first AP may be used for data transmission.

  At block 1610, the motion state of the MS can be determined.

  At block 1615, a second AP may be identified.

  At block 1620, the motion state of the second AP may be determined.

  At block 1625, a determination may be made as to whether the movement state of the second AP is stationary. If the movement state of the second AP is not stationary (eg, moving), at block 1635, a backoff timer may be started. However, if the movement state of the second AP is stationary, at block 1630, a determination may be made as to whether the MS has moved or has moved in the recent past. If the MS is not moving or has not moved in the recent past, at block 1655, the second AP may be used for data transmission. However, if the MS is moving or has moved in the recent past, at block 1635, a backoff timer can be started. In some cases, further actions can be delayed until the back-off timer expires. In one example, the duration of the backoff timer may depend on past movements of the MS and / or specifically identified APs. At the expiration of the backoff timer, at block 1640, the MS motion state may be determined again.

  At block 1645, a determination may be made as to whether the difference between the MS motion state and the second AP motion state meets a threshold. If the difference between the MS motion state and the AP motion state meets a threshold, at block 1655, the second AP may be used for data transmission. However, if the difference between the MS motion state and the AP motion state does not meet the threshold, then at block 1650, the second AP may not be used for data transmission. In some embodiments, the operations in blocks 1625, 1630, and 1640 may be performed by the motion state determination module 305 described with reference to FIGS. 3 and / or 4, and blocks 1645, 1655, 1650, and The operations at 1635 may be performed by the connection usage module 310 described with reference to FIGS. 3 and / or 4.

  Thus, the method 1600 can be used to avoid poor connections. Note that the method 1600 is only one implementation and the operation of the method 1600 may be rearranged or possibly modified to allow other implementations.

  FIG. 17 is a flowchart illustrating another method 1700 for managing an interface for wireless communication. For clarity, one of the APs 105 described with reference to FIGS. 1, 5, 6, 7, 8, 8, 9, 10, 11, 12, and / or 13. The method 1700 is described below with reference to FIG. In one implementation, the AP connection management module 510 described with reference to FIGS. 5, 6, and / or 13 executes one or more sets of code to control the functional elements of the AP 105. The functions described below can be implemented.

  At block 1705, a request for a connection from the MS may be received.

  At block 1710, a determination may be made as to whether the MS is blacklisted. In some embodiments, the determination as to whether the MS is blacklisted may be made using the blocking module 615 described with reference to FIG.

  If block 1715 determines that the MS is blacklisted, the request for connection may be denied. In one example, a request for a connection can be ignored. In some embodiments, the request may be rejected by the blocking module 615 described with reference to FIG.

  Thus, the method 1700 can be used to avoid poor connections. Note that the method 1700 is only one implementation and the operation of the method 1700 may be rearranged or possibly modified to allow other implementations.

  FIG. 18 is a flowchart illustrating yet another method 1800 for avoiding a connection failure. For clarity, one of the APs 105 described with reference to FIGS. 1, 5, 6, 7, 8, 8, 9, 10, 11, 12, and / or 13. The method 1800 is described below with reference to FIG. In one implementation, the AP connection management module 510 described with reference to FIGS. 5, 6, and / or 13 executes one or more sets of code to control the functional elements of the AP 105. The functions described below can be implemented.

  At block 1805, a request for a connection from the MS may be received.

  At block 1810, the MS may be identified. For example, the MS may be identified based on the content of the request for a connection received from the MS.

  At block 1815, a determination may be made as to whether the MS is blacklisted. If it is determined that the MS is blacklisted, at block 1820, the request for connection may be denied. However, if it is determined that the MS is not blacklisted, at block 1825, a connection with the MS may be established. In some cases, the AP can monitor the connection with the MS.

  At block 1830, if the connection is broken, the duration of the connection may be determined. In some embodiments, the connection may be monitored and the duration of the connection may be determined using the connection monitoring module 605 described with reference to FIG.

  At block 1835, a determination may be made as to whether the duration is less than a threshold value. In some cases, a threshold may be set to avoid a connection when the duration of the connection may be too short for the connection to be a useful connection for the MS.

  At block 1840, a connection failure may be associated with the identified MS. For example, the number of connection failures can be associated with the identified MS, along with a time stamp for each connection failure.

  At block 1850, a determination may be made as to whether the number of identified MS connectivity failures within a time period is greater than a threshold. In one example, the threshold may be based on the number of poor connections within a time period (eg, the last 48 hours). For example, the threshold may be the highest percentage of MS based on the number of poor connections in the most recent time period. Thus, the particular MS that is blacklisted can change dynamically depending on the number of poor connections associated with other MSs. If the number of poor connections in that time period is greater than the threshold, at block 1845, the identified MS can be blacklisted. Although blacklisting is shown as relying on the disconnection with the AP, it should be understood that the MS can be blacklisted or removed from the blacklist without any interaction with the AP. For example, a change in the number of poor connections associated with other MSs can result in APs being blacklisted or removed from the blacklist.

  Thus, the method 1800 can be used to avoid poor connections. Note that the method 1800 is only one implementation and the operation of the method 1800 may be reordered or possibly modified to allow other implementations.

  The detailed description set forth above with reference to the appended drawings describes exemplary embodiments and is not intended to represent the only embodiments that may be implemented or fall within the scope of the claims. As used throughout this specification, the term “exemplary” means “serving as an example, instance, or illustration” and does not mean “preferred” or “advantageous over other embodiments”. . The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.

  The techniques described herein may be used for various wireless communication systems such as cellular wireless systems, peer-to-peer wireless communications, wireless local access networks (WLANs), ad hoc networks, satellite communication systems, and other systems. The terms “system” and “network” are often used interchangeably. These wireless communication systems include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and / or others Various wireless communication technologies can be used, such as various wireless technologies. In general, wireless communication occurs according to a standardized implementation of one or more radio communication technologies called radio access technologies (RAT). A wireless communication system or network that implements radio access technology may be referred to as a radio access network (RAN).

  Examples of radio access technologies that use CDMA techniques include CDMA2000, Universal Terrestrial Radio Access (UTRA), and the like. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. Releases 0 and A of IS-2000 are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is generally called CDMA2000 1xEV-DO, high-speed packet data (HRPD), or the like. UTRA includes wideband CDMA (WCDMA®) and other variants of CDMA. Examples of TDMA systems include various implementations of a global system for mobile communications (GSM). Examples of radio access technologies using OFDM and / or OFDMA include Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802. 20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM® are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.

  A communication network that can accommodate some of the various disclosed embodiments can be a packet-based network that operates according to a layered protocol stack. For example, communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. A radio link control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. The medium access control (MAC) layer can perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also use hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency. At the physical layer, transport channels can be mapped to physical channels.

  Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any of them Can be represented by a combination.

  Various exemplary blocks and modules described in connection with the disclosure herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices. May be implemented or implemented using discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor is also implemented as a combination of computing devices, eg, a DSP and microprocessor combination, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. obtain. The processor may optionally be in electronic communication with the memory, in which case the memory stores instructions that are executable by the processor.

  The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement functions may also be physically located at various locations, including distributed states such that some of the functions are implemented at different physical locations. Also, as used herein, including the claims, “or” used in the list of items modified by “at least one of” is, for example, “A, B, or C An enumeration such as “at least one of them” means A or B or C or AB or AC or BC or ABC (ie A and B and C).

  Both computer program products or computer readable media include computer readable storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media can be RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or a desired computer-readable program in the form of instructions or data structures. Any other medium that can be used to carry or store the code and that can be accessed by a general purpose or special purpose computer or general purpose or special purpose processor can be provided. Also, any connection is properly termed a computer-readable medium. For example, software transmits from a website, server, or other remote light source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, wireless, and microwave If so, wireless technologies such as coaxial cable, fiber optic cable, twisted pair, DSL, or infrared, radio, and microwave are included in the definition of the medium. As used herein, a disk and a disc are a compact disc (CD), a laser disc (registered trademark) (disc), an optical disc (disc), a digital versatile disc (disc). (DVD), floppy disk, and Blu-ray disc, which typically reproduces data magnetically, while the disc is optical with a laser To play data. Combinations of the above are also included within the scope of computer-readable media.

  The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit and scope of the present disclosure. obtain. Throughout this disclosure, the term “example” or “exemplary” indicates an example or instance and does not imply or require any preference for the referenced example. Accordingly, the present disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

100 wireless communication systems, systems, wireless networks
105 Base station (or cell), access point (AP), LTE / LTE-A access point, macro cell
105-a Small cell, small cell Wi-Fi access point, small cell access point
105-b, 105-c, 105-e, 105-g AP
105-d-1 first AP
105-d-2 second AP
105-f-1 1st AP
105-f-2 2nd AP
115 Communication devices, devices, mobile stations (MS), mobile devices
115-a, 115-b, 115-c, 115-d, 115-e, 115-f, 115-g, 115-h MS
125 Communication link
125-a first outgoing link
125-b Second transmission link, transmission link
130 core network
132 Backhaul link, backhaul
134 Backhaul link
110 Geographic area, coverage area
205 MS receiver module
210, 210-a, 210-b, 210-c MS connection management module
215 MS transmitter module
305 Motion state determination module
305-a Motion state determination module
310 Connection use module
310-a connection module
405 Motion detection submodule
410 Crowdsourcing Submodule
415 Learning Submodule
420 Connection monitoring submodule
425 Connection establishment submodule
430 Traffic switching submodule
435 Backoff submodule
505 AP receiver module
510, 510-a, 510-b AP connection management module
515 AP transmitter module
605 AP connection monitoring module
610 black listing module
615 Blocking module
705, 740, 825, 945, 1020, 1230 connection
720, 820, 925 broadcast
745 data traffic
805, 905, 1205 First connection, connection
850 traffic
1005, 1105 Connection request
1030 cutting
1220 Response
1215 Measurement report
1300 MIMO communication system
1320, 1364 Transmit processor
1330 Transmit (TX) MIMO processor
1332 Modulator, Demodulator
1332-a to 1332-x Transmit modulator, modulator
1334 Antenna
1334-a to 1334-x, 1352-a to 1352-n Antenna
1336, 1356 MIMO detector
1338, 1358 Receive processor
1340, 1380 processor
1342, 1382 memory
1352-a to 1352-n MS antenna
1354 Demodulator
1354-a to 1354-n Demodulator, Modulator / Demodulator
1366 MIMO processor, Transmit MIMO processor

Claims (46)

A method for managing data transmission, comprising:
Using a first connection with a first access point for data transmission;
Determining a movement state of the mobile device based on sensor data from at least one sensor in the mobile device;
Identifying a second access point;
Determining whether to use the second access point for data transmission based at least in part on the determined motion state of the mobile device. Determining the movement state of the mobile device comprises:
The method of claim 1, comprising determining the motion state based on an acceleration of movement of the mobile device. Determining the movement state of the mobile device comprises:
The method of claim 1, comprising determining the motion state based on an angular rotation speed of the mobile device. The method of claim 1, further comprising determining a motion state of the second access point. Determining whether to use the second access point for data transmission;
Determining whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point; The method according to claim 4. Determining whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point;
The method of claim 5, comprising determining to use the second access point when the determined motion state of the mobile device and the motion state of the second access point are the same. The method described. Determining whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point;
Use the second access point when a relative difference between the determined motion state of the mobile device and the determined motion state of the second access point is within a threshold. 6. The method of claim 5, comprising the step of determining: Determining the movement state of the second access point,
5. The method of claim 4, comprising learning the motion state of the second access point based at least in part on a previous connection with the second access point. Determining the movement state of the second access point,
5. The method of claim 4, wherein crowdsourcing information about the second access point comprises the information including the motion state of the second access point. Determining whether to use the second access point for data transmission;
5. The method of claim 4, comprising determining whether a backoff timer has been met. The method of claim 10, further comprising adjusting a duration of the backoff timer based at least in part on a previous connection with the second access point.   The method of claim 10, wherein a duration of the backoff timer is access point specific. Determining whether to use the second access point;
The method of claim 1, comprising determining whether a connection with the second access point should be established. Determining whether to use the second access point;
The method of claim 1, comprising determining whether to switch the data transmission to an established connection with the second access point. Associating the determined motion state with the identified second access point;
2. The method of claim 1, further comprising storing information about the identified second access point and its associated motion state.   The method of claim 1, wherein the first access point includes a macro cell access point and the second access point includes a small cell access point.   The method of claim 1, wherein the at least one sensor comprises at least one of an accelerometer and a gyroscope. An apparatus for managing data transmission,
Means for using the first connection with the first access point for data transmission;
Means for determining a movement state of the mobile device based on sensor data from at least one sensor in the mobile device;
Means for identifying a second access point;
Means for determining whether to use the second access point for data transmission based at least in part on the determined motion state of the mobile device.   19. The apparatus of claim 18, wherein the means for determining the motion state of the mobile device determines the motion state based on acceleration of movement of the mobile device.   19. The apparatus of claim 18, wherein the means for determining the motion state of the mobile device determines the motion state based on an angular rotation speed of the mobile device. The apparatus of claim 18, further comprising means for determining a motion state of the second access point. The means for determining whether to use the second access point for data transmission;
Means for determining whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point; 24. The apparatus of claim 21, comprising. An apparatus for managing data transmission,
A processor;
A memory in electronic communication with the processor, wherein the memory embodies instructions, the instructions by the processor,
Using a first connection with a first access point for data transmission,
Determining a movement state of the mobile device based on sensor data from at least one sensor in the mobile device;
Identifying a second access point, and determining whether to use the second access point for data transmission based at least in part on the determined motion state of the mobile device A device that is feasible to do things. The instructions for determining the motion state of the mobile device are by the processor,
24. The apparatus of claim 23, wherein the apparatus is executable to determine the movement state based on acceleration of movement of the mobile device. The instructions for determining the motion state of the mobile device are by the processor,
24. The apparatus of claim 23, wherein the apparatus is executable to determine the movement state based on an angular rotation speed of the mobile device. The instructions are executed by the processor;
24. The apparatus of claim 23, wherein the apparatus is executable to perform a movement state determination of the second access point. The instructions for determining whether to use the second access point for data transmission are by the processor,
To determine whether to use the second access point based on the determined motion state of the mobile device and the determined motion state of the second access point 27. The apparatus of claim 26, wherein the apparatus is executable. A computer program product for managing data transmission, comprising a non-transitory computer readable medium storing instructions, said instructions being processed by a processor,
Using a first connection with a first access point for data transmission,
Determining a movement state of the mobile device based on sensor data from at least one sensor in the mobile device;
Identifying a second access point, and determining whether to use the second access point for data transmission based at least in part on the determined motion state of the mobile device A computer program product that is executable to do things. The instructions for determining the motion state of the mobile device are by the processor,
30. The computer program product of claim 28, executable to perform determining the motion state based on acceleration of movement of the mobile device. The instructions for determining the motion state of the mobile device are by the processor,
30. The computer program product of claim 28, executable to perform the motion state determination based on an angular rotation speed of the mobile device. A method for managing connections,
Receiving a request for a connection from a mobile device;
At an access point, determining whether the mobile device is blacklisted when the number of previous connections associated with the mobile device exceeds a threshold; Blacklisted steps,
Determining that the mobile device is blacklisted, rejecting the request for the connection from the mobile device.   32. The method of claim 31, wherein the previous connection comprises a connection having a duration that fails to meet a time threshold.   32. The method of claim 31, wherein a previous connection comprises a connection where the mobile device is disconnected to leave the access point's coverage area.   32. The method of claim 31, wherein the mobile device is blacklisted when the number of previous connections in a time period exceeds a threshold. 32. The method of claim 31, further comprising establishing a connection with the mobile device upon determining that the mobile device is not blacklisted. Identifying the mobile device;
Determining a duration of the connection with the mobile device;
Identifying the connection as a previous connection when the duration of the connection fails to meet a threshold;
Identifying the time of the previous connection;
Associating the previous connection with the identified mobile device;
36. The method of claim 35, further comprising:   32. The method of claim 31, wherein the access point comprises a small cell access point. A device for managing connections,
Means for receiving a connection request from a mobile device;
In an access point, means for determining whether the mobile device is blacklisted, wherein the mobile device exceeds a threshold number of previous connections associated with the mobile device Sometimes blacklisted means,
Means for rejecting the request for the connection from the mobile device upon determining that the mobile device is blacklisted.   40. The apparatus of claim 38, wherein the previous connection comprises a connection having a duration that fails to meet a time threshold.   40. The apparatus of claim 38, wherein the previous connection comprises a connection where the mobile device is disconnected to leave the access point coverage area. A device for managing connections,
A processor;
A memory in electronic communication with the processor, wherein the memory embodies instructions, the instructions by the processor,
Receiving a connection request from a mobile device;
At an access point, determining whether the mobile device is blacklisted when the number of previous connections associated with the mobile device exceeds a threshold An apparatus that is executable to perform being blacklisted and rejecting the request for the connection from the mobile device upon determining that the mobile device is blacklisted.   42. The apparatus of claim 41, wherein the previous connection comprises a connection having a duration that fails to meet the time threshold.   42. The apparatus of claim 41, wherein the previous connection comprises a connection in which the mobile device is disconnected to leave the access point coverage area. A computer program product for managing a connection, comprising a non-transitory computer readable medium storing instructions, said instructions being processed by a processor,
Receiving a connection request from a mobile device;
At an access point, determining whether the mobile device is blacklisted when the number of previous connections associated with the mobile device exceeds a threshold A computer program product that is executable to make a request to be blacklisted and to reject the request for the connection from the mobile device upon determining that the mobile device is blacklisted .   45. The computer program product of claim 44, wherein the previous connection comprises a connection having a duration that fails to meet a time threshold.   45. The computer program product of claim 44, wherein the previous connection comprises a connection in which the mobile device is disconnected to leave the access point coverage area.

Images