FIGURES 1 through 4, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system. It should be observed that method steps and system components have been represented by conventional symbols in the figures, showing only specific details that are relevant for an understanding of the present disclosure. Further, details that may be readily apparent to person ordinarily skilled in the art may not have been disclosed. In the present disclosure, relational terms such as first and second, and the like, may be used to distinguish one entity from another entity, without necessarily implying any actual relationship or order between such entities.

Embodiments of the present disclosure described herein provide a method and system for synchronizing attributes among multiple electronic devices.

FIGURE 1 illustrates a block diagram of an environment 100, in accordance with which various embodiments can be implemented.

The environment 100 includes a plurality of electronic devices, for example an electronic device 105a and an electronic device 105b, connected through a network 110. In some embodiments, the network 110 is a low energy Bluetooth® network. Examples of the electronic devices include, but are not limited to, a computer, a laptop, a mobile device, a hand held device, a Personal Digital Assistant (PDA), a Bluetooth® enabled watch, and other Bluetooth® enabled devices.

The electronic devices include a first electronic device for initiating synchronization of one or more attributes with a second electronic device. Examples of the one or more attributes include, but are not limited to, time, day, date, month, year and calendar. The attributes for time further can be extended to seconds, divisions of a second. The synchronization is performed using attribute commands. The attribute commands include one of a read command and a write command. The electronic device 105a can act as the first electronic device and the electronic device 105b can act as the second electronic device. In some embodiments, the electronic device 105a can act as the second electronic device and the electronic device 105b can act as the first electronic device.

The electronic device 105a includes a plurality of components for enabling synchronization of the one or more attributes with the electronic device 105b. The electronic device 105a, including the components, is explained in detail in FIGURE 2.

FIGURE 2 illustrates a block diagram of the electronic device 105a, in accordance with one embodiment. The electronic device 105a includes a bus 205 for communicating information, and a processor 210 coupled to the bus 205 for processing the information. Examples of the information include attributes and attribute values. The electronic device 105a also includes a memory 215, for example, a random access memory (RAM) coupled to the bus 205 for storing information to be used by the processor 210. The memory 215 can be used for storing temporary information to be used by the processor 210. The electronic device 105a can further include a read only memory (ROM) 220 coupled to the bus 205 for storing static information to be used by the processor 210. A storage unit 225, for example a magnetic disk, hard disk or optical disk, can be provided and coupled to the bus 205 for storing the information.

The electronic device 105a can be coupled via the bus 205 to a display 230, for example, a cathode ray tube (CRT) or liquid crystal display (LCD), for displaying information. An input device 235, including various keys, is coupled to the bus 205 for communicating information to the processor 210. In some embodiments, cursor control 240, for example a mouse, a trackball, a joystick, or cursor direction keys, for communicating information to the processor 210 and for controlling cursor movement on the display 230 can also be present.

In one embodiment, the steps of the present disclosure are performed by the electronic device 105a using the processor 210. The information can be read into the memory 215 from a machine-readable medium, for example the storage unit 225. In alternative embodiments, hard-wired circuitry can be used in place of or in combination with software instructions to implement various embodiments.

The machine-readable medium can be a medium providing data to a machine to enable the machine to perform a specific function. The machine-readable medium can be a storage media. Storage media can include non-volatile media and volatile media. The storage unit 225 can be a non-volatile media. The memory 215 can be a volatile media. All such media are tangible to enable the instructions carried by the media to be detected by a physical mechanism that reads the instructions into the machine.

Examples of the machine readable medium include, but are not limited to, a floppy disk, a flexible disk, hard disk, magnetic tape, a CD-ROM, optical disk, punchcards, papertape, a RAM, a PROM, EPROM, and a FLASH-EPROM.

The electronic device 105a also includes a communication interface 245 coupled to the bus 205 for enabling data communication. Examples of the communication interface 245 include, but are not limited to, a Bluetooth® port.

In some embodiments, the processor 210 can include one or more processing units for performing one or more functions of the processor 210. The processing units are hardware circuitry performing specified functions.

