JP6796925B2 - Context-aware wireless roaming - Google Patents

Description

The priority claim in this application is made by the attached application data sheet, request, or transmitter (if appropriate and if present). To the extent permitted by the type of application of the present application, the present application is incorporated by reference to the following applications.
Indian patent provisional application (case number FT-12-01IN and application number 3427 / DEL / 2012), filing date November 6, 2012, lead inventor Sudhir HIRUDAYARAJ, invention name, context-aware wireless roaming.

Areas: Wireless roaming of wireless mesh networks requires advances in cost, profitability, performance, efficiency, and practicality of use.

Related Techniques: References to techniques and concepts herein, including those intended for context, definition, or comparison, unless otherwise specified as known or well known, such techniques or concepts have been used in the past. It should not be construed as an acceptance of being known or part of the prior art. Any reference cited herein, including patents, patent applications, and publications, whether specifically incorporated or not, refers to this reference for any purpose. Is incorporated herein by reference in its entirety.
Prior art document information related to the invention of this application includes the following (including documents cited at the international stage after the international filing date and documents cited when domestically transferred to another country).
(Prior art document)
(Patent document)
(Patent Document 1) US Patent Application Publication No. 2009/5000502
(Patent Document 2) US Patent Application Publication No. 2005/0271021
(Patent Document 3) US Patent Application Publication No. 2005/0288021
(Patent Document 4) US Patent Application Publication No. 2004/0121772
(Patent Document 5) US Patent Application Publication No. 2003/0036374
(Patent Document 6) US Patent Application Publication No. 2005/02555856
(Patent Document 7) UK Patent Application Publication No. 2,464,480
(Patent Document 8) U.S. Patent Application Publication No. 2007/0209051
(Patent Document 9) US Patent Application Publication No. 2006/0019663
(Patent Document 10) Korean Publication No. 10-2003-0013363

Common wireless infrastructures that support roaming of mobile units are switches of traffic between clients connected to the mobile unit and those connected to a fixed backbone network, respectively. However, it is subject to one or more of the following problems:
1. 1. Unpredictable handoff pattern: The mobile unit can instantaneously roam between access points (APs) based on signal strength, which leads to unexpected changes in RF conditions and even unexpected data rates. Leads to change.
2. 2. Unnecessary handoffs: Each handoff from one access point to another involves disruption and link building, as well as additional penalties for rerouting traffic through the new access point and associated loss. .. In traditional wireless infrastructure, no measures have been taken to minimize such handoffs.
3. 3. Ping-pong effect: When the mobile unit selects a particular access point based purely on the basis of signal strength, the phenomenon related to the above unnecessary handoff problem frequently occurs and is bad or bad. Stable RF conditions result in roaming only to return to the original connection within a short period of time. This tends to occur when the mobile unit makes a roaming decision to the next access point too early or too late.
4. Sticking to Unstable RF Zones: Overlapping Fresnel zones and other RF reductions can result in unstable RF zones, but even if the signal strength is very strong, data traffic will be packet loss or throughput. It may be affected by fluctuations. For example, the area immediately around the antenna of a radio unit is an unstable area with unpredictable RF characteristics, but sudden fluctuations always occur when the mobile unit passes through the antenna. Traffic is automatically adversely affected if the mobile unit decides to roam to an access point in such an area.

Therefore, it is desired to improve the wireless infrastructure to better support roaming of mobile units and eliminate or avoid the above problems.

The present invention may be implemented in many ways, eg, processes, products, devices, systems, compositions, and computer-readable storage media (optical mass storage devices such as disks and / or magnetic mass storage devices). , Integrated circuits with non-volatile storage such as flash storage), or as computer-readable media such as computer networks in which program instructions are sent over optical or electronic communication links. A detailed description will describe one or more embodiments of the invention that allow improvements in cost, profitability, performance, efficiency, and usefulness of use in the above areas. The detailed description includes an overview to facilitate understanding of the rest of the detailed description. The overview includes one or more exemplary embodiments of systems, methods, products, and computer-readable media that follow the concepts described herein. As discussed in more detail in the conclusion section, the present invention includes all possible modifications and variants within the claims issued.

The wireless network infrastructure has static and roaming mobile nodes (including one or more types of access points), avoiding unnecessary handoffs and unstable RF zones, and at least selected context-aware type. It makes it possible to provide context-aware services by mobile nodes to connected clients. More specifically, at least each of the selected static nodes can provide context information to a mobile node that can recognize the context, and the context information is the relative position of the static node. And direction, details of the information handled by the static node, special flags indicating relevant and imminent changes in the parameters mentioned above (coming upcoming changes in direction, for example, at the end of the line of the terminal). , And the range of signal strength grounds that define the RF zone for stable mobile nodes. Each of the mobile nodes capable of recognizing each context creates a context map from time to time, which at least partially determines the next connection of the mobile node to the static node and the preferred timing of its changes. It makes it possible.

Figures 1а and 1b illustrate default route implementation plans for roadways and railways, respectively. Figures 1а and 1b illustrate default route implementation plans for roadways and railways, respectively. FIG. 2 is a flowchart showing an example of a default route viewed from the overall image of the mobile node. FIG. 3 illustrates the details of the hardware aspects of the access point (AP) based on selected embodiments. FIG. 4 illustrates the details of the software aspect of the access point based on the selected embodiment.

