When the BlackBerry debuted in 1999, carrying one was a hallmark of powerful executives and savvy technophiles.Most executives that wears ID lanyards might have already own a Blackberry.
People who purchased one either needed or wanted constant access to e-mail, a calendar and a phone. The BlackBerry’s manufacturer, Research in Motion (RIM), reported only 25,000 subscribers in that first year. But since then, its popularity has skyrocketed.
 Image courtesy RIM |
In September 2005, RIM reported 3.65 million subscribers, and users describe being addicted to the devices. The BlackBerry has even brought new slang to the English language. There are words for flirting via BlackBerry (blirting), repetitive motion injuries from too much BlackBerry use (BlackBerry thumb) and unwisely using one’s BlackBerry while intoxicated (drunk-Berrying). While some people credit the BlackBerry with letting them get out of the office and spend time with friends and family, others accuse them of allowing work to infiltrate every moment of free time.
In this article, we’ll examine the “push” technology at the center of the device’s popularity, RIM’s former dispute with patent holder NTP Incorporated and its current dispute with Visto Corporation. We’ll also explore BlackBerry hardware and software.
“Push” Technology
RIM Revenue
Source: |
A PDA does a lot of the same things a BlackBerry does, and the PDA made its
debut several years before the BlackBerry. But until recently, the only way to make the information on most PDAs match the
information on a person’s computer was to automatically or manuallysync the PDA. This could be time-consuming and inconvenient. It could also lead to exactly the conflicts that having a PDA is supposed to prevent. For example, a manager might schedule a meeting on the PDA, not knowing that an assistant had just scheduled a meeting for the same time on a networked calendar.
A BlackBerry, on the other hand, does everything a PDA can do, and it syncs itself continually throughpush technology. BlackBerry Enterprise Server or Desktop Redirector software “pushes,” or redirects, new e-mail, calendar updates, documents and other data straight to the user over the Internet and the cell phone network.
First, the software senses that a new message has arrived or the data has changed. Then, it compresses, packages and redirects the information to the handheld unit. The server uses hypertext transfer protocol (HTTP) and transmission control protocol (TCP) to communicate with the handhelds. It also encrypts the data with triple data encryption standard (DES) or advanced encryption standard (AES).
 A person can send and receive messages and phone calls on a BlackBerry from virtually any location. |
The software determines the capabilities of the BlackBerry and lets people establish criteria for the information they want to have delivered. The criteria can include message type and size, specific senders and updates to specific programs or databases.
Once all of the parameters have been set, the software waits for updated content. When a new message or other data arrives, the software formats the information for transmission to and display on the BlackBerry. It packages e-mail messages into a kind of electronic envelope so the user can decide whether to open or retrieve the rest of the message.
| BlackBerry Devices in the United States70 percent of BlackBerry subscribers live in the United States |
The BlackBerry listens for new information and notifies the user when it arrives by vibrating, changing an icon on the screen or turning on a light. The BlackBerry does not poll the server to look for updates. It simply waits for the update to arrive and notifies the user when it does. With e-mail, a copy of each message also goes to the user’s inbox on the computer, but the e-mail client can mark the message as read once the user reads it on the BlackBerry.
People describe BlackBerry use as an addiction, and this is why. Not only do they give people constant access to their phones, they also provide continual updates to e-mail, calendars and other tools.
Lately, RIM had been dealing with issues of patent infringement.
The Patent Dispute
Patent law can be tricky, and the claims companies make in their patents can be hard to quantify. But here is the basic dilemma that RIM and the BlackBerry were facing — NTP Incorporated holds several patents for wireless e-mail technology. RIM’s push technology is similar to, but more complex than, the technology NTP has patented. NTP had accused RIM of patent infringement, and judges and juries agreed. The patent dispute and a delayed rollout of new BlackBerry models caused a slight slowdown in RIM’s rapid growth.
The dispute between NTP and RIM started in 2001, when NTP sued RIM. Courts have generally ruled in NTP’s favor, granting monetary settlements and injunctions against RIM. RIM, however, has appealed the rulings and had requested a review of NTP’s patents. The United States Patent and Trademark Office (USPTO) has overturned several of the patents in question.
 People compose e-mail on a BlackBerry using a QWERTY keyboard and typing with their thumbs. Unfortunately, the BlackBerry’s e-mail capabilities are the focus of a patent dispute. |
