Pearson Education, Inc., 221 River Street, Hoboken, New Jersey , (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.
If you are looking for more details, kindly visit our website.
This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.
To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:
For inquiries and questions, we collect the inquiry or question, together with name, contact details ( address, number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an . We use this information to address the inquiry and respond to the question.
For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), address, number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.
Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.
Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.
If you have elected to receive newsletters or promotional mailings and special offers but want to unsubscribe, simply .
On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an . Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.
We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via or in accordance with the users' wishes when a user submits their information through our Contact Us form.
Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.
Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.
This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.
This site currently does not respond to Do Not Track signals.
Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.
This site is not directed to children under the age of 13.
Pearson may send or direct marketing communications to users, provided that
Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.
If a user's personally identifiable information changes (such as your postal address or address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at and we will process the deletion of a user's account.
Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.
Pearson does not rent or sell personal information in exchange for any payment of money.
While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may a request for no sale of their personal information to .
California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.
Pearson may disclose personal information, as follows:
This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.
Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.
We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.
For more information, please visit California Triangle.
(or, The Design of Exchange Direct Push in Exchange SP2)
Background
I bought my first cell in the summer of – the venerable Nokia . With the attendant giddy excitement of a new consumer electronics purchase, I started adding names and numbers to the addressbook on the . This bubble was to burst when I would arrive at work to realize that the contacts and appointments I’d spent the last few years entering into Outlook were isolated from those on the . There may have been custom solutions to keeping the two synchronized, but a cursory search on Nokia’s site did not yield anything obvious – certainly, nothing out-of-the-box existed at that time for my setup.
Fine, I thought. For now, I’ll resign myself to manually entering each contact twice – once on the , and once in Outlook. But this sucks.
And so it was until the Nokia came out. I bought it on literally the first day that Seattle’s AT&T Wireless store stocked them, as this was the first offered by Nokia that met my specifications:
Note that between the and the , I also owned the (yes, the Charlie’s Angels ). Consider what this means : Upon buying the , I had to manually copy every contact from the to the – if the store personnel had the capacity to use custom tools to do this for me, they didn’t offer. And this process had to be repeated when I moved from the to the . Finally, all the while, I ran the risk of losing my current and, with it, all of my carefully-entered contacts. Best case, this meant an incredibly laborious, error-prone, eye-crossing two hours spent manually entering contacts into my replacement – and only if I happened to be diligent about doubly entering every contact into both Outlook and the . Worst case, this meant some lost contacts and the all-too-familiar emails whose contents read something like, "I’ve lost my and your numbers; please send me your contact information!"
If the double-entry of contacts in Outlook and the sucked, this really sucked.
With the in hand, I was ready to trounce several of these issues:
I installed the synchronization software onto my laptop and connected the using infrared. Problems surfaced immediately upon completing the first synchronization, however:
Ok; so, annoying, but not the end of the world. Some of this can be attributed to ambiguities in mapping from one set of schema for contact and calendar items to another, to limited storage on the device, and perhaps to early versions of the software (though I was using version 4). I lived with this for about a year, burned through two ’s, upgraded to the Nokia , and lived with that and a similar synchronization experience for about another year.
During that time, things were manageable: the upgrades I mentioned were fairly painless because my Exchange account contained the authoritative copies of the data, and, with each new , I just pulled down all the data by way of Outlook at the first synchronization. However, it was still less than ideal: upon modifying a contact or an appointment on my calendar, I had to remember to align the infrared ports of my and laptop (I tried repeatedly and unsuccessfully to find a USB cable for connecting the two), kick off the synchronization software, and wait for it to complete. Making this a part of my daily routine was just tedious.
Enter the Motorola MPx200. This was the first offered by my service provider that ran a Windows Mobile operating system and was of an appropriately small form factor . The significance of the running a Windows Mobile operating system is that the would be running ActiveSync, which would provide high-fidelity synchronization of the , calendar appointments, and contacts in my Exchange mailbox . This would be supported both over-the-air with a GPRS connection and via USB/infrared using the desktop ActiveSync software that was provided along with the .
A further nicety of the MPx200 was the cradle and the single power/data USB connector it used – this meant that I could cradle the on my desk upon arriving to work, let it charge and sync all day, and pluck it from the cradle upon heading home, fully charged and synchronized .
The Design of AUTD
So, things are looking pretty good now (our story began in the summer of ; it is now the fall of ). What’s the problem, then? Well, the device synchronizes itself on a schedule, the most frequent setting of which is every five minutes. I’ve always interpreted the setting "How often would you like to sync?" as "By how much would you like to be out of date?" This meant that I may well pluck the device from its cradle before the next scheduled sync has occurred and miss some updates. Further, scheduled syncs over the air are fairly costly: most folders don’t contain changes. Finally, these unnecessary syncs cost power and adversely affect the lifetime of the battery of the device.
Yes, we offered an always up-to-date (AUTD) solution based on text messaging at that time, but I wasn’t happy with what was required in terms of provisioning and the server-side enforcement of latency so as to mitigate the impact of AUTDv1 on server performance.
What to do.
Around this time, we had begun looking into what it would take to offer an up-to-date mobile solution ("AUTD," from here on) that competed with the likes of RIM, Good, et al. I liked the up-to-date nature of their solutions but had not personally adopted them for reasons of device choice (again with the form factor), setup costs (in terms of money, deployment overhead, and operational overhead), or both. Being on the Exchange team, we’ve always got two sets of customers: the administrative staff and end users, and we wanted to build a solution that worked well for both. By enumerating our requirements and constraints, we essentially painted ourselves into a corner (happily, this corner contained the solution):
Within this definition of the problem, we came up with the following solution:
I’ve omitted some details here, but that is what is going on under the covers when you check the "Enable up-to-date notifications via HTTP" checkbox in Exchange System Manager in Exchange SP2, and it has the benefit of working on any mobile operator network that supports internet connectivity. Since the hopes of increased revenues of most mobile operators appear to be pinned on the possibility of selling users on data-enabled applications, this seemed like a safe enough bet.
Further, by using HTTP, we do not require enterprises to open any inbound ports beyond what they’ve already had to open in order to support Outlook Web Access (OWA), Outlook’s RPC-over-HTTP feature, and ActiveSync itself. Finally, the client-initiated nature of HTTP makes the device ultimately responsible for connectivity with Exchange, so upon receiving the request for change notifications from the device, Exchange will return a response immediately if any changes have occurred since the last synchronization. This is how we prevent "dropped" notifications. If the device ever drifts out of coverage, it will enter a re-try loop and connect as soon as it is able. The network resilience logic of the device can also be triggered on the timeout limit having elapsed before a response from the server is received.
So there we have it: an up-to-date mobile solution that is friendly for administrators and users alike. Changes trickle into the in the same way that they do into Outlook on the desktop. In fact, updates appear on the before they do in Outlook and OWA!
Now then, if you’ve been paying attention, you’ve probably noticed that AUTD requires a persistent data connection twixt the device and Exchange, and you’ve got a few issues with this:
What the previous three points add up to is that AUTD is actually better for mobile operator networks and device battery life than the solution based on scheduled sync that is used by devices that mobile operators sell today. We’ve had a bit of difficulty in getting this point across to some mobile operators.
As you might guess, we’ve been running early versions of this in Exchange for a few months now. One of the more satisfying testaments to the utility of our AUTD solution is watching upper management bump into each other in the halls as they consult their devices for the that just arrived or for the location of the meeting for which they’re already ten minutes late.
Conclusion
To let out a little secret, I’m not actually all that interested in having up-to-date on my , though that aspect of it is a big favorite for our upper-management types around here. For me, having updates that I make to my calendar and contacts “just appear” on the without any special, conscious action on my part was the motivating idea behind all of this.
For more Timing Synchronization for Mobile Networksinformation, please contact us. We will provide professional answers.
- Sami Khoury