Software Application Framework for Network-Connected Devices

• US 20100235261A1
• Filed: 04/30/2010
• Published: 09/16/2010
• Est. Priority Date: 08/08/2002
• Status: Abandoned Application

• Current Assignee: Shoreline Innovations, LLC
• Original Assignee: Shoreline Innovations, LLC
• Inventors: Bilange, Eric, Lloyd, David B.
• Application Number:
  US12/772,059
• Publication Number:
  US 20100235261A1
• Time in Patent Office: Days
• US Class Current: 705/27
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06Q 20/1235 with control of digital rights management [DRM]
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0645 Rental transactions; Leasing transactions
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

A facility for provisioning and managing registered applications is described. Registered applications can be downloaded to a mobile device from an application provisioning server. When the download is complete, the mobile device may begin execution of the registered application. However, at least portions of the registered application cannot be executed by the mobile device without first passing control to an application provisioning server via a network connection. Upon receiving temporary control of the registered application, the application provisioning server can perform tasks such as license verification and other tasks before turning control of the application back to the mobile device.

Claims

1-30. -30. (canceled)

31. A method for managing a registered application on a mobile receiving device, the method comprising:

sending the registered application to the mobile receiving device from an application provisioning server communicating with the mobile receiving device via a wireless network connection;

receiving via the wireless network connection, at said application provisioning server, a request from the registered application for a license or unlock code at a time when the registered application has been started at a first entry point in the registered application, for the first time, on the mobile receiving device;

authenticating, at said application provisioning server, the license or unlock code; and

sending the authentication of the license or unlock code, over the wireless network connection, to the registered application that has been started on the mobile receiving device, wherein the authentication of the license or unlock code permits interaction between (i) the registered application that has been started on the mobile receiving device and (ii) a user and wherein the authentication of the license or unlock code permits subsequent sessions of the registered application to be run beginning at a second entry point in the registered application on the mobile receiving device.

32. The method of claim 31, further comprising associating an identifier with the mobile receiving device, wherein the identifier is stored on the mobile receiving device, wherein the identifier is configured for authorizing the mobile receiving device to execute the registered application.

33. The method of claim 31, wherein the registered application includes a registered MIDlet that permits the application provisioning server to take control of the registered application, via the wireless network connection, that has been started on the mobile receiving device during the authenticating step.

34. The method of claim 31, wherein the registered application includes an underlying game application.

35. The method of claim 31, wherein the application provisioning server is associated with a wireless service provider.

36. The method of claim 31, the method further comprising sending an update of the registered application from the application provisioning server to the mobile receiving device via the wireless connection after the authenticating, wherein the update of the registered application is customized for use on the type of the mobile receiving device.

37. The method of claim 31, wherein the registered application is developed using an application skeleton and is, prior to download onto the mobile receiving device, reconfigured to be compatible with the type of the mobile receiving device.

38. The method of claim 32, wherein the identifier is a license key.

39. The method of claim 31, wherein the authenticating comprises verifying that the registered application has a license that permits the registered application to run on the mobile receiving device.

40. The method of claim 39, wherein the license comprises an expiration date and wherein the verifying comprises determining whether the expiration date is before or after a time when the verifying is performed.

41. The method of claim 39, wherein the license specifies a number of uses and wherein the verifying comprises determining whether a number of times the registered application has been used on the receiving device exceeds or does not exceed the number of uses specified in the license.

42. The method of claim 39, wherein the license is a rental license.

43. The method of claim 31, wherein the method further comprises performing a billing function for usage of the registered application on the mobile receiving device.

44. The method of claim 31, wherein the method further comprises receiving, at said application provisioning server, via the wireless network connection, from the registered application a high score generated by the registered application on the mobile receiving device.

45. The method of claim 31, wherein the method further comprises receiving from the registered application feedback regarding a quality of the registered application.

46. The method of claim 31, wherein the license binds the registered application to a hardware identification of the mobile receiving device.

47. The method of claim 31, wherein the authenticating comprises:

determining whether the registered application has a valid license that permits the registered application to run on the mobile receiving device and, when the registered application does not have a valid license to run on the mobile receiving device, the license management further comprises sending an offer to purchase a license to the mobile receiving device.

48. The method of claim 31, wherein the method further comprises receiving, at said application provisioning server, from the registered application a high score generated by the registered application on the receiving device via the wireless network.

49. The method of claim 39, wherein the license is a rental subscription.

50. The method of claim 39, wherein the license is a limited free trial.

51. The method of claim 39, wherein the license is a coin-op.

52. The method of claim 39, wherein the license is a feature charge.

53. The method of claim 31, wherein the request from the registered application for a license or unlock code comprises a license or unlock code that has not been authenticated by the application provisioning server.

54. The method of claim 31, wherein the request from the registered application for a license or unlock code does not comprise a license or unlock code that has not been authenticated by the application provisioning server.

55. The method of claim 31, wherein the sending the authentication of the license or unlock code, over the wireless network, comprises sending the license or unlock code to the mobile receiving device.

56. The method of claim 31 wherein the authentication of the license or unlock code permits interaction between (i) the registered application that has been started on the mobile receiving device and (ii) a user and wherein the authentication of the license or unlock code permits subsequent sessions of the registered application to be run beginning at a second entry point in the registered application on the mobile receiving device without any requirement for accessing the application provisioning server.