In November of 2005, a United States district judge ruled that a previous monetary settlement between the two companies was not enforceable. On January 23, 2006, the United States Supreme Court turned down RIM’s request to review the district court ruling. The big concern was that this decision would lead to an injunction prohibiting BlackBerry sales and service in the United States. The U.S. Department of Justice requested a 90-day stay for essential government employees in the event of an injunction. RIM suggested the possibility of a software work-around that would not infringe on NTP’s patents, and RIM and NTP began negotiations through a court-appointed mediator.
RIM and NTP have settled their dispute. The cost — $612.5 million. The result — NTP grants RIM a license to NTP’s patents. According to a press release issued by both companies on March 3, 2006, here’s the agreement:
“The licensing and settlement agreement relates to all patents owned and controlled by NTP and covers all of RIM’s products, services and technologies. NTP grants RIM an unfettered right to continue its business, including its BlackBerry® related business. The resolution permits RIM and its partners to sell RIM products and services completely free and clear of any claim by NTP, including any claims that NTP may have against wireless carriers, channel partners, suppliers or customers in relation to RIM products or services, (including BlackBerry Connect and Built-In technology), or in relation to third party products and services, to the extent they are used in connection with RIM products and services.”
Next, we’ll look at the BlackBerry’s hardware and software.
| Future Cases?Although now settled, the RIM/NTP dispute raises the question of why other companies that provide smart phones with push technology are not in court as well. Some of these companies have licenses from NTP to use patented technology. Others use technology that does not conflict with NTP’s patents. Regardless of whether an injunction eventually shuts down RIM’s business in the United States, more companies are likely to introduce PDAs and smart phones with push e-mail and data capabilities, until constant access to e-mail and an updated calendar is as common as a cellphone. |
I have been telling IT professionals for quite some time that I believe the best way to provide applications to users is through a terminal server. The terminal services make it possible to run applications on machines that never would have otherwise supported them. For instance, I frequently administer my servers by remotely controlling them from a PDA that’s running Windows CE. Normally, Windows CE would be incapable of running User Manager for Domains or any of the other administrative tools. However, because the applications are actually running on the server itself, my PDA makes an excellent administration tool.
Nonetheless, for all their good points the terminal services don’t do well in one area of IT administration. Until recently it has traditionally been a very poor solution for supporting remote users. Let’s look at reasons why the terminal services do not make the best remote admin tool and a way to overcome these limitations.
Limitations of the terminal services for remote users
The terminal services work by sending screen images to the user and by sending a user’s keystrokes and mouse motions back to the server. These transmissions have traditionally consumed much more bandwidth than a remote connection would support. I have personally witnessed users remotely accessing a terminal server over a modem, and the entire session could be best described as painfully slow.
Another reason why the terminal services have been traditionally bad for remote users is because of the way that the user has been forced to access the terminal services. Normally, if a user will be accessing the terminal services they will dial into a RAS server, authenticate into the network, and then begin a terminal session. Again, the concept of dialing in just isn’t conducive to a well-performing terminal session.
Everything changes with Windows Server 2003
Recently there have been two changes that make the terminal services better suited to remote operations. These include the widespread deployment of broadband connections, and the implementation of Windows Server 2003. Windows Server 2003’s version of the terminal services relies on the Remote Desktop Protocol (RDP). This is the same protocol used by Windows XP’s Remote Assistance feature. RDP is designed to be much faster than its predecessor. It also allows for greater color depth than was previously available and supports the transmission of sound.
Since broadband Internet access and the RDP make terminal service access more feasible for remote users, it might be tempting to give all of your remote users terminal server access. However, one big challenge that must be overcome is most companies have a limited supply of IP addresses.
NAT problems
Normally, when a company gets Internet access, the ISP will provide them with one IP address. Since each PC must have its own IP address, it has become common to assign each PC a bogus IP address. The one real IP address is assigned to the router or firewall that is physically connected to the Internet. This machine uses what’s known as a Network Address Translation (NAT) firewall. NAT allows you to create an entire network of bogus IP addresses. When someone needs to access the Internet, the request is sent to the NAT firewall and it makes the request to the Web site on behalf of the person. In doing so, the request appears to have come from the network’s one legitimate IP address. When the Web site replies to the request, the reply is sent to the NAT firewall. The NAT firewall receives the request and then forwards it to the appropriate bogus IP address on the private network.
When it comes to accessing the Terminal Services, NAT presents a couple of problems. One problem is that the terminal server does not have a legitimate IP address. Therefore, the server is not accessible to the outside world. Only PCs on the private, internal network are usually able to access such servers. The second challenge is NAT is configured to block all unauthorized traffic types. This includes terminal server traffic.
Port forwarding
Just because there are challenges involved in accessing the terminal services across a NAT firewall doesn’t mean doing so is impossible. You can access a terminal server externally by using something called port forwarding. The basic idea of port forwarding is that someone from the outside world would configure her terminal server client to connect to the terminal server. However, the connection must be made by entering your network’s one legitimate IP address. Remember that this IP address is assigned to your firewall / router rather than to the terminal server. The trick is to know that the terminal services use port number 3389. Therefore, when connecting, enter the network’s one legitimate IP address followed by a colon and the number 3389 (for example, 147.100.100.1:3389).
In addition, the NAT firewall must be configured to support port forwarding by telling NAT that any traffic coming in on port 3389 must be redirected to your terminal server. For this step you can enter the server’s private IP address. The actual port forwarding mapping procedure varies from firewall to firewall, but in general it simply involves entering the port number (3389) and the private IP address of the terminal server.
Simple registry tweak
The down side to using port forwarding is that you can only access one terminal server from the outside world. The reason is that you can only map a port number to one private IP address. Therefore, if port 3389 is mapped to one terminal server, then it can’t be mapped to a second terminal server. However, there is no reason why you can’t map port number 3390 to your second terminal server. The only trick is that you must configure the second server’s terminal services to listen on port number 3390 rather than 3389.