A detailed description of one or more embodiments of the invention will be given below in conjunction with the accompanying figures illustrating selected details of the invention. The present invention will be described in the context of embodiments. The embodiments are understood herein as merely exemplary, and the invention is expressly limited to any or all, or any or all of the embodiments herein. However, the present invention includes a number of alternative, modified, and equivalent forms. Various verbal labels (but not limited to, first, last, certain, various, different, other, specific, choices, so that the description is not monotonous. , Etc.) may be applied to distinguish the set of embodiments. As used herein, such labels are not expressly intended to convey quality or any form of preference or prejudice, but merely to conveniently distinguish between separate sets. It's just a thing. The order of the actions of some of the disclosed processes can be changed within the scope of the present invention. Whenever a variety of embodiments are used to describe differences in the characteristics of a process, method, and / or program instruction, a number of diverse embodiments follow predetermined or dynamically determined criteria. Other embodiments are contemplated in which one static selection and / or dynamic selection of a plurality of modes of operation corresponding to each of the above is performed. In the following description, a number of specific details are provided to provide a full understanding of the present invention. The details are shown by way of example, and the present invention may be practiced in accordance with the claims without some or all of those details. For the sake of clarity, the technical materials known in the art related to the present invention are not described in detail so as not to unnecessarily obscure the present invention.

Preface
This preface is included only to aid in a quicker understanding of the detailed description, and the present invention is limited to the concepts presented in this overview (including explicit examples, if any). By no means limiting, any overview paragraph necessarily is a contracted view of the entire subject and does not imply an exhaustive or limited description. For example, the following overview provides summary information limited to certain embodiments due to space and organization. There are many other embodiments, including embodiments in which the claims are ultimately derived, which are discussed throughout the rest of the specification.

The wireless network infrastructure has static and roaming mobile nodes (including one or more types of access points, also known as APs), avoiding unnecessary handoffs and unstable RF zones, and at least selected. It makes it possible to provide a context-aware service by a mobile node (also called a mobile unit) that can recognize the context to a connected client. More specifically, at least each of the selected static nodes (also called static units) allows the provision of context-aware mobile nodes (also called "roaming metadata"). Contextual information in context recognition is related and imminent changes in the location and direction of the static node (relative position and direction to the mobile node), the details of the information handled by the static node, and the above parameters. It relates to a special flag (also called a "marker") to indicate, and a signal intensity range that defines an RF zone for a stable mobile node.

According to some embodiments, the context information provided by the static node is an additional one or more resource utilization metrics of the static node (one or more calculations, storage, and network loading). Etc.) are included. According to various embodiments, the mobile node independently establishes additional contextual information locally, one or more: the location of the mobile node as determined by GPS, set by the administrator. The location of the mobile node in the context (eg, compensation for the end of the conformance, or the distance to a particular end), and a particular radio contact (individual) in multiple radio contacts of the mobile node set by the administrator. It independently and locally establishes additional contextual information such as antenna type, placement, and orientation) selection. According to various embodiments, the particular radio communication selection is either static or dynamic and follows a predetermined criterion (such as a determined role in the direction of the connection). ..

The contextual information, no matter how established, allows the context-aware mobile node to determine the best possible choice for handoffs with the next access point, reducing bad handoffs. It provides a location and / or direction-aware service to Klein connected to a context-aware mobile node. The location and direction context information provided by the static node enables location recognition of the context-aware mobile node, continues to determine the optimal handoff, and continues to provide location / direction services, which they continue to provide. It is also provided in areas where GPS services are not available / or in unstable areas (such as tunnels, subway connections, etc. where radio is available), and in embodiments where GPS is not available. is there. The resource utilization context information provided by the static node should belong to the static node that is not overloaded to the context-aware mobile node, assuming that other factors are equivalent. It allows you to make a choice.

Based on information, signal strength, and connection history obtained from said static nodes in the vicinity, each of the context-aware mobile nodes is imminent, which can affect their relative position, direction of movement, and operation. Create a context map for your changes and update the map regularly. The context map, at least in part, allows the next change of the static node of the context-aware mobile node and its preferred timing determination. The context map allows the mobile node to connect to the smallest possible static unit on a given route. This minimizes handoffs and the loss caused by them, avoids the ping-pong effect (as described in the background section), and also provides information such as video data from cameras installed along the road or route. It is preferred to provide access to information on sequential, ordered manners, such as.

In the embodiments herein, a static node (also known as a static unit) is an "access point" on the assumption that the mobile node (also known as a mobile unit) is not explicitly described as an access point. It is a general explanation of what can be done. In any case, according to various embodiments, one or more of each client node running with each mobile node is in ad hoc mode (peer-to-peer) or infrastructure mode (the mobile node is at least the client node). On the other hand, it is understood that it communicates by (playing a role as a mobile node). The mobile node implemented to recognize the context is called a context recognition type mobile node. In various embodiments, all mobile nodes in the mesh network are preferably, but not required, context-aware mobile nodes. Furthermore, from the perspective of a static access point, it is understood that mobile nodes are viewed as clients.

In various embodiments, at least some of the static nodes serve as one or more fixed backbones, the Internet, wide area networks, and gateways to the Internet. Moreover, in various embodiments, at least some static nodes provide access to a stream of individual information, such as an individual video camera connected to the static node.

An exemplary embodiment
What follows to conclude the introduction to the detailed description is a collection of exemplary embodiments, including at least some exemplary embodiments explicitly listed as "ECs" (exemplary combinations). Yes, it provides an additional description of the various types of embodiments according to the concepts described herein. These examples do not mean that they are exclusive, exhaustive, or restrictive to each other, and the invention is not limited to these exemplary embodiments, but within the scope of the published claims. Includes all possible modifications and variants.

EC1) A wireless mobile node
A means of automatically capturing and interpreting roaming metadata advertised by one or more static access points in the vicinity of the mobile node.
A method of automatically reconfiguring mobile nodes, incidentally based on default criteria, as a means of associating with the next access point in the sequence list communicated via the roaming metadata.
The mobile node and static access point are separate nodes in a wireless mesh network.

