WO2006121292A1 - Method and apparatus for keeping information in routing tables consistent throughout a wireless network - Google Patents
Method and apparatus for keeping information in routing tables consistent throughout a wireless network Download PDFInfo
- Publication number
- WO2006121292A1 WO2006121292A1 PCT/KR2006/001756 KR2006001756W WO2006121292A1 WO 2006121292 A1 WO2006121292 A1 WO 2006121292A1 KR 2006001756 W KR2006001756 W KR 2006001756W WO 2006121292 A1 WO2006121292 A1 WO 2006121292A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- access point
- data
- block
- checksum
- information
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/021—Ensuring consistency of routing table updates, e.g. by using epoch numbers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
Definitions
- a predetermined mesh access point determines whether address data has been requested by a mesh access point (hereinafter referred to as an external mesh access point) other than the predetermined mesh access point or a station (hereinafter referred to as the external station) associated with a mesh access point other than the predetermined mesh access point.
- the address data of the predetermined mesh access point may be requested by an external mesh access point or an external station when the external mesh access point or the external station does not address data of its own or determines based on a checksum that its address data, if any, does not match the address data of the predetermined mesh access point.
- the block list also includes a plurality of block indexes for the respective blocks 110 through 130 and a plurality of pieces of station quantity information corresponding to the respective blocks 110 through 130 wherein the piece of station information in each block specifies the number of stations whose information is stored in the block.
- the station addresses included in the blocks 110 through 130 may be the MAC addresses of the stations associated with the predetermined mesh access point.
- a station's MAC address and sequence number are referred to as a local association tuple (LAT).
- LAT local association tuple
- Each of the blocks 110 through 130 comprises a block index, a piece of station quantity information specifying the number of stations whose information is stored in the corresponding block (i.e., a piece of LAT quantity information), and one or more LATs.
- a station's sequence number may be a serial number required for managing a frame to associate/disassociate the station with/from the predetermined mesh access point.
- FIG. 4 is a diagram for explaining the format of a local association base checksum
- the predetermined mesh access point may periodically transmit the LABC 200 including the first through N-th checksum data 210 through 230 to an external station or an external mesh access point. If the external station or the external mesh access point determines that it has different checksum data from the first through N-th checksum data 210 through 230 of the LABC 200, it may issue a request for retransmission of station information corresponding to the block of the LAB 100 whose checksum data is different from the checksum data of the external station or the external mesh access point. Then, the predetermined mesh access point may transmit the station information corresponding to all the blocks 110 through 130 or the station information corresponding to only the block whose checksum data is different from the checksum data of the external station or the external mesh access point. Therefore, it is possible to reduce the amount of data transmitted over networks to keep station information consistent throughout the network and enhance the efficiency of the network.
- operation S212 if the received data is determined in operation S210 to have been transmitted in a different mode than the full base diffusion mode, it is determined whether the received data corresponds to part of the LAB, particularly, a block of the LAB, or checksum data. If the received data is determined in operation S212 to be a block of the LAB, it appears that an external station or an external mesh point receiving data from the mesh access point in operation S210 has received the LABC from the predetermined mesh access point, has determined that its checksum data for a block of the LAB differs from the LABC and thus has issued a request for retransmission of the block of the LAB.
- operation S214 if it is determined in operation S212 that the received data is checksum data, the received data is examined by comparing it with checksum data that was previously received. If the received data is identical to the previous checksum data, it appears that the status of stations listed in a block corresponding to the received data has not changed. However, if the received data is not identical to the previous checksum data, it appears that station information has changed because the status of the stations listed in the block corresponding to the received data has changed. Therefore, in operation S240, a request for transmission of all data regarding the block corresponding to the received data is issued to the predetermined mesh access point. If the predetermined mesh access point transmits the data regarding the block corresponding to the received data in response to the request issued in operation S240, the same operations as operations S212, S230, and S232 can be carried out.
- the predetermined mesh access point may transmit expired checksum data or expired LABs.
- a LAB or a LABC contains lifetime information specifying when the LAB or the LABC will expire. Therefore, a LABC or a LAB may not be valid any longer after its expiration date.
- a station or a mesh access point receiving an expired LABC or an expired LAB may issue a request for retransmission of a non-expired LABC or a non-expired LAB to the predetermined mesh access point.
- the method illustrated in FIG. 5 may be carried out by various types of wireless network devices, such as mesh access points or mesh points, as long as the wireless network devices can generate and maintain a routing table.
- FIG. 6 is a diagram for explaining the format of a block transmission request frame according to an exemplary embodiment of the present invention.
- a block transmission request frame 300 is a frame used for a receiving mesh access point or a receiving station to issue a request for retransmission of data regarding predetermined blocks to a sending mesh access point if current checksum data corresponding to the predetermined blocks is different from previous checksum data corresponding to the pre- determined blocks.
- the block transmission request frame 300 includes the MAC address of the receiving mesh access point or the receiving station, the MAC address of the sending mesh access point, and a list of a plurality of first through N-th block indexes 310 through 330 corresponding to the blocks requested by the receiving mesh access point or the receiving station.
- FIG. 7 is a diagram for explaining the format of a global association base (GAB) comprising all information about a plurality of stations associated with a wireless network, according to an exemplary embodiment of the present invention.
- a GAB 400 is a collection of a plurality of pieces of station association information gathered from LABs.
- the GAB 400 comprises a plurality of first through third global association tuples (GATs) 410 through 430.
- Each of the first through third GATs includes a block index, a plurality of stations associated with a predetermined mesh access point, the MAC address of the predetermined mesh access point, expiration time information, and the addresses and sequence numbers of the stations associated with the predetermined mesh access point.
- the first GAT 410 includes a block index corresponding to a block including a group of stations associated with the predetermined mesh access point, the MAC address of the predetermined mesh access point, and expiration time information specifying when the first GAT 410 expires.
- An example of an expiration time specified in the expiration time information may be a result of adding a current time to a lifetime specified in a received LAB or LABC.
- the received checksum data may be added to the GAB 400.
- checksum data generated using a hash function or a hash table may be added to the GAB 400 and may be compared with checksum data transmitted later by the predetermined mesh access point, thereby making it possible to determine whether the statuses of stations corresponding to the checksum data transmitted by the predetermined mesh access point have changed.
- the external access point or the external mesh point station may generate checksum data for one or more blocks corresponding to the received checksum data and compare the generated checksum data with the received checksum data.
- the external mesh access point or the external mesh point station may be able to perform a routing operation using the GAB 400.
- the external mesh access point or the external mesh point station can determine what mesh access point a station of interest is associated with based on the GAB 400. Thereafter, the external mesh access point or the external mesh point station transmits data to the mesh access point that the station of interest is determined to be associated with so that the data can be transmitted to the station of interest.
- the highest sequence number is considered to be the most recent sequence number, and thus, the first station is determined to be associated with a mesh access point corresponding to the highest sequence number. Thereafter, data to be transmitted to the first station may be routed to the mesh access point corresponding to the highest sequence number.
- the deletion of information from the routing table, the modification of information stored in the routing table, and/or the addition of information to the routing table may be performed while updating the GAB 400.
- modules indicates a software component or a hardware component such as a field- programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).
- the unit performs a particular function but is not restricted to software and hardware.
- the unit may be included in an addressable storage medium or may be configured to play one or more processors. Accordingly, units may include components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of a program code, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and parameters.
- FIG. 8 is a block diagram of a mesh access point according to an exemplary embodiment of the present invention.
- a mesh access point 500 generates a LAB and a LABC based on a plurality of pieces of information about a plurality of stations associated with the mesh access point 500 and transmits the LAB and the LABC.
- the mesh access point 500 receives a plurality of pieces of information about a plurality of stations associated with another mesh access point and generates and manages a GAB and a routing table based on the plurality of pieces of information.
- a mesh point like the mesh access point 500, may receive a LAB and a LABC and generate a GAB and a routing table based on the received LAB or LABC.
- a LAB generation unit 510 generates a LAB.
- the LAB may include a plurality of blocks, and each of the blocks includes a block index, the MAC addresses and sequence numbers of a group of a plurality of stations associated with the mesh access point 500, and station quantity information, as illustrated in FIG. 3.
- the LAB generation unit 510 may modify the LAB in units of the blocks or generate a new LAB and transmit the modified LAB or the new LAB when a station other than the stations listed in the LAB is associated with the mesh access point 500 or when one of the stations listed in the LAB is disassociated with the mesh access point 500. If the LAB is too large to be transmitted at a time, it may be transmitted in units of the blocks.
- a LABC generation unit 520 generates a LABC comprising checksum data corresponding to each of the blocks of the LAB generated by the LAB generation unit 510 and transmits the LABC.
- the checksum data for each of the blocks of the LAB may be generated by a hash unit 530.
- An example of the LABC is illustrated in FIG. 4. If the LABC is too large to be transmitted at a time, it may be transmitted in units of the blocks of the LAB.
- the hash unit 530 generates checksum data by converting data of the blocks of the
- the hash function 530 converts each of the blocks of the LAB generated by the LAB generation unit 510 into checksum data.
- the checksum data is much smaller than the blocks of the LAB, and thus, data loss may be inevitable during the conversion of each of the blocks of the LAB into the checksum. Therefore, different blocks of the LAB may be converted into the same checksum data.
- time information specifying until when the checksum data is valid such as lifetime information, may be set in the checksum data.
- the hash unit 530 may also be used for examining a LABC received by a GAB generation unit 550 regarding a mesh access point other than the mesh access point 500.
- a transmission unit 570 transmits data, e.g., the LAB generated by the LAB generation unit 510 or the LABC generated by the LABC generation unit 520, over a wireless network.
- the transmission unit 570 may transmit a request frame requesting transmission of data of a predetermined block to a mesh access point other than the mesh access point 500.
- a reception unit 560 receives data, e.g., a LAB or a LABC, from a mesh access point other than the mesh access point 500 over the wireless network.
- the reception unit 560 may receive a request frame requesting a predetermined block transmitted by a mesh access point other than the mesh access point 500.
- a GAB generation unit 550 generates a GAB.
- the GAB comprises information about a plurality of stations associated with the wireless network, which is of a mesh type.
- a routing table 540 stores information specifying what APs in the wireless network stations are associated with and is thus referenced to transmit data to a station associated with an AP other than the mesh access point 500.
- the routing table 540 may be maintained using the GAB generated by the GAB generation unit 550.
- the GAB is obtained by gathering a plurality of LABs received by the reception unit 560. An example of the GAB is illustrated in FIG. 7. It may be determined whether each of a plurality of GATs of the GAB is valid by comparing the GAB with LABC data received by the reception unit 560.
- the GAB generation unit 550 may compare checksum data generated in advance by the hash unit 530 with received LABC. Alternatively, the GAB generation unit 550 may generate checksum data for each GAT whenever LABC data is received and compare the checksum data with the received LABC data.
- the routing table 540 is used for determining what AP each of a plurality of stations listed in the GAB generated by the GAB generation unit 550 is associated with. In order to transmit data to a predetermined station, the data can be transmitted to a mesh access point that the predetermined station is associated with. When a station is newly associated with a predetermined mesh access point listed in the GAB generated by the GAB generation unit 550 or when one of a plurality of stations associated with the predetermined mesh access point is disassociated from the predetermined mesh access point, information indicating this association or disassociation is reflected in the routing table 540, thereby enabling a communication path to the to be established in the wireless network.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008508764A JP4541439B2 (en) | 2005-05-11 | 2006-05-11 | Method and apparatus for matching routing table information in a wireless network |
CN2006800157745A CN101171799B (en) | 2005-05-11 | 2006-05-11 | Method and apparatus for keeping information in routing tables consistent throughout a wireless network |
EP06768479A EP1880513A4 (en) | 2005-05-11 | 2006-05-11 | Method and apparatus for keeping information in routing tables consistent throughout a wireless network |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US67968005P | 2005-05-11 | 2005-05-11 | |
US60/679,680 | 2005-05-11 | ||
KR10-2005-0065331 | 2005-07-19 | ||
KR1020050065331A KR100703780B1 (en) | 2005-05-11 | 2005-07-19 | Method and apparatus for supporting consistency of routing table's data in wireless network |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006121292A1 true WO2006121292A1 (en) | 2006-11-16 |
Family
ID=37396756
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2006/001756 WO2006121292A1 (en) | 2005-05-11 | 2006-05-11 | Method and apparatus for keeping information in routing tables consistent throughout a wireless network |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP1880513A4 (en) |
WO (1) | WO2006121292A1 (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6831921B2 (en) * | 2002-03-27 | 2004-12-14 | James A. Higgins | Wireless internet access system |
WO2005011312A2 (en) * | 2003-07-16 | 2005-02-03 | Interdigital Technology Corporation | Method and system for transferring information between network management entities of a wireless communication system |
US20050074019A1 (en) * | 2003-10-03 | 2005-04-07 | Nortel Networks Limited | Method and apparatus for providing mobile inter-mesh communication points in a multi-level wireless mesh network |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030005306A1 (en) * | 2001-06-29 | 2003-01-02 | Hunt Preston J. | Message digest based data synchronization |
US7292535B2 (en) * | 2002-05-23 | 2007-11-06 | Chiaro Networks Ltd | Highly-available OSPF routing protocol |
US20040246902A1 (en) * | 2003-06-02 | 2004-12-09 | Weinstein Joseph J. | Systems and methods for synchronizing multple copies of a database using datablase digest |
-
2006
- 2006-05-11 WO PCT/KR2006/001756 patent/WO2006121292A1/en active Application Filing
- 2006-05-11 EP EP06768479A patent/EP1880513A4/en not_active Withdrawn
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6831921B2 (en) * | 2002-03-27 | 2004-12-14 | James A. Higgins | Wireless internet access system |
WO2005011312A2 (en) * | 2003-07-16 | 2005-02-03 | Interdigital Technology Corporation | Method and system for transferring information between network management entities of a wireless communication system |
US20050074019A1 (en) * | 2003-10-03 | 2005-04-07 | Nortel Networks Limited | Method and apparatus for providing mobile inter-mesh communication points in a multi-level wireless mesh network |
Non-Patent Citations (1)
Title |
---|
See also references of EP1880513A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP1880513A4 (en) | 2010-12-01 |
EP1880513A1 (en) | 2008-01-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7710934B2 (en) | Method and apparatus for keeping information in routing tables consistent throughout wireless network | |
CN108464024B (en) | Network node, wireless device, medium and method for handling wireless device capabilities | |
CN1202689C (en) | Arrangement for secure communication and key distribution in telecommunication system | |
US20200107342A1 (en) | Route update method, scheduling request cancellation method, and device | |
JP2019520763A (en) | Network slice selection method, apparatus and system | |
KR101281215B1 (en) | Communicating system information in a wireless communication network | |
US20050054359A1 (en) | Mobile communications system, radio base station, scheduling apparatus, scheduling method employed in the same, and program therefor | |
JP2015080237A (en) | Methods, apparatus and systems for decentralized coexistence management for controlling operation of multiple radios | |
JP2014239482A (en) | Multi-link support for network based mobility management systems | |
US20090232053A1 (en) | Wireless communication apparatus having acknowledgement function and wireless communication method | |
WO2018170626A1 (en) | Connection recovery method, access and mobility management function entity, and user equipment | |
JP2013509034A (en) | Group owner selection with cross request | |
US20110069691A1 (en) | Method of transmitting and receiving data in network environment with wired and wireless networks bridged using relay portal | |
JP2022524748A (en) | Communication method, communication device, session management function entity, user plane function entity and computer program | |
US8059598B2 (en) | Wireless communication system and method for managing service flow identifier in the same | |
US20210144589A1 (en) | Apparatus and methods for eht multi-band a-msdu operation | |
WO2015143763A1 (en) | Load information transfer method, system, network elements and computer storage medium | |
US9503995B2 (en) | Method and system for synchronous service-flow transmission in heterogeneous network | |
JP5174953B2 (en) | Wireless communication system, wireless communication terminal, and communication control method | |
US7983234B2 (en) | Wireless communication apparatus with a block acknowledgement function and a wireless communication method | |
EP1880513A1 (en) | Method and apparatus for keeping information in routing tables consistent throughout a wireless network | |
CN111901776A (en) | Communication method and related communication equipment | |
WO2022149316A1 (en) | Base station, communication device, and communication method | |
CN106550349B (en) | Management method, server and the service node of subscription data based on group | |
KR101298299B1 (en) | Method for authenticating of a mesh point and thereof serporting mesh network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200680015774.5 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006768479 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2008508764 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2068/MUMNP/2007 Country of ref document: IN |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWP | Wipo information: published in national office |
Ref document number: 2006768479 Country of ref document: EP |