Sign In to Follow Application
View All Documents & Correspondence

Method And System For Synchronizing Communication In A Bluetooth Low Energy (Ble) Mesh Network

Abstract: ABSTRACT A method and a system for synchronizing communication between nodes in a Bluetooth Low Energy (BLE) mesh network. In this network, each node generates, based on at least one of own transmission parameter, a seed value, wherein the seed value represents next data advertisement instance of corresponding node. Further, the seed value of each node is communicated to other nodes (i.e. 1-hop neighbor nodes) in the BLE mesh network. Further, based on data transfer requirements (as indicated by the data transmission time/interval conveyed by the seed value) of a node, every other node in the BLE mesh network synchronizes own data transmission and reception settings, such that no two (i.e. 1-hop neighbor) nodes transmit data at the same time. FIG. 1

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
10 June 2015
Publication Number
52/2016
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
patent@bananaip.com
Parent Application
Patent Number
Legal Status
Grant Date
2024-01-31
Renewal Date

Applicants

SAMSUNG R&D Institute India - Bangalore Private Limited
# 2870, Orion Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanekundi Circle, Marathahalli Post,Bangalore-560 037, India

Inventors

1. Ajeet Kumar Singh
44, Anugrah Layout, Behind Sheyas Residency,Mahadevpura, Bangalore -560016
2. Arzad Alam Kherani
Phoenix Builiding Locn: 2-05-720, Bagmane Constellation Tech Park, Bangalore
3. Daekyu Choi
416 Maetan-dong, Yeongtong-gu, Suwon-si Gyeonggi-do, 443-742 Korea
4. Anand Sudhakar Chiddarwar
#1902, 1st Floor, 4th Main, 8th A Cross, New Thippasandra, Bnaglore -560075
5. Sang-jun moon
416 Maetan-dong, Yeongtong-gu, Suwon-si Gyeonggi-do, 443-742 Korea

Specification

CLIAMS:CLAIMS
What is claimed is:
1. A method for synchronizing communication of at least two nodes of a plurality of nodes in a Bluetooth Low Energy (BLE) mesh network, said method comprising:
generating a first seed value by a first node in said BLE mesh network, wherein said first seed value represents next data advertisement instance of said first node;
generating a second seed value by a second node in said BLE mesh network, wherein said second seed value represents next data advertisement instance of said second node;
communicating said first seed value to said second node, by said first node;
communicating said second seed value to said first node, by said second node;
synchronizing at least one of a data transmission and data reception setting, based on said first seed value, by said second node; and
synchronizing at least one of a data transmission and data reception setting, based on said second seed value, by said first node.
2. The method as claimed in claim 1, wherein said first seed value is generated based on at least one transmission parameter of said first node, by said first node.
3. The method as claimed in claim 1, wherein said second seed value is generated based on at least one transmission parameter of said second node, by said second node.
4. The method as claimed in claim 1, wherein said second node is a 1-hop neighbor of said first node.
5. The method as claimed in claim 1, wherein communicating said first seed value to said second node further comprises of encoding said first seed value in at least one of a control message and a data message, by said first node.
6. The method as claimed in claim 1, wherein communicating said second seed value to said first node further comprises of encoding said second seed value in at least one of a control message and a data message, by said second node.
7. The method as claimed in claim 1, wherein synchronizing at least one of said data transmission and data reception settings according to said first seed value, by said second node further comprises of:

scanning for at least one message from said first node, at a transmission time specified in said first seed value, by said second node; and
selecting a data transmission time different from the data transmission time of said first node, as specified in said first seed, by said second node.
8. The method as claimed in claim 1, wherein synchronizing at least one of said data transmission and data reception settings according to said second seed value, by said first node further comprises of:

scanning for at least one message from said second node, at a data transmission time specified in said second seed value, by said first node; and
selecting a data transmission time different from the data transmission time of said second node, as specified in said second seed, by said first node.
9. A system for synchronizing communication of at least two nodes of a plurality of nodes in a Bluetooth Low Energy (BLE) mesh network, said system configured for:
generating a first seed value, by a first node in said BLE mesh network, wherein said first seed value represents next data advertisement instance of said first node;
generating a second seed value, by a second node in said BLE mesh network, wherein said second seed value represents next data advertisement instance of said second node;
communicating said first seed value to said second node, by said first node;
communicating said second seed value to said first node, by said second node;
synchronizing at least one of a data transmission and data reception setting, based on said first seed value, by said second node; and
synchronizing at least one of a data transmission and data reception setting, based on said second seed value, by said first node.
10. The system as claimed in claim 9, wherein said first node is configured to generate said first seed value, based on at least one transmission parameter of said first node.
11. The system as claimed in claim 9, wherein said second node is configured to generate said second seed value, based on at least one transmission parameter of said second node.
12. The system as claimed in claim 9, wherein said first node is configured to communicate said first seed value to said second node, by encoding said first seed value in at least one of a control message and a data message.
13. The system as claimed in claim 9, wherein said second node is configured to communicate said second seed value to said first node, by encoding said second seed value in at least one of a control message and a data message.
14. The system as claimed in claim 9, wherein said second node is configured to synchronize at least one of said data transmission and data reception settings, according to said first seed value, by:

scanning for at least one message from said first node, at a transmission time specified in said first seed value, by a scanning module in said second node; and
selecting a data transmission time different from the data transmission time of said first node, as specified in said first seed, by a scheduler in said second node.
15. The system as claimed in claim 9, wherein said first node is configured to synchronize at least one of said data transmission and data reception settings, according to said second seed value by:

scanning for at least one message from said second node, at a data transmission time specified in said second seed value, by a scanning module in said first node; and
selecting a data transmission time different from the data transmission time of said second node, as specified in said second seed, by said first node.

Date: 10th June 2015 Signature:
Kalyan Chakravarthy ,TagSPECI:FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005

COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)

TITLE OF THE INVENTION

“METHOD AND SYSTEM FOR SYNCHRONIZING COMMUNICATION BETWEEN NODES IN A BLUETOOTH SMART NETWORK”

APPLICANTS:

Name Nationality Address
SAMSUNG R&D Institute India - Bangalore Private Limited India # 2870, Orion Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanekundi Circle, Marathahalli Post, Bangalore-560 037, India

The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-
TECHNICAL FIELD
[001] The embodiments herein relate to Bluetooth smart networks and, more particularly, to synchronize communication between nodes in a Bluetooth smart network.

BACKGROUND
[002] Bluetooth low energy (BLE)/Bluetooth smart network is a wireless personal area network technology, aimed to provide low cost Bluetooth connection between devices. BLE operates in the same Industrial, Scientific & Medical (ISM), license-free, 2.4- to 2.483-GHz frequency band as that of classic Bluetooth, and relays on frequency hopping technology. Certain features of the BLE wireless technology such as, but not limited to ultra-low peak, average and idle mode power consumption, ability to run for years on standard coin-cell batteries, low cost, multi-vendor, interoperability and enhanced range, robustness equal to Classic Bluetooth technology, good real-time features (if a small number of nodes are connected), and very short wake-up / connection time makes it suitable for use in devices such as watches, toys, toothbrush, mobile phones, medical devices and so on.
[003] In the case of data transfer over connectionless BLE networks, certain nodes directly receive data from the transmitting node, some nodes receive data being relayed by other nodes in the network. The node (which is not the destination) that receives the data from another node needs to relay the data to other nodes in the network, so that the data finally reaches the destination. One disadvantage of these connectionless transfer based BLE mesh networks is that more than one node may communicate/transmit data at the same time. This causes interference, which in turn results in loss of data. Another disadvantage of the existing BLE mesh networks is that all nodes listen to the network (i.e. scans the network for messages) all the time. In any communication device that serves as a node in the network, scanning is done at the expense of power. This is even more critical in the case of portable/mobile devices, as the battery life is a major concern.