EC2) Automatically determines whether the wireless mobile node described in EC1 and the signal strength measured for the currently connected access point is within the default signal strength range communicated by the roaming metadata. Have a means to evaluate
The default criteria for the resetting is a function, at least the measured signal intensity does not exceed the defined signal intensity range.

EC3) The wireless mobile node described in EC1 and further having a means for automatically determining whether or not the mobile node encounters a marker with which the mobile node communicates via the roaming metadata.
The default criterion for the reset is a function that at least determines the encounter with the marker.

EC4) The wireless mobile node described in EC1 and further
Has a means to automatically determine the status of the Fresnel zone ,
The default criterion for the reset is a function, at least the status of the Fresnel zone .

EC5) The wireless mobile node described in EC1 further having means for automatically determining the location and direction of movement based on the roaming metadata.

EC6) The wireless mobile node described in EC1, the roaming metadata is embedded in information elements (IEs) of beacon frames of one or more static access points.

EC7) A wireless mobile node described in EC1, said mobile node is reciprocal with at least one revision of the 802.11 standard.

EC8) The wireless mobile node described in EC2, the mobile node can move via a conformance that moves along a nominally predetermined route along a transportation corridor.

EC9) The wireless mobile node described in EC8, the mobile node is a mobile access point, and can provide a context-based service to a mobile client connected to the mobile node.

EC10) The wireless mobile node described in EC9, the context-based service comprising a video stream from the static access point to which the mobile node is currently connected.

EC11) The wireless mobile node described in EC9, wherein the mobile node and a client of the mobile node provide a connection to a fixed backbone via the connected static access point.

EC12) The wireless mobile node described in EC8, the overall data throughput measured by said mobile node minimizes the loss of packets attributed to unstable RF zones and is non-optimal to access points. It increases by eliminating the necessary handoffs.

EC13) The wireless mobile node described in EC8, the default criteria for reconfiguring is the current signal strength, history of past connections, and advertisements of static access points of said mobile node in the vicinity. It includes a context map created by the mobile node based on the roaming metadata provided and updated regularly.

EC14) The wireless mobile node described in EC13, the context map further determines when the mobile node is disconnected from a predetermined static access point among the plurality of static access points. It is used for.

EC15) The wireless mobile node described in EC13, the context map further indicates at what timing the mobile node enables connection to a predetermined static access point among the plurality of static access points. It is used to determine.

EC16) A wireless mesh network
A means for identifying the ( access) order of static node access points in the wireless mesh network, and
A means of delivering the order to the mobile nodes of the wireless mesh network,
A means of determining the next static node access point that is optimal for each mobile node as a roam destination in the static node access point,
Have,
The handoff of the mobile node between the static node access points, which is contrary to the order , is eliminated.

EC17) A computer-readable medium that has a set of instructions stored in the medium and causes the processing element to perform an operation when executed by the processing element.
Automatically captures, interprets, and interprets roaming metadata advertised by one or more wireless static access points on nearby wireless mobile nodes.
Accidentally, based on the default criteria, the wireless mobile node automatically connects to the next best wireless static access point at the wireless static access point based on the sequence list communicated by the roaming data. Reset and reset
It automatically assesses whether the signal strength of the observed currently connected wireless static access point is within the defined signal strength range communicated by the roaming metadata.
From a predetermined wireless static access point among the plurality of wireless static access points, it is automatically determined at what timing the wireless mobile node needs to be connected and disconnected.
It automatically determines if the wireless mobile node has encountered the marker communicated by the roaming metadata.
The location and direction of movement of the wireless mobile node are automatically determined based on the roaming metadata.
The wireless mobile node and the wireless static access point are different nodes in a wireless mesh network.

EC18) A method that automatically captures and interprets roaming metadata advertised by one or more wireless static access points on nearby wireless mobile nodes.
Automatically connect the wireless mobile node to the next best wireless static access point in the wireless static access point, based on the sequence list communicated by the roaming metadata as a response to the default criteria. It is intended to be reset
The wireless mobile node and the wireless static access point are different nodes in a wireless mesh network.

EC19) The method according to EC18, which automatically determines whether the measured signal intensity of the currently connected access point is within the predetermined signal intensity range communicated by the roaming metadata. To evaluate
The default criterion for the reset is a function such that the measured signal intensity exceeds at least the range of the predetermined signal intensity.

EC20) The method described in EC18, which also automatically determines if the mobile node has encountered a marker communicated by the roaming metadata.
The default criterion for the reset is a function, at least determining that the marker has been encountered.

EC21) The method described in EC18, wherein the default criteria for the reconfiguration is the current signal strength, history of past connections, and static access points at the nearby mobile node by the mobile node. It has a context map created by the mobile node based on the roaming metadata advertised in and updated regularly.

EC22) In the method described in EC21, the context map is further used to determine when to disconnect from the predetermined static access point.

EC23) In the method described in EC21, the context map is further used to determine when the mobile node is enabled to connect to a predetermined static access point among the plurality of static access points. It is used.

EC24) The method described in EC18, which automatically determines the status of the Fresnel zone.
The default criteria is a function that minimizes packet loss due to at least the Fresnel zone status and unstable RF zones measured by the mobile node, and unnecessary handoffs to suboptimal access points. The overall data throughput increased by removal.

EC25) In the method described in EC18, the location and direction of movement are automatically determined based on the roaming metadata.
The mobile node is the mobile node enabled to provide a service to a mobile client connected to the mobile node based on the context.

EC26) The method described in EC25, wherein the mobile node is enabled to perform a reconfiguration and provides context-based services in a radio-enabled area without the need for a clear view of the sky. To do.

