KR20100020925A - Apparatus for providing inter-piconet multi hop mesh communication in wireless personal area network and method thereof - Google Patents

Abstract

PURPOSE: An apparatus and a method for providing inter-piconet multi hop mesh communication in wireless personal area network are provided to make a tree-based routing service and an optimal routing service possible thereby supplying a high speed multi-hop telecommunication function between PICONET. CONSTITUTION: A mesh network operating in adjacent to a device are determined by searching a network existing in adjacent to the device(S120). If the mesh network does not exist, a parameter related to a primitive for starting the mesh network as a mesh PICONET coordinator of new mesh network(S140). Each device transmits a beacon frame generated based on the parameter to adjacent devices of the device thereby communicating in a way of single hop mode based on the beacon frame.

Description

Apparatus and method for multi-hop mesh communication between piconets in personal wireless communication network (APAN) {APPARATUS FOR PROVIDING INTER-PICONET MULTI HOP MESH COMMUNICATION IN WIRELESS PERSONAL AREA NETWORK AND METHOD THEREOF}

TECHNICAL FIELD The present invention relates to an apparatus and method for multi-hop mesh communication between piconets in a personal wireless communication network (WPAN). In particular, the present invention relates to a mesh communication apparatus and a method for transmitting data through multi-hop between piconets in a personal wireless communication network (WPAN).

The present invention is derived from a study conducted as part of the IT growth engine technology development project of the Ministry of Knowledge Economy [Task Management Number: 2006-S-071-03, Title: Development of ultra-fast multimedia transmission UWB solution].

Wireless Personal Area Network (hereinafter referred to as "WPNA") is a compact, low-power, portable multimedia that includes wireless connections to audio / video devices, computers, and peripherals that are located within 10 meters of each other. By supporting communication between devices, it is a technology that can support various services.

In general, WPAN begins with the connection of two or more devices, namely the formation of a piconet.

In this case, since the devices constituting the piconet forming the WPAN can communicate only in a single hop method, when the WPAN is formed through a plurality of piconets, communication is impossible even though a physical link exists between devices included in different piconets. There is this.

An object of the present invention is to provide an apparatus and method for inter-piconet mesh network communication in a WPAN to provide a multi-hop communication function between a plurality of piconets.

A multi-hop mesh communication method between piconets according to an aspect of the present invention is a multi-hop mesh communication method between device piconets in a personal wireless communication network (WPAN). Determining the existence of a mesh network operating in the step of determining a parameter related to a primitive for starting the mesh network as a mesh piconet coordinator of the new mesh network, and generating the parameter based on the parameter. Transmitting the beacon frame to a plurality of devices in the vicinity of the device so that each of the plurality of devices communicates in a single hop manner based on the beacon frame.

At this time, the multi-hop mesh communication method between piconets may further include joining the mesh network when the mesh network exists.

The search result may also include a piconet ID of the mesh network.

In this case, the parameters may include a mesh ID, a tree ID, and a beacon origin ID.

According to another aspect of the present invention, a method of multi-hop mesh communication between piconets is a method of multi-hop mesh communication between piconets of a device in a personal wireless communication network (WPAN). Selecting a parent piconet to which the device joins based on the corresponding scan information, and joining the parent piconet and assigning a tree ID from the coordinator of the parent piconet.

In this case, the mesh network may include a plurality of piconets, and the scan information may include a mesh ID of the mesh network, each piconet ID of the plurality of piconets, and an operation channel of the mesh network.

In this case, the selecting of the parent piconet may be selected based on the hop count to the coordinator, the link state, and the allocable channel time resource.

At this time, the multi-hop mesh communication method between piconets may further include generating a child piconet of a parent piconet.

The generating of the child piconet may include: initializing a mesh parameter including a piconet ID and an operation channel of the child piconet, generating a beacon based on the mesh parameter, and beacons to devices that are not joined to the mesh network through the operation channel. It may include the step of transmitting.

The generating of the child piconet may further include requesting channel time allocation from the coordinator, and receiving the allocated channel time from the coordinator. The transmitting of the beacon may include: Beacons can be sent over the operating channel during the time.

According to an aspect of the present invention, in a WPNA environment in which multiple piconets exist, a tree-based routing service and an optimal routing service may be defined by defining a mesh sublayer and a mesh sublayer management entity and defining primitives in each service access point. By doing so, there is an effect that can provide a high speed multi-hop communication function between piconets.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, without excluding other components unless specifically stated otherwise.

Hereinafter, a multi-hop mesh multi-hop mesh communication apparatus and method therefor in a personal wireless communication network according to an embodiment of the present invention will be described with reference to the accompanying drawings.

First, various forms of a piconet constituting a conventional personal wireless communication network (hereinafter, also referred to as 'WPAN') will be described with reference to FIGS. 1 to 3.

1 is a configuration diagram according to an embodiment of a piconet constituting a conventional WPAN.

At this time, the WPAN includes one piconet.

As shown in FIG. 1, the first piconet 10 includes one piconet coordinator (hereinafter referred to as 'PNC') and a plurality of devices (DEVice, hereinafter referred to as 'DEV'), that is, the first piconet coordinator. A device DEV 1 13, a second device DEV 2 15, a third device DEV 3 17 and a fourth device DEV 4 19.

The piconet coordinator (PNC) 11 selects an arbitrary device among a plurality of devices included in the first piconet 10, and the device selected as the piconet coordinator (PNC) 11 uses a beacon frame to display the first piconet (PNC). Manage the basic timing of 11).

The plurality of devices 13, 15, 17, and 19 included in the first piconet 10, including the piconet coordinator (PNC) 11, communicate in a single hop manner using beacon information included in the beacon frame. For example, the first device 13 may communicate in a single hop manner using a link between the first device 13 and the third device 17, but the first device via the second device 15. It is not possible to communicate with the third device 17 in a multi-hop manner using the link between the 13 and the second device 15 and the link between the second device 15 and the third device 17.

2 is a configuration diagram according to another embodiment of a piconet constituting a conventional WPAN.

At this time, the WPAN includes two piconets coexisting on the same channel.

As shown in FIG. 2, the first piconet 10 includes a first piconet coordinator (PNC 1) 11, a first device (DEV 1) 13, a second device (DEV 2) 15, and a first piconet 10. Three devices (DEV 3) 17 and a fourth device (DEV 4) 19.

The second piconet 20 includes a second piconet coordinator (PNC 2) 13, a fifth device (DEV 5) 21, a sixth device (DEV 6) 23, and a seventh device (DEV 7) 25 ) And an eighth device (DEV 8) 27.

At this time, the first piconet 10 corresponds to the parent piconet with respect to the second piconet 20, and the second piconet 20 corresponds to the child piconet with respect to the first piconet 10, and the first piconet as the parent piconet ( One of the plurality of devices 13, 15, 17, and 19 included in 10), that is, the first device 13 serves as a piconet coordinator of the second piconet 20 that is a child piconet.

In this case, the devices 13, 15, 17, and 19 included in the first piconet 10 including the first piconet controller 11 communicate with each other in a single hop manner, and the second piconet controller ( The devices 21, 23, 25, and 27 included in the second piconet 20, which are child piconets including 13), also communicate with each other in a single hop manner.

However, the piconet coordinator 13 of the second piconet 20, which is a child piconet, may communicate with devices 21, 23, 25, and 27 included in the second piconet 20 in a single hop manner, and the parent piconet The devices 11, 15, 17, and 19 included in the first piconet 10 may also communicate in a single hop manner.

However, other devices 21, 23, 25, and 27 except for the second piconet controller 13 in the second piconet 20 may belong to different piconets, that is, devices 11, which belong to the first piconet 10. 15, 17, 19 and the single hop method as well as the far hop method under the relay of the second piconet coordinator 13 is not possible.

3 is a configuration diagram according to another embodiment of a piconet constituting a conventional WPAN.

At this time, the WPAN includes a plurality of piconets coexisting on the same channel.

As shown in FIG. 3, the first piconet 10 includes a first piconet coordinator PNC 1 11, a first device DEV 1 13, a second device DEV 2 15, and a first piconet 10. Three devices (DEV 3) 17 and a fourth device (DEV 4) 19.

The second piconet 20 includes a second piconet coordinator (PNC 2) 13, a fifth device (DEV 5) 21, a sixth device (DEV 6) 23, and a seventh device (DEV 7) 25 ) And an eighth device (DEV 8) 27.

The third piconet 30 may include a third piconet coordinator (PNC 3) 19, a ninth device DEV 9 31, a tenth device DEV 10 33, and an eleventh device DEV 11 35. ) And a twelfth device (DEV 12) 37.

The fourth piconet 40 includes a fourth piconet coordinator (PNC 4) 25, a thirteenth device (DEV 13) 41, a fourteenth device (DEV 14) 43, and a fifteenth device (DEV 15) 45. ) And a sixteenth device (DEV 16) 47.

In this case, the first piconet 10 corresponds to the parent piconet with respect to the second piconet 20 and the third piconet 30, and the second piconet 20 and the third piconet 30 correspond to the first piconet 10. The first device 13 of the plurality of devices 13, 15, 17, and 19 included in the first piconet 10 serves as a piconet coordinator of the second piconet 20. The fourth device 19 of the plurality of devices 13, 15, 17, and 19 included in the first piconet 10 serves as a piconet coordinator of the third piconet 30.

In addition, the second piconet 20 corresponds to a parent piconet with respect to the fourth piconet 40, and the fourth piconet 40 corresponds to a child piconet with respect to the second piconet 20, and corresponds to the second piconet 20. The seventh device 25 of the plurality of devices 21, 23, 25, and 27 included serves as a piconet coordinator of the fourth piconet 40.

In this case, the devices 13, 15, 17, and 19 included in the first piconet 10 including the first piconet controller 11 communicate with each other in a single hop manner, and the second piconet controller 13 The devices 21, 23, 25, and 27 included in the second piconet 20, which are child piconets, also communicate with each other in a single hop manner. In addition, the devices 31, 33, 35, and 37 included in the third piconet 30 including the third piconet controller 19 also communicate with each other in a single hop manner, and the third piconet controller 25 includes a third piconet controller 25. Devices 41, 43, 45, and 47 included in the four piconets 40 also communicate with each other in a single hop manner.

However, the piconet coordinator 13 of the second piconet 20 may include the devices 21, 23, 25, and 27 included in the second piconet 20 and the devices 11 included in the first piconet 10. 15, 17, and 19 may communicate with each other in a single hop manner, but devices 11, 23, 25, and 27 included in the second piconet 20 and devices 11 included in the first piconet 10 may be used. , 15, 17, and 19) cannot communicate with devices belonging to other piconets in a single hop mode or a multi-hop mode.

In addition, the piconet coordinator 19 of the third piconet 30 may include the devices 31, 33, 35, and 37 included in the third piconet 30 and the devices 11, included in the first piconet 10. 13, 15, and 17 may communicate with each other in a single hop manner, but devices 31, 33, 35, and 37 included in the third piconet 30 and devices 11 included in the first piconet 10 may be used. , 13, 15, and 17) cannot communicate with devices belonging to other piconets in a single hop mode or a multi-hop mode.

In addition, the piconet coordinator 25 of the fourth piconet 40 may include the devices 41, 43, 45, and 47 included in the fourth piconet 40 and the devices 13, included in the second piconet 20. 21, 23, 27 may be communicated in a single hop, but the devices (13, 43, 45, 47) included in the fourth piconet 40 and the devices (13) included in the second piconet 20 , 21, 23, 27) cannot communicate with devices belonging to different piconets in a single hop mode or a multi-hop mode.

As such, in the related art, since single hop communication is possible in a single piconet, communication with members belonging to other piconets has been impossible.

Next, a mesh network communication apparatus for multi-hop mesh communication between piconets in a personal wireless communication network (WPAN) according to an embodiment of the present invention will be described with reference to FIG. 4.

4 is a diagram illustrating a configuration of a mesh network communication apparatus according to an embodiment of the present invention.

As shown in FIG. 4, the mesh network communication apparatus 100 includes a frame convergence sublayer module 110, a mesh sublayer module 130, a mac sublayer module 150, and a physical layer module 170. .

The frame convergence sublayer module 110 includes a frame convergence sublayer (hereinafter referred to as FCSL) 111 and a device management entity (hereinafter referred to as 'DME') 113. Include.

The mesh sublayer module 130 may include a mesh service access point (hereinafter referred to as a mesh SAP) 131, a mesh sublayer management entity service access point, hereinafter referred to as a mesh sublayer management entity service access point. (Also referred to as 'MHME SAP') 133, a mesh sublayer 135 and a mesh sublayer management entity (hereinafter referred to as 'MHME') 137.

Mesh SAP 131 defines primitives related to the transmission and reception of asynchronous data and primitives related to the transmission and reception of isochronous data. In this case, the types and contents of primitives defined by the Mesh SAP 131 may follow Table 1.

MHME SAP 133 defines the primitives associated with the mesh network. At this time, the type and content of the primitives defined by the MHME SAP 133 may follow Table 2.

In this case, the PIB represents a Personal Area Network Information Base (hereinafter referred to as PIB), and the MPNC represents a Mesh Piconet Coordinator (hereinafter also referred to as MPNC).

The mesh sublayer 135 configures a mesh command frame by reflecting a request of the MHME 137 to provide a mesh routing service. In this case, the types of the command frame and the data frame included in the mesh sublayer 135 may be shown in Table 3.

In Table 3, LLC represents Logical Link Control and SNAP represents Sub-Network Access Protocol.

In this case, the tree ID request frame is used when the child MPNC requests a tree ID (TREEID) and a tree ID block from the parent MPNC, and the tree ID allocation frame indicates a tree ID (TREEID) and a tree ID to the parent MPNC. Used when allocating blocks.

In addition, in Table 3, the server announcement frame is used when the MPNC provides server information to one or more MPNCs, the server query frame is used when a child MPNC requests server information from a parent MPNC, and the link status request frame serves as a topology server. The parent MPNC is used to check the link status of the child MPNCs, and the link status registration frame is used to inform the link status information to the parent MPNC that the child MPNC acts as a topology server.

In addition, in Table 3, the path discovery frame is used by the source MPNC to find the optimal path, and the path announcement frame is optimal when the parent MPNC acting as the topology server knows the best destination MPNC according to the received path discovery frame. Used to inform the destination MPNC, the path shaping frame is used to set the path to the source MPNC when the MPNC receives the path announcement frame.

The MHME 137 finds an optimal path using a tree-based routing service based on a tree ID assigned to a tree structure consisting of parent-child piconets and the MPNC of a parent piconet serving as a topology server. Provides optimal routing service based on

The MAC sublayer module 150 includes a MAC service access point (MAC Service Access Point, hereinafter referred to as 'MAC SAP') 151, and a MAC sublayer management entity service access point (hereinafter referred to as MAC sublayer management entity service access point). Also referred to as 'MLME SAP' 153, MAC Sublayer 155 and MAC Sublayer Management Entity (hereinafter referred to as 'MLME') (157).

The MLME SAP 153 further defines primitives related to mesh information in addition to the existing primitives based on IEEE 802.15.3 MAC. At this time, the kind and content of the primitives additionally defined by the MLME SAP 153 may follow Table 4.

The physical layer module 170 may include a physical layer service access point (hereinafter referred to as a 'PHY SAP') 171, a physical layer management entity service access point, hereinafter referred to as a physical layer service access point (PHY SAP). Also known as 'PLME SAP' (173), Physical Layer (hereinafter referred to as 'PHY Layer') (175), and Physical Layer Management Entity (hereinafter referred to as 'PLME') (177) ).

Next, a mesh network communication apparatus (hereinafter also referred to as a device) 100 according to an embodiment of the present invention will be described with reference to FIG. 5 for a mesh network for multi-hop mesh communication between piconets in a personal wireless communication network (WPAN). Explain how to get started.

5 is a diagram illustrating a mesh network start method according to an embodiment of the present invention.

As shown in FIG. 5, first, the device 100 searches for a mesh network existing around the device 100 (S110).

Next, the device 100 determines whether there is a mesh network operating in the vicinity of the device 100 according to the search result (S120).

If the mesh network does not exist, the device 100 sets the MPNC operation mode so that the device 100 operates as a mesh piconet coordinator (MPNC) of the mesh network (S130).

Thereafter, the device 100 performs a mesh initialization procedure for determining a parameter related to a primitive for starting a mesh network (S140). In this case, the parameters may include a mesh ID, a tree ID, and a beacon origin ID.

Next, the device 100 generates a beacon (Beacon) based on the determined parameter (S150).

Thereafter, the device 100 transmits the generated beacons (S160).

On the other hand, if there is a mesh network, the device 100 joins the mesh network (S170).

Next, when the mesh network communication apparatus (hereinafter, also referred to as a device) 100 according to an embodiment of the present invention starts a mesh network according to FIG. 5, the message flows inside the device 100. Explain about. In this case, the device 100 may follow FIG. 4.

6 is a diagram illustrating a message flow at the start of a mesh network according to an embodiment of the present invention.

As shown in FIG. 6, first, the DME 113 of the device 100 transmits an MHMH-SCAN.request primitive requesting the existence of a mesh network to the mesh sublayer 135 (S201).

Thereafter, the mesh sublayer 135 transmits the MLMH-SCAN.request primitive to the vein sublayer 155 according to the received MHMH-SCAN.request primitive (S203).

Next, the MAC sublayer 155 performs a scan procedure according to the received MLMH-SCAN.request primitive (S205).

Thereafter, the MAC sublayer 155 may set the MLME-SCAN.confirm primitive including the mesh ID, the tree ID, and the piconet ID of the mesh network operating around the device 100 according to the scan result. Transfer to (S207).

Next, the mesh sublayer 135 transmits to the DME 113 an MHME-SCAN.confirm primitive including information on a mesh network operating in the vicinity of the device 100 based on the received MLME-SCAN.confirm primitive. (S209).

Subsequently, the DME 113 and the mesh sublayer 135 include a mesh ID, a tree ID, and a beacon origin ID when there is no mesh network operating around the device 100 according to the MHME-SCAN.confirm primitive. A mesh initialization procedure for determining parameters required for the MHME-START.request primitive is performed (S211). At this time, if there is a mesh network found in the scanning procedure, the device 100 may join the mesh network.

Next, the DME 113 transmits an MHME-START.request primitive to the mesh sublayer 135 to start the mesh network (S213).

Thereafter, the mesh sublayer 135 transmits an MLME-MESH-CAPABILITY.request primitive including a parameter related to the mesh network according to the received MHME-START.request primitive to the MAC sublayer 155 (S215).

Next, the MAC sublayer 155 performs a mesh piconet coordinator start (MPNC initialization) procedure, that is, an MPNC operation mode setting and parameter initialization according to the received MLME-MESH-CAPABILITY.request primitive (S217).

Thereafter, the MAC sublayer 155 transmits the MLME-MESH-CAPABILITY.confirm primitive to the mesh sublayer 135 according to the result of the mesh piconet coordinator start procedure (S219).

Next, the mesh sublayer 135 transmits an MLME-START.request primitive to the MAC sublayer 155 so that the MAC sublayer 155 starts the piconet according to the received MLME-MESH-CAPABILITY.confirm primitive (S221). ).

Thereafter, the sublayer 155 performs a beacon preparation procedure according to the received MLME-START.request primitive (S223).

Next, the pulse sublayer 155 transmits the MLME-START.confirm primitive to the mesh sublayer 135 according to the result of the beacon preparation procedure (S225).

Thereafter, the mesh sublayer 135 transmits the MHME-START.confirm primitive to the DME 113 according to the received MLME-START.confirm primitive to inform the DME 113 of the result of the beacon preparation procedure (S227).

Next, a mesh network communication apparatus (hereinafter referred to as a device) 100 according to an embodiment of the present invention will be described with reference to FIGS. 7 and 8 for multi-hop mesh communication between piconets in a personal wireless communication network (WPAN). A method of forming a tree of the mesh network will be described.

7 is a diagram illustrating a tree forming method of a mesh network according to an embodiment of the present invention.

As shown in FIG. 7, first, the device 100 searches for a mesh network existing around the device 100 (S310). In this case, the device 100 may obtain scan information including parameters such as a mesh ID, a tree ID, a piconet ID, an operation channel, and the like of a mesh network in the vicinity as a mesh network discovery result.

Thereafter, the device 100 selects a parent piconet to which the device 100 joins based on a mesh network search result, that is, scan information (S330). In this case, the device 100 may select a parent piconet to which the device 100 may subscribe based on the number of hops to the root, link status, and allocable channel time resource based on the scan information.

Next, the device 100 joins the selected parent piconet (S350). In this case, if the device 100 succeeds in joining the parent piconet, the device 100 may be assigned a tree ID from the mesh piconet coordinator of the parent piconet.

Thereafter, when the device 100 is assigned a tree ID, the device 100 generates a child piconet of a parent piconet that is a mesh piconet coordinator (S370). At this time, the child piconet generation method will be described in detail with reference to FIG. 8.