OBJECT OF INVENTION

[004] An object of the embodiments herein is to provide at least one option for a node in a Bluetooth Low Energy (BLE) mesh network/Bluetooth smart network to measure own data transmission requirements.
[005] Another object of the embodiments herein is to provide at least one option for the node to dynamically generate a seed value that represents the node’s next data advertisement time instance.
[006] Another object of the embodiments herein is to provide at least one option for the node to communicate the generated seed value to other nodes in the BLE mesh network.
[007] Another object of the embodiments herein is to provide at least one option for the node to synchronize data transmission and data reception settings based on seed value communicated by other nodes in the BLE mesh network.

SUMMARY
[008] Embodiments further disclose a system for synchronizing communication of at least two nodes of a plurality of nodes in a Bluetooth Low Energy (BLE) mesh network. The system generates a first seed value, by a first node in the BLE mesh network, wherein the seed value represents next data advertisement instance of the first node. Further, a second node in the BLE mesh network generates a second seed value, wherein the second seed value represents next data advertisement instance of the second node. The first node communicates the first seed value to the second node, and the second node communicates the second seed value to the first node. Further, the second node synchronizes at least one of a data transmission and data reception setting, based on the first seed value. Similarly, the first node synchronizes at least one of a data transmission and data reception setting, based on the second seed value.
[009] In view of the foregoing, an embodiment herein provides a method for synchronizing communication of at least two nodes of a plurality of nodes in a Bluetooth Low Energy (BLE) mesh network. Initially, a first seed value is generated by a first node in the BLE mesh network, wherein the seed value represents next data advertisement instance of the first node. Further, a second seed value is generated by a second node in the BLE mesh network, wherein the second seed value represents next data advertisement instance of the second node. The first seed value is communicated to the second node, by the first node, and the second node synchronizes data transmission and reception settings, based on the first seed value. Similarly, the second seed value is communicated to the first node, by the second node, and the first node synchronizes data transmission and reception settings, based on the second seed value.
[0010] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES
[0011] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[0012] FIG. 1 illustrates a block diagram which depicts a Bluetooth Low Energy (BLE) mesh network, as disclosed in the embodiments herein;
[0013] FIG. 2 is a block diagram which depicts components of a node in the BLE mesh network, as disclosed in the embodiments herein;
[0014] FIG. 3 is a flow diagram that shows steps involved in the process of communicating data using synchronized communication between nodes in a BLE mesh network, as disclosed in the embodiments herein;
[0015] FIG. 4a is a diagram that depicts working of an example implementation of the synchronized BLE mesh network, as disclosed in the embodiments herein; and
[0016] FIGs 4b and 4c are example figures that depict service advertisement and data advertisement process, respectively, in a BLE mesh network that use seed based synchronization, as disclosed in the embodiments herein.

