CN101977406A - Quick service flow establishing method in wireless MESH network - Google Patents
Quick service flow establishing method in wireless MESH network Download PDFInfo
- Publication number
- CN101977406A CN101977406A CN2010105491016A CN201010549101A CN101977406A CN 101977406 A CN101977406 A CN 101977406A CN 2010105491016 A CN2010105491016 A CN 2010105491016A CN 201010549101 A CN201010549101 A CN 201010549101A CN 101977406 A CN101977406 A CN 101977406A
- Authority
- CN
- China
- Prior art keywords
- service flow
- node
- add
- msh
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention belongs to the technical field of mobile communication, and discloses a quick service flow establishing method applied in a wireless MESH network. The method comprises the following steps of: classifying the service flow establishing method according to the establishing flow and the establishing speed of service flow, wherein the establishing method comprises slow service flow establishment and quick service flow establishment; aiming at the quick service flow establishment in a process of constructing the service flow, sending MSH-SF-ADD-REQ request message for establishing the service flow by a source node; after an intermediate node receives the MSH-SF-ADD-REQ request message sent by a request node of the service flow, immediately generating MSH-SF-ADD-RSP message and MSH-SF-ADD-REQ message, and adding the MSH-SF-ADD-RSP message and the MSH-SF-ADD-REQ message into DSCH (downlink sharing channel) message for sending; after a next hop node of the link receives the MSH-SF-ADD-REQ message sent by the intermediate node, returning MSH-SF-ADD-RSP message to the intermediate node; and after the source node receives the MSH-SF-ADD-RSP message returned by the intermediate node, returning MSH-SF-ADD-ACK message to the intermediate node; and after the intermediate node receives the MSH-SF-ADD-RSP message returned by the next hop node, returning MSH-SF-ADD-ACK message to the next hop node so as to realize quick establishment of whole service flow.
Description
Technical field
The present invention relates to wireless communication technology field, specifically, the present invention relates to the service flow method for building up in the Wireless MESH network media access control system.
Background technology
In Wireless MESH network, management service flow is the important component part in the media access control protocol, is the key technology that realizes the QoS security mechanism in the MESH network; Management service flow mainly comprises the refreshing of deletion, service bandwidth of modification, the service flow of foundation, the service flow of service flow, the request of service bandwidth; Generally, a service flow and following association of characteristics: 1) Link ID: end-to-end service stream of unique sign in the global scope.2) qos parameter set: this parameter set comprises characteristics such as type of service, minimax service rate, time delay, shake, transmission policy.
Set up in the process in service flow, need in multi-hop MESH network, set up the service flow from the source node to the destination node, and the speed that source node is set up service flow to destination node will directly influence the lifting of entire system performance, therefore, need that service flow is set up flow process and will simplify and optimize.
Summary of the invention
The purpose of this invention is to provide quick service flow method for building up in a kind of Wireless MESH network.Specifically may further comprise the steps:
Steps A: source node need be when destination node sends data, and the upper level applications of source node need be carried out alternately with MAC layer management service flow module;
After step B:MAC layer management service flow module receives that the service flow of upper level applications transmission is set up request, need resolve and handle the DL_QoS_CREATE.request primitive that upper level applications sends, the management service flow module be carried out the MSH_SF_ADD_REQ message generation that service flow is set up;
Step C: after source node MAC layer management service flow module generates service flow control message, carry out between source node and the destination node alternately, carry out service flow and set up;
Step D: finish quick service flow and set up process.
In the described steps A, the interaction flow between the upper level applications of source node and the MAC layer management service flow module is as follows:
Steps A 1: upper level applications sends the DL QoS CREATE.request primitive (this primitive mainly comprises destination node IP address, service flow type and qos parameter etc.) that comprises the QoS of survice parameter to MAC layer management service flow module;
Steps A 2: after the requesting node of service flow receives that the service flow of service flow recipient node answer is set up return information MSH_SF_ADD_RSP, the MAC layer of service flow request node need send DL_QoS_CREATE.confirmation primitive to upper level applications, service flow has been set up successfully notified the upper strata.
Among the described step B, after source node MAC layer is received the DL_QoS_CREATE.request primitive of upper level applications transmission, need to resolve the qos parameter in the DL_QoS_CREATE.request primitive, if source node can be accepted this qos parameter, then with this qos parameter structure MSH_SF_ADD_REQ message, if source node can not be accepted this qos parameter, then source node MAC course upper level applications sends and sets up the service flow failure information, and resends the foundation that DL_QoS_CREATE.request primitive carries out service flow after informing upper strata modification qos parameter.
Among the described step C, detailed interaction flow between source node and the destination node in setting up the service flow process may further comprise the steps (with the whole piece communication link comprise A, B, three nodes of C are the example analysis, wherein, A is a source node, B is an intermediate node, and C is a destination node):
Step C1: source node A sends the MSH_SF_ADD_REQ request message of setting up service flow;
Step C2: intermediate node B generates MSH_SF_ADD_RSP message and MSH_SF_ADD_REQ message after receiving the MSH_SF_ADD_REQ request message that the requesting node of service flow sends immediately,
Step C3: MSH_SF_ADD_RSP message and MSH_SF_ADD_REQ message joined in the DSCH message send (wherein, MSH_SF_ADD_RSP message replies to the requesting node A of service flow, and MSH_SF_ADD_REQ message sends to the next-hop node C on the link);
Step C4: receive the MSH_SF_ADD_REQ message of intermediate node B transmission as the next-hop node C of link after, reply MSH_SF_ADD_RSP message to intermediate node;
Step C5: after source node A receives the MSH_SF_ADD_RSP message of intermediate node B answer, reply MSH_SF_ADD_ACK message to intermediate node;
Step C6: after intermediate node B receives the MSH_SF_ADD_RSP message of next-hop node C answer, reply MSH_SF_ADD_ACK message to next-hop node.
In addition, set up in the process in service flow, need finish the maintenance of transaction management information and the management of Link ID, the specific design method is as follows:
(1) needs in the process transaction management information is safeguarded setting up of service flow.The operation of service flow each time that source node is initiated all is affairs (comprising the establishment, deletion, change of service flow etc.), and wherein, all affairs are formed a chained list, and the affairs on the same service flow are also formed a chained list.TransactionID is by the unique distribution of node of initiating affairs, and initiating affairs node NodeID+transaction ID can affairs of unique identification;
(2) when dynamically setting up service flow, the initiation node of service flow is that service flow is distributed unique Link ID, this Link ID=source node NodeID+SeqNum, and wherein Node ID is the source node numbering, SeqNum is a random number.
The invention has the beneficial effects as follows: the present invention is a quick service flow method for building up in a kind of Wireless MESH network, and purpose is set up speed in raising whole piece service flow, improves the entire system performance.
Description of drawings
Fig. 1 is that service flow is set up the link schematic diagram;
Fig. 2 is upper strata and MAC layer primitives interoperation flow chart;
Fig. 3 is that the quick service flow of multinode is set up schematic diagram;
Fig. 4 is that the quick service flow of multinode is set up flow chart;
Fig. 5 is that source node A service flow is set up the handling process in the process;
Fig. 6 is that intermediate node B service flow is set up the handling process in the process;
Fig. 7 is that destination node C service flow is set up the handling process in the process.
Embodiment
In order to make purpose of the present invention, technical scheme and advantage clearer,, quick service flow method for building up in the Wireless MESH network of the present invention is further elaborated below in conjunction with drawings and Examples.Should be appreciated that specific embodiment described herein only in order to explanation the present invention, and be not used in qualification the present invention.
Describe quick service flow method for building up in the Wireless MESH network of the present invention below in detail.
Before service flow foundation in the Wireless MESH network, need define the whole piece communication link, as shown in Figure 1, a communication link comprises n+2 node (n 〉=1) in the Wireless MESH network, one of them node is a source node, and a node is a destination node, and n node is intermediate node.
Source node is before destination node sends data, and the source node upper strata need be carried out alternately to source node MAC layer management service flow module, and as shown in Figure 2, concrete interaction flow is:
Step 01: upper level applications sends the DL_QoS_CREATE.request primitive (this primitive mainly comprises destination node IP address, service flow type and qos parameter etc.) that comprises the QoS of survice parameter to MAC layer management service flow module;
The DL_QoS_CREATE.request primitive that step 02:MAC layer parse upper layers application program sends;
The qos parameter of step 03:MAC layer by resolving among the step S2 judges whether to receive this service flow and sets up request, if can accept this service flow request, then enters step 04, otherwise, change step 05 over to;
Step 04:MAC layer management service flow module generates the MSH_SF_ADD_REQ request message, and sends to the Requested Party that service flow is set up, and enters step 06 then;
Step 05: source node MAC course upper level applications sends and sets up the service flow failure information, and resends the foundation that DL_QoS_CREATE.request primitive carries out service flow after informing upper strata modification qos parameter, finishes;
Step 06: source node receives that service flow is requested the MSH_SF_ADD_RSP information that node is replied;
Step 07: the MAC layer of service flow request node need send DL_QoS_CREATE.confirmation primitive to upper level applications, service flow has been set up successfully notified the upper strata, finishes.
With a communication link 3 nodes being arranged below is that example is carried out quick service flow and set up the flow process introduction, and as shown in Figure 3 and Figure 4, the whole piece communication link comprises A, B, three nodes of C, wherein, A is a source node, and B is an intermediate node, C is a destination node, and it is as follows that whole communication link service flow is set up flow process:
Step S1: source node A sends the MSH_SF_ADD_REQ request message of setting up service flow;
Step S2: intermediate node B generates MSH_SF_ADD_RSP message and MSH_SF_ADD_REQ message after receiving the MSH_SF_ADD_REQ request message that the requesting node A of service flow sends immediately;
Step S3: intermediate node B joins MSH_SF_ADD_RSP message and MSH_SF_ADD_REQ message in the DSCH message and sends (wherein, MSH_SF_ADD_RSP message replies to the requesting node A of service flow, and MSH_SF_ADD_REQ message sends to the next-hop node C on the link);
Step S4: receive the MSH_SF_ADD_REQ message of intermediate node B transmission as the next-hop node C of link after, reply MSH_SF_ADD_RSP message to intermediate node;
Step S5: after source node A receives the MSH_SF_ADD_RSP message of intermediate node B answer, reply MSH_SF_ADD_ACK message to intermediate node;
Step S6: after intermediate node B receives the MSH_SF_ADD_RSP message of next-hop node C answer, reply MSH_SF_ADD_ACK message to next-hop node;
Step S7: the flow process of setting up of finishing quick service flow.
In addition, in Fig. 3, t1 represents that destination node sends the time of DSCH_SF_ADD_RSP message to intermediate node among the figure, t2 represents that source node sends the time of DSCH_SF_ADD_ACK message to intermediate node, t3 represents that intermediate node sends time of DSCH_SF_ADD_ACK message to destination node, and machine information was preengage and obtained when these times all were each nodes oneself by the transmission of neighbor node broadcasting.
The foundation of service flow is to realize that the triggering of service flow is to be finished by upper level applications in the management service flow subsystem in the MAC agreement.To carry out labor to the implementation step of setting up of service flow between a plurality of nodes below:
Describe source node A, intermediate node B, destination node C below respectively and set up handling process in the process in service flow:
For source node A, its service flow set up in the flow process the execution flow process as shown in Figure 5, concrete steps comprise:
Step SA1: the application program of source node A sends DL_QoS_CREATE.request primitive to the MAC layer;
Qos parameter is resolved and preserved to step SA2:MAC layer to DL_QoS_CREATE.request primitive;
Step SA3: the MAC layer of source node A judges whether this node satisfies the QoS demand of this service flow, if satisfy, enters step SA4, otherwise, change step SA5 over to;
Management service flow subsystem in the step SA4:MAC layer protocol generates DSCH_SF_ADD_REQ message according to the qos parameter of preserving, and changes execution in step SA6 over to;
Step SA5:MAC layer can be set up service flow and unsuccessfully inform upper level applications, and allows upper level applications revise the foundation of carrying out service flow behind the qos parameter again, re-executes step SA1;
Step SA6: the MAC layer of source node A is added to the DSCH_SF_ADD_REQ information that generates in the DSCH message, when DSCH message send opportunity arrives next time by the time, the DSCH information broadcast is gone out, and open the T1 timer simultaneously, wait for the DSCH_SF_ADD_RSP message that intermediate node B replys;
Step SA7: source node A judges whether to receive the DSCH_SF_ADD_RSP message of intermediate node B answer, if receive, then enters step SA8, otherwise changes step SA11 over to;
Step SA8: this node upwards layer sends DL_QoS_CREATE.confirm primitive, and next-hop node has been accepted the report information upper strata that this service flow is set up;
Step SA9: then generate DSCH_SF_ADD_ACK message, reservation sends the chance of DSCH message next time then, when transmission arrives opportunity, the DSCH_SF_ADD_ACK message that generates joined in the DSCH message sends; Service flow is set up successfully, finishes;
Step SA10: source node A judges whether the T1 timer expires, if the T1 timer expires, and execution in step SA11 then, otherwise change step SA7 over to;
Step SA11: source node A starts the T3 timer;
Step SA12: source node A judges whether the T3 timer expires, if not yet due, waits for that then the T3 timer expires, if expire, then service flow is set up failure, finishes.
For intermediate node B: its service flow set up in the flow process the execution flow process as shown in Figure 6, concrete steps comprise:
Step SB1: intermediate node B receives the DSCH_SF_ADD_REQ information that source node A sends;
Step SB2: intermediate node B resolves the qos parameter in the DSCH_SF_ADD_REQ information of receiving source node A transmission and judges, intermediate node B judges whether to accept this qos parameter, if accept, execution in step SB3 then, if Node B can not be accepted this qos parameter, then Node B is left intact;
Step SB3: intermediate node B generates DSCH_SF_ADD_RSP message (this IE sends to source node A) and DSCH_SF_ADD_REQ message (this IE sends to destination node C) simultaneously;
Step SB4: two message that generate among the forwarding step SB5 in the DSCH message sending of Node B next time, while opening timing device T1 and T2, wherein, T1 is that intermediate node B is after destination node C sends DSCH_SF_ADD_REQ message, wait for the DSCH_SF_ADD_RSP message that destination node C replys, T2 is intermediate node B after source node A sends DSCH_SF_ADD_RSP message, waits for that reception sources node A replys DSCH_SF_ADD_ACK message;
Step SB5: judge whether the T2 timer expires, if not yet due, execution in step SB6 then, otherwise, finish the intermediate node service flow and set up flow process;
Before expiring, receives step SB6:T2 that source node A replys DSCH_SF_ADD_ACK message, finishes the service flow handling process;
Step SB7: judge whether the T1 timer expires, if not yet due, execution in step SB8 then, otherwise, finish the intermediate node service flow and set up flow process;
Step SB8: received that before T1 expires destination node C replys DSCH_SF_ADD_RSP message;
Step SB9: after receiving that destination node C replys DSCH_SF_ADD_RSP message, then generate DSCH_SF_ADD_ACK message, and in the DSCH message that next time sends, DSCH_SF_ADD_ACK message is sent to destination node C, finish intermediate node service flow handling process.
For destination node C: its service flow set up in the flow process the execution flow process as shown in Figure 7, concrete steps comprise:
Step SC1: destination node C receives the DSCH_SF_ADD_REQ message that intermediate node B sends;
Step SC2: destination node C resolves the qos parameter in the DSCH_SF_ADD_REQ information of receiving intermediate node B transmission and judges, destination node C judges whether to accept this qos parameter, if acceptance, then execution in step SC3, otherwise, be left intact;
Step SC3: destination node C generates DSCH_SF_ADD_RSP message, and in the DSCH of the transmission next time message of reservation DSCH_SF_ADD_RSP message is sent to intermediate node B;
Step SC4: destination node C opening timing device T2, wait for that intermediate node B replys DSCH_SF_ADD_ACK message;
Step SC5: before T2 expires, receive the DSCH_SF_ADD_ACK message that intermediate node B replys, then finish the destination node service flow and set up flow process, otherwise, execution in step SC6;
Step SC6: judge whether the T2 timer expires,, then finish the destination node service flow and set up flow process if expire, otherwise, execution in step SC5.
In conjunction with the accompanying drawings to the description of the specific embodiment of the invention, others of the present invention and feature are conspicuous to those skilled in the art by above.
More than specific embodiments of the invention are described and illustrate it is exemplary that these embodiment should be considered to it, and be not used in and limit the invention, the present invention should make an explanation according to appended claim.
Claims (7)
1. service flow method for building up fast in the Wireless MESH network is characterized in that this method mainly may further comprise the steps:
Steps A: source node need be when destination node sends data, and the upper level applications of source node need be carried out alternately with the MAC layer management service flow module of this node before data send;
Step B: after source node MAC layer management service flow module received that the service flow of upper level applications transmission is set up request, the management service flow module was carried out service flow control message and is generated;
Step C: after source node MAC layer management service flow module generates service flow control message, carry out between source node and the destination node carrying out the flow process of setting up of the quick service flow of service flow alternately;
Step D: finish quick service flow and set up process.
2. by quick service flow method for building up in the described a kind of Wireless MESH network of claim 1, it is characterized in that in the described steps A, the interaction flow between the upper level applications of source node and the MAC layer management service flow module is as follows:
Steps A 1: upper level applications sends the DL_QoS_CREATE.request primitive (this primitive mainly comprises destination node IP address, service flow type and qos parameter etc.) that comprises the QoS of survice parameter to MAC layer management service flow module;
Steps A 2: after the requesting node of service flow receives that the service flow of service flow recipient node answer is set up return information MSH_SF_ADD_RSP, the MAC layer of service flow request node need send DL_QoS_CREATE.confirmation primitive to upper level applications, service flow has been set up successfully notified the upper strata.
3. by quick service flow method for building up in the described a kind of Wireless MESH network of claim 1, it is characterized in that, among the described step B, after source node MAC layer is received the DL_QoS_CREATE.request primitive of upper level applications transmission, need to resolve the qos parameter in the DL_QoS_CREATE.request primitive, if source node can be accepted this qos parameter, then with this qos parameter structure MSH_SF_ADD_REQ message, if source node can not be accepted this qos parameter, then source node MAC course upper level applications sends and sets up the service flow failure information, and resends the foundation that DL_QoS_CREATE.request primitive carries out service flow after informing upper strata modification qos parameter.
4. by quick service flow method for building up in the described a kind of Wireless MESH network of claim 1, it is characterized in that, among the described step B, after source node MAC layer is received the DL_QoS_CREATE.request primitive of upper level applications transmission, generate the classifier rules node according to information such as the IP version that comprises in the DL_QoS_CREATE.request primitive, source address, destination address, source port number, destination slogans, after supplying service flow to set up, when the upper strata had data to send, the parameter in packet and the classifier rules node was mated.
5. by quick service flow method for building up in the described a kind of Wireless MESH network of claim 1, it is characterized in that, among the described step C, detailed interaction flow between source node and the destination node may further comprise the steps (with the whole piece communication link comprise A, B, three nodes of C are the example analysis, wherein, A is a source node, and B is an intermediate node, and C is a destination node):
Step C1: source node A sends the MSH_SF_ADD_REQ request message of setting up service flow;
Step C2: intermediate node B generates MSH_SF_ADD_RSP message and MSH_SF_ADD_REQ message after receiving the MSH_SF_ADD_REQ request message that the requesting node of service flow sends immediately;
Step C3: intermediate node B joins MSH_SF_ADD_RSP message and MSH_SF_ADD_REQ message in the DSCH message and sends, wherein, MSH_SF_ADD_RSP message replies to the requesting node A of service flow, and MSH_SF_ADD_REQ message sends to the next-hop node C on the link;
Step C4: receive the MSH_SF_ADD_REQ message of intermediate node B transmission as the next-hop node C of link after, reply MSH_SF_ADD_RSP message to intermediate node;
Step C5: after source node A receives the MSH_SF_ADD_RSP message of intermediate node B answer, reply MSH_SF_ADD_ACK message to intermediate node;
Step C6: after intermediate node B receives the MSH_SF_ADD_RSP message of next-hop node C answer, reply MSH_SF_ADD_ACK message to next-hop node.
Wherein, the MSH_SF_ADD_REQ message format is defined as follows:
Create/Modify/Delete indicator service flow type code position
0: set up service flow
1: revise service flow
2: the deletion service flow
This message value is 0
Transaction ID affairs ID (set up by identification service stream
The numbering of process)
The destination node of Destination Node ID service flow
Link ID service flow is initiated the link that node distributes
ID number
Service Type service/type of service
0:SMS (short message service)
1:nRTS (non-real-time service)
2:RTS (real time business)
Traffic priority affair priority
Reserved keeps the position
The maximum reserved rate of Maximum Sustained Traffic Rate
Minimum Tolerable Traffic Rate minimal service speed
Tolerated Jitter tolerance shake index
Maximum Latency maximum delay
The MSH_SF_ADD_RSP/ACK message format is defined as follows:
Create/Modify/Delete indicator service flow type code position
0: set up service flow
1: revise service flow
2: the deletion service flow
This message value is 0
Transaction ID affairs ID (set up by identification service stream
The numbering of journey)
ACK/RSP indicator MSH_SF_ADD_RSP/ACK mark
Know the position
0:MSH_SF_ADD_RSP message
1:MSH_SF_ADD_ACK message
Reserved keeps the position
6. by quick service flow method for building up in the described a kind of Wireless MESH network of claim 1, it is characterized in that, need in the process transaction management table is safeguarded setting up of service flow.The operation of service flow each time that source node is initiated all is affairs (comprising the establishment, deletion, change of service flow etc.), and wherein, all affairs are formed a chained list, and the affairs on the same service flow are also formed a chained list.TransactionID is by the unique distribution of node of initiating affairs, and initiating affairs node Node ID+transaction ID can affairs of unique identification.
7. by quick service flow method for building up in the described a kind of Wireless MESH network of claim 1, it is characterized in that, when dynamically setting up service flow, the initiation node of service flow is that service flow is distributed unique Link ID, this Link ID=source node Node ID+SeqNum, wherein NodeID is the source node numbering, and SeqNum is a random number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105491016A CN101977406B (en) | 2010-11-18 | 2010-11-18 | Quick service flow establishing method in wireless MESH network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105491016A CN101977406B (en) | 2010-11-18 | 2010-11-18 | Quick service flow establishing method in wireless MESH network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101977406A true CN101977406A (en) | 2011-02-16 |
| CN101977406B CN101977406B (en) | 2013-11-13 |
Family
ID=43577246
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010105491016A Active CN101977406B (en) | 2010-11-18 | 2010-11-18 | Quick service flow establishing method in wireless MESH network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101977406B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101047586A (en) * | 2006-06-29 | 2007-10-03 | 华为技术有限公司 | Service QoS ensuring method and device for radio mesh network |
| CN101119322A (en) * | 2007-09-11 | 2008-02-06 | 杭州华三通信技术有限公司 | Packet processing method and node equipment in MESH network |
| CN101202769A (en) * | 2006-12-14 | 2008-06-18 | 华为技术有限公司 | Method and system for node identifying in wireless Mesh network |
| WO2009061096A1 (en) * | 2007-11-09 | 2009-05-14 | Lg Electronics Inc. | Mesh deterministic access (mda) procedure in wireless mesh network and wireless device supporting the same |
-
2010
- 2010-11-18 CN CN2010105491016A patent/CN101977406B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101047586A (en) * | 2006-06-29 | 2007-10-03 | 华为技术有限公司 | Service QoS ensuring method and device for radio mesh network |
| CN101202769A (en) * | 2006-12-14 | 2008-06-18 | 华为技术有限公司 | Method and system for node identifying in wireless Mesh network |
| CN101119322A (en) * | 2007-09-11 | 2008-02-06 | 杭州华三通信技术有限公司 | Packet processing method and node equipment in MESH network |
| WO2009061096A1 (en) * | 2007-11-09 | 2009-05-14 | Lg Electronics Inc. | Mesh deterministic access (mda) procedure in wireless mesh network and wireless device supporting the same |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101977406B (en) | 2013-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11272570B2 (en) | Method and apparatus for transmitting and receiving data in mesh network using Bluetooth | |
| KR101107902B1 (en) | Qos request and information distribution for wireless relay networks | |
| CN1645838B (en) | Self network organized and distance concerned multi-routing method for complete route information | |
| US20070064950A1 (en) | Wireless communication system, wireless communication device, method of wireless communication, and computer program | |
| US20050288008A1 (en) | Radio communication network system | |
| WO2011106984A1 (en) | Method for transmitting data in parallel by mobile terminal and mobile terminal thereof | |
| CN102186206A (en) | Relay data path architecture for wireless network | |
| CN103763750B (en) | Method for fast achieving packet forwarding in wireless ad hoc network of TDMA protocol | |
| CN105072563A (en) | Method and apparatus for device-to-device communication | |
| CN104283602A (en) | Cluster relay method, device and system | |
| CN101179511A (en) | Method of obtaining network address, and access equipment | |
| WO2022082513A1 (en) | Routing method and apparatus | |
| KR100755709B1 (en) | Method for multicast routing using MPR set information | |
| KR20020037285A (en) | Mobile communication system and distributed broadcast information control method in mobile communication system | |
| Cianci et al. | Content centric services in smart cities | |
| KR20090054759A (en) | Network coding system of the multicast member node | |
| Ahn et al. | A multipoint relay selection method for reliable broadcast in ad hoc networks | |
| US11974252B2 (en) | Communication device and communication system for selecting resources to be used for data transmission | |
| CN101977406B (en) | Quick service flow establishing method in wireless MESH network | |
| JP2015233172A (en) | Packet transfer method, radio communication system, and radio communication device | |
| CN114424621B (en) | Buffer status report transmission method and device | |
| Peng et al. | A novel TDMA-MAC protocol for VANET using cooperative and opportunistic transmissions | |
| KR20070023951A (en) | Method for transmitting message based on zigbee networks | |
| CN105188025A (en) | Method and system for sending positioning reference signals | |
| JPWO2008114327A1 (en) | Address resolution method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |