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

Abstract

An apparatus for providing intelligent synchronization includes a processing element configured to receive a message indicating that data for synchronization is available. The processing element may also be configured to select, in response to receipt of the message, a synchronization method from a plurality of synchronization methods based at least in part on whether the apparatus includes new data that has not been communicated to a synchronization element.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates generally to synchronization techniques, and more particularly to methods, apparatus and apparatus for providing intelligent synchronization between devices. Computer program product. L prior art 3 invention background

10 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. Scale and mobile technology & handle related consumer needs while providing more $activity and immediateness of information transfer. Current and future road technologies continue to assist in the ease of information transfer and the right

User's convenience. Among them, the time series of demand for increasing the ease of information transfer is about transmitting bribes. The service can be a type of specific media or communication application desired by the user, such as - music player, game console, e-book, short message, email, and the like. The service can also be an interactive application in which the user can communicate with the network device to perform a task or achieve a goal. Services may be provided from a network feeder or other network device or even from an endpoint such as, for example, a mobile phone, a mobile television, an action gaming system, a mobile computer, and the like. SUMMARY OF THE INVENTION The present invention provides a two-way communication in which the supply of services involves two-way communication between devices. The service synchronization between devices is full at periodic intervals, for example, in emails. In the case of service, an email feeds σ. It may be periodically synchronized with a remote device, such as a laptop or a mobile endpoint, either directly or by providing synchronized data. In some cases, a wired or wireless communication network may be used to initiate a communication between the synchronization server and the remote device, and the tween may be at a regular interval, for example, or in response to receipt of new data. Synchronization. During data synchronization, the synchronization server can revoke, such as a new email message to the remote device, and the remote device can pass any changes to the synchronized feeder, such as reading an email or ^ The intended e-mail is ready to be transmitted to a recipient. Alternatively, the remote device can change the communication to the email server or remote device, and the email server can exchange changes through the synchronization server. 1 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 traditional methods, efforts have been made to reduce the amount of data and the number of routes through the signal during data synchronization. However, such a mechanism cannot be performed in an authenticated manner and cannot be initiated on a remote device, which may be required in a particular situation. Therefore, it is desirable to provide a mechanism by which synchronization can be performed in a smart manner to avoid the above disadvantages. In this way, users of mobile terminals and other electronic devices can further customize the synchronization of their devices, thereby enhancing the user experience in using their devices. 6 200823681 Therefore, there are provided methods, devices and "program products" for providing intelligent synchronization between devices. In accordance with an exemplary embodiment of the present invention, in response to receiving a message that is attempted to be synchronized with a network element (eg, a server), the client device may first determine whether the client device changes and (4) has not been transmitted to The new information of the dragon is not related to the received message. In the exemplary embodiment, if the client device does not change, a first step method such as "fast push synchronization" can be performed.

Row. However, if the client device has a change, the client device can reject the synchronization and then initiate a second synchronization method. 10 15 20 Normative implementation of wealth, providing a way to provide intelligent synchronization. The financial law includes receiving - information. This message indicates that a read can be obtained for the same. The method may 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 that is not connected to the Internet. In his non-standard embodiment, a 4-program product is provided to provide intelligent synchronization. The computer program product includes at least a computer readable, storage body, and a computer readable code portion stored therein. Private month is optional: the code part contains the _ and the second executable part. The mouth is used to receive _ messages. This message can be used to synchronize the experience—+ to use. The executable portion of the younger one is used to respond to the method of synchronizing, at least in part, based on new data of whether the client device includes V and is not connected to the H network component. The same, he π New Zealand implementation of the towel, to provide a device to provide smart with the 7 200823681 5 • step by step. The device includes a processing component configured to receive a message. This message indicates that the data to be synchronized is available. The processing element 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 available for synchronization 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, whether the client device includes new data that has not been communicated to the network component The basis is 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 indicating the presence of data to be synchronized to a client device for synchronization, 15 to communicate a message indicating that the client device is available for synchronization The data, and to receive only one confirmation from the client device, in response to the client device not storing new material, or receiving a synchronization request from the client device in response to the client device having new material. 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. 8 200823681 5 The following is a description of the embodiments of the present invention in the general terms of the present invention. 1 is a schematic block diagram of a wireless communication system according to an exemplary embodiment of the present invention; FIG. 3 illustrates a wisdom for providing wisdom according to an exemplary embodiment of the present invention. Block diagram of a system for synchronizing; 10 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 an exemplary embodiment in accordance with the present invention. a block diagram of one of the client synchronization elements; FIG. 5B illustrates a block diagram of the synchronization element 15 according to an exemplary embodiment of the present invention; FIG. 6 is a control flow diagram illustrating an exemplary embodiment of the present invention The first synchronization method of the embodiment; FIG. 7 is a control flow chart illustrating the second synchronization method according to an exemplary embodiment of the present invention; FIG. 1 is an exemplary method for providing intelligent synchronization according to an exemplary embodiment of the present invention; and FIG. 9 is a flowchart according to another exemplary embodiment in accordance with the present invention. An exemplary method to provide intelligent synchronization. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The embodiments of the present invention will 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 the 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 telephones described hereinafter and are merely illustrative of one type of action endpoints that would benefit from embodiments of the present invention and therefore should not be taken as limiting embodiments of the present invention. The scope. 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 TV, game 15 device, knee Other types of action endpoints for desktop 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 terminal 1A includes an antenna 12 (or multiple antennas) operative 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 receiver 16 respectively. The signals include information sent in accordance with the air interface standard of the applicable cell system, as well as user voice, received data and/or user generated data. In this regard, the mobile endpoint 1 can operate with one or more air interface standards, protocol, module type and access type. By way of illustration, the mobile endpoint 1 can operate in accordance with any of the first, first 'third and/or fourth generation communication protocols or the like. For example, the mobile endpoint 10 can be based on second generation (2G) wireless protocols IS-136 (TDMA), GSM, and IS-95 (CDMA), according to third generation (3G) 10 wireless communication protocols, such as UMTS, CDMA2000. , WCDMA and TD-SCDMA, operating in accordance with fourth generation (4G) wireless communication protocols and/or the like. 15 20 It should be understood that the controller 20 includes the private path required to implement the functions of the mobile terminal. For example, controller 2A can include a digital signal processor device, a microprocessor 11 device, a number of different ratio-to-digital converters H, digits to 'converters, and/or other support circuits. The control and signal processing functions of the action endpoints are assigned between the wires according to their individual performance. Controlling the Pirates 20 can also include Wei Lai's revolving and interpolating messages and information before modulation and transmission. Control (4) can be included - (4) voice coding can be G 3 internal shell data machine. Furthermore, the controller can include 1 force = operation - a software program that can be stored in the memory. An example of a crying control = 20 (four) operation - a connection program, such as - a traditional web page cutting program, may allow the mobile terminal 1G to transmit and receive web pages, such as location-based content and/or other web page content, 11 200823681 It is for example based on a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP) or the like. The mobile terminal 10 can also include a user interface including a wheeled I, such as a conventional earphone or speaker 24, a ringer 22, a microphone 5 26, a display 28, and a user input interface. It is coupled to the 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 digital (〇_9) and associated 10 buttons (#, *) and other buttons for operating action endpoint 10. Alternatively, keypad 30 can include a conventional QWERTY keypad configuration. The keypad 3〇 can also contain many different softkeys with associated functions. Additionally or alternatively, the action endpoint 10 can include an interface device such as a rocker or other user input interface. The mobile endpoint 10 further includes a battery 34, such as a shock cell 15 cell package, for powering a number of different circuits that are required to operate the action endpoint 10, and optionally providing mechanical shock as A detectable output. The action endpoint 10 can further include a User Identification Module (UIM) 38. The UIM 38 is generally a memory device with 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), and the like. UIM 38 generally stores information elements related to an action subscriber. In addition to the UIM 38, the action endpoint 1 can be equipped with memory. For example, the mobile endpoint 10 can include volatile memory, such as volatilization 12 200823681 random access memory (RAM), which includes a pool 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 ticker 42 may additionally or additionally comprise an EEPROM, flash memory or the like, such as that available from SanDisk Corporation of Simnyvale, California or Lexar Medialnc. of Hemont, California. The memory can store any of the pieces 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 device identification, 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 will be derived 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 15 to a base station or base station (BS) 44 or for Receive signals. 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 1 is making a call and receiving a call, the msc 46 can route the call to or from the mobile endpoint 10. The MSC 46 may also provide a connection to the ground trunk when the action 20 endpoint is involved in a call. In addition, the MSC 46 can control the feeding of messages to and from the mobile terminal 10, and can also control the messaging of the mobile endpoints to a messaging center and vice versa. It should be noted that although the MSC 46 is shown in the system of FIG. 2, the MSC 46 is merely an exemplary network device, and the embodiment of the present invention 13 200823681 is 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, the MSC 46 is coupled to a gateway device (GTW) 48, and the GTW4_ is coupled to a WAN, such as the 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. For example, a processing element as described below may include one or more processing elements associated with a computing system 52 (two in Figure 2), the original server 54 (one shown in Figure 2). Or similar, as described below. The BS 44 can also be coupled to a messaging GPRS (General Packet Radio Service) Support Node (SGSN) 56. As is known to those skilled in the art, the SGSN 56 is generally capable of performing similar functions to the packet switching service of the 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 GTW 48, such as a GTW GPRS Support Node (GGSN), and the 20 GGSN 60 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 center of δίΐ. 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 6 (^aSGSN 56 is also capable of controlling the message of the mobile endpoint 10 to feed to the call center and to feed the message from the center of the transmission 14 200823681 to the action 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 1 via the Internet 50 'SGSN 56 and GGSN 60. . In this regard, devices such as computing system 52 and/or original server 54 can communicate with mobile endpoints 1 across SGSN 56, GPRS core network 58 and GGSN 60. By directly or indirectly connecting the mobile endpoint 1 and other devices (eg, the metering system 52, the original server 54, etc.) to the Internet 5, the mobile endpoint 1 can communicate with other devices and with each other, such as According to Hypertext Transfer Protocol 10 (HTTP) and/or the like, to perform many different functions of the action endpoint 1 . Although not every component of every possible mobile network is shown and described herein, it should be appreciated that the mobile endpoint 1 can be coupled via Bs 44 to one or more of many different networks. In this regard, the network can be based on many 15th generation GG), second generation (2G), 2.5G, 2.75G, third generation (3G e-mail ' 3.9G 'di four generation (4G) mobile communication protocol and / or any similar or more to support communication. For example, one or more networks can support communication according to 2G wireless communication protocols IS-136 (TDMA), GSM and IS-95 (CDMA). For example, one or more networks can support communications in accordance with 2.5G Wireless Protocol 20 GPRS, Enhanced Data GSM Environment (EDGE) or the like. Further, for example, one or more networks can be based on 3G wireless protocols. To support communications, such as a Universal Mobile Telephone System (UMTS) network, which uses 觅-frequency coded multi-directional proximity (WCDMA) radio access technology. Some narrow-band AMPS (NAMPS), and TACS, the network can also be used from Embodiment 15 of the Invention 200823681 Benefits, dual-mode or higher-mode mobile stations are also the same (eg, digital/analog or TDMA/CDMA/analog phones). The mobile endpoint 10 can be further coupled to one or more wireless access points ( AP) 62. The AP 62 may include a configuration to move the endpoint 1 according to techniques such as, for example, Communication access point, radio frequency (RF), Bluetooth (BT), infrared (irDA) or any of a number of different wireless network technologies, including 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. AP 62 may 10 be coupled to the Internet 50. The MSC 46, AP 62 may be directly coupled to the Internet 50. In one embodiment, however, the ap 62 is indirectly coupled to the Internet 50 via a GTW 48. Again, in an embodiment, the BS 44 may 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 perhaps any other device to the Internet 50, The mobile endpoints 1 may communicate with each other to communicate with the metering system to thereby perform many different functions of the mobile endpoints, such as to transfer material, content or the like to the computing system η, and/or from Computing system 52 receives content, materials or the like. When used herein, 1 ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, Limiting the spirit and scope of the embodiments of the present invention. Although not shown in FIG. 2, in addition to or instead of splicing the mobile terminal 1 to the computing system S2 across the Internet, the mobile terminal Point 1〇 and calculation 16 200823681

The system 52 can be coupled to one another and communicate according to, for example, the following, Rp, 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 the computing system % may additionally or otherwise include a removable memory that is capable of storing content that may thereafter be transferred to the mobile endpoint 10. Again, action

Endpoint 10 can be coupled to one or more electronic devices, such as printers, digital projectors, and/or other multimedia capture, generation and/or storage devices (e.g., other endpoints). As with computing system 52, mobile endpoint 10 is configurable to communicate with a portable electronic device's technology based on any of wired or wireless communication technologies such as, for example, RF, Βτ, (5) eight or many. It includes 1^ it, LAN, WLAN, WiMAX, UWB technology and/or the like. In an exemplary embodiment, the data may be communicated between the client devices such as the mobile endpoints of the mobile endpoint 1Q of FIG. 1 and the first, and the first server, on the system of FIG. Or between any client device that communicates with a feeder b or a 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 that Figure 2 is only provided for the remainder (4). The connection between the device and the server of any tree thief scale is taken into account. 20 block diagrams of a system for synchronizing data in accordance with an exemplary implementation of the present invention. The system of Figure 3 will be described for the purpose of the eight models (4) and the action gamma link of Figure 1. However, it is contemplated that the system of Figure 3 can also be used in conjunction with a number of different other devices, and therefore, embodiments of the present invention should not be limited to applications on the device of the mobile terminal of Figure 1. It should also be noted that while an example of a configuration for providing a smart synchronization system is illustrated in the figure, the embodiment of the present invention can be implemented in many other configurations. Referring now to Figure 3, the system includes a client device 7 that communicates with a synchronized servo state 72 over a carrier network 74. The carrier network π can be similar to the network of the system described in connection with Figure 2. As shown in Figure 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' an authentication 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 10 Internet Message 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 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, FIG. 4 shows an alternative configuration in which a synchronization server 72 is indirectly communicated 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 FIG. 4, the local network 76, the device can communicate with a monitor device 86. The local network 20 76' device 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 of Figure 3. Server 78, verifies the counterparts of server 80 and content server 82, except that they are configured to communicate with monitoring device 86 rather than directly with synchronization server 72. The monitor device 86 can be configured to monitor this 18 200823681 "I of the road 76 to know that there is a new electronically detectable e-mail device 78 that is related to, for example, the 毋 毋 毋 衣 , , In order to learn that the incoming < ίι, 4_ is sent to send a response _ to the new information (ie, used to synchronize the clothing 7 is ^ φ, with the material), the monitor device 86

. If the second request or another start through the synchronization 四 (4) ·, the new information to the communication of the two devices 70. The system of the fourth figure can also be - the outward fire lining replaces the firewall of the brother 3 map 84 and adds an additional direction Internal fire protection_, which is disposed on the communication path between the synchronization server 72 and the monitor device 86. It can be understood that the embodiment of FIG. 3 corresponds to a synchronization server 72 1 . Path 76, a related solution, while the embodiment of FIG. 4 illustrates a scheme in which the synchronization server 72 can be associated with the local network 76 alone or in combination with other local networks. Thus, it can be operated by a third party. Synchronization server 72' of Fig. 4. Synchronization server 72' can be quite similar to synchronization server 15 72 of Fig. 3, except that synchronization server 72 can be configured to communicate with monitor device 86. It is not directly in communication with the device of the local network 76'. Therefore, the operation of an embodiment of the present invention will now be described with further reference to the synchronization server 72 of Figure 3. However, it should be understood that the synchronization of Figure 4 Server 72, can be synchronized with the servo The server 72 operates in a similar manner. According to one embodiment of the present invention, the synchronization device 72 (and the synchronization server 72) can include a synchronization component 92. In this regard, the synchronization component 92 can be any component or device implemented in a combination of hardware, software or hardware and software, which can be initiated by the client device 70 in an exemplary embodiment. One of the at least one first synchronization method and one second synchronization method 19 200823681 provides synchronization between the client device 70 and a server or local network 76. In other words, the synchronization component 92 The communication configured to manage the data between the client device 70 and the server or device of the local network 76 is used for the purpose of synchronizing 5 data during the data period initiated by a user (e.g., the user of the client device 70). In an exemplary embodiment, the 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 In more detail To describe. Thus, the synchronization component of the type that is an executable application can operate under the control of the processing elements of the synchronization server 72. The processing component 1 can execute instructions related to the executable application, which are stored on the sync server 72 or can be otherwise accessed to the processing device of the synchronous servo cry. 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 an embodiment 15 of the present invention. In an exemplary embodiment, customer slot 70 may include a client synchronization component 94. In this regard, the client 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, 20 selecting 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 them, such as 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 20 200823681, such as email vessels 78 and 78, if desired. In other words, in the exemplary T embodiment, the client synchronization component 94 can be configured to do how (and the village & when) to synchronize with the synchronized navigation H 72, considering the customer installation b 7) Whether there is a change (for example, new data) is to be communicated to the device or the feeder of the local network 76 by synchronizing the server 72 5 . As an alternative, synchronization can be performed, for example, by email dragon (four) or other local network 76 devices. In the present description, there will be a description of the DfL between the client device 70 and the synchronized feeder 72Pa1. However, it should be understood that these communications may actually be performed between the synchronization component 92 and the client synchronization component 94, which are related to the synchronization of the specifically listed components of the synchronization component 92 and the client synchronization component 94. Communication. In addition, it should be understood that communication between the synchronization component 92 and the customer synchronization component 94 occurs through the carrier network %, even though the carrier network 74 may not be specifically mentioned in this regard. In an exemplary embodiment, the client synchronization component 94 can be implemented as an application for execution, configured to select a synchronization based on whether the client device 7 has a change to communicate to the synchronized server 72. The method, as will be described in more detail below. As such, the client synchronization component 94, in an executable application, can be operated under 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 components described herein can be implemented in a number of ways. For example, the processing element can be implemented as a J-processor, a common processor, a controller or many other processing devices or devices such as an ASIC (Application Specific Integrated Circuit). In an exemplary embodiment, the communication between the client device 70 and the synchronization server may be initiated by, for example, the client device 70 as a synchronization period of five. In this regard, the client device 70 can be manually (eg, by deliberate user actions, such as pressing a button or a selection-illustration) or automatically (eg, in response to receiving a notification of new material or in a pre- The time of the definition or schedule) 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. In this way, the start can include a conversation about the packet. The security negotiation packet may contain, 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 the receipt of the security negotiation packet, the synchronization server 72 can establish a connection with the client device 7. After the connection is made, the client device 7G can communicate the information to the synchronization server 72 to verify the communication channel between the client device 7 and the synchronized feeder. The further information may include, for example, an _ identification tag for identifying the client device 70 and the authentication information. The verification message may include a device password (which is provided to the client device 7 by the synchronization server 72), a serial number and a random word. The skirt password can be used to uniquely identify the client device 70 to the synchronization server 72 while facilitating the connection sequence number to prevent replay attacks. The random language can be a value that is randomly generated with each U communication, such that if a subsequent communication includes a previously used lingo, then subsequent communications can be identified as a replay attack. In response to the same: 22 200823681 The device password on the device 72 matches an expected device password, the communication channel can be verified and, for example, the synchronization server 72 can store the interface or port record of the communication channel associated with the client device. Therefore, when the synchronization server 72 receives an indication, it is from the monitor device % or a specific device or a local network % server indicating that there is data for synchronization with the client device 70. The synchronization server 72 can interface with the interface associated with the client device 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 a pattern of synchronization requirements 10 (e.g., describing a first synchronization method or a second synchronization method). Additionally or alternatively, the message may include information to be synchronized or at least part of the data. A message can also be called a push message or a push notification. In an exemplary embodiment, communication between the client device 7A and the synchronization servo device 72 can be protected by a secure method and/or include timing monitoring, for example, to prevent a firewall from overtime. In this regard, Figure 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 1 that is configured to provide correlation with the client device 70 and the synchronization server 72 and a detection interval timer 106. Encryption service for communication between the two. The 'synchronization element 92' as shown in FIG. 5B may include an encryption element 102 configured to provide encryption associated with communication between the synchronization server and the client device 7 and a detection interval timer 107. service. 23 200823681 In an exemplary embodiment, an RSA algorithm can be used to provide an RSA public key for use in encrypting the client device 7 and synchronizing the server for 72 communications. The synchronization server η can decode the communication received from the client device 7 using a pair of RSA private keys. Similarly, each household device can use the RSA common round to decode communications received from the synchronization server 72, which has been encrypted by the RSA private key. Thus, client device encryption component 100 can store or otherwise access the RSA public key, and encryption component 102 can store or otherwise access the RSA private key. The RSA common redundancy key may be initially stored on the client device 7 during application loading a guest 10 synchronization component 94, which is uniquely generated by the synchronization component 92 of the synchronization server 72. The key is to correspond 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 7 and the synchronization server 72, the synchronization component 92 can transmit a detection message to the client device 70. The detection message informs the client device 7 of the detection 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 7 and the detection interval timer 1〇7 of the synchronization server 72 can be reset every 20 times in response to receiving the detection message or at the client device 70. Or synchronize the communication received on server 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 re-established. Additionally or alternatively, if the detector interval timer 1〇7 expires, 24 200823681 the synchronized vessel 72 can release the interface connection previously associated with the customer device (4) (e.g., in response to an interface error). In an exemplary embodiment, the _ interval can be defined as - the rate of full hearing cuts is the time of the fire wall. In an exemplary embodiment, at least a portion of the synchronization server 5 72 (e.g., synchronization component 92) can be configured to transmit a _specific type of message to the client device 70 in response to receiving the indicated presence for use with the client. Set up 7 instructions for synchronizing new data. For example, synchronization component 92 can generate a first message (eg, a -type message) associated with the first synchronization method, or a second message associated with the second synchronization method (eg, a second Type 10 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 Synchronize the server 72. If new material is detected, client device 70 can ignore the message or otherwise reject the synchronization. However, the client device 70 may initiate a synchronization request by the second synchronization method or may initiate a second synchronization method at a later time depending on the user-defined setting. Synchronization requirements are based on manual or on a predetermined schedule. If no new material is detected on the client device 70, the client device 7 (e.g., client synchronization component 94) can process the first message, which in an exemplary embodiment can include synchronization The data is thereby synchronized with the synchronization server 72. In an exemplary embodiment of 25 200823681, the synchronization server 72 is configurable to select whether to transmit the first or second information 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 7 by being stored on the synchronization server 72 based on or based on the network information of the client device 70. It can be accessed by the synchronization servo 72 in other ways. As described above, instead of receiving the first message, the client device 7 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. on. 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 word "new" is used to refer to the information relating to the synchronization server 72 as "new." Thus, in this context, the term 'new word' does not mean that the data system was recently established on the client device 7 but that the data can be located on the client device 70 for any length of time before the data is communicated to the synchronization server 72. And when used here, this information can still be considered as new material. In addition, it should be understood that the new information can reflect the changes since the last synchronization of the existing data on the customer's Lori and . In particular, the Department said that 'new information or changes in existing information should be understood as occurring before the receipt of the first-party information, thereby making these changes or new information, and the total is also -", The message of Bao Xingdi is irrelevant to the content of the first message. As briefly described above, client device 70 can be configured to receive user input 26 200823681, which defines when and/or how to initiate synchronization in response to rejection of a message (eg, a first message) in response to client device 70. A change was detected. 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 the same 5-step operation can be defined. For the time period. The client device 70 can also be configured to receive an input that defines whether synchronization through 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 of 10 seconds 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 the e-mail is specifically used as an example of the material to be synchronized when describing the operation of one embodiment of the present invention, the embodiments of the present invention are not limited to the application of the e-mail service. The embodiment of the email is also predicted to be used for synchronizing the calendar, accessing the data, synchronizing the files, and synchronizing the negative database. 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, the first diagram 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 27 200823681 method . As shown in FIG. 6, a message 11 can be transmitted (e.g., from the synchronization server 72) to the client device to establish a useful overnight information to notify the client device 70 of the material that 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. 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 7 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 customer 10 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 (e.g., 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. Therefore, as shown in FIG. 6, if the client device 70 does not have or otherwise has no new data, then the synchronization can be completed by the client device 70 receiving only the message and making corresponding changes on the client device 7 without Further information is provided to the communication of the synchronization 20 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 28 200823681 synchronization may be used. Method. In addition, it should be noted that the messages exchanged in Figures 6 and 7 are merely examples of exchangeable messages and are not intended to limit the embodiments of the present invention. Also shown in Figure 7, a message 150 can be sent (e.g., from the synchronization server 72) during the communication (10) established to the client device 70. The message 5 I50 can inform 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. In response to receiving the message 15 客户, the client device 7 can determine at operation 152 whether the client device 70 has any new data or changes that have not been transmitted to the sync server 72. In response to the client device 7G having a change or new resource, the client device 70 may refuse to further process the message 15 at operation 154. Immediately or at a later time, as pre-defined by the user of the customer 70, the client device 7 can then communicate a synchronization request 156 to the synchronization server 72 to initiate synchronization. Synchronization of data. In response to receiving the synchronization request 156, the synchronized feeder 72 and the client device can exchange new data and synchronize (4) to 158. Such a material can be exchanged from the synchronization server 72 to the client device 7 and from the client device to the synchronous (four) server 72. Listening and / or verifying information is also exchanged. Login information and other information exchanges to close synchronization events can also be exchanged for escaping. Thus, as shown in Figure 7, if the client device 7 includes a new beta, 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 synchronized feed pirate 72, respectively. If it is not detected on the customer's %, 29 200823681 to the new material, you can complete a quick push synchronization. However, if a new data item 70 is detected, the synchronization server 72 can initiate a synchronization event through a different synchronization method. Different types of synchronization methods may be required. The user-initiated synchronization timing may be selected by the user, and / 5 or the user may define a 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. In this manner, the user can further customize the synchronization of the client device, thereby enhancing the user experience when using the client device 70. 10 Figure 8 is a flow chart providing intelligent sacredness in accordance with an exemplary method in accordance with an exemplary embodiment of the present invention. In this regard, one embodiment of the method for providing intelligent synchronization in accordance with one of FIG. 8 may include during operation of a data element on a client device with a network element (eg, the same v-component). Optional initial operation. At operation 15, an suffocation can be received. In an exemplary embodiment, the message may be received from a network element. The message indicates that the data to be synchronized is available (for example, on a network condition). In response to receiving the message, at least one of the plurality of synchronization methods may be selected at operation 220 based on whether the client device includes new data that has not been communicated to the network element. In an exemplary embodiment, the synchronization method can be selected from a first synchronization method or a second synchronization. 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 the method for synchronizing synchronization may include an optional initial reception of a message on a network component at 30 200823681 5 Operation, the message indicates that the data to be synchronized 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 type 10 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 for providing intelligent synchronization in accordance with FIG. 9 can include receiving an indication at operation 300 indicating the presence of data intended for synchronization to a client device 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 32p, 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. 20 Figures 6, 7, 8 and 9 above each represent 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 31 200823681 may be implemented by computer program instructions. In this regard, the monthly instruction to implement the above procedure 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 by J, any such computer program instructions can be loaded onto a computer or other programmable device (ie, hardware) to produce a machine such that instructions are executed on a computer or other planable device. Used to 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 used to guide a computer or other programmable device to operate in a specific manner so that the computer can read it. The instructions in the body produce a manufactured object that contains the instructions, which are now described in the block diagram or step. Computer program instructions can also be programmed 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 planable 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 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 flowcharts or blocks and combinations of steps or steps in the flowcharts can be implemented by a specific purpose hardware-based computer system that performs a particular function or step, or A combination of hardware and computer instructions. The above-mentioned merits can be implemented in many ways. For example, any suitable method for performing each of the above functions can be used to carry out the practice of the present invention 32 200823681. In the embodiment, all or a portion of the components of the present invention are generally operated under the control of a computer program product, and the computer program product for performing the embodiment of the present invention includes - computer readable storage The media, non-volatile storage media, and computer-readable code portions, such as one, are beta-electrical devices that are used in storage media that can be accessed by computers. Many modifications and other embodiments of the inventions set forth herein are contemplated by the skilled artisan, and the inventions that are associated therewith benefit from the above description and the guidance in the related drawings. 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 only and not for the purpose of limitation. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic block diagram of a mobile terminal 15 according to an exemplary embodiment of the present invention; FIG. 2 is a wireless communication system according to an exemplary embodiment of the present invention. FIG. 3 is a block diagram showing a system for providing intelligent synchronization according to an exemplary embodiment of the present invention; FIG. 4 is a diagram illustrating an exemplary embodiment of the present invention for providing Block diagram of other systems of intelligent synchronization; FIG. 5A illustrates a block diagram of a client synchronization component in accordance with an exemplary embodiment of the present invention; FIG. 5B illustrates synchronization of one of the exemplary embodiments of the present invention 33 200823681 Block diagram of components; FIG. 6 is a control flow diagram illustrating a first synchronization method in accordance with an exemplary embodiment of the present invention; ^ FIG. 7 is a control flow diagram illustrating an exemplary embodiment of the present invention A second synchronization method of the embodiment 5; a flowchart of an exemplary method for providing intelligent synchronization according to an exemplary embodiment of the present invention; 9 and a graph of a flow chart based exemplary method of synchronizing according to other intelligent accordance with one exemplary embodiment of the present invention to provide a ^. 10 [Main component symbol description] 10...Action endpoint 44---BS 12...Antenna 46--MSC 14...Transmitter 48 ...GTW 16...Receiver 50···Internet 20...Controller 52...Computation system 22...Vibrator 54...original server 24...remaining 56...SGSN 26...microphone 58...GPRS 28...display 60--GGSN 30...keypad 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 34 200823681 80...validation server 82...content server 84...firewall 92...synchronization element 94... Customer synchronization component 72'···synchronization server 76'··local network 78'···email server 80'···authentication server 82'···content server 86...monitor Device 88...Outbound firewall 90...Inward firewall 92,94···Customer synchronization component 100,102···Customer encryption component 106,107...detection interval timer

35

Claims (1)

200823681 X. Patent Application Range: 1. A method comprising: receiving, on a client device, a message indicating that data is available for synchronization; and in response to receiving the message, from a plurality of synchronization methods, At least a portion selects a synchronization method based on whether the client device includes new data that has not been communicated to a network element. 2. The method of claim 1, wherein the selecting the synchronization method comprises selecting one of a first synchronization method or a second synchronization method. 3. The method of claim 2, further comprising performing the first synchronization method with the network element to respond to the client device not including the new material. 4. The method of claim 2, further comprising performing the second synchronization method with the network element to respond to the client device including the new material. 5. The method of claim 1, wherein the method further comprises: in response to the client device not including the new material, accepting the message and making corresponding changes on the client device without further communicating the data content to the network element. 6. The method of claim 1, further comprising rejecting the message in response to the client device including the new material. 7. The method of claim 6, further comprising initiating communication with the network element to receive the new data by exchanging a plurality of communication signals with the network element. 36. The method of claim 7, further comprising receiving a user input defining at least one rule for determining when to initiate communication with the network element. 9. The method of claim 2, wherein receiving the message comprises receiving one of a first message associated with the first synchronization method or a second message associated with the second synchronization method. 10. The method of claim 9, further comprising selecting the second synchronization method to receive the second message, or selecting the first synchronization based on whether the client device includes the new data The method or one of the second synchronization methods responsive to receiving one of the first messages. 11. The method of claim 1, further comprising receiving a detection message at a predetermined interval to verify the continuity of the data period. 12. The method of claim 1, further comprising inquiring a user to select whether to initiate synchronization via the selection synchronization method. 13. A computer program product comprising at least one computer readable storage medium having a computer readable code portion stored therein, the computer readable code portion comprising: a first executable portion And for receiving a message on a client device, the indication is available for synchronizing the data; and a second executable portion for receiving the message in response to the plurality of synchronizations In the method, at least a part of the client device is selected based on the new information of the client device is a network component of the selected device. The second step-by-step method - the commander-synchronization method or a second-same method, such as the application for the patent garden, the third-executable part, A from the production (five), which further includes Synchronizing, and executing the first gate method with the remote network component to respond to the client device not including the new data. Γ:=范! The computer program product of item 14, the further step includes - the same as the oxification side, the _ (four) the network component to perform the first synchronization method, in response to the customer I include The new information. 17. If the computer program product of the 13th patent scope includes the executable part of the r-r, the singularity of the customer's device does not include a new material, and the customer's device is received. The corresponding change is made without further communicating the data content to the network element. 18. A computer program product as claimed in claim 13 further comprising - a third executable portion for rejecting the message in response to the new material. Including a computer program product of claim 18, which further includes a fourth part executable portion for initiating communication with the network element to transmit through the network element Exchange of communication signals: new information. 20. The computer program product of claim 19, wherein the step 1-5 comprises a fifth executable portion for receiving _ user input, wherein: 38 200823681 at least one rule to determine when to execute and The beginning of the communication of the network element. 21. The computer program product of claim 14, wherein the first executable portion includes an instruction to receive the message, comprising receiving a first message associated with the first synchronization method or The second synchronization method is related to one of the second messages. 22. The computer program product of claim 21, further comprising a third executable portion for selecting the second synchronization method in response to receiving the second message, or whether the client device includes The new data is used to select one of the first synchronization method or the second synchronization method in response to receiving the first message. 23. The computer program product of claim 13 further comprising a third executable portion for receiving a detection message at a predetermined interval to verify continuity of the data period. 24. The computer program product of claim 13 further comprising a third executable portion for inquiring a user to select whether to initiate synchronization via the selected synchronization method. 25. A device comprising a processing component configured to: receive a message indicating that data is available for synchronization; and in response to receiving the message, at least one of a plurality of synchronization methods A synchronization method is selected based in part on whether the devices include new data that has not been communicated to a network element. 26. The apparatus of claim 25, wherein the processing element is further configured to select a first synchronization method or a second synchronization method. 39 200823681 27. The apparatus of claim 26, wherein The processing element is further configured to perform the first synchronization method with the network element to respond that the client device does not include new material. 28. The device of claim 26, wherein the processing component is further configured to perform the second synchronization method with the network component to respond to the client device including the new material. 29. The apparatus of claim 25, wherein the processing component is further configured to accept the message and to make a corresponding change on the client device without further data in response to the client device not including the new data. Content communication to the network element. 30. The apparatus of claim 25, wherein the processing component is further configured to reject the message in response to the client device including the new material. 31. The device of claim 30, wherein the processing component is further configured to initiate communication with the network component to receive the new data by exchanging signals with the network component. 32. The device of claim 31, wherein the processing component is configured to receive a user input defining at least one rule for determining when to perform subsequent initiation of communication with the network component. 33. The device of claim 26, wherein the processing component is further configured to receive a first message associated with the first synchronization method or a second message associated with the second synchronization method . 34. The device of claim 33, wherein the processing component further 40 200823681 is configured to select the second synchronization method in response to receiving the second message, or whether the client device includes the new material Responding to receiving the first message to select one of the first synchronization method or the second synchronization method. 35. The device of claim 25, wherein the processing component is further configured to receive a detection message at a predetermined interval to verify continuity during the data period. 36. The device of claim 25, wherein the processing component is further configured to query a user to select whether to initiate synchronization via the selected synchronization method. 37. The device of claim 25, wherein the device is implemented as a row of endpoints. 38. An apparatus, comprising: means for receiving a message indicating that information for synchronizing is available; and for receiving the message in response, at least a portion of the client device includes not yet being communicated to Based on the new data of the network component, a device for selecting a synchronization method from among multiple synchronization methods is used. 39. The device of claim 38, wherein the means for selecting further comprises means for selecting a first synchronization method or a second synchronization method. 40. A device comprising a processing component configured to: receive an indication that there is information intended for synchronization with a client device; 41 200823681 communication a message indicating the client device Information for synchronizing is available; and receiving confirmation from one of the client devices to respond to the client device having no new data or synchronizing requests from one of the client devices to respond to the client device having new data. 41. The device of claim 40, wherein the processing component is further configured to perform an exchange of a plurality of communication signals with the client device to respond to the synchronization request. 42. A method, comprising: receiving an indication that there is data intended for synchronization to a client device; communicating a message indicating that the client device is available for synchronization; and receiving Confirmation from one of the client devices to respond to the client device having no new data or synchronizing requests from one of the client devices to respond to one of the client devices having new data. 43. The method of claim 42, wherein the method further comprises performing an exchange of the plurality of communication signals with the client device in response to receiving the synchronization request. 42