8 is a diagram illustrating a method for generating a child piconet according to an embodiment of the present invention.

As shown in FIG. 8, first, the device 100 initializes a mesh parameter, that is, a mesh ID, a tree ID, and an operation channel so that the device 100 operates as a mesh piconet coordinator of a child piconet (S371).

Next, the device 100 requests channel time allocation (hereinafter, referred to as "CTA") to the mesh piconet coordinator of the parent piconet (S373).

Thereafter, the device 100 receives an allocated channel time from the mesh piconet coordinator of the parent piconet (S375).

Next, the device 100 generates a beacon based on the initialized mesh parameter and the allocated channel time in operation S377.

Thereafter, the device 100 transmits the generated beacon through the initialized operating channel (S379). The device 100 may transmit a beacon to a peripheral device that is not joined to the mesh network so that the peripheral devices may join the mesh network.

Next, referring to FIG. 9, when a mesh network communication apparatus (hereinafter, also referred to as a “device”) 100 according to an embodiment of the present invention forms a tree of a mesh network according to FIGS. 7 and 8, a device; Next, the message flow in the interior will be described. In this case, the device 100 may follow FIG. 4.

9 is a diagram illustrating a message flow in forming a tree of a mesh network according to an embodiment of the present invention.

As shown in FIG. 9, first, the DME 113 of the device 100 requests an MHME-SCAN.request primitive requesting whether a mesh network exists to find a mesh network operating in the vicinity of the device 100. The transmission is transmitted to the mesh sublayer 135 (S401).

Next, the mesh sublayer 135 transmits the MLMH-SCAN.request primitive to the vein sublayer 155 according to the received MHMH-SCAN.request primitive (S403).

Thereafter, the MAC sublayer 155 performs a scan procedure according to the received MLMH-SCAN.request primitive (S405).

Next, the MAC sublayer 155 may generate an MLME-SCAN.confirm primitive including parameters such as a mesh ID, a tree ID, a piconet ID of the mesh network operating in the vicinity of the device 100, and an operation channel according to the scan result. The mesh is transmitted to the sub-layer 135 (S407).

Subsequently, the mesh sublayer 135 transmits an MHME-SCAN.confirm primitive to the DME 113 including information on a mesh network operating around the device 100 based on the received MLME-SCAN.confirm primitive. (S409).

Next, based on the received MHME-SCAN.confirm primitive, the DME 113 subscribes to the best Mesh PicoNet Coordinator (hereinafter referred to as "Mesh PicoNet Coordinator") based on the number of hops to the root, link status, and allocable channel time resources. Also referred to as 'MPNC' (S411).

Thereafter, the DME 113 transmits an MHME-ASSOCIATE.request primitive for requesting to join the mesh network to the mesh sublayer 135 (S413).

Next, the mesh sublayer 135 transmits the MLME-ASSOCIATE.request primitive to the MAC sublayer 155 according to the received MHME-ASSOCIATE.request primitive (S415).

Thereafter, the MAC sublayer 155 performs a Piconet association procedure according to the received MLME-ASSOCIATE.request primitive (S417).

Next, the MAC sublayer 155 transmits the MLME-ASSOCIATATE.confirm primitive to the mesh sublayer 135 according to the result of the piconet joining procedure (S419).

Thereafter, the mesh sublayer 135 transmits the MHME-ASSOCIATATE.confirm primitive including the piconet subscription result to the DME 113 according to the received MLME-ASSOCIATATE.confirm primitive (S421).

Next, the DME 113 transmits an MHME-TREEID-ASSIGN.request primitive for the child MPNC to request a tree ID from the parent MPNC to the mesh sublayer 135 (S423).

Thereafter, the mesh sublayer 135 receives an allocated tree ID TREEID from the parent MPNC according to the received MHME-TREEID-ASSIGN.request primitive (S425).

Next, the mesh sublayer 135 transmits an MHME-TREEID-ASSIGN.confirm primitive including the received tree ID to the DME 113 (S427).

Thereafter, the DME 113 transmits an MHME-START.request primitive for starting the mesh network to the mesh sublayer 135 to start the child piconet generation procedure (S429).

Next, the mesh sublayer 135 transmits to the MAC sublayer 155 an MLME-MESH-CAPABILITY.request primitive including mesh parameters such as a mesh ID and a tree ID according to the received MHME-START.request primitive. (S431).

Thereafter, the MAC sublayer 155 performs an MPNC initialization procedure, that is, mesh parameter initialization, so that the device operates as a child MPNC according to the received MLME-MESH-CAPABILITY.request pyramid (S433).

Next, the MAC sublayer 155 transmits the MLME-MESH-CAPABILITY.confirm primitive to the mesh sublayer 135 according to the result of the MPNC initialization procedure (S435).

Thereafter, the mesh sublayer 135 transmits the MLME-START.request primitive to the vein sublayer 155 according to the received MLME-MESH-CAPABILITY.confirm primitive (S437).

Next, the MAC sublayer 155 performs a Channel Time Allocation (hereinafter referred to as a "CTA") procedure according to the received MLME-START.request primitive (S439).

Thereafter, the pulse sublayer 155 performs a beacon preparation procedure according to the received MLME-START.request primitive (S441).

Next, the pulse sublayer 155 transmits the MLME-START.confirm primitive to the mesh sublayer 135 according to the result of the beacon preparation procedure (S443).

Thereafter, the mesh sublayer 135 transmits the MHME-START.confirm primitive to the DME 113 according to the received MLME-START.confirm primitive to inform the DME 113 of the result of the beacon preparation procedure (S445).

Next, a configuration of a piconet constituting a personal wireless communication network (hereinafter, also referred to as a “WPAN”) according to an embodiment of the present invention will be described with reference to FIG. 10.

10 is a diagram illustrating a configuration of a piconet constituting a WPAN according to an embodiment of the present invention.

At this time, the WPAN according to an embodiment of the present invention is composed of four piconets existing on the same channel.

As shown in FIG. 10, the first piconet 210 includes one mesh piconet coordinator (hereinafter, referred to as 'MPNC'), that is, a first mesh piconet coordinator (MPNC 1) 211 and a plurality of first piconet coordinators. Mesh device (Mesh DEVice, hereinafter also referred to as 'MDEV'), that is, a first mesh device (MDEV 1) 213, a second mesh device (MDEV 2) 215, and a third mesh device (MDEV 3) 217 ) And a fourth mesh device (MDEV 4) 219.

The second piconet 220 includes a second mesh piconet coordinator (MPNC 2) 213, a fifth mesh device (MDEV 5) 221, a sixth mesh device (MDEV 6) 223, and a seventh mesh device (MDEV). 7) 225 and an eighth mesh device (MDEV 8) 227.

The third piconet 230 includes a third mesh piconet coordinator (MPNC 3) 219, a ninth mesh device (MDEV 9) 221, a tenth mesh device (MDEV 10) 233, and an eleventh mesh device (MDEV). 11) 235 and a twelfth mesh device (MDEV 12) 237.

The fourth piconet 240 includes a fourth mesh piconet coordinator (MPNC 4) 225, a thirteenth mesh device (MDEV 13) 241, a fourteenth mesh device (MDEV 14) 243, and a fifteenth mesh device (MDEV). 15) 245 and a sixteenth mesh device (MDEV 16) 247.

In this case, the first piconet 210 corresponds to the parent piconet for the second piconet 220 and the third piconet 230, and the second piconet 220 and the third piconet 230 correspond to the first piconet 210. The first mesh device 213 of the plurality of mesh devices 213, 215, 217, and 219 included in the first piconet 210 corresponds to a child piconet of the second piconet 220. MPNC 2) and a fourth mesh device 219 of the plurality of mesh devices 213, 215, 217, and 219 included in the first piconet 210 is a mesh piconet coordinator of the third piconet 230. Plays the role of (MPNC 3).

In addition, the second piconet 220 corresponds to the parent piconet with respect to the fourth piconet 240, and the fourth piconet 240 corresponds to the child piconet with respect to the second piconet 220, and corresponds to the second piconet 220. The seventh mesh device 225 among the plurality of mesh devices 221, 223, 225, and 227 included as the mesh piconet coordinator MPNC 4 of the fourth piconet 230.

Hereinafter, a method of sending data from the fifteenth mesh device (MDEV 15) 245 of the fourth piconet 240 to the eleventh mesh device (MDEV 11) 235 of the third piconet 230 will be described.

First, when the fifteenth mesh device (MDEV 15) 245 wants to send data to the eleventh mesh device (MDEV 11) 235, the source mesh device, that is, the fifteenth mesh device (MDEV 15) 245. Configures a data frame including a mesh header and data to be transmitted to the destination mesh device, that is, the eleventh mesh device (MDEV 11) 235. In this case, the fifteenth mesh device (MDEV 15) 245 sets a source tree ID and a source ID to a value corresponding to the source mesh device in the mesh header, and sets a destination tree ID and a destination tree ID. The destination ID may be set to a value corresponding to the destination mesh device.

Next, the fifteenth mesh device (MDEV 15) 245 transmits a data frame to a fourth mesh piconet coordinator (MPNC 4) 225, which is a mesh piconet coordinator of the fourth piconet 240 including the source mesh device.

Subsequently, the fourth mesh piconet coordinator (MPNC 4) 225 interprets the received data frame to be a mesh piconet coordinator of the second piconet 220 including the fourth mesh piconet coordinator (MPNC 4) 225. The data frame is transmitted to the mesh piconet coordinator (MPNC 2) 213.

Next, the second mesh piconet coordinator (MPNC 2) 213 interprets the received data frame to be a mesh piconet coordinator of the first piconet 210 including the second mesh piconet coordinator (MPNC 2) 213. The data frame is transmitted to the mesh piconet coordinator (MPNC 1) 211.

Subsequently, the first mesh piconet coordinator (MPNC 1) 211 interprets the received data frame to determine a third mesh piconet coordinator (MPNC 3) 219, which is a mesh piconet coordinator of the third piconet 230 including a destination mesh device. Send the data frame.

Next, the third mesh piconet coordinator (MPNC 3) 219 interprets the received data frame and transmits the data frame to the eleventh mesh device (MDEV 11) 235 which is a destination mesh device.

Next, a structure of a data frame configured by a mesh device included in a wireless personal area network (hereinafter, also referred to as a “WPAN”) according to an embodiment of the present invention will be described with reference to FIG. 11.

FIG. 11 illustrates a structure of a data frame included in a mesh device according to an embodiment of the present invention. FIG.

As shown in FIG. 11, the data frame P100 includes a mesh header P110 including information related to data transmission and data P130 to be actually transmitted.

