TWI428762B - Method, apparatus and computer program product for providing intelligent synchronization - Google Patents

Description

Method, device, and computer program product for providing intelligent synchronization Field of invention

Embodiments of the present invention generally relate to synchronization techniques, and more particularly to methods, apparatus, and computer program products for providing intelligent synchronization between devices.

Background of the invention

The modern communications era has brought about a huge expansion of wired and wireless networks. Computer networks, television networks and telephone networks are experiencing an unprecedented technological expansion spurred by consumer demand. Wireless and mobile network technologies have addressed the relevant consumer needs while providing more flexibility and impliedness in information transfer.

Current and future road technologies continue to assist in the ease of information transfer and user convenience. Among the reasons for the need to increase the ease of information transfer is the transfer of services to users of an action endpoint. The service can be a type of specific media or communication application desired by the user, such as a music player, a gaming machine, an e-book, a short message, an email, and the like. The service can also be a type of interactive application in which a user can communicate with a network device to perform a task or achieve a goal. Services may be provided from a network server or other network device or even from a mobile endpoint, such as, for example, a mobile phone, a mobile television, a mobile gaming system, a mobile computer, and the like.

Summary of invention

For many services where the supply of services involves two-way communication of information between devices, data synchronization between devices is satisfactory at periodic intervals. For example, in the case of an email service, an email server can be periodically synchronized with a remote device, such as a laptop or an action endpoint, directly or by providing synchronized data to a The way to synchronize the server. In some cases, a wired or wireless communication network can be used to initiate a communication between the synchronization server and the remote device during which data synchronization can be accomplished, for example, at regular intervals or in response to receipt of new data. Chemical. During data synchronization, the synchronization server can communicate changes, such as a new email message to the remote device, and the remote device can communicate to the synchronization server for any changes, such as reading emails or newly drafted emails. Be prepared to be transmitted to a recipient. Alternatively, the remote device can change the communication to the email server or the remote device, and the email server can exchange the changes through the synchronization server.

Traditional synchronization procedures typically require a relatively large amount of data to be exchanged over a relatively high number of communication signals. Therefore, battery consumption and processing power are quickly and disadvantageously consumed. In order to reduce the shortcomings of the traditional methods, efforts have been made to reduce the number of data and the number of routes of communication signals during data synchronization. However, such a mechanism cannot be performed in an authenticated manner, nor can it be initiated on a remote device, which may be desirable in certain situations.

Therefore, it is desirable to provide a mechanism by which synchronization can be performed in a smart manner to avoid encountering the above disadvantages. In this way, users of mobile endpoints and other electronic devices can further customize the synchronization of their devices, thereby enhancing the user experience in using their devices.

Accordingly, a method, apparatus and computer program product for providing intelligent synchronization between devices are provided. In accordance with an exemplary embodiment of the present invention, in response to receiving a message attempting to synchronize with a network element (e.g., a server), a client device may first determine if the client device has any changes (e.g., has not been transmitted to the servo) New information), which is not related to the received message. In an exemplary embodiment, if the client device has not changed, a first synchronization method such as a fast push-in synchronization can be performed. However, if the client device has a change, the client device may reject the synchronization and then initiate a second synchronization method.

In an exemplary embodiment, a method of providing intelligent synchronization is provided. The method includes receiving a message. This message indicates that the data to be synchronized is available. The method can also include selecting, in response to receiving the message, a synchronization method based on at least a portion of the plurality of synchronization methods based on whether the client device includes new data not communicated to a network component.

In other exemplary embodiments, a computer program product for providing intelligent synchronization is provided. The computer program product includes at least one computer readable storage medium having a computer readable code portion stored therein. The computer readable code portion contains the first and second executable portions. The first executable portion is for receiving a message. This message indicates that the data to be synchronized is available. The second executable portion is configured to receive the message in response, and select at least one of the plurality of synchronization methods based on whether the client device includes new data that has not been communicated to a network component. method.

In other exemplary embodiments, an apparatus for providing intelligent synchronization is provided. The device includes a processing component configured to receive a message. This message indicates that the data to be synchronized is available. The processing component can also be configured to receive the message in response to selecting a synchronization from at least a portion of the plurality of synchronization methods based on whether the device includes new data that has not been communicated to a network component. method.

In other exemplary embodiments, an apparatus for providing intelligent synchronization is provided. The device includes means for receiving a message. This message indicates that the data to be synchronized is available. The apparatus can further include means for selecting, in response to receiving the message, from at least a portion of the plurality of synchronization methods based on whether the client device includes new data that has not been communicated to the network component To choose a synchronization method.

In other exemplary embodiments, an apparatus for providing intelligent synchronization is provided. The apparatus includes a processing component configured to receive an indication that there is data intended for synchronization to a client device for communicating a message indicating that the client device is available for synchronizing data, And to receive only one confirmation from the client device in response to the client device not storing new data, or receiving a synchronization request from the client device in response to the client device having new data.

Embodiments of the present invention can provide methods, apparatus, and computer program products for use in a system in which synchronization of data between a client device and a server is required. As a result, for example, the mobile endpoints and other electronic devices may benefit from determining the use of data synchronization based on the state of the action endpoint associated with new data that has not been detected by the network element (eg, the server) at the endpoint of the action. Synchronization method.

Simple illustration

Having thus described the embodiments of the present invention in the general terms of the invention, reference to the drawings, which are not necessarily drawn to scale, and wherein: FIG. 1 is a schematic representation of an action endpoint in accordance with an exemplary embodiment of the present invention. Figure 2 is a block diagram of a wireless communication system in accordance with an exemplary embodiment of the present invention; and Figure 3 illustrates a block of a system for providing intelligent synchronization in accordance with an exemplary embodiment of the present invention. FIG. 4 illustrates a block diagram of another system for providing intelligent synchronization in accordance with an exemplary embodiment of the present invention; FIG. 5A illustrates a block of a client synchronization component in accordance with an exemplary embodiment of the present invention. Figure 5B is a block diagram illustrating a synchronization element in accordance with an exemplary embodiment of the present invention; and Figure 6 is a control flow diagram illustrating a first synchronization method in accordance with an exemplary embodiment of the present invention; Figure 7 is a control flow diagram illustrating a second synchronization method in accordance with an exemplary embodiment of the present invention; and Figure 8 is a flow chart in accordance with an exemplary embodiment in accordance with the present invention Exemplary methods for providing the intelligent synchronization; and a ninth graph a flowchart providing an exemplary method based intelligent synchronization of other embodiments according to an exemplary embodiment according to the present invention for one.

Detailed description of the preferred embodiment

Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some but not all embodiments of the invention are shown. In fact, the present invention may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy the applicable legal requirements. . Like reference numerals refer to like elements.

1 is a schematic block diagram of a mobile endpoint 10, such as a mobile telephone, in accordance with an exemplary embodiment of the present invention. However, it should be understood that the mobile phone described and hereinafter described is merely illustrative of one type of action endpoint that would benefit from embodiments of the present invention and therefore should not be taken as limiting the scope of embodiments of the present invention . One embodiment of the action endpoint 10 is illustrated and will be described below for exemplary purposes, such as a portable digital assistant (PDA), pager, mobile computer, mobile television, gaming device, laptop Other types of action endpoints for computers, cameras, video recorders, GPS devices, and other types of voice and text communication systems can be readily utilized with embodiments of the present invention. Furthermore, embodiments of the invention may be readily utilized without a mobile device.

The systems and methods of embodiments of the present invention will be substantially described below and linked to a mobile communication application. However, it should be appreciated that the systems and methods of embodiments of the present invention can be used in conjunction with many different other applications, outside of the mobile communications industry and the mobile communications industry.

The mobile endpoint 10 includes an antenna 12 (or multiple antennas) that is operable to communicate with a transmitter 14 and a receiver 16. The mobile endpoint 10 further includes a controller 20 or other processing component that provides signals to and receives signals from the transmitter 16 respectively. The signals include information transmitted in accordance with the air interface standard of the applicable cell system, as well as user speech, receiving data and/or user generated data. In this regard, the mobile endpoint 10 is capable of operating in one or more air interface standards, communication protocols, module types, and access patterns. By way of illustration, the mobile endpoint 10 can operate in accordance with any of the first, second, third and/or fourth generation communication protocols or the like. For example, the mobile endpoint 10 can be based on second generation (2G) wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA), according to third generation (3G) wireless communication protocols, such as UMTS, CDMA2000, WCDMA and TD-SCDMA operate in accordance with fourth generation (4G) wireless communication protocols and/or the like.

It will be appreciated that the controller 20 includes circuitry to implement the functionality of the mobile endpoint 10. For example, controller 20 can include a digital signal processor device, a microprocessor device, a number of different analog to digital converters, digital to analog converters, and/or other support circuits. The control and signal processing functions of the mobile endpoint 10 are assigned between these devices based on their individual capabilities. Controller 20 may also include functionality to perform whirling encoding and interpolating messages and data prior to modulation and transmission. Controller 20 may additionally include an internal voice coder and may include an internal data modem. Moreover, controller 20 can include functionality to operate one or more software programs that can be stored in memory. For example, controller 20 can operate a connection program, such as a conventional web browser. The connection program can then allow the mobile endpoint 10 to transmit and receive web content, such as location-based content and/or other web page content, for example, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP). Or similar.

The mobile terminal 10 can also include a user interface including an output device such as a conventional earphone or speaker 24, a ringer 22, a microphone 26, a display 28, and a user input interface coupled to Controller 20. A user input interface that allows the mobile endpoint 10 to receive data, may include any of a number of devices that allow the mobile endpoint 10 to receive data, such as a keypad 30, a touch display (not shown), or other input device . In embodiments including keypad 30, keypad 30 may include conventional numerals (0-9) and associated buttons (#, *) and other buttons for operating action endpoint 10. Alternatively, keypad 30 can include a conventional QWERTY keypad configuration. The keypad 30 can also contain a number of different soft keys with associated functions. Additionally or alternatively, the mobile endpoint 10 can include an interface device such as a rocker or other user input interface. The action endpoint 10 further includes a battery 34, such as a vibrating battery package, for powering a number of different circuits that are required to operate the action endpoint 10, and optionally providing mechanical shock as a The detected output.

The action endpoint 10 can further include a User Identification Module (UIM) 38. UIM 38 is typically a memory device having a built-in processor. The UIM 38 may include, for example, a Subscriber Identity Module (SIM), a Universal Integrated Circuit Card (UICC), a Universal Subscriber Identity Module (USIM), a Removable User Identification Module (R-UIM), etc. . UIM 38 typically stores information elements related to an action subscriber. In addition to the UIM 38, the action endpoint 10 can be equipped with memory. For example, the mobile endpoint 10 can include a volatile memory 40, such as a volatile random access memory (RAM), that includes a pass-through area for temporary storage of data. The mobile endpoint 10 may also include other non-volatile memory 42, which may be embedded and/or may be removable. The non-volatile memory 42 may additionally or additionally comprise an EEPROM, flash memory or the like, such as that available from SanDisk Corporation of Sunnyvale, California or Lexar Media Inc. of Fremont, California. The memory can store any of a plurality of segments of information and data used by the mobile endpoint 10 to implement the functionality of the mobile endpoint 10. For example, the memory can include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that uniquely identifies the mobile endpoint 10.

2 is a schematic block diagram of a wireless communication system in accordance with an exemplary embodiment of the present invention. Referring now to Figure 2, an illustration of a system that would benefit from one embodiment of the present invention is provided. As shown, one or more of the mobile endpoints 10 can each include an antenna 12 (or multiple antennas) for transmitting signals to or receiving signals from a base station or base station (BS) 44. . Base station 44 can be part of one or more cells or mobile networks, each of which contains elements required to operate the network, such as a mobile switching center (MSC) 46. Operationally, when the mobile endpoint 10 is making a call and receiving a call, the MSC 46 can route the call to or from the mobile endpoint 10. When the mobile endpoint 10 is involved in a call, the MSC 46 may also provide a connection to the ground trunk. In addition, the MSC 46 can control the feeding of messages to and from the mobile endpoint 10, and can also control the feeding of messages from the endpoint 10 to a messaging center and vice versa. It should be noted that although the MSC 46 is shown in the system of Figure 2, the MSC 46 is merely an exemplary network device, and embodiments of the present invention are not limited to use in a network using an MSC.

The MSC 46 can be coupled to a data network, such as a local area network (LAN), a public area network (MAN), and/or a wide area network (WAN). The MSC 46 can be directly coupled to the data network. In one embodiment, however, MSC 46 is coupled to a gateway device (GTW) 48, and GTW 48 is coupled to a WAN, such as Internet 50. In turn, devices such as processing elements (e.g., personal computers, server computers, or the like) can be coupled to the mobile endpoint 10 via the Internet 50. For example, a ㄉ processing element as described below may include one or more processing elements associated with a computing system 52 (two shown in FIG. 2), an original server 54 (one shown in FIG. 2) or Similarly, as described below.

The BS 44 may also be coupled to a messaging GPRS (General Packet Radio Service) Support Node (SGSN) 56. As is known to those skilled in the art, SGSN 56 is generally capable of performing functions similar to the packet switching service to MSC 46. The SGSN 56, like the MSC 46, can be coupled to a data network, such as the Internet 50. The SGSN 56 can be directly coupled to the data network. In a more exemplary embodiment, however, SGSN 56 is coupled to a packet switching core network, such as a GPRS core network 58. The packet switched core network is then coupled to other GTWs 48, such as a GTW GPRS Support Node (GGSN) 60, which is coupled to the Internet 50. In addition to the GGSN 60, the packet switching core network can also be coupled to the GTW 48. Also, the GGSN 60 can be coupled to a messaging center. In this regard, GGSN 60 and SGSN 56, like MSC 46, are capable of controlling the feeding of messages such as MMS messages. The GGSN 60 and SGSN 56 are also capable of controlling the messaging of the mobile endpoint 10 to the messaging center and feeding the message from the messaging center to the mobile endpoint 10.

In addition, by coupling the SGSN 56 to the GPRS core network 58 and the GGSN 60, devices such as a computing system 52 and/or the original server 54 can be coupled to the mobile endpoint 10 via the Internet 50, the SGSN 56 and the GGSN 60. In this regard, devices such as computing system 52 and/or original server 54 can communicate with mobile endpoint 10 across SGSN 56, GPRS core network 58, and GGSN 60. By directly or indirectly connecting the mobile endpoint 10 and other devices (e.g., computing system 52, original server 54, etc.) to the Internet 50, the mobile endpoint 10 can communicate with other devices and with each other, such as according to hypertext transfer. Agreement (HTTP) and/or the like to thereby perform many different functions of the action endpoint 10.

While not every component of every possible mobile network is shown and described herein, it should be appreciated that the mobile endpoint 10 can be coupled via BS 44 to any of a number of different networks. In this regard, the network can be based on many first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G e-mail, 3.9G, fourth-generation (4G) mobile communication protocols. And/or any similar or more to support communication. For example, one or more networks can support communication according to 2G wireless protocols IS-136 (TDMA), GSM and IS-95 (CDMA). For example, one or more networks can support communications based on 2.5G wireless protocol GPRS, Enhanced Data GSM Environment (EDGE) or the like. Furthermore, for example, one or more networks can be based on 3G wireless protocols. Support communications, such as a Universal Mobile Telephone System (UMTS) network, which uses wideband coded multi-directional proximity (WCDMA) radio access technology. Some narrowband AMPS (NAMPS), and TACS, networks are also available from the present invention. Embodiments benefit from the same dual-mode or higher-mode mobile stations (eg, digital/analog or TDMA/CDMA/analog phones).

The mobile endpoint 10 can be further coupled to one or more wireless access points (APs) 62. The AP 62 may include an access point configured to communicate with the mobile endpoint 10, such as, for example, the following techniques, radio frequency (RF), Bluetooth (BT), infrared (IrDA), or any of a number of different wireless networking technologies. , which includes wireless LAN (WLAN) technology, such as IEEE 802.11 (eg, 802.11a, 802.11b, 802.11g, 802.11n, etc.), WiMAX technology, such as IEEE 802.16, Ultra Wideband (UWB) technology, such as IEEE 802.15 and/or the like By. The AP 62 can be coupled to the Internet 50. As with MSC 46, AP 62 can be directly coupled to Internet 50. In one embodiment, however, AP 62 is coupled to Internet 50 indirectly via a GTW 48. Moreover, in an embodiment, BS 44 can be considered as other APs 62. As will be appreciated, by directly or indirectly connecting the mobile endpoint 10 and computing system 52, the original server 54, and/or any of a number of other devices to the Internet 50, the mobile endpoints 10 can communicate with each other, Communication with the computing system is thereby performed to perform many different functions of the action endpoint 10, such as to transfer material, content or the like to the computing system 52, and/or to receive content, material or the like from the computing system 52. As used herein, the words "material", "content", "information" and the like are used interchangeably to refer to the information that can be transmitted, received, and/or stored. As such, the use of any of these words should not be used to limit the spirit and scope of the embodiments of the invention.

Although not shown in FIG. 2, in addition to or in lieu of coupling the mobile endpoint 10 to the computing system 52 across the Internet 50, the mobile endpoint 10 and computing system 52 can be coupled to one another and communicated according to, for example, the following, RF, BT, IrDA or any of a number of different wired or wireless communication technologies including LAN, WLAN, WiMAX, UWB technology and/or the like. One or more of computing systems 52 may additionally or otherwise include a removable memory capable of storing content that may thereafter be transferred to mobile endpoint 10. Moreover, the mobile endpoint 10 can be coupled to one or more electronic devices, such as printers, digital projectors, and/or other multimedia capture, production and/or storage devices (eg, other endpoints). As with computing system 52, mobile endpoint 10 is configurable to communicate with the portable electronic device, including USB according to any of technologies such as RF, BT, IrDA or many different wired or wireless communication technologies, including USB , LAN, WLAN, WiMAX, UWB technology and/or the like.

In an exemplary embodiment, the data can be communicated between the client device such as a mobile endpoint of the mobile endpoint 10 of FIG. 1 and the server of the second graph system on the system of FIG. Or between any client device that communicates with a server or network device. Thus, it should be understood that the system of Figure 2 is not required for communication between the server and the client device, but Figure 2 is only provided for demonstration purposes. Any wired or wireless connection between a client device and a server is considered.

Figure 3 illustrates a block diagram of a system for providing intelligent synchronization in accordance with an exemplary embodiment of the present invention. The system of Figure 3 will be described in conjunction with the action endpoint 10 of Figure 1 for purposes of demonstration. However, it should be noted that the system of Figure 3 can also be used in conjunction with many different other devices, both mobile and fixed, and thus, embodiments of the present invention should not be limited to action endpoints 10 such as Figure 1. Application on the device. It should also be noted that while FIG. 3 illustrates an example of a configuration of a system for providing intelligent synchronization, many other configurations may be used to implement embodiments of the present invention.

Referring now to FIG. 3, the system includes a client device 70 that communicates with a synchronization server 72 over a carrier network 74. Carrier network 74 can be similar to the network of the system described in connection with FIG. As shown in FIG. 3, the synchronization server 72 can communicate with one or more devices of a local network 76, which can be, for example, a corporate network. The local network 76 can include an email server 78, a verification server 80, and one or more content servers 82. The content server 82 can include, for example, a switching server, a domino server, an Internet Information Access Protocol (IMAP) server, and the like. In an exemplary embodiment, firewall 84 may be configured in a communication chain between synchronization server 72 and carrier network 74. In addition, wired or wireless communication may be established between the elements of Figure 3, and these communications may or may not use an encryption mechanism.

It should also be noted that communication between the synchronization server 72 and the local network 76 can be direct or indirect. In this regard, Figure 4 shows a further configuration in which a synchronization server 72' is in indirect communication with a local network 76'. Thus, Figure 4 illustrates a block diagram of another system for providing intelligent synchronization in accordance with an exemplary embodiment of the present invention. For example, as shown in Figure 4, the device of local network 76' can communicate with a monitor device 86. The device of the local network 76' may include an email server 78', a verification server 80', and one or more content servers 82', each of which may be similar to the email server of FIG. 78. Verify that the counterparts of server 80 and content server 82 are configured in addition to communicating with monitoring device 86 rather than directly communicating with synchronization server 72. The monitor device 86 can be configured to monitor the devices of the local network 76 to learn that there is new information associated with the client device 70. For example, the monitor device 86 can monitor the email server 78' to learn the incoming email message, which is intended to be transmitted to the client device 70. In response to detecting new information (i.e., data for synchronization), the monitor device 86 may request or otherwise initiate communication of the new information through the synchronization server 72' to the client device 70. The system of Fig. 4 can also replace the firewall 84 of Fig. 3 with an outgoing firewall 88 and add an additional inbound firewall 90 that is disposed on the communication path between the synchronization server 72' and the monitor device 86. Thus, it can be appreciated that the embodiment of FIG. 3 corresponds to a scheme in which the synchronization server 72 is particularly associated with the local network 76', while the embodiment of FIG. 4 illustrates that the synchronization server 72' can be localized. The network 76 is associated with the solution alone or in combination with other local networks. Thus, the synchronization server 72' of Fig. 4 can be operated by a third party.

The synchronization server 72' can be quite similar to the synchronization server 72 of Figure 3, except that the synchronization server 72' can be configured to communicate with the monitor device 86 rather than directly with the device of the local network 76'. outer. Accordingly, the operation of one embodiment of the present invention will now be described with further reference to the synchronization server 72 of FIG. However, it should be understood that the synchronization server 72' of Figure 4 can operate in a manner substantially similar to the synchronization server 72. In accordance with an embodiment of the present invention, synchronization server 72 (and synchronization server 72') may include a synchronization component 92. In this regard, the synchronization component 92 can be any component or device implemented in hardware, software, or a combination of hardware and software that can be initiated by the client device 70 only in an exemplary embodiment. During a data period, Li has at least one of a first synchronization method and a second synchronization method to provide synchronization between the client device 70 and a server or local network 76 device. In other words, the synchronization component 92 is configured to manage communication of data between the client device 70 and the server or device of the local network 76 for a data period initiated by a user (e.g., a user of the client device 70). Do the purpose of data synchronization. In an exemplary embodiment, synchronization component 92 can be implemented as an executable application configured to provide at least conventional synchronization, and so-called "fast push" synchronization, which will be described in more detail below. Describe it. As such, the synchronization component 92, which is an executable application, can operate under the control of the processing elements of the synchronization server 72. The processing elements can execute instructions related to the executable application, which are stored on the memory of the synchronization server 72 or can be otherwise accessed to the processing elements of the synchronization server 72.

Client device 70 may be the mobile endpoint 10 of FIG. 1 or any other client device having at least one processing element capable of executing instructions in accordance with embodiments of the present invention. In an exemplary embodiment, client device 70 may include a client synchronization component 94. In this regard, customer synchronization component 94 can be any component or device implemented in hardware, software, or a combination of hardware and software that can operate in accordance with embodiments of the present invention, as described in greater detail below. The client synchronization component 94 can be configured to receive a message in response to select a plurality of synchronization methods based on whether the client device includes new data for communication via the synchronization component 92 that is independent of receipt of the message. One of, for example, at least a first synchronization method or a second synchronization method. In an exemplary embodiment, the message may be received from the synchronization component 92 of the synchronization server 72. The message can also be received from any other device, such as email servers 78 and 78', if desired. In other words, in an exemplary embodiment, the client synchronization component 94 can be configured to determine how (and possibly when) the synchronization with the synchronization server 72 is made, considering whether the client device 70 has a change ( For example, the new data is to be communicated to a device or a server of the local network 76 via the synchronization server 72. As a different approach, synchronization may be performed by, for example, an email server 78 or other local network 76 device.

In this description, a description will be given of the communication between the client device 70 and the synchronization server 72. However, it will be appreciated that these communications may actually occur between the synchronization component 92 and the client synchronization component 94, which is related to the synchronization associated with the synchronization of the synchronization component 92 and the client synchronization component 94. . Additionally, it should be understood that communication between the synchronization component 92 and the client synchronization component 94 occurs through the carrier network 74, even though the carrier network 74 may not be specifically mentioned in this regard.

In an exemplary embodiment, client synchronization component 94 can be implemented as an executable application configured to select a synchronization method based on whether client device 70 has a change to communicate to synchronization server 72, As will be described in more detail below. As such, the client synchronization component 94, in an executable application, can be operated under the control of one of the client devices 70 (eg, controller 20 of FIG. 1), which is executable and executable. The associated instructions are stored on one of the memory of the client device 70 or otherwise accessible to the processing elements of the client device 70. The processing elements described herein can be implemented in a number of ways. For example, the processing element can be implemented as a processor, a common processor, a controller or many other processing devices or devices including integrated circuits such as, for example, an ASIC (Application Specific Integrated Circuit).

In an exemplary embodiment, communication between client device 70 and synchronization server 72 may be initiated by, for example, client device 70 as a synchronization period. In this regard, the client device 70 can be manually (eg, by deliberate user actions, such as pressing a button or selecting an icon) or automatically (eg, in response to receiving a notification of new material or in a prior The time of the definition or schedule is to start the synchronization period. The initiation of the synchronization period may include the login of the client device 70 on the synchronization server 72. As such, the initiation may include a communication of a secure negotiation packet. The security negotiation packet may include, for example, a user name and password associated with the user, a device ID, an expected encryption method, and/or a public key, which corresponds to the intended encryption method. In response to receipt of the secure negotiation packet, the synchronization server 72 can establish a connection with the client device 70.

After the connection is established, client device 70 can communicate further information to synchronization server 72 to verify the communication channel between client device 70 and synchronization server 72. Further information may include, for example, an identification tag that identifies the client device 70 and the authentication information. The verification information may include a device password (which is provided to the client device 70 by the synchronization server 72), a connection sequence number, and a random language. The device password can be used to uniquely identify the client device 70 to the synchronization server 72 while the connection sequence number can be bypassed to prevent replay attacks. The random language can be a value that is randomly generated with each communication such that if a subsequent communication includes a previously used random language, the subsequent communication can be identified as a replay attack. In response to the device password matching the expected device password on the synchronization server 72, the communication channel can be verified and, for example, the synchronization server 72 can store a record of the interface or port of the communication channel associated with the client device 70. Thus, when the synchronization server 72 receives an indication from the monitor device 86 or a server of a particular device or local network 76 indicating that there is data to synchronize with the client device 70, synchronization occurs. The server 72 can assist with the interface or port associated with the client device 70 and transmit a message indicating that the data for synchronization can be obtained. If desired, in an exemplary embodiment, the message may be required to be synchronized with one of the client devices 70. In other embodiments, the message may identify the type of synchronization required (eg, describing a first synchronization method or a second synchronization method). Additionally or alternatively, the message may include data to be synchronized or at least a portion of the data. A message can also be called a push message or a push notification.

In an exemplary embodiment, communication between client device 70 and synchronization server 72 may be protected by a secure method and/or include timing monitoring, for example, to prevent a firewall from being out of time. In this regard, FIG. 5A illustrates a block diagram of a client synchronization component 94 in accordance with an exemplary embodiment of the present invention. Figure 5B illustrates a block diagram of a synchronization element 92 in accordance with an exemplary embodiment of the present invention. As shown in FIG. 5A, the client synchronization component 94 can include a client encryption component 100 configured to provide communication between the client device 70 and the synchronization server 72 and a detection interval timer 106. Encryption service. As shown in FIG. 5B, the synchronization component 92 can include an encryption component 102 configured to provide encryption services related to communication between the synchronization server 72 and the client device 70 and a detection interval timer 107. .

In an exemplary embodiment, an RSA algorithm can be used to provide an RSA public key for use in encrypting signals communicated between client device 70 and synchronization server 72. Synchronization server 72 can decode the communication received from client device 70 using a corresponding RSA private key. Similarly, client device 70 may use the RSA public key to decode communications received from synchronization server 72, which has been encrypted by the RSA private key. As such, the client device encryption component 100 can store or otherwise access the RSA public key, and the encryption component 102 can store or otherwise access the RSA private key. The RSA public key may be initially stored on the client device 70 during loading of an application corresponding to the client synchronization component 94, which is the only key generated by the synchronization component 92 of the synchronization server 72. Corresponding to the RSA private key held by the synchronization server 72 in response to the loading of the application on the client device 70.

In an exemplary embodiment, in response to the establishment of a communication channel between the client device 70 and the synchronization server 72, the synchronization component 92 can transmit a detection message to the client device 70. The detection message can notify the client device 70 to detect the interval on which the synchronization server 72 will issue a further detection message to verify the continuity of the communication channel. In this regard, the detection interval timer 106 of the client device 70 and the detection interval timer 107 of the synchronization server 72 can each be reset in response to receiving the detection message or at the client device 70 or the synchronization servo. The communication received on the unit 72. Thus, for example, if the detection interval timer 106 expires (such as may occur when the communication channel has been lost for any reason), the client device 70 can be notified that the connection is lost, thus enabling the connection to be reestablished. Additionally or alternatively, if the detector interval timer 107 expires, the synchronization server 72 can drop the interface connection previously associated with the client device 70 (e.g., in response to an interface error). In an exemplary embodiment, the detection interval may be defined as a rate that satisfies the firewall to prevent the firewall from being timed out.

In an exemplary embodiment, at least a portion of the synchronization server 72 (e.g., synchronization component 92) can be configured to transmit a particular type of message to the client device 70 in response to receiving the indicated presence for use with the client device. 70 instructions for synchronizing new materials. For example, the synchronization component 92 can generate a first message (eg, a first type of message) associated with the first synchronization method, or a second message associated with the second synchronization method (eg, a second Type message). However, it should be noted that additional types of messages and synchronization methods can also be used. The client synchronization component 94 can be configured to interpret each of the first message, the second message, and/or any additional messages, such as associated with a corresponding (generally different) synchronization method, as described in more detail below. of. Thus, in response to receiving the first message, the client synchronization component 94 can determine whether there is new material on the client device 70 (independent of the first message and a content related to the first message) that has not been transmitted to the synchronization. Server 72. If new material is detected, client device 70 may ignore the message or otherwise reject the synchronization. However, the client device 70 may initiate a synchronization request by the second synchronization method immediately according to the user-defined setting or may initiate a synchronization at a later time by the second synchronization method. The requirements are based on manual or on a predetermined schedule. If no new material is detected on the client device 70, the client device 70 (e.g., client synchronization component 94) can process the first message, which in an exemplary embodiment can include data for synchronization. Thereby, synchronization with the synchronization server 72 is performed. In an exemplary embodiment, the synchronization server 72 can be configured to select whether to transmit the first or second message based on device performance associated with the client device 70. The performance of the client device 70 can be determined during the previous communication with the client device 70, or stored on the synchronization server 72 or can be synchronized by the network information associated with the client device 70 or based thereon. Server 72 is otherwise accessed.

As described above, instead of receiving the first message, the client device 70 can receive the second message from the synchronization server 72. Thus, in response to receiving the second message, the client synchronization component 94 can be configured to reject the synchronization and initiate a synchronization request in a second synchronization method, either immediately or at a later time. In an exemplary embodiment, client synchronization component 94 is configurable to query a user to initiate or reject initial synchronization via a selective synchronization method in response to receiving a second message. message.

It should be noted that in an exemplary embodiment, the term "new" material should be understood to refer to information relating to the synchronization server 72 being "new." Thus, in this context, the new word does not in any way mean that the data system was recently established on the client device 70. Rather, the data may be on the client device 70 for any length of time prior to being communicated to the synchronization server 72, and when used herein, the data may still be considered new. In addition, it should be appreciated that the new information may reflect changes in the existing data on the client device 70 since the last synchronization. In this regard, changes to new materials or existing materials should be understood as occurring prior to the receipt of the first message, thereby making such changes or new information relating to the first message and The content of a message is irrelevant.

As briefly described above, client device 70 can be configured to receive user input that defines when and/or how to initiate synchronization after rejecting processing a message (eg, a first message) in response to detecting on client device 70. change. In this regard, the user-defined settings can be used to define a timer period during which a communication period can be established, or a limit on the number of communication periods or synchronization operations can be defined, which can be performed for a given period of time. period. The client device 70 can also be configured to receive an input that defines whether synchronization via the second synchronization method is required immediately after rejecting the processing of the message (e.g., the first message), or whether synchronization is required at a later time. For example, a predetermined time can be set to provide a fixed delay before synchronization is required. Alternatively, a specific time can be set or other more complex rules can be used to define when synchronization is required. In other words, the client synchronization component 94 can be configured to receive a user input that defines rules for determining when to initiate communication with the synchronization component.

It should also be noted that although an email is specifically used as an example of data to be synchronized when describing the operation of one embodiment of the present invention, embodiments of the present invention are not limited to applications for email services. The embodiment of the email is also predicted to be used for synchronizing calendars, accessing data, synchronizing files, synchronizing databases, and the like.

Figure 6 is a control flow diagram illustrating a first synchronization method in accordance with an exemplary embodiment of the present invention. In this regard, FIG. 6 illustrates a control flow diagram of a message service in accordance with a fast push-in synchronization method in accordance with an exemplary embodiment of the present invention. In an exemplary embodiment, the fast push-in synchronization method of FIG. 6 may be the first synchronization method, although it should be understood that the first and second synchronization methods may each be any suitable synchronization method.

As shown in FIG. 6, a message 110 can be transmitted (e.g., from the synchronization server 72) during a communication period established to one of the client devices 70 to notify the client device 70 that the data is useful for synchronization. In an exemplary embodiment, the data used for synchronization may be data that has not been communicated to the client device 70. This information may have been received on the synchronization server 72 (or other device) and is intended for use by the client device 70. In response to receiving the message 110, the client device 70 can determine at operation 112 whether the client device 70 has any new data or changes that have not been transmitted to the synchronization server 72. In response to client device 70 having no changes or new material, client device 70 can receive and process message 110 at operation 114. In this regard, the message 110, which may be referred to as a fast push-in sync message (eg, the first message), may include data for synchronization. Therefore, the data for synchronization has been received and no new data is provided to the synchronization server 72, and the client device 70 can turn off communication with the synchronization server 72. In an exemplary embodiment, client device 70 can communicate a confirmation message 116 to synchronization server 72. Confirmation may not include information. Thus, as shown in FIG. 6, if the client device 70 does not have or otherwise has no new material, the synchronization can be accomplished by the client device 70 receiving only the message and making corresponding changes on the client device 70 without further The data content is communicated to the synchronization server 72.

Figure 7 is a control flow diagram illustrating a second synchronization method in accordance with an exemplary embodiment of the present invention. It should be understood that although FIG. 7 illustrates one example of a message service associated with the second synchronization method, other message services may be used in accordance with embodiments of the present invention, and virtually any other synchronization method may be used. . In addition, it should be noted that the messages exchanged in Figures 6 and 7 are merely examples of exchangeable messages and are not meant to limit the embodiments of the present invention.

As also shown in FIG. 7, a message 150 can be transmitted during the communication period established to one of the client devices 70 (e.g., from the synchronization server 72). The message 150 can notify the client device 70 that there is a presence of data to be synchronized (e.g., received on the synchronization server 72) and intended for the client device 70. In response to receiving the message 150, the client device 70 can determine at operation 152 whether the client device 70 has any new data or changes that have not been transmitted to the synchronization server 72. In response to client device 70 having changed or new material, client device 70 may refuse to further process message 150 at operation 154. Immediately or at a later time, as previously pre-defined by the user of the client device 70, the client device 70 can then communicate a synchronization request 156 to the synchronization server 72 to initiate the data for synchronization. Synchronization. In response to receiving the synchronization request 156, the synchronization server 72 and the client device 7070 can exchange new data and data for synchronization on 158. Thus, the data can be exchanged from the synchronization server 72 to the client device 70 and from the client device 70 to the synchronization server 72. Registration and/or verification information can also be exchanged at 160. Login information and other information exchanges to close synchronization events can also be exchanged on 162. Therefore, as shown in FIG. 7, if the client device 70 includes new data, synchronization can be initiated by the client device 70 through the exchange of multiple communication signals with the synchronization server 72.

Thus, as shown in Figures 6 and 7, at least two different synchronization methods can be provided by based on whether the client device 70 includes new material associated with the synchronization server 72, respectively. If no new data is detected on the client device 70, a fast push-in synchronization can be completed. However, if new data is detected, client device 70 can synchronize server 72 to initiate a synchronization event via a different synchronization method. The different types of synchronization methods can be predetermined, the timing of the user-initiated synchronization can be selected by the user, and/or the user can define the type of connection between the client device 70 and the synchronization server 72. For example, the user can choose to connect via LAN, GPRS, dial-up GSM, wireless card, etc. As such, the user can further customize the synchronization of the client device 70, thereby enhancing user experience when using the client device 70.

Figure 8 is a flow diagram that provides intelligent synchronization in accordance with an exemplary method in accordance with an exemplary embodiment of the present invention. In this regard, one embodiment of a method for providing intelligent synchronization in accordance with one of FIG. 8 can include during operation of a data element on a client device with a network element (eg, a synchronization element) during operation 200. Optional initial operation. At operation 210, a message can be received. In an exemplary embodiment, a message can be received from a network element. The message may indicate that the data to be synchronized (eg, on a network element) is available. In response to receiving the message, at least one portion of the plurality of synchronization methods can be selected at operation 220 based on whether the client device includes new data that has not been communicated to the network component. In an exemplary embodiment, the synchronization method can be selected from a first synchronization method or a second synchronization method. However, in other embodiments, the synchronization method can be selected from a plurality of synchronization methods.

As an alternative to the exemplary method described with reference to FIG. 8, another embodiment of a method for providing intelligent synchronization may include an optional initial operation of receiving a message on a network element, the message indicating Information for synchronization is available. The message can be received from a client device. The message may indicate that the data to be synchronized is available on the client device. In response to receiving the message, at least a portion of the synchronization method can be selected based on whether the network component includes new material that has not been communicated to the client device. In an exemplary embodiment, the synchronization method can be selected from a plurality of synchronization methods. It should also be appreciated that the network element can include, for example, a synchronization server, and an email server, a database, and/or the like.

Figure 9 is a flow diagram that provides intelligent synchronization in accordance with other exemplary methods in accordance with an exemplary embodiment of the present invention. In this regard, one embodiment of a method of providing intelligent synchronization in accordance with FIG. 9 can include receiving an indication at operation 300 indicating the presence of data intended for a client device and for synchronization. At operation 310, a message can be communicated indicating that the client device can obtain the data for synchronization. The method can further include receiving, at operation 320, an acknowledgment from the client device in response to the client device having no new material or one of the client device synchronization requests in response to the client device having new material. In an exemplary embodiment, an optional operation 330 can include performing an exchange of a plurality of communication signals with a client device in response to receiving a synchronization request.

Each of Figures 6, 7, 8 and 9 above represents a flow chart of a system, method and program product in accordance with an exemplary embodiment of the present invention. Each block or step of the flowchart will be understood, and the combination of blocks in the flowchart can be implemented by many different devices, such as hardware, firmware, and/or software, including one or more computer programs. instruction. For example, one or more of the above products may be implemented by computer program instructions. In this regard, computer program instructions for implementing the above-described programs can be stored by a memory device of an account management component and executed by a built-in processor in the account management component. As will be appreciated, any such computer program instructions can be loaded onto a computer or other planable device (ie, hardware) to create a machine such that instructions executed on a computer or other planable device are used to create Implement the functions described in the flowchart block or step. The computer program instructions can also be stored in a computer readable memory that can be directed to a computer or other programmable device to operate in a particular manner so that it can be stored in a computer readable memory. The instructions produce a manufactured item containing the instructions, which are now described in the flowchart block or step. Computer program instructions can also be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on a computer or other planable device to produce a computer-implemented program, such that it can be executed on a computer or other The instructions on the programmable device provide the steps to implement the functions described in the flowchart blocks or steps.

Accordingly, blocks or steps of a flowchart are a combination of methods for performing a particular function, a combination of steps for performing a particular function, and a program instruction method for performing a particular function. It will also be appreciated that one or more of the blocks or steps of the flowcharts and combinations of steps or steps in the flowcharts can be implemented by a particular purpose-based computer system that performs a particular function or step, or a particular use. A combination of hardware and computer instructions.

The above functions can be performed in many ways. For example, any suitable method for performing each of the above described functions can be used to carry out embodiments of the present invention. In one embodiment, all or a portion of the components of the present invention are typically operated under the control of a computer program product. The computer program product for carrying out the method of the embodiments of the present invention comprises a computer readable storage medium, such as a non-volatile storage medium, and a computer readable code portion, such as a series of computer instructions, implemented In a computer readable storage medium.

Numerous modifications and other embodiments of the inventions set forth herein will come to mind to those skilled in the <RTIgt; Therefore, it is understood that the embodiments of the invention are not limited to the specific embodiments disclosed and the modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are used herein, they are used in a generic and descriptive sense and not for the purpose of limitation.

10. . . Action endpoint

44. . . BS

12. . . antenna

46. . . MSC

14. . . Transmitter

48. . . GTW

16. . . receiver

50. . . Internet

20. . . Controller

52. . . Computing system

twenty two. . . Ringer

54. . . Original server

twenty four. . . horn

56. . . SGSN

26. . . microphone

58. . . GPRS

28. . . monitor

60. . . GGSN

30. . . Key board

62. . . AP

34. . . Capacitor

70. . . Client device

38. . . UIM

72. . . Synchronization server

40. . . Volatile memory

74. . . Carrier network

42. . . Non-volatile memory

76. . . Email server

80. . . Authentication server

80’. . . Authentication server

82. . . Content server

82’. . . Content server

84. . . Firewall

86. . . Monitor device

92. . . Synchronization component

88. . . External firewall

97. . . Customer synchronization component

90. . . Inward firewall

72’. . . Synchronization server

92,94. . . Customer synchronization component

76’. . . Local network

100,102. . . Customer encryption component

78’. . . Email server

106,107. . . Detection interval timer

1 is a schematic block diagram of a mobile terminal according to an exemplary embodiment of the present invention; FIG. 2 is a schematic block diagram of a wireless communication system according to an exemplary embodiment of the present invention; A block diagram of a system for providing intelligent synchronization in an exemplary embodiment of the present invention; and FIG. 4 illustrates a block diagram of another system for providing intelligent synchronization in accordance with an exemplary embodiment of the present invention; 5A is a block diagram of a client synchronization component in accordance with an exemplary embodiment of the present invention; FIG. 5B is a block diagram illustrating a synchronization component in accordance with an exemplary embodiment of the present invention; and FIG. 6 is a control Flowchart, which illustrates a first synchronization method in accordance with an exemplary embodiment of the present invention; FIG. 7 is a control flow diagram illustrating a second synchronization method in accordance with an exemplary embodiment of the present invention; A flow chart according to an exemplary method for providing intelligent synchronization according to an exemplary embodiment of the present invention; and FIG. 9 is a flow chart according to another embodiment according to the present invention Exemplary embodiment of an exemplary method for providing the intelligent synchronization.

70. . . Client device

72. . . Synchronization server

74. . . Carrier network

76. . . Email server

80. . . Authentication server

82. . . Content server

84. . . Firewall

92. . . Synchronization component

94. . . Customer synchronization component

Claims (13)

A method comprising: receiving, on a client device, a message indicating that data for synchronization is available via a particular synchronization method, the message including at least a portion of the data for synchronization; and the client device Determining whether the client device includes new data that has not been communicated with a network component; in the event that the client device includes new data that has not been communicated with the network component, the message is not received and is optionally provided at the client device Another method of synchronizing the exchange of data between the client device and the network component; and receiving the message if the client device does not include new data that has not been communicated with the network component, and without further transferring the data to Under the network element, a corresponding change is made in the client device. The method of claim 1, further comprising performing another synchronization method with the network element in response to determining that the client device includes the new material. The method of claim 1, further comprising initiating communication with the network element via the exchange of a plurality of communication signals with the network element to receive the new material. The method of claim 3, further comprising receiving a user input defining at least one rule for determining when to initiate communication of the origin with the network element. For example, in the method of claim 1, wherein receiving the message includes One of a first message associated with the particular synchronization method or a second message associated with the other synchronization method. The method of claim 5, further comprising: in response to receiving the second message, selecting the another synchronization method, or in response to receiving the first message, based on the Whether the client device includes the new material to select the particular synchronization method or one of the other synchronization methods. The method of claim 1, further comprising receiving a detection message at a predetermined interval to verify continuity of the data period. The method of claim 1, further comprising prompting a user to select whether to initiate synchronization through the another synchronization method. A computer program product embodied in a computer readable medium, comprising a computer program code for causing execution of a method as claimed in any one of claims 1 to 8. A device comprising a computer program code for causing execution of the method of any one of claims 1 to 8. A device comprising a processor and a memory including a computer code, the memory and the computer code configured to cause the device to perform at least the following actions: receiving an indication that the presence exists via a a specific method for scheduling data for a client device for synchronization; transmitting a message indicating that the data for synchronization is available to the client device, the message including at least a portion of the resource for synchronization Receiving confirmation from one of the client devices and accepting the message to respond to the client device having no new data, and in response to receiving the acceptance, providing for synchronization without receiving further data from the client device Transmitting the data to the client device; and in response to the client device having new data and not accepting the message, receiving a synchronization request from the client device to request that the client device be provided via another synchronization method Synchronization of data exchange between the devices. A method, comprising: receiving an indication that there is data for synchronization to a client device via a specialization method; causing a message to be transmitted to indicate that the data for synchronization is available to the client device The message includes at least a portion of the data for synchronization; receiving confirmation from one of the client devices and accepting the message to respond to the client device having no new material, and responding to receiving the acceptance such that no recipient is received from the client Providing the data for synchronization to the client device under the transfer of further information of the device; and receiving a synchronization request from the client device in response to the client device having new data and not accepting the message, requesting via the request Another synchronization method provides synchronization of the exchange of data between the client device and the device. As one of the methods of claim 12, which further includes execution and The plurality of communication signals of the client device are exchanged in response to receiving the synchronization request.