EC27) In the method described in EC21, the context map further includes context information, the context information is established by the mobile node independently of the context information, and the context information is static. It was provided by the access point.

EC28) According to the method described in EC27, the context information established by the mobile node is the position of the mobile node determined by GPS, the position set by the administrator of the mobile in the preference, and the mobile. It includes one or more of a particular radio preference set by the administrator and the computed result of a default function on multiple radios of a node.

EC29) In the method of EC21, the roaming data advertised by the static access point is one or more: the position and orientation of the static node relative to the mobile node, served by the static node. It has information details, higher signs of imminent change, a region of signal intensity values that defines a stable RF zone on the mobile node, and a metric of utilization of at least one of the static nodes.

EC30) In the method described in EC18, the roaming metadata is embedded in one or more 802.11 management frames.

Optimal connection for mobile wireless roaming
The various examples provide a range of signal intensities relative to each access point of the static node and are configured to make the best decision when each context-aware mobile node connects to the access point and then disconnects. Will be done. This is done by using a pair of signal intensity values (Rmin, Rmax). Rmin identifies the lowest signal strength threshold and allows connection with the access point. At signal intensities below Rmin, the mobile unit does not make a connection with the access point. Rmax specifies the maximum signal intensity threshold, and connection with access points beyond that is not desirable. For signal intensities above Rmax (and associated with short paths), the mobile unit automatically disconnects from the access point corresponding to the signal above Rmax, even if that signal is lower than that of the current access point (and). And perhaps even if it is located farther from the current access point), it is desirable to connect to the next best access point.

In at least some contextual cognitive embodiments, the signal intensity corresponds to the received signal intensity index (RSSI), and RSSIs above Rmax (also referred to as "RSSI-bad") are "bad Fresnel". Associated with "zone" (or simply "bad zone"). The location of the bad zone (which is associated with harmful interference from echoes) is generally different for each access point with respect to the RSSI-bad and fractionated area. Bad Fresnel Zone is a range that can be predicted by the height of the antennas of static nodes and mobile nodes and the distance between the antennas. It is determined experimentally by (known).

Mobile wireless roaming along a default route
The context-aware roaming techniques taught herein are mobile nodes (heavy rails, light rails, and fast train monorails, maglev railways, metros, subways, elevated railways, cities, in embodiments of wireless networks. Especially useful when inter-electric rails, trams, new transportation systems, other airport transportation, and buses) repeatedly roam using default routes, especially as seen in metropolitan traffic developments. is there. In the embodiment with such a predetermined path, the infrastructure is with an order to the access point of static nodes, to enable it to transmit the order to the mobile node. The mobile node is then enabled to be used to determine the best next access point to roam to, thereby eliminating unnecessary unordered handoffs (like ping-pong), at least some default. in embodiments involving path, whereas to the direction of the loop, or mutually different directions parallel path (for example, "outbound" and "inbound") is present with each set of access points attached sequence for each path direction To do. In such embodiments, each of the mobile node an access point sequence is attached, it is programmed to connect only those corresponding to the direction in which the node proceeds. This enables the use of traditional static node access points provided by software for managing the management side to broadcast static roaming metadata.

In the first type of default route embodiment, the order is transmitted via access point sequence numbers (eg, AP1, AP2, AP3 ... AP4) contained in the roaming metadata. In an embodiment relating to a second type of default route (not necessarily including the first type), the order is by a context-aware mobile node, for example as a test run (calibration, mapping, training run) of the default route. Detected via (known).

Implementation of metadata for roaming
As an example only, in at least some 802.11 embodiments, the roaming metadata is broadcast (advertised) via data embedded in the information element (IE) of the beacon frame in 802.11. .. That is, the IE of the beacon frame in 802.11 is used to make roaming more efficient. Context-aware mobile nodes are enabled to absorb roaming metadata from IE, which traditional mobile clients simply ignore. According to various embodiments, roaming metadata (context information) is propagated using one or more of the following: a) IE of the 802.11 beacon frame, and b) 802.11 of one or more. Other management frames, one or more probe requests and responses to them.

To take advantage of traditional hardware and software for static node access points, the processing management software programs the access point to deliver the desired roaming metadata (eg, via 802.11 beacon frame IE). Although used for this, it is static roaming metadata in at least some embodiments and is specific to each of the access points. That is, any of the relative position and orientation (relative to the static node having the mobile node), bad zone information, markers, and other roaming metadata programmed for broadcasting is at each access point. Everything.

To take advantage of other traditional hardware, the context-aware mobile node has been extended (such as by upgrading firmware) to capture and decode the roaming metadata from the static node, making a default decision in real time. The ability to evaluate the tree in terms of roaming metadata and other metric data (eg RSSI) and dynamically modify their access point connections as appropriate is added.

Roaming example based on a default route
1a and 1b are plan views illustrating examples of managed routes, which are mobile nodes based on roadways and railroads, respectively. Some features are shown more identifiable in FIG. 1a, but this is to reduce visual complexity and the embodiments are identical unless otherwise specified. .. In FIG. 1a, two small segments of the roadway are illustrated at the top of the figure as roadway RDW1 121 and roadway 2 122. The abbreviations in the upper center of these figures are intended to indicate that there is a considerable distance to the left and right of the road / rail segment. The following description describes the embodiment of FIG. 1a. Replace "Railway", "Railway", RLW1, RLW2, MN5, MN6, MN7, and MN8 with "Carriageway", "Carriageway", RDW1, RDW2, MN1, MN2, MN3, and MN4, respectively. And the embodiment of FIG. 1b will be described. Each mobile node is installed at a selected location within each convergence (eg, one of the two ends of the train, or a position that offsets the distance from one end, for convenience and engineering economy. Determined from the aspect of the situation).

In some of the embodiments, there are a plurality of mobile nodes in the same convergence (such as placing mobile nodes at each end of the train).

As shown in detail below, the mobile nodes MN1, MN2, MN3, and MN4 move on the roadway, and the static nodes SN1, SN2, SN3, and SN4 are adjacent to the roadway. Illustratively, SN1 is statically associated with SN4 (via link 150-10), and similarly SN2 is statically associated with SN3 (via link 150-11). SN3 and SN4 are further associated with SN6 and SN5 (with various links illustrated), network 160, respectively, and further have SN7, SN8, SN9, and SN10. SN8 is also designated as a central server, and in some embodiments features for centralized management and / or storage of at least some static and mobile nonodes (monitoring, serving, authorization, operation logging, and backup). And it is used as a database). Network 160 supports the implementation of default routes in context-aware roaming in the backbone or part thereof, intranets, wide area networks, or other network infrastructures. In some embodiments, the network 160 is connected to or is part of the Internet 170. The associations are for illustration purposes only, and different associations are possible.

At the time corresponding to the illustration, the mobile nodes MS1 111 and MS2 112 are moving from right to left on the roadway RDW1 121. The static nodes SN1 101 and SN2 102 advertise that they control right-to-left traffic according to an ordered sequence and that they each have a bad Fresnel zone BFZ1 141 and BFZ2142. At the same time, in the time of illustration, the mobile nodes MN3 113 and MN4 114 are moving from left to right on the roadway RDW2 122. Static nodes SN3 103 and SN4 104 are they responsible for the traffic from the left according to (SN3 after SN4) ordered sequence to the right, to advertise that it have a respective defective Fresnel zone BFZ3 143 and BFZ4 144. Each of the bad Fresnel zones corresponds to a static node and is demarcated by the advertised Rmax value.

While moving from right to left, MN1 and MN2 are programmed to be associated with only SN2 and SN1 according to the sequence numbers advertised by these static nodes. In the time corresponding to the illustration, the MN2 is associated with the SN2, but enters the BFZ2 and changes its association with the SN1, which is detected corresponding to the Rmax value advertised for the BFZ2. It is inferred from the RSSi value. Similarly, while moving from left to right, MN3 and MN4 are programmed to be associated with only SN3 and SN4 according to the sequence numbers advertised by their static nodes. At the moment shown, MN3 is associated with SN4, but changes its association to SN3 with intrusion into BFZ4, which is the detected RSSI corresponding to the Rmax value advertised for BFZ4. It is inferred through the value.

Each static node of SN1, SN2, SN3, and SN4 is optionally connected to at least each of the video cameras VC1 181, VC2 182, VS3 183, and VC4 184. According to various embodiments, the video camera is intended for at least the operator and / or passenger of the corresponding static node associated with the mobile node (eg, such as a traffic stop, platform, or surrounding area). It provides a selected video stream in which improvements in safety, security, and efficiency (eg, by showing pedestrian density / traffic flow) are noticeable in advance.

FIG. 2 is a flowchart illustrating an embodiment of a default route in consideration of a mobile node. The mobile node (eg, any of MN1, MN2, MN3, or MN4 in FIGS. 1a or 1b) is initialized in action 210. In action 220, the new ordered sequence of the access point corresponding to a particular predefined path (AP) is approved, and the specific access points in the ordered sequence are selected and used with associated by the mobile node. In action 230, the roaming metadata currently advertised by the associated access point is captured, decoded, and further executed (if applicable, performed as needed or in place). To be taken).

The association with the current access point will continue in harmony with the regular status assessment. In particular, regular assessments are performed to determine if a mobile node has entered a bad Fresnel zone or has detected a marker (advertised by roaming metadata) indicating a route change (eg, a turnaround at the final terminal of the line). Will be done. An assessment of the defective Fresnel zone (exemplified by whether RSSI exceeds Rmax) is represented by decision 240. If the mobile node is in the bad Fresnel zone, in action 245, the mobile node changes its connection to the next access point in the current sequential sequence. If it is assumed that the mobile node is not in the bad Fresnel zone, a rerouting marker check is performed in decision 250. Upon notification of the route change (by checking the corresponding marker), the control flow loops back to the execution of action 220 (as described above). If neither a bad Fresnel zone nor a rerouting is detected, the connection to the current access point continues unchanged and the control flow loops back to perform action 230 (also as described above).

AP hardware
FIG. 3 illustrates selected details of hardware aspects in an embodiment of AP (either static or mobile node in FIGS. 1a or 1b). The illustrated APs are used in various types of storage, including volatile read / write memory "memory bank" elements 301.1-2 via DRAM memory interface 302, and non-volatile read / write memory flash 303 and EEPROM 304 elements. It includes a concatenated processor 305. According to various embodiments, the processor further comprises an Ethernet® interface 306 for providing multiple Ethernet® ports 307 for establishing a wired link and packets for establishing a wireless link. It is connected to wireless interfaces 309- A and 309-N for providing wireless communication. The wired link provides communication between the illustrated AP and, for example, other APs or centralized resources. The radio link provides communication between the illustrated AP and, for example, another AP and / or a client of the illustrated AP. In some embodiments, some wireless interfaces are compatible with the IEEE 802.11 wireless communication standards (eg, any of 802.11a, 802.11b, 802.1g, and 802.11n). In some embodiments, the GPS subsystem 310 provides a source of additional location context information. In some embodiments, one or more nodes are a) different types b) different installation locations, and c) a plurality of nodes with one of the directions in which different administrators are set. Has a radio . For purposes of illustration only, in some embodiments, different antennas of the same mobile node are configured by the administrator to point in opposite directions. The illustrated area securing is merely an example, and another similar AP embodiment is also possible.