The mesh header P110 includes a mesh frame control field P111, a mesh ID field P112, a source tree ID field P113, and a destination tree ID field. (P114), Source ID field (P115), Destination ID field (P116), Mesh Sequence number field (P117), and Time To Line, hereinafter 'TTL' (Also referred to as') field P118.

The mesh frame control field P111 determines a transmission method and a transmission frame type of a data frame.

The mesh ID field P112 indicates a corresponding mesh ID.

The source tree ID field P113 indicates a tree ID of the source mesh piconet coordinator.

The destination tree ID field P114 indicates a tree ID of the destination mesh piconet coordinator.

The source ID field P115 indicates the device ID of the source mesh device.

The destination ID field P116 indicates the device ID of the destination mesh device.

The mesh sequence number field P117 indicates a mesh sequence number for maintaining frame transmission order and preventing duplicate transmission.

The life time field P118 indicates the maximum number of hops allowed while the data frame is being transmitted.

Next, a mesh network communication apparatus (hereinafter referred to as a device) 100 according to an embodiment of the present invention will be described with reference to FIG. 12 of a personal area network information base (hereinafter, also referred to as a 'PIB'). In the case of setting a specific parameter to a specific value, a message flow in the device 100 will be described. In this case, the device 100 may follow FIG. 4.

12 is a diagram illustrating a parameter setting method of a PIB according to an embodiment of the present invention.

As shown in FIG. 12, first, the DME 113 of the device 100 transmits an MHME-SET.request primitive to the mesh sublayer 135 to request to set a specific parameter of the PIB to a specific value ( S501).

Next, the mesh sublayer 135 transmits to the DME 113 an MHME-SET.confirm primitive indicating a result of setting a specific parameter of the PIB to a specific value according to the received MHME-SET.request primitive (S503). In this case, the mesh sublayer 135 may set a specific parameter of the PIB of each layer to a specific value by using primitives of the pulse sublayer 155 or the physical layer 175.

Next, referring to FIG. 13, a mesh network communication apparatus (hereinafter, also referred to as a “device”) 100 according to an embodiment of the present invention may be referred to as a personal area network information base (hereinafter, referred to as a “PIB”). When the current value of a specific parameter is requested, the message flow in the device 100 will be described. In this case, the device 100 may follow FIG. 4.

13 is a diagram illustrating a parameter request method of a PIB according to an embodiment of the present invention.

As shown in FIG. 13, first, the DME 113 of the device 100 transmits an MHME-GET.request primitive to the mesh sublayer 135 to request a current value of a specific parameter of the PIB (S601). .

Next, the mesh sublayer 135 transmits an MHME-GET.confirm primitive including a current value of a specific parameter of the PIB to the DME 113 according to the received MHME-GET.request primitive (S603). In this case, the mesh sublayer 135 may identify the PIB of each layer by using primitives of the pulse sublayer 155 or the physical layer 175.

Next, a mesh network communication apparatus (hereinafter referred to as a device) 100 according to an embodiment of the present invention will be described with reference to FIG. 14 of a personal area network information base (hereinafter, also referred to as a 'PIB'). In the case of resetting the parameter, a message flow in the device 100 will be described. In this case, the device 100 may follow FIG. 4.

14 is a diagram illustrating a parameter reset method of a PIB according to an embodiment of the present invention.

As shown in FIG. 14, first, the DME 113 of the device 100 sends an MHME-RESET.request primitive to the mesh sublayer 135 requesting to maintain a parameter of the PIB at a default value or a current state value. It transmits (S701).

Next, the mesh sublayer 135 transmits an MHME-RESET.confirm primitive including a result of resetting a parameter of the PIB according to the received MHME-RESET.request primitive to the DME 113 (S703). In this case, the mesh sublayer 135 may reset the PIB of each layer by using primitives of the pulse sublayer 155 or the physical layer 175.

Next, a mesh network communication apparatus (hereinafter referred to as a 'device') 100 that is a mesh piconet coordinator (hereinafter, also referred to as 'MPNC') according to an embodiment of the present invention will be described with reference to FIG. 15. In the case of withdrawing the message flow in the device 100 will be described. In this case, the device 100 may follow FIG. 4.

15 is a diagram illustrating a message flow when leaving a mesh network according to an embodiment of the present invention.

As shown in FIG. 15, first, the DME 113 of the device 100 transmits an MHME-STOP.request primitive to the mesh sublayer 135 to perform a mesh network withdrawal procedure (S801).

Next, the mesh sublayer 135 transmits the MLME-STOP.request primitive to the pulse sublayer 155 according to the received MHME-STOP.request primitive (S803).

Thereafter, the MAC sublayer 155 performs a shutdown procedure according to the received MLME-STOP.request primitive (S805).

Next, the pulse sublayer 155 transmits the MLME-STOP.confirm primitive to the mesh sublayer 135 according to the result of the withdrawal procedure (S807).

Thereafter, the mesh sublayer 135 transmits the MHME-STOP.confirm primitive to the DME 113 according to the received MLME-STOP.confirm primitive to inform the DME 113 of the withdrawal result of the mesh network (S809).

Next, referring to FIG. 16, a mesh network communication apparatus (hereinafter, also referred to as a 'device') 100 which is a child mesh piconet coordinator (hereinafter, referred to as 'MPNC') according to an embodiment of the present invention is a parent. The message flow in the device 100 when leaving the mesh network according to the mesh network withdrawal command of the MPNC will be described. In this case, the device 100 may follow FIG. 4.

16 is a diagram illustrating a message flow when leaving a mesh network according to another embodiment of the present invention.

As shown in FIG. 16, first, the Mac sublayer 155 of the device 100 includes a PicoNet Coordinator Shutdown Information Element (hereinafter referred to as a 'PNC Shutdown IE') from the parent MPNC. Receive a beacon (Beacon) (S901).

Next, the MAC sublayer 155 transmits an MLME-DISASSOCIATE.indication primitive including the device ID DEVID and the device address DEVAddress of the parent MPNC to the mesh sublayer 135 (S903).

Subsequently, the mesh sublayer 135 transmits the MHME-DISASSOCIATE.indication primitive including the device ID DEVID and the device address DEVAddress of the parent MPNC to the DME 113 according to the received MLME-DISASSOCIATE.indication primitive. (S905).

Next, the DME 113 determines whether the parent MPNC transmitting the beacon is a mesh coordinator according to the received MHME-DISASSOCIATE.indication primitive (S907). At this time, the mesh coordinator represents the highest parent MPNC of the mesh network. For example, if the mesh network follows FIG. 10, the mesh network becomes a first mesh piconet coordinator (MPNC 1) 211.

If the parent MPNC is a mesh network, the DME 113 and the mesh network 135 start the mesh network with the mesh coordinator of the new mesh network (S909).

On the other hand, if the parent MPNC is not a mesh network, the DME 113 selects another parent MPNC to join the mesh network again (S911).

The embodiments of the present invention described above are not only implemented by the apparatus and method but may be implemented through a program for realizing the function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded, The embodiments can be easily implemented by those skilled in the art from the description of the embodiments described above.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a configuration diagram according to an embodiment of a piconet constituting a conventional WPAN.

2 is a configuration diagram according to another embodiment of a piconet constituting a conventional WPAN.

3 is a configuration diagram according to another embodiment of a piconet constituting a conventional WPAN.

4 is a diagram illustrating a configuration of a mesh network communication apparatus according to an embodiment of the present invention.

5 is a diagram illustrating a mesh network start method according to an embodiment of the present invention.

6 is a diagram illustrating a message flow at the start of a mesh network according to an embodiment of the present invention.

7 is a diagram illustrating a tree forming method of a mesh network according to an embodiment of the present invention.

8 is a diagram illustrating a method for generating a child piconet according to an embodiment of the present invention.

9 is a diagram illustrating a message flow in forming a tree of a mesh network according to an embodiment of the present invention.

10 is a diagram illustrating a configuration of a piconet constituting a WPAN according to an embodiment of the present invention.

FIG. 11 illustrates a structure of a data frame included in a mesh device according to an embodiment of the present invention. FIG.

12 is a diagram illustrating a parameter setting method of a PIB according to an embodiment of the present invention.

13 is a diagram illustrating a parameter request method of a PIB according to an embodiment of the present invention.

14 is a diagram illustrating a parameter reset method of a PIB according to an embodiment of the present invention.

15 is a diagram illustrating a message flow when leaving a mesh network according to an embodiment of the present invention.

16 is a diagram illustrating a message flow when leaving a mesh network according to another embodiment of the present invention.

Claims (10)

A method of multi-hop mesh communication between piconets of a device in a personal wireless communication network (WPAN), Searching for a network existing in the vicinity of the device and determining whether there is a mesh network operating in the vicinity of the device according to a search result; If the mesh network does not exist, determining a parameter associated with a primitive for starting the mesh network as a mesh piconet coordinator of the new mesh network; And Transmitting a beacon frame generated based on the parameter to a plurality of devices around the device, such that each of the plurality of devices communicates in a single hop manner based on the beacon frame. Communication method. The method of claim 1, And if the mesh network exists, subscribing to the mesh network. The method of claim 2, The search results are A method of multi-hop mesh communication between piconets including piconet ID of the mesh network. The method of claim 1, The parameter is Method of multi-hop mesh communication between piconets including mesh ID, tree ID and beacon origin ID. A method of multi-hop mesh communication between piconets of a device in a personal wireless communication network (WPAN), Searching for a mesh network existing in the vicinity of the device; Selecting a parent piconet to which the device joins based on scan information corresponding to a search result; And And joining the parent piconet and allocating a tree ID from the coordinator of the parent piconet. The method of claim 5, The mesh network includes a plurality of piconets, The scan information is And a mesh ID of the mesh network, each piconet ID of the plurality of piconets, and an operating channel of the mesh network. The method of claim 5, The selecting step A method of multi-hop mesh communication between piconets, wherein the parent piconets are selected based on the number of hops to the coordinator, link status, and allocable channel time resources. The method of claim 5, And generating a child piconet of the parent piconet. The method of claim 8, Generating the child piconet Initializing a mesh parameter including a piconet ID and an operation channel of the child piconet; Generating a beacon based on the mesh parameters; And And transmitting the beacon to a device not joined to the mesh network through the operating channel. The method of claim 9, Generating the child piconet Requesting a channel time allocation from the coordinator; And Receiving the assigned channel time from the coordinator, The step of transmitting the beacons Piconet to multi-hop mesh communication method for transmitting the beacon through the operation channel during the allocated channel time.

Images