DETAILED DESCRIPTION OF EMBODIMENTS
[0017] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0018] The embodiments herein disclose a method and system for synchronized communication between nodes in a Bluetooth Low Energy (BLE) mesh network/Bluetooth smart network by synchronizing data transmission and data reception time of nodes in the BLE mesh network. Referring now to the drawings, and more particularly to FIGS. 1 through 4, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0019] FIG. 1 illustrates a block diagram which depicts a Bluetooth Low Energy (BLE) mesh network, as disclosed in the embodiments herein. The BLE mesh network 100 (hereinafter referred to as “network”) comprises of a plurality of nodes 101. It is to be noted that the terms Bluetooth Low Energy (BLE) mesh network and Bluetooth smart network are used interchangeably, throughout the specification.
[0020] A node 101 can be any User Equipment and/or network component that can be configured to connect with at least one other node 101, to form a network 100, wherein each message broadcasted by a node 101 to reach destination node(s) in the network 100. For example, the node 101 can be a mobile phone, a laptop, a tablet computer or any such device with Bluetooth connectivity support. It is to be noted that the network 100 as in the Fig. 1 is formed using 5 nodes 101. However, the number of nodes 101 that constitute that network 100 can vary based on requirements. Further, all nodes 101 in the network 100 can be considered equivalent to each other in terms of functioning.
[0021] In an embodiment, each node 101 can be configured to generate and transmit at least one own data transmission requirement, preferably in terms of data transmission intervals, as a seed value, to other nodes 101 in the network. Other nodes 101 in the network 100 can be configured to identify transmission interval of the node 101 that transmitted the seed value, upon receiving the seed value. Each node 101 in the network 100 can be further configured to synchronize own data transmission and data reception settings, such that no two nodes i.e. 1-hop neighboring nodes transmit data at the same time. In a preferred embodiment, each node 101 in the network 100 can be configured to synchronize data transmission and data reception settings, based on seed value of corresponding 1-hop neighbor nodes. It is to be noted that the terms ‘other nodes’ and ‘1-hop neighbor nodes’ are used interchangeably throughout the specification. Each node 101 in the network 100 can be further configured to enter a scan mode, at time intervals in which another node 101 in the network 100 transmits the data, and collect the data transmitted by one other node 101. The node 101 can be further configured to add delay or offset to extent or lower the scanning time, according to requirements. The node 101 can be further configured to enter an idle mode when no other node 101 in the network 100 is transmitting data. In a preferred embodiment, the seed value is encoded in header of all control and data messages transmitted by the node 101.
[0022] The node 101 can be further configured to encode, in addition to the seed value, at least one additional parameter, that can be used to synchronize the data transmission and data reception settings in certain scenarios, in header of control and data messages. A few examples of such additional parameters are mentioned below:
1. Role
2. Length of data to be transmitted
3. Start and End of data
4. Priority (indicating emergency data)
[0023] The node 101 can be further configured to transmit own messages, receive at least one message, and/or act as a relay node. Function of the relay node is to act as an intermediate node for another two nodes 101 to communicate. In this scenario, the relay node receives the message being transmitted by another node, and relays to another node, which can be the destination of the message. In various embodiments, the network 100 can be connection-oriented or connectionless. If the network 100 is a connection oriented type, the synchronization (of data transmission and data reception) is done dynamically while setting up the network 100 i.e. while establishing connections between nodes 101 in the network 100. If the network 100 is a connectionless type, then the synchronization is done in real-time, while nodes 101 in the network 100 are communicating each other.
[0024] FIG. 2 is a block diagram which depicts components of a node in the BLE mesh network, as disclosed in the embodiments herein. The node 101 comprises of an Input/Output (I/O) interface 201, a message parsing module 202, a scheduler 203, a timer module 204, and a scanning module 205.
[0025] The I/O interface 201can be configured to provide at least one channel with at least one suitable communication protocol, for the node 101 to communicate with at least one other node 101, and/or one other network component. The I/O interface 201 can be further configured to provide at least one interface for a user to communicate with the node 101. The I/O interface 201 can be further configured to transmit and receive all sort of messages (which may be existing and user-defined) as part of the BLE communication.
[0026] The message parsing module 202 can be further configured to collect at least one message from the I/O interface 201 and/or the scanning module 205, and parse the message to extract components of the message. For example, the message parsing module 202 can extract the seed value being communicated by other nodes 101, and transmit the seed value to the scheduler 203.
[0027] The scheduler 203 can be configured to identify, based on seed value received from every other node 101 in the network 100, corresponding transmission intervals of each node 101. The scheduler 203 can be further configured to schedule transmission intervals of own node 101, at an interval that do not overlap with transmission time of any other node 101. The scheduler 203 can be further configured to instruct the scanning module 205, to perform scanning, at the transmission intervals of at least one other node 101 in the network 100.
[0028] The scanning module 205 can be configured to enter a scanning mode and perform scanning, at transmission intervals specified by other nodes 101 in the network 100. The scanning module 205 can be further configured to synchronize the scanning intervals, with the help of the timer module 204. The scanning module 205 can be further configured to enter an idle mode at times when no other node 101 in the network 100 is transmitting any data.
[0029] FIG. 3 is a flow diagram that shows steps involved in the process of communicating data using synchronized communication between nodes in a BLE mesh network, as disclosed in the embodiments herein. Initially, a node 101 identifies (302) at least one other node 101 in the network 100. In a preferred embodiment, the node 101 identifies at least one other node 101, by executing a service advertisement process (as depicted in Fig. 4b). In the service advertisement process, the node 101 starts a new thread, and sends service advertisements. The node 101 also scans for service advertisements from at least one other node 101. If at least one other node 101 is found within a specified time period, the node 101 enters a data transmission /data advertisement period.
[0030] In the data transmission over advertisement phase, the node 101 advertises and transmits data to at least one destination node. In a preferred embodiment, while transmitting control and data packets related to the data being transmitted, the node 101 generates a seed value, wherein the seed value indicates parameters such as but not limited to transmission intervals, length of data, and priority of data. The seed value can be generated based on at least one parameter such as, but not limited to traffic load, battery level of the node, role criticality, and urgency of data to be transmitted.
[0031] Each node 101 in the network 100 can be configured to synchronize, based on the seed value communicated by every other node 101 in the network 100, own data transmission and data reception parameters. The node 101 transmits (306) data and control messages, at the time specified in the seed value transmitted. The same node 101 enters a scan mode and scans (308) the network for messages from another node 101 in the network, at a specified transmission interval of that particular node. For example, while a first node 101.a (as depicted in Fig. 1) is transmitting data at the specified transmission interval, other nodes 101 in the network 100 enters a scan mode, and scans for any message from the first node. This transmission and scanning processes are repeated by all nodes 101 in the network.
[0032] For example, consider a seed based synchronization scenario (as depicted in Fig. 4b) in which the network 100 comprises of three nodes 101; node 1, node 2, and node 3, which are represented by the numbers 1, 2, and 3 respectively. As depicted, the node 1 transmits advertisement at time instance '0', and at the same time, node 2 and node 3 enters scan mode and scans for message from node 1. Further, the node 2 transmits data at time instance '1', and the node 1 and node 3 scans the network for messages from node 2 at the same time. Similarly, node 1 and node 2 enters scan mode and scans for messages from node 3, while the node 3 is transmitting data at time instance '2'. Here, the working of node 1, node 2,and node 3 are synchronized such that each node is aware of data transmission interval of every other node i.e. corresponding 1-hop neighbor nodes and their 1-hop neighbor nodes in the network 100, and accordingly synchronizes own data transmission and reception intervals.
[0033] In an embodiment, in a scenario wherein a node 101 receives an urgent message, and needs to transmit ahead of the scheduled transmission interval, a flag value that indicates the urgency can be added in the header of data and control messages being transmitted, and other nodes 101, upon seeing this flag value, can adjust the data transmission intervals accordingly. In an embodiment, the data transmission and scan intervals of the node 101 can be made equal, so as to increase probability of reception of messages by the nodes. Further, scanning intervals can be decided such that the scan starts prior to the data transmission interval specified by the other node 101, and ends after the transmission interval of the other node 101. This can help to receive data even if there is a delay in the data transmission.
[0034] For reliability in data transfers, after transmitting a data, the node 101 that transmitted the data can wait for an acknowledgement, for a pre-set time period, and check (310) if the data packet can be considered to be acknowledged. In a preferred embodiment, the acknowledgement in this scenario is based on an 'overhearing' condition in which the node 101 that transmitted the data receives the same packet, while at least one other 1-hop neighbor node 101 that received the data retransmits/relays it. The node 101 that transmitted the data can be configured to consider the relay/retransmission of same data back from at least one other node, as an acknowledgement for the data transmitted. If the acknowledgement is not received within a pre-set time period, the node 101 can re-transmit (312) the data, based on application requirements. The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.
[0035] FIG. 4a is an example diagram that depicts working of a node in the synchronized BLE mesh network, as disclosed in the embodiments herein. The node 101 is referred to as device 1, in the figure. In this figure, blocks above the 'standby line' indicate advertisement events i.e. data transmission intervals by the node 1, and the blocks below the standby line indicate the time intervals at which the node 101 scans for advertisements from other nodes.
[0036] The data transmission by the node 1 at the service advertisement period, as well as at the data advertisement period also is depicted in the figure. As depicted, in the service advertisement period, the node 1 sends frequent messages to identify at least one other node in the network 100. Further, in the data advertisement period, the node transmits data only in the data transmission intervals indicated by the seed value generated, and scans for messages from other nodes, in the data transmission intervals specified in seed values transmitted by each of those nodes.
[0037] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0038] The embodiments disclosed herein specify a system for synchronizing working of nodes in a BLE mesh network. The mechanism allows synchronization of data transmission and reception intervals, providing a system thereof. Therefore, it is understood that the scope of protection is extended to such a system and by extension, to a computer readable means having a message therein, said computer readable means containing a program code for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment using the system together with a software program written in, for ex. Very high speed integrated circuit Hardware Description Language (VHDL), another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including, for ex. any kind of a computer like a server or a personal computer, or the like, or any combination thereof, for ex. one processor and two FPGAs. The device may also include means which could be for ex. hardware means like an ASIC or a combination of hardware and software means, an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means are at least one hardware means or at least one hardware-cum-software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. Alternatively, the embodiment may be implemented on different hardware devices, for ex. using a plurality of CPUs.
[0039] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims as described herein.