In operation, the processor fetches instructions from any combination of multiple storage elements (such as DRAM, flash, and EEPROM) that operate as computer-readable media and executes the instructions. Some instructions correspond to the software associated with the behavior of the mobile node, which captures the mobile node, decodes it, and executes the advertised roaming metadata for context-aware wireless roaming. Some instructions correspond to software that takes into account bad Fresnel zones and operates mobile nodes according to the selection of the best access point. In some embodiments, some instructions correspond to software associated with default route-based roaming. In some embodiments, some instructions correspond to all or part of the software illustrated in FIG. 4, such as NMS Manager 401, Ethernet Driver 414, and Wireless Driver 415. ..

AP software
FIG. 4 is a selective detail of software aspects in an embodiment of an AP such as either the static or mobile node of FIG. 1a or 1b, as further described below. Various software modules are illustrated in the context in which the Associated Press and communication capabilities are conceptually illustrated as hardware interface 420. The software illustrated is Network Management System Manager (also known as NMS Manager, NMS) that interacts with Network Interface Manager 402 and Fault, Configuration, Accounting, Performance, and Security Manager (FCAPS Manager, also known as FCAPS ). ) 401 is included. The network interface manager is illustrated on Ethernet® interface 306 (also shown in FIG. 3) and wireless interface 309 (representative of wireless interfaces 309-A ... 309-N in FIG. 3). It manages material network interfaces such as AP's Ethernet® and wireless interfaces. The network interface manager assists the NMS in passing from the management software to FCAPS in changing dynamic settings (at the request of the user). In some embodiments, the FCAPS includes the ability to store and read configuration information, and the FCAPS function serves a function that requires persistence configuration information for all applications. FCAPS optionally helps collect error information and statistics and performance data from various running AP modules. FCAPS selectively passes some or all of the collected information, statistics, and data to the NMS.

The kernel interface 410 is interfaced with the AP core function 411 and the flash file system module 413. The AP core function 411 includes a routing and transport protocol layer 411a implemented on both static and mobile nodes, and at least a context recognition function 411b implemented by context-aware mobile nodes. The transport protocol includes TCP and UDP. In some embodiments, the minimal static node AP core functionality does not require any changes from the routing and transport protocol layer 411a implemented in traditional APs, and context-aware metadata is traditional processing management. It is programmable to be advertised through the application (as described elsewhere herein). In some embodiments, the mobile node AP core function can additionally implement the context recognition function 411b by upgrading the firmware of the conventional AP. The context recognition function 411b has a function of capturing, decoding, and using roaming metadata advertised by the selected static node. According to various embodiments, the mobile node independently locally provides additional contextual information (roaming metadata), such as one or more, within the location of the mobile node as determined by the GPS subsystem, within a convergence. Establish an administrator-configured mobile node location, and an administrator-configured preference for a particular radio (antenna type, placement, and orientation) of multiple mobile node radios . Illustrative use of roaming metadata by mobile nodes is: roaming based on AP-specific (Rmin, Rmax) signal intensity boundaries, based on commanded AP sequences (eg, certain default routes). Roaming, marker recognition-based actions (eg adopting different commanded AP sequences at the end of the transit line), and context-aware service provision (eg video stream from the next transit stop location) included.

It is conceptually illustrated that the flash file system module interfaces with the flash driver 416 and the flash river is coupled to a non-volatile hardware element 423, which is shown in the flash 303 and FIG. It represents a flash file system (ie, data organized in non-volatile memory) stored in any combination of EEPROM 304 elements. Layer 2 Abstraction Layer 412 interfaces with Ethernet routing and transport protocols and radio drives, 414 and 415, respectively. The Ethernet (registered trademark) driver is conceptually illustrated as being connected to the Ethernet (registered trademark) interface 306 of FIG. In some embodiments, the software includes a serial driver. The software is stored on a computer-readable medium (ie, any combination of DRAM, flash and EEPROM elements) and is executed by a programmable element such as processor 305 in FIG. The partitioning illustrated above is merely an example, and many other similar layer arrangements are possible.

In various embodiments, all or part of the software, which is associated with operating an AP to capture, decode, and execute roaming metadata for advertised context-aware wireless roaming. Or all or part of the software related to operating mobile nodes according to the best access point selection considering bad Fresnel zones, and / or performing roaming according to a given route. All combinations are included in any combination of NMS Manager 401, AP Core Function 411, Ethernet Driver 414, Radio Driver 415, and other software modules not specifically shown in FIG. ..

Example of implementation technique
In some embodiments, all or one of the operations performed by a processor, microprocessor, on-chip system, application-specific integrated circuit, hardware accelerator, or some other integrated circuit. Various combinations of parts, all or part of operations that provide all or part of the aforementioned AP and context-aware operations such as the control flow of FIG. 2 and the AP core function of FIG. Is specified by a specification that interacts with execution by a computer system. The specification is consistent with various descriptions such as hardware description language, circet description, netlist description, mask description, or layout description. Descriptions by way of example include: Verilog, VHDL, SPICE, as well as SPICE variations such as PSpice, IBIS, LEF, DEF, GDS-II, PASIS, or other descriptions. In some embodiments, the execution includes any combination of interpretation, compilation, simulation, and synthesis, which are logic and / or circets suitable for inclusion in one or more integrated circuits. Produce, certify, or 1 or specify. Embodiments are therefore devised in which at least a portion of any one or more of the context-aware elements described herein is implemented in hardware. Each of the integrated circuits can be designed and / or manufactured according to different techniques according to different embodiments. These techniques include programmable techniques (field or mask programmable gateway array integrated circuits), semi-custom techniques (all or partly cell-based integrated circuits), and fully custom techniques (substantially specialized integration). Circuits), combinations of these, or any other technique that conforms to the design and / or manufacture of integrated circuits.