The one or more functions include scanning the Bluetooth® network for one or more attributes of the second electronic device. The one or more functions also include establishing a low energy Bluetooth® connection between the first electronic device and the second electronic device. Further, the one or more functions include synchronizing the attributes of the second electronic device and one or more attributes of the first electronic device.

FIGURE 3 illustrates a flow diagram for time and date synchronization between a first electronic device 105a and a second electronic device 105b, in accordance with one embodiment.

In the illustration, a synchronization profile, for example an ultra low power Bluetooth® profile connection, is established between the first electronic device 105a and the second electronic device 105b. The first electronic device 105a is an initiator device and the second electronic device 105b is a target device where time and date attribute values of the first electronic device is to be synchronized.

The first electronic device 105a sends a read attribute command 305 to the second electronic device 105b for reading one or more attributes, for example an attribute time and an attribute date. The second electronic device 105b then sends a read attribute response 310, with the attributes and the attribute values. For example, if the time and the date in the second electronic device 105b are 1:05:48 PM and 1st October, 2009 respectively, then the read attribute response 310 includes attribute time and an attribute value 130548, and the attribute date and the attribute value 011009.

In the illustration, the first electronic device 105a has a time corresponding to 1:10:52 PM and date 2nd October 2009, and the corresponding attributes value are 011052 and 021009 respectively. A write attribute command 315 is sent to the second electronic device 105b for writing the attribute time with the value 0110522 and 021009. In some embodiments, the writing of attributes can be specific to different applications.

Upon receiving the write attribute command, the second electronic device 105b acknowledges by sending a write attribute response 320. The time and date on the second electronic device 105b is changed to 1:10:52 PM and date 2nd October, 2009.

In some embodiments, the second electronic device 105b can reject the write command 315.

Upon receiving the write attribute response, the first electronic device 105a can terminate the ultra low power Bluetooth® profile connection.

FIGURE 4 illustrates a flowchart for a method for enabling synchronization of attributes among multiple electronic devices, for example a first electronic device and a second electronic device, over a low energy Bluetooth® network, in accordance with one embodiment.

The method starts at step 405.

At step 410, a low energy Bluetooth® network is scanned for one or more attributes of the second electronic device by the first electronic device. The attributes are advertised by the second electronic device. The attributes of the second electronic device are identified by the first electronic device. Examples of the attributes include, but are not limited to, time, day, date, month, year and calendar.

The electronic devices utilize one of an ultra low power Bluetooth®, a dual mode Bluetooth®, or a combination thereof.

At step 415, a low energy Bluetooth® connection is established between the first electronic device and the second electronic device. The first electronic device establishes the low energy Bluetooth® connection based on the identification of the one or more attributes, received from scanning of step 410. The connection can be associated with Bluetooth® profiles. The profiles define the attributes and protocols supported by each electronic device. A common supported protocol is then utilized by the electronic devices for further communication. For example, a synchronization profile can be defined for ultra low power Bluetooth®.

At step 420, the attributes of the second electronic device and one or more attributes of the first electronic device are synchronized.

In some embodiments, the synchronization is performed by writing one or more attribute values of the first electronic device to the second electronic device.

In some embodiments, the synchronization includes reading attributes of the second electronic device. The attributes are received in response to a read attribute command sent to the second electronic device by the first electronic device. The received attributes include the attributes listed in the read attribute command and an attribute value for each attribute in the second electronic device. A user associated with the first electronic device can then choose to synchronize the attributes of the second electronic device with the attributes of the first electronic device by sending a write attribute command to the second electronic device. The write attribute command includes the attributes values corresponding to the attributes of the first electronic device.

In some embodiments, the attribute commands are associated with a sixteen (16) bit Universal Unique Identifier (UUID), for example OX0046.

In other embodiments, one or more attributes values read from the second electronic device are written to the first electronic device.

In some embodiments, the synchronization also can include comparing the attributes of the first electronic device with the attributes of the second electronic device. If the attributes of the second electronic device differs from the corresponding attributes of the first electronic device, then the attributes of the first electronic device is applied to the second electronic device. If the attributes of the second electronic device is similar to the corresponding attributes of the first electronic device then the electronic devices are considered to be synchronized.

The method stops at step 425.

Although the present disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.