CLAIMS
What is claimed is:
1. A method for synchronizing communication of at least two nodes of a plurality of nodes in a Bluetooth Low Energy (BLE) mesh network, said method comprising:
generating a first seed value by a first node in said BLE mesh network, wherein said first seed value represents next data advertisement instance of said first node;
generating a second seed value by a second node in said BLE mesh network, wherein said second seed value represents next data advertisement instance of said second node;
communicating said first seed value to said second node, by said first node;
communicating said second seed value to said first node, by said second node;
synchronizing at least one of a data transmission and data reception setting, based on said first seed value, by said second node; and
synchronizing at least one of a data transmission and data reception setting, based on said second seed value, by said first node.
2. The method as claimed in claim 1, wherein said first seed value is generated based on at least one transmission parameter of said first node, by said first node.
3. The method as claimed in claim 1, wherein said second seed value is generated based on at least one transmission parameter of said second node, by said second node.
4. The method as claimed in claim 1, wherein said second node is a 1-hop neighbor of said first node.
5. The method as claimed in claim 1, wherein communicating said first seed value to said second node further comprises of encoding said first seed value in at least one of a control message and a data message, by said first node.
6. The method as claimed in claim 1, wherein communicating said second seed value to said first node further comprises of encoding said second seed value in at least one of a control message and a data message, by said second node.
7. The method as claimed in claim 1, wherein synchronizing at least one of said data transmission and data reception settings according to said first seed value, by said second node further comprises of:

scanning for at least one message from said first node, at a transmission time specified in said first seed value, by said second node; and
selecting a data transmission time different from the data transmission time of said first node, as specified in said first seed, by said second node.
8. The method as claimed in claim 1, wherein synchronizing at least one of said data transmission and data reception settings according to said second seed value, by said first node further comprises of:

scanning for at least one message from said second node, at a data transmission time specified in said second seed value, by said first node; and
selecting a data transmission time different from the data transmission time of said second node, as specified in said second seed, by said first node.
9. A system for synchronizing communication of at least two nodes of a plurality of nodes in a Bluetooth Low Energy (BLE) mesh network, said system configured for:
generating a first seed value, by a first node in said BLE mesh network, wherein said first seed value represents next data advertisement instance of said first node;
generating a second seed value, by a second node in said BLE mesh network, wherein said second seed value represents next data advertisement instance of said second node;
communicating said first seed value to said second node, by said first node;
communicating said second seed value to said first node, by said second node;
synchronizing at least one of a data transmission and data reception setting, based on said first seed value, by said second node; and
synchronizing at least one of a data transmission and data reception setting, based on said second seed value, by said first node.
10. The system as claimed in claim 9, wherein said first node is configured to generate said first seed value, based on at least one transmission parameter of said first node.
11. The system as claimed in claim 9, wherein said second node is configured to generate said second seed value, based on at least one transmission parameter of said second node.
12. The system as claimed in claim 9, wherein said first node is configured to communicate said first seed value to said second node, by encoding said first seed value in at least one of a control message and a data message.
13. The system as claimed in claim 9, wherein said second node is configured to communicate said second seed value to said first node, by encoding said second seed value in at least one of a control message and a data message.
14. The system as claimed in claim 9, wherein said second node is configured to synchronize at least one of said data transmission and data reception settings, according to said first seed value, by:

scanning for at least one message from said first node, at a transmission time specified in said first seed value, by a scanning module in said second node; and
selecting a data transmission time different from the data transmission time of said first node, as specified in said first seed, by a scheduler in said second node.
15. The system as claimed in claim 9, wherein said first node is configured to synchronize at least one of said data transmission and data reception settings, according to said second seed value by:

scanning for at least one message from said second node, at a data transmission time specified in said second seed value, by a scanning module in said first node; and
selecting a data transmission time different from the data transmission time of said second node, as specified in said second seed, by said first node.

Date: 10th June 2015 Signature:
Kalyan Chakravarthy
ABSTRACT

A method and a system for synchronizing communication between nodes in a Bluetooth Low Energy (BLE) mesh network. In this network, each node generates, based on at least one of own transmission parameter, a seed value, wherein the seed value represents next data advertisement instance of corresponding node. Further, the seed value of each node is communicated to other nodes (i.e. 1-hop neighbor nodes) in the BLE mesh network. Further, based on data transfer requirements (as indicated by the data transmission time/interval conveyed by the seed value) of a node, every other node in the BLE mesh network synchronizes own data transmission and reception settings, such that no two (i.e. 1-hop neighbor) nodes transmit data at the same time.

FIG. 1

Documents

Application Documents

# Name Date
1 2905-CHE-2015-Annexure [31-01-2024(online)].pdf 2024-01-31
1 Form5.pdf 2015-06-24
2 2905-CHE-2015-IntimationOfGrant31-01-2024.pdf 2024-01-31
2 FORM3.pdf 2015-06-24
3 form 2.pdf 2015-06-24
3 2905-CHE-2015-PatentCertificate31-01-2024.pdf 2024-01-31
4 Drawings_CS.pdf 2015-06-24
4 2905-CHE-2015-PETITION UNDER RULE 137 [31-01-2024(online)]-1.pdf 2024-01-31
5 2905-CHE-2015-PETITION UNDER RULE 137 [31-01-2024(online)].pdf 2024-01-31
5 2905-CHE-2015-FORM-26 [15-03-2018(online)].pdf 2018-03-15
6 2905-CHE-2015-RELEVANT DOCUMENTS [31-01-2024(online)]-1.pdf 2024-01-31
6 2905-CHE-2015-FORM-26 [16-03-2018(online)].pdf 2018-03-16
7 2905-CHE-2015-RELEVANT DOCUMENTS [31-01-2024(online)].pdf 2024-01-31
7 2905-CHE-2015-FER.pdf 2019-08-07
8 2905-CHE-2015-Written submissions and relevant documents [31-01-2024(online)].pdf 2024-01-31
8 2905-CHE-2015-OTHERS [07-02-2020(online)].pdf 2020-02-07
9 2905-CHE-2015-Annexure [19-01-2024(online)].pdf 2024-01-19
9 2905-CHE-2015-FER_SER_REPLY [07-02-2020(online)].pdf 2020-02-07
10 2905-CHE-2015-Correspondence to notify the Controller [19-01-2024(online)].pdf 2024-01-19
10 2905-CHE-2015-DRAWING [07-02-2020(online)].pdf 2020-02-07
11 2905-CHE-2015-CORRESPONDENCE [07-02-2020(online)].pdf 2020-02-07
11 2905-CHE-2015-FORM-26 [19-01-2024(online)].pdf 2024-01-19
12 2905-CHE-2015-CLAIMS [07-02-2020(online)].pdf 2020-02-07
12 2905-CHE-2015-US(14)-HearingNotice-(HearingDate-30-01-2024).pdf 2024-01-17
13 2905-CHE-2015-ABSTRACT [07-02-2020(online)].pdf 2020-02-07
14 2905-CHE-2015-CLAIMS [07-02-2020(online)].pdf 2020-02-07
14 2905-CHE-2015-US(14)-HearingNotice-(HearingDate-30-01-2024).pdf 2024-01-17
15 2905-CHE-2015-CORRESPONDENCE [07-02-2020(online)].pdf 2020-02-07
15 2905-CHE-2015-FORM-26 [19-01-2024(online)].pdf 2024-01-19
16 2905-CHE-2015-Correspondence to notify the Controller [19-01-2024(online)].pdf 2024-01-19
16 2905-CHE-2015-DRAWING [07-02-2020(online)].pdf 2020-02-07
17 2905-CHE-2015-FER_SER_REPLY [07-02-2020(online)].pdf 2020-02-07
17 2905-CHE-2015-Annexure [19-01-2024(online)].pdf 2024-01-19
18 2905-CHE-2015-OTHERS [07-02-2020(online)].pdf 2020-02-07
18 2905-CHE-2015-Written submissions and relevant documents [31-01-2024(online)].pdf 2024-01-31
19 2905-CHE-2015-RELEVANT DOCUMENTS [31-01-2024(online)].pdf 2024-01-31
19 2905-CHE-2015-FER.pdf 2019-08-07
20 2905-CHE-2015-RELEVANT DOCUMENTS [31-01-2024(online)]-1.pdf 2024-01-31
20 2905-CHE-2015-FORM-26 [16-03-2018(online)].pdf 2018-03-16
21 2905-CHE-2015-PETITION UNDER RULE 137 [31-01-2024(online)].pdf 2024-01-31
21 2905-CHE-2015-FORM-26 [15-03-2018(online)].pdf 2018-03-15
22 Drawings_CS.pdf 2015-06-24
22 2905-CHE-2015-PETITION UNDER RULE 137 [31-01-2024(online)]-1.pdf 2024-01-31
23 form 2.pdf 2015-06-24
23 2905-CHE-2015-PatentCertificate31-01-2024.pdf 2024-01-31
24 FORM3.pdf 2015-06-24
24 2905-CHE-2015-IntimationOfGrant31-01-2024.pdf 2024-01-31
25 2905-CHE-2015-Annexure [31-01-2024(online)].pdf 2024-01-31
25 Form5.pdf 2015-06-24

Search Strategy

1 Search2905-CHE-2015_29-07-2019.pdf

ERegister / Renewals

3rd: 30 Apr 2024

From 10/06/2017 - To 10/06/2018

4th: 30 Apr 2024

From 10/06/2018 - To 10/06/2019

5th: 30 Apr 2024

From 10/06/2019 - To 10/06/2020

6th: 30 Apr 2024

From 10/06/2020 - To 10/06/2021

7th: 30 Apr 2024

From 10/06/2021 - To 10/06/2022

8th: 30 Apr 2024

From 10/06/2022 - To 10/06/2023

9th: 30 Apr 2024

From 10/06/2023 - To 10/06/2024

10th: 30 Apr 2024

From 10/06/2024 - To 10/06/2025

11th: 10 Jun 2025

From 10/06/2025 - To 10/06/2026