# US 7,613,453 B2 · System and method for provisioning a third party mobile device emulator > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 7,613,453 B2 - Document ID: US7613453B2 - Status: Granted - Kind: B2 - Application number: 11/266,327 - Filed: 2005-11-04 - Published: 2007-05-10 - Granted: 2009-11-03 - Earliest claimed: 2005-11-04 - Assignees: Research In Motion Limited - Inventors: Mahmud-Ul Hassan; Nicholas Wilson - Web page: https://patentgrep.com/patent/US7613453B2 ## CPC - H04M 3/42161: {via computer interface} - H04M 2203/053: remote terminal provisioning, e.g. of applets - Y10S 707/99931: Database or file accessing - Y10S 707/99953: Recoverability - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS ## Abstract A method and apparatus for provisioning a third party mobile device emulator from desktop provisioning software, the method having 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. ## Claims ### Claim 1 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 a provisioning file to the common file space from one of the third party mobile device emulator and the desktop provisioning software; wherein said writing steps includes: transferring a data file to the common file space; and once the transferring step is complete, writing an indicator file to the common file space; and reading the files from the other of the third party mobile device emulator and the desktop provisioning software. ### Claim 2 (depends on 1) The method of claim 1, wherein said writing step utilizes a file transfer protocol. ### Claim 3 (depends on 1) The method of claim 1, further comprising the step of deleting the files from the common file space once the reading step is complete. ### Claim 4 (depends on 1) The method of claim 1, wherein the desktop provisioning software includes a variable designating whether the desktop provisioning software will provision a third party mobile device or the third party mobile device emulator, said method further comprising reading said variable prior to said designating step. ### Claim 5 (depends on 1) The method of claim 1, wherein said desktop provisioning software is adapted to configure a client residing on one of a third party mobile device or the third party mobile device emulator. ### Claim 6 (depends on 1) The method of claim 1, further comprising signaling via indicator file names. ### Claim 7 (depends on 1) The method of claim 1, wherein reading the files the method further comprises each one of the third party mobile device emulator and the desktop provisioning software polling the common file space for files written by the other one of the third part mobile device emulator and the desktop provisioning software. ### Claim 8 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, said third party mobile device emulator and said desktop provisioning software being: configured to write data files to the common file space, followed by an indicator file to designate that the writing of the data file is complete; and configured to read the files from the common file space written by the other of the third party mobile device emulator and the desktop provisioning software. ### Claim 9 (depends on 8) The system of claim 8, wherein the system is on a personal computer. ### Claim 10 (depends on 8) The system of claim 8, further comprising a communications means accessible by both the desktop provisioning software and the third party mobile device emulator. ### Claim 11 (depends on 10) The system of claim 10, wherein said communications means is a UDP/TCP/IP port connecting to a network. ### Claim 12 (depends on 11) The system of claim 11, further comprising an enterprise server and a wireless gateway connected to the network, wherein said third party mobile device emulator, once provisioned, can communicate with the wireless gateway and the enterprise server. ### Claim 13 (depends on 8) The system of claim 8, wherein said desktop provisioning software is adapted to configure a client residing on one of a third party mobile device or the third party mobile device emulator. ### Claim 14 (depends on 8) The system of claim 8, wherein the desktop provisioning software includes a variable designating whether the desktop provisioning software will provision a third party mobile device or the third party mobile device emulator. ### Claim 15 (depends on 8) The system of claim 8, wherein the desktop provisioning software and the third party mobile device emulator are adapted to communicate with the common file space using a file transfer protocol. ### Claim 16 (depends on 8) The system of claim 8, wherein each of the desktop provisioning software and the third party mobile device emulator are adapted to delete the once the respective one of the desktop provisioning software and the third party mobile device emulator have finished reading the files. ### Claim 17 (depends on 8) The system of claim 8, wherein each one of the desktop provisioning software and the third party mobile device emulator is further configured to signal to the other one of the desktop provisioning software and the third party mobile device emulator via indicator file names. ### Claim 18 (depends on 8) The system of claim 8, wherein each one of the third party mobile device emulator and the desktop provisioning software is further configured to poll the common file space for files written by the other one of the third part mobile device emulator and the desktop provisioning software.