In some embodiments, all or part of an operation characterized by having a set of instructions stored on a computer-readable medium is the execution of one or more program instructions, one or more. Executes binary instructions produced by the interpretation and / or compilation of statements in the source and / or script language of, or by compiling, translating, and / or interpretation of programming and / or script language statement information. This is processed by executing and / or interpreting one or more program instructions. The statement is compatible with any standard programming or scripting language (eg C, C ++, Fortran, Pascal, Ada, JAVA®, VBScript, and Shell). One or more program instructions, language statements, or binary instructions are optionally stored in one or more computer-readable storage media elements. In various embodiments, some, all or various parts of a program instruction are implemented as one or more functions, routines, sub-routines, inline routines, procedures, macros, or parts thereof.

Conclusion
Certain choices are made in the description solely for convenience in creating the text and drawings, and unless otherwise indicated, those choices are by themselves the structure of the aforementioned embodiments or It should not be construed as conveying additional information about the behavior. Examples of selections include the specific organization or assignment of designations used for figure numbers, and element identifiers (such as callouts and numeric identifiers) used to identify and refer to features and elements of embodiments. Contains a specific organization or assignment of.

The word "inclusions" or "inclusion" is clearly intended to be interpreted as an abstraction that describes a logical set of open ranges, and is physically unless the word "within" is explicitly followed. It is not intended to convey inclusion.

Although the aforementioned embodiments have been described in some detail for clarity of explanation and understanding, the present invention is not limited to the details presented. There are many embodiments of the present invention. The embodiments of the disclosure are exemplary and not limited.

It will be appreciated that many variations in configuration, arrangement, and use are possible that are consistent with the description, and that these modifications are within the claims of the issued patent. For example, the bit widths of interconnects and functional units, clock rates, and the types of techniques used can vary according to different embodiments in each component block. The names given to interconnects and logic are merely examples and should not be construed as limiting the concepts described. The order and arrangement of the flow chart and flow chart processes, operations, and functional elements can vary according to various embodiments. Also, unless otherwise specified, the specified range of values, the maximum and minimum values used, or other specific specifications (eg, the type of flash memory technology, the number of entries or stages in registers and buffers) , Are merely those of the aforementioned embodiments and are expected to track improvements and changes in the techniques and should not be construed as a limitation.

Instead of the techniques described above, functionally equivalent techniques known in the art can be used to perform various components, subsystems, actions, functions, routines, subroutines, inline routines, procedures, macros, or parts thereof. Can be used for. Also, many functional aspects of the embodiment have faster processing (to facilitate the transition of previously hardware features to software) and higher integration densities (formerly software hardware). Selectively hardware (ie, dedicated circuits, etc.) or software (ie, programmed controller), depending on design constraints and technical trends that depend on the embodiment (to facilitate the transition to wear). It is also understood that this can be achieved (or by some method with a processor). Specific variations of the various embodiments are not limited to, but are limited to different divisions, different form factors and configurations, use of different operating systems and other system software, different interface standards, network protocols, etc. Or the use of communication links, including other variations that should be expected when implementing the concepts described herein in accordance with the specific technical and business constraints of a particular application.

Each embodiment is described with details and environmental context that go far beyond what is required for minimal implementation of many aspects of each of the aforementioned embodiments. Those skilled in the art will appreciate that some embodiments omit the components or functions of the disclosure without altering the basic collaboration between the remaining elements. Therefore, it is understood that many of the disclosure details are not required to implement the various aspects of the aforementioned embodiments. To the extent that the remaining elements are distinguishable from the prior art, the components and features omitted are not limiting the concepts described herein.

All such modifications in design are not substantial changes to the teachings conveyed by the aforementioned embodiments. It is also understood that the embodiments described herein have broad applicability to other computing and networking applications and are not limited to the particular application or industry of the aforementioned embodiments. To. Therefore, the present invention should be construed as including any possible modifications and variations that are within the claims of the issued patent.

Claims (20)

