|Publication number||US7613453 B2|
|Application number||US 11/266,327|
|Publication date||Nov 3, 2009|
|Filing date||Nov 4, 2005|
|Priority date||Nov 4, 2005|
|Also published as||US8126446, US8688098, US20070105538, US20080288237, US20120149355|
|Publication number||11266327, 266327, US 7613453 B2, US 7613453B2, US-B2-7613453, US7613453 B2, US7613453B2|
|Inventors||Mahmud-UL Hassan, Nicholas Wilson|
|Original Assignee||Research In Motion Limited|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (9), Non-Patent Citations (1), Referenced by (2), Classifications (12), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application relates to mobile device emulators, and in particular, relates to third party mobile device emulators on which client software is running.
As mobile devices and mobile data devices become more complex, one option being introduced by device manufacturers is to include client software on the mobile device. Specifically, the mobile device manufacturer can create the hardware and some software for the mobile device to operate. However, a different software maker can provide specialized software, such as e-mail applications, calendar applications and other data or non-data functionality.
In operation, the mobile device provides a platform for running the client software, which, when integrated with the third party mobile device, provides an enhanced experience for the user.
A mobile communications device, such as a cellular telephone, is typically formed of software, firmware, and hardware adapted to provide communications services over a compatible wireless communications network. This process of forming the relationship between the mobile communications device and the service is known in the art as provisioning. Typically, a network operator provisions the mobile communications device via a subscription to a service contract. Thus, once the mobile communications device has been provisioned, the user of the mobile communications device is often referred to as a subscriber. In a voice and data network such as GSM, GPRS, CDMA, or various other third generation networks such as EDGE or UMTS, both voice and data services may be available to mobile communications devices. Such voice services include voice calling and SMS, and such data services include Internet browsing, email, and MMS.
The data is typically supplied from a personal computer and a connection between the personal computer and the mobile device is established to provision the device. On a third party mobile device, a client is typically provisioned from a desktop using desktop provisioning software. A third party enabler module can be useful when the party that manufactures the mobile device does not create the client software. The module allows communication between the desktop or personal computer and the third party mobile device.
When developing client software, the software maker often requires emulation of the third party mobile device on a personal computer in order to ensure that the software runs correctly before it is implemented on an actual third party mobile device. Third party mobile device manufacturers often create emulators for their products. However, due to the nature of the emulator, the third party manufacturers generally do not provide simulation of communication means such as serial ports, Bluetooth™ connections, IrDA connections or other interfaces typically used for provisioning.
The present system and method will be better understood with reference to the drawings in which:
The present system and method provides a way to provision a third party mobile device emulator without having to significantly re-write the provisioning code, nor requiring modification of the third party emulator.
Specifically, the present application provides for provisioning of an emulator using a file transfer protocol (FTP) transport and a proprietary protocol for communications. Further, a shared directory on the PC is used by both the desktop provisioning software and the emulator in order to ensure effective communication.
The present application therefore provides a method for provisioning a third party mobile device emulator from desktop provisioning software comprising the steps of; designating a common file space between the third party mobile device emulator and the desktop provisioning software; writing files to the common file space from one of the third party mobile device emulator and the desktop provisioning software; and reading the files from the other of the third party mobile device emulator and the desktop provisioning software.
The present application further provides a system for provisioning a third party mobile device emulator comprising: desktop provisioning software; the third party mobile device emulator; and a common file space accessible by both the desktop provisioning software and the third party mobile device emulator, wherein said third party mobile device emulator and said desktop provisioning software are adapted to write files to the common file space and read the files from the common file space written by the other of the third party mobile device emulator and the desktop provisioning software.
On a mobile data device, provisioning of the data device is required for various reasons. These can include providing software updates, providing private keys for secure e-mail transfer, bulk loading a calendar to match the users desktop calendar, among others. Typically this is done from a personal computer to the mobile device. When a client is incorporated onto a third party mobile device, the provisioning requires an additional enabler on the personal computer in order to ensure that communications can effectively occur between the mobile device and the personal computer to effectively provision the client software. Reference is now made to
As will be appreciated by those skilled in the art, mobile device 120 can be manufactured by a different entity than the party that created client software 124.
When a user wishes to provision client software 124 on mobile device 120, a connection is made between mobile device 120 and personal computer 100. Such connections are known in the art, and can include various serial connections such as a USB connection, short range wireless communications such as Bluetooth™ or IrDA, or a radio link communication through a wireless network.
In an exemplary situation, a user wishes to synchronize the calendar on mobile device 120 with a desktop calendar. In this case, desktop provisioning software 110 on personal computer 100 is used to retrieve the calendar information. The calendar information can either reside on personal computer 100 or on a separate computer if personal computer 100 has communication means.
The information is then passed through third party enabler 112, allowing communication with the specific mobile device 120, whereupon it is passed to client software 124 on mobile device 120.
As will be appreciated by those skilled in the art, when developing client software 124, it is convenient, and sometimes necessary to emulate mobile device 120 to create client software 124. This saves the developer from having to upload software changes to mobile device 120 and ensures that the client software 124 is working on an emulator prior to implementation on a physical mobile device 120.
Reference is now made to
When a software manufacturer other than the mobile device manufacturer is creating client software for the mobile device, one problem with current emulators 220 is that they generally do not provide access to standard provisioning for the client software.
Various options to provision the emulator are possible. These could include using a second computer and a connection between the computers, where a port on the computer is used by the emulator as an input and output port. The above would generally use a null modem cable in order to provide access to the emulator. However, this is an undesirable solution since it requires a second computer and is inconvenient for software developers.
A further problem is that the manufacturer of the mobile device emulator 220 may not want to provide a means to “talk” to the emulator. Device manufacturers often have proprietary software that talks to their device's emulator. This communication software 222 is typically not useful for third party software makers because the interfaces supplied are not configurable for use by the third party software makers.
In one embodiment of the present application, provisioning is done through a file transfer protocol (FTP) communication in which files are transferred according to a specific communication protocol and data can be provisioned in this way. This is explained in more detail with reference to
Still referring to
The above can be illustrated by the exemplary flow chart of commands as illustrated in
As illustrated in
Further, desktop provisioning software 310, which corresponds with desktop provisioning software 210 of
When emulator 320 is started it transfers a file to the common file space with a particular name. In the example of
The provisioning software 310 polls the common file space for files being written to it. Once it sees that the file ‘START’ was written in step 350 it knows that it can start to provision the emulator 320.
In step 352, the desktop writes a file to the common file space 330 with a specific name. In the example of
Emulator 320 polls the common file space and when it sees ‘PCOK’ written it then goes and retrieves the ‘COMMAND’ file in step 356 and in step 358 deletes the ‘COMMAND’ file and the ‘PCOK’ file.
As would be appreciated by those skilled in the art, the ‘COMMAND’ file can be a large file if it contains significant data, and the reason for providing a ‘PCOK’ file and a ‘COMMAND’ file is to ensure the ‘COMMAND’ file has been fully written before it is retrieved by emulator 320. ‘PCOK’ is only written after ‘COMMAND’ file has been completely written onto the common file space 330.
Once emulator 320 has retrieved ‘COMMAND’ file, the client software 223 reads the contents of the ‘COMMAND’ file and interprets them. In the present example, client software 223 sees that the provisioning software wants to know more about aspects of emulator 320, and this information is provided in a ‘RESPONSE’ file in step 360 and a ‘PHONEOK’ file in step 362.
Provisioning software 310 polls the common file space and when it sees the ‘PHONEOK’ file it retrieves the ‘RESPONSE’ file in step 364 and then in step 366 deletes both the ‘RESPONSE’ file and the ‘PHONEOK’ file from the common file space.
The provisioning software and the emulator 310 thus communicate in this way back and forth by providing a ‘COMMAND’ or a ‘RESPONSE’ file followed by a ‘PCOK’ or a ‘PHONEOK’ file in order to facilitate communications between the two applications.
Once the emulator wants to simulate that it has disconnected from provisioning software 310, it can delete the ‘START’ command in step 368.
Referring again to
As seen in
The provisioning process enables the emulator 220 to communicate with wireless gateway infrastructure. This wireless gateway infrastructure can be the same wireless gateway 250 that exists for use by a mobile device. This allows testing of the client software on emulator 220 in a realistic manner, which emulates the communication present in an actual mobile device. Further, enterprise server 260 can store certain information, such as security keys and addressing information, which can be used by desktop provisioning software 210 in order to provision emulator 220.
As will be appreciated by those skilled in the art, peer to peer software does need to be written in order to communicate between the desktop provisioning software 210 and emulator 220, but rather common file space 230 is used with the FTP protocol illustrated in
Reference is now made to
A feature call on the divided architecture 400 from the client applications 406 would normally go through a client OS 432. The client OS 432 may include a number of primitives for interacting with host OS and host hardware 434, which includes a host user interface 436. However, in the case that the client applications 406 are built onto the certified host communications device 402 and because the certified host communications device 402 has already acquired certification for its host dependent features such as hardware, software and firmware, it is preferable to have the client OS 432 interact with a host abstraction layer 438 instead of having the client OS 432 directly interacting with the features. The host abstraction layer 438 converts calls from the client applications 406 to host calls through a native interface 440. The native interface 440 invokes host applications 442 in order to use the host dependent features on the certified host communications device 402. The host applications 442 may include a variety of applications such as, but not limited to, a host contacts application 444 including an address book having phone numbers, e-mail addresses or other contact information for individuals or companies, a telephone-related application 446, an SMS application 448, a multi-media message service (“MMS”) application 450, and other certified applications 452. These individual host applications are started within the host application 442, and a request from the client application 406 is sent through the client OS 432 to the host abstraction layer 438 where the request is converted with the native interface 440 for the host applications 442.
Because the host applications 442 invoke the features of the certified host communications device 402 rather than the client applications 406 directly utilizing the features, the divided architecture 400 enables the client applications 406 to run in a host environment and use the features of the certified host communications device 402 without having to re-certify. The divided architecture 400 therefore enables the uncertified client, which is the data communications client 404, to be added to the certified host communications device 402 after certification, including an after-market addition to the certified host communications device 402.
One example of a client application using the above described method and system includes the making of a telephone call when the certified host communications device 402 is a cellular telephone. In the host environment, making of the telephone call simply involves using the host applications 442 to create the telephone call where the host applications 442 use certified hardware, firmware and software to connect through a wireless system. However, in the client applications 406, the above described divided architecture 400 requires invoking one of the host applications 442 in order to make the telephone call. The invoked client application could be the address book associated with the contacts application 412, which includes phone numbers for individuals. A user may wish to select a telephone number of a particular individual from the address book associated with the contacts application 412, and to have the cellular telephone, which is the certified host communications device 402 in this example, to make a call to that particular individual. In order to accomplish this task, the user may select the telephone number and select an option to dial that phone number. In this case, the contacts application 412 indicates through the virtual machine 408 to the client OS 432 that it needs to make a telephone call. Instead of using the host dependent feature directly from the client OS 432, a notification is sent to the host abstraction layer 438, which invokes an appropriate application of the host applications 442 through the native interface 440, to make the telephone call. In this example, the invoked host application would be the telephone-related application 446, which starts the telephone call, and the user proceeds as if the telephone call had been started from the client applications 406.
The client applications 406 may also provide the user an option to use the SMS application 448 or the MMS application 450 to contact the individual instead of the telephone number. In each of these cases, a different application of the host applications 442 is invoked, but this task is accomplished similarly through the host abstraction layer 438 and the native interface 440. Alternatively, the messages application 410, which includes a telephone number, may be invoked from the client applications 406.
As one skilled in the art will realize, data is supplied between the client applications 406 and the host applications 442. In the example above, the telephone number would be supplied to the host application 442 including the telephone-related application 446, the SMS application 448, and the MMS application 450.
It is further desirable to be able to activate a selected client application of the client applications 406 from one of the host applications 442. A client application selection application 454 uses a client abstraction layer 456 to activate an application within the client applications 406. The client application selection application 454 calls a function that is translated in the client abstraction layer 456. The client abstraction layer 456 then uses the virtual machine 108 to activate the selected client application of the client applications 406. The client abstraction layer 456 may either inject the client OS 432 event into the virtual machine 408 causing the selected client application of the client applications 406 to become active or, alternatively, may perform a “reverse native call” through the client OS 432 or via a client connect 458 to manipulate the native representation of some client object causing the selected client application of the client application 406 to become active. The client connect 458 can be used for network features for the client applications 406, which enables, for example, the data communications client 404 to communicate using a specific protocol that was not originally supported on the certified host communications device 402. The client connect 458 involves a protocol stack to perform this communication between the data communications client 404 and the certified host communications device 402, and increases and improves client functionality.
Where the host mobile station 1502 is enabled for two-way communication, it will incorporate a communication subsystem 1506, including both a receiver 1508 and a transmitter 1510, as well as associated components such as one or more, preferably embedded or internal, a receiver antenna 1512 and a transmitter antenna 1514, local oscillators (“LO”s) 1516, and a processing module such as a digital signal processor (“DSP”) 1518. As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem 1506 will be dependent upon the communication network in which the device is intended to operate. For example, host mobile station 1502 may include the communication subsystem 1506 designed to operate within the Mobitex™ mobile communication system, the DataTAC™ mobile communication system, General Packet Radio Service (“GPRS”) network, Universal Mobile Telecommunications System (“UMTS”) network, Enhanced Data for Global System for Mobile Communications (“GSM”) Evolution (“EDGE”) network or Code Division Multiple Access (“CDMA”) network.
Network access requirements will also vary depending upon the type of network 1504. For example, in the Mobitex and DataTAC networks, the host mobile station 1502 is registered on the communication network 1504 using a unique identification number associated with each mobile station. In UMTS and GPRS networks, and in some CDMA networks, however, network access is associated with a subscriber or user of the host mobile station 1502. A GPRS mobile station therefore requires a subscriber identity module (“SIM”) card in order to operate on a GPRS network, and a Removable User Identity Module (“RUIM”) in order to operate on some CDMA networks. Although the host mobile station 1502 would not fully function without a valid SIM/RUIM card if it is a GPRS/UMTS/ICDMA mobile station, local or non-network communication functions, as well as legally required functions (if any) such as “911” emergency calling, may still be available. However, the host mobile station 1502 will be unable to carry out any other functions involving communications over the communication network 1504. A SIM/RUIM interface 1520, which is configured to accept a SIM/RUIM card, is normally similar to a card-slot into which the SIM/RUIM card can be inserted and ejected like a diskette or a Personal Computer Memory Card International Association (“PCMCIA”) card. The SIM/RUIM card can have approximately 64K of memory and hold many key configuration 1522, and other information 1524 such as identification, and subscriber related information.
When required network registration or activation procedures have been completed, the host mobile station 1502 may send and receive communication signals over the communication network 1504. Signals received by the receiver antenna 1512 from the communication network 1504 are input to the receiver 1508, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection and the like, and in the example system shown in
The communication network 1504 may further communicate with multiple systems (not shown). For example, the communication network 1504 may communicate with both an enterprise system and a web client system in order to accommodate various clients with various service levels.
The host mobile station 1502 preferably includes a microprocessor 1534, which controls the overall operation of the host mobile station 1502. Communication functions, including at least data and voice communications, are performed through the communication subsystem 1506. The microprocessor 1534 also interacts with further device subsystems such as flash memory 1536, a display 1538, random access memory (“RAM”) 1540, auxiliary input/output (I/O) subsystems 1542, a serial port 1544, a keyboard 1546, a speaker 1548, a microphone 1550, other communications subsystem 1552, and any other compatible device subsystems, which is generally designated as 1554. Some of the subsystems shown in
Operating system software used by the microprocessor 1534 is preferably stored in a persistent store such as the flash memory 1538, which may instead be a read-only memory (“ROM”) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile memory such as the RAM 1540. Received communication signals may also be stored in the RAM 1540.
As shown in
In a data communication mode, a received signal such as a text message or web page download will be processed by the communication subsystem 1506 and input to the microprocessor 1534, which preferably further processes the received signal for output to the display 1538, or alternatively to the auxiliary I/O subsystems 1542. The user of the host mobile station 1602 may also compose data items such as e-mail messages for example, using the keyboard 1546, which is preferably a complete alphanumeric keyboard or telephone-type keypad, in conjunction with the display 1538 and possibly with the auxiliary I/O subsystems 1542. Such composed items may then be transmitted over the communication network 1504 through the communication subsystem 1506.
For voice communications, overall operation of the host mobile station 1502 is similar, except that the received signals would preferably be output to the speaker 1548 and signals for transmission would be generated by the microphone 1550. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the host mobile station 1502. Although voice or audio signal output is preferably accomplished primarily through the speaker 1548, the display 1538 may also be used to provide an indication of the identity of a calling party, the duration of a voice call, or other voice call related information for example.
The serial port 1544, such as Universal Serial Bus (“USB”), in
Although many services may be available on a given network, only those subscribers who use mobile communications devices that have been provisioned for those services will be able to benefit from them. This limitation may present problems for both the subscriber and the network operator. On one hand, the subscriber may desire an existing service he does not have, i.e. an upgrade, or desire disabling a service, i.e. a downgrade. On the other hand the operator may want to offer a new service, but may hesitate if subscribers cannot benefit from them. One known solution is to provide an out of band communications link, such as a Universal Serial Bus (“USB”), on the mobile communications device, and enable the subscriber to load new software onto the mobile communications device via the out of band communication link using a personal computer, thus re-provisioning the mobile communications device. This solution may be an unacceptable solution to both the subscriber and the operator as there is a significant risk that the mobile communications device, by error, receives a wrong or incomplete load, and may require servicing. Furthermore, this solution may be unacceptable to the subscriber who does not have access to a personal computer. However, because the host mobile station 1502 is a host communications device that hosts the data communications client 404, the data communications client 404 may be provisioned directly by the user of host mobile station 1502.
The embodiments described herein are examples of structures, systems or methods having elements corresponding to elements of the techniques of this application. This written description may enable those skilled in the art to make and use embodiments having alternative elements that likewise correspond to the elements of the techniques of this application. The intended scope of the techniques of this application thus includes other structures, systems or methods that do not differ from the techniques of this application as described herein, and further includes other structures, systems or methods with insubstantial differences from the techniques of this application as described herein.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6496979 *||Apr 10, 1998||Dec 17, 2002||Microsoft Corporation||System and method for managing application installation for a mobile device|
|US20030018825||Jul 17, 2001||Jan 23, 2003||Johnson Hollis Bruce||Methods and systems for providing platform-independent shared software components for mobile devices|
|US20030066063 *||May 17, 2001||Apr 3, 2003||Yasuhiro Yokota||Information processing apparatus, information processing method, information processing system, and storage medium|
|US20030212753||Jul 23, 2002||Nov 13, 2003||Chien-Chou Lai||Method and system of data synchronization using HTTP|
|US20040249785 *||Sep 25, 2003||Dec 9, 2004||Thomas Gauweiler||Method of designing a database access system and system for updating a database access system|
|US20050125460 *||Jan 6, 2004||Jun 9, 2005||Lindeng Yu||[method for resotoring backup data]|
|US20060004685 *||Jun 30, 2004||Jan 5, 2006||Nokia Corporation||Automated grouping of image and other user data|
|US20060274784 *||Jun 2, 2005||Dec 7, 2006||Mediatek Incorporation||Methods and systems for cross-platform message exchange|
|US20070078859 *||Oct 3, 2005||Apr 5, 2007||Steve Arnold||Method, system, apparatus, and software product for an intelligent transfer log|
|1||A.S.Tanenbaum:"Modern Operating Systems" 2001, Prentice-Hall, Inc. US.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US20090235189 *||Mar 4, 2009||Sep 17, 2009||Alexandre Aybes||Native support for manipulation of data content by an application|
|US20100022233 *||Jan 28, 2010||Samsung Electronics Co., Ltd.||Method of remote control for portable device and system using the same|
|U.S. Classification||455/418, 455/419, 455/420, 707/999.001, 707/999.01, 707/999.202|
|Cooperative Classification||Y10S707/99953, Y10S707/99931, H04M3/42161, H04M2203/053|
|Dec 27, 2005||AS||Assignment|
Owner name: RESEARCH IN MOTION LIMITED, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HASSAN, MAHMUD-UL;WILSON, NICHOLAS;REEL/FRAME:017392/0183
Effective date: 20051103
|Mar 12, 2013||FPAY||Fee payment|
Year of fee payment: 4