It ’s a mobile node,
Means for automatically obtaining interpret one or more roaming metadata advertised by a static access points in the neighborhood of the mobile node,
In response to the default criteria, and the roaming metadata based on the order list of a plurality of different directions brought about by the best following static access of the said mobile node more static access points A means to automatically reconfigure to connect to the point,
Have,
The best next static access point is
One of the first pre-fixed set of static access point of the first ordered list of the ordered list of each of the plurality of directions when moving a specific path on which there is the mobile node in a first direction Yes,
One of the second pre-fixed set of static access point of the second ordered list of the ordered list of each of the plurality of directions when the mobile node moves on the particular path in a second direction Oh it is,
Wherein at least a portion of the first pre-fixed set of static access point does not overlap with the set of static access point of the second pre-fixed,
The mobile node and the static access point are different nodes of the wireless mesh network.
Mobile node. The mobile node according to claim 1, and the signal intensity measured for one static access point currently connected is within the range of the predetermined signal intensity notified by the roaming metadata. Has a means to automatically evaluate
The default criterion is a function such that at least the intensity of the measured signal exceeds the range of the predetermined signal intensity.
Mobile node. The mobile node according to claim 1, further comprising means for automatically determining whether the mobile node encounters a marker notified by the roaming metadata.
The default criterion is a function that determines at least whether the marker has been encountered.
Mobile node. The mobile node according to claim 1, wherein the default criteria is based on the current signal strength of at least some of the static access points, past connection history, and advertised roaming metadata. Has a context map created by the mobile node and updated regularly.
Mobile node. The mobile node according to claim 4, wherein the context map is further used to determine when the mobile node disconnects from a predetermined static access point among the plurality of static access points. A mobile node that is a thing. The mobile node according to claim 4, wherein the context map further determines when a connection to a predetermined static access point of the plurality of static access points of the mobile node is activated. A mobile node that is used for. The mobile node according to claim 1, further recognizing that the index of the intensity of the received signal is larger than the threshold value, and automatically recognizing that the mobile node is within the Fresnel zone. Have and
The default criteria is at least a function of the mobile node being within the Fresnel zone.
Mobile node. The mobile node according to claim 1, further comprising means for automatically determining the location and direction of movement based on the roaming metadata.
The mobile node is a mobile access point enabled to provide context-based services to mobile clients connected to the mobile node.
Mobile node. It's a wireless mesh network
A means by which the static node access points of the wireless mesh network specify the access order of the static node access points of the wireless mesh network in each of a plurality of directions.
A means by which the static node access point transmits the access order for each of the specified directions to the mobile node of the wireless mesh network.
The mobile node, means for determining the best next static node access point of the plurality of the static node access point as Rohm destinations of the mobile node,
Have,
The best next static node access point first first access order of the access order of each of the plurality of directions when moving on special route that each of the mobile node in a first direction already constant of one of the set of static nodes access point, when the respective mobile node moves on the particular path in the second direction and the second access of the plurality of direction-specific access order Ri 1 Tsudea the second previously fixed set of static nodes access point sequence,
Wherein at least a portion of the first pre-fixed set of static access point does not overlap with the static access point of the second pre-fixed,
Of the mobile node handoffs between the static node access points
Those that violate the access order for each of the plurality of directions are deleted.
Wireless mesh network. A non-transitory computer-readable medium that has a set of instructions stored on the medium and causes the processing element to perform an operation when they are executed by the processing element.
Automatically acquire and further interpret roaming metadata advertised by one or more wireless static access points in the vicinity of the wireless mobile node.
Depending on the default criteria, and on the basis of the order list for each of a plurality of directions brought about by the roaming metadata, the best of the next radio static access points among the plurality of the radio static access point It automatically reconfigures the wireless mobile node to connect,
The best next radio static access point, when moving on a particular route is the wireless mobile node in a first direction a first of the first ordered list of the ordered list of each of the plurality of directions It is one of a set of previously fixed radio static access point, when the mobile node moves on the particular path in the second direction of the second ordered list of the ordered list of each of the plurality of directions 1 Tsudea set of radio static access point of the second pre-fixed is,
Wherein at least a portion of the first pre-fixed set of static access point does not overlap with the set of static access point of the second pre-fixed,
The wireless mobile node and the wireless static access point are different nodes in a wireless mesh network.
A computer-readable medium that is a storage medium. The non-transitory computer-readable medium of claim 10, which causes the processing element to perform an operation when further instructions are executed.
It automatically evaluates that the measured signal intensity of one of the currently connected wireless static access points is within the defined signal intensity range indicated by the roaming metadata.
Automatically determines when the wireless mobile node needs to be connected and disconnected from a predetermined wireless static access point among the plurality of the wireless static access points.
Computer-readable medium. The non-transitory computer-readable medium of claim 11, which causes the processing element to perform an operation when further instructions are executed.
It automatically determines if the wireless mobile node itself has encountered a marker signaled by the roaming metadata.
The location and direction of movement of the wireless mobile node is automatically determined based on the roaming metadata.
Computer-readable medium. The way
Automatically retrieves , interprets, and interprets roaming metadata advertised by one or more wireless static access points in the vicinity of a wireless mobile node.
In response to the default criteria, and the roaming based on the ordered list of a plurality of different directions brought about by the metadata, a plurality of the radio static access point caries Chide best next radio static access point It automatically resets to connect the wireless mobile node to.
The best next radio static access point, when moving on a particular route is the wireless mobile node in a first direction a first of the first ordered list of the ordered list of each of the plurality of directions It is one of a set of previously fixed radio static access point, when the mobile node moves on the particular path in the second direction of the second ordered list of the ordered list of each of the plurality of directions 1 Tsudea set of radio static access point of the second pre-fixed is,
At least a portion said wireless mobile node and the radio static access point does not overlap with the set of static access point of the second pre-fixed wireless mesh of the set of static access point of the first pre-fixed Different nodes in the network,
Method. The method according to claim 13, wherein the measured signal intensity of the currently connected 1 wireless static access point is within the range of the predetermined signal intensity notified by the roaming metadata. It is an automatic evaluation
The default criterion is a function in which the intensity of the measured signal exceeds the range of the predetermined signal intensity.
Method. The method of claim 13 further automatically determines if the wireless mobile node itself has encountered a marker signaled by the roaming metadata.
The default criterion is a function that determines at least whether the marker has been encountered.
Method. 13. The method of claim 13, wherein the default criteria is based on the current signal strength of at least some of the wireless static access points, past connection history, and advertised roaming metadata. A method of having a context map created by the wireless mobile node and updated regularly. The method of claim 16, wherein the context map further determines when the wireless mobile node disconnects from a given wireless static access point among the plurality of the wireless static access points. The method that is used. The method of claim 16, wherein the context map further indicates when the connection to a predetermined wireless static access point of the plurality of wireless static access points of the wireless mobile node is activated. The method that is used to determine. The method according to claim 13, further recognizing that the index of the intensity of the received signal is larger than the threshold value and automatically recognizing that the mobile node is within the Fresnel zone. ,
The default criteria is at least a function of the mobile node being within the Fresnel zone.
Method. 13. The method of claim 13, which further automatically determines the location and direction of travel based on the roaming metadata.
The wireless mobile node is a mobile access point enabled to provide context-based services to mobile clients connected to the wireless mobile node.
Method.

Images