Apparatus and Method for Bundling Application Services With Inbuilt Connectivity Management

• US 20100153228A1
• Filed: 08/27/2009
• Published: 06/17/2010
• Est. Priority Date: 12/16/2008
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Ahmavaara, Kalle I.
• Granted Patent: US 9,197,706 B2
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

An apparatus and method for bundling application services with inbuilt connectivity management comprising launching a software application; detecting a need for connectivity to use the service associated with the software application; establishing connectivity; determining whether connectivity is established; and executing the service associated with the software application utilizing the established connectivity.

Claims

1. A method for bundling application services with inbuilt connectivity management comprising:

launching a software application;

detecting a need for connectivity to use the service associated with the software application;

establishing connectivity; and

executing the service associated with the software application utilizing the established connectivity.

2. The method of claim 1 further comprising determining whether connectivity is established.

3. The method of claim 1 wherein the software application comprises at least one parameter for connectivity.

4. The method of claim 3 wherein the step of establishing uses at least one parameter associated with the software application.

5. The method of claim 1 wherein the software application performs the detecting step.

6. The method of claim 1 wherein a user performs the detecting step.

7. The method of claim 1 wherein the inbuilt connectivity management comprises information necessary to establish connectivity.

8. The method of claim 7 wherein the information identifies a connectivity agent that negotiates connectivity on behalf of the software application.

9. The method of claim 8 wherein the connectivity agent is reachable via a connectivity network and is identified by one of the following:

a fully qualified domain name (FQDN), a service address, or an Internet protocol (IP) address.

10. The method of claim 7 wherein the information comprises connectivity negotiation instructions.

11. The method of claim 1 wherein the inbuilt connectivity management further comprises information provided to an entity within a user device to execute a connectivity establishment signal via a connectivity network.

12. The method of claim 11 wherein the information is provided through an application programming interface (API) between the software application and the entity.

13. The method of claim 11 wherein the information comprises connectivity negotiation instructions.

14. The method of claim 11 wherein the inbuilt connectivity management further comprises specific information to be passed to a connectivity agent wherein the specific information pertains either to the software application or to the connectivity agent.

15. The method of claim 1 wherein connectivity is available for purchase in connectivity chunks.

16. The method of claim 15 wherein the connectivity chunks are defined in terms of allowed data volume.

17. The method of claim 15 wherein the connectivity chunks are defined in terms of allowed connectivity time.

18. The method of claim 15 wherein the price of the connectivity chunks is based on characteristics of the connectivity chunks.

19. The method of claim 15 wherein a connectivity agent comprises information regarding a payment method for purchasing the connectivity chunks.

20. The method of claim 15 wherein at least one connectivity chunk of the connectivity chunks is used for executing the service associated with the software application.

21. The method of claim 15 wherein the inbuilt connectivity management comprises information regarding a payment method.

22. The method of claim 21 wherein the payment method is one of the following:

a token accepted by a connectivity network selling chunks of connectivity, identity of a payment agent, information to be delivered to the payment agent to pay the connectivity network on behalf of the software application, payment executed via a payment agent, a credit card number or a pre-established credit or debit amount.

23. An access terminal for bundling application services with inbuilt connectivity management comprising:

a software application for detecting a need for connectivity to use the service associated with the software application;

a processor for launching the software application;

a communications component for establishing connectivity per directions from the software application; and

wherein the processor executes the service associated with the software application utilizing the established connectivity.

24. The access terminal of claim 23 wherein the communication component further determines whether connectivity is established.

25. The access terminal of claim 23 wherein the software application comprises at least one parameter for connectivity.

26. The access terminal of claim 25 wherein at least one parameter associated with the software application is used for establishing the need for connectivity.

27. The access terminal of claim 23 wherein the inbuilt connectivity management comprises information necessary to establish connectivity.

28. The access terminal of claim 27 wherein the information identifies a connectivity agent that negotiates connectivity on behalf of the software application.

29. The access terminal of claim 28 wherein the connectivity agent is reachable via a connectivity network and is identified by one of the following:

a fully qualified domain name (FQDN), a service address, or an Internet protocol (IP) address.

30. The access terminal of claim 27 wherein the information comprises connectivity negotiation instructions.

31. The access terminal of claim 23 wherein the inbuilt connectivity management further comprises information provided to an entity within a user device to execute a connectivity establishment signal via a connectivity network.

32. The access terminal of claim 31 wherein the information is provided through an application programming interface (API) between the software application and the entity.

33. The access terminal of claim 31 wherein the information comprises connectivity negotiation instructions.

34. The access terminal of claim 31 wherein the inbuilt connectivity management further comprises specific information to be passed to a connectivity agent wherein the specific information pertains either to the software application or to the connectivity agent.

35. The access terminal of claim 23 wherein connectivity is available for purchase in connectivity chunks.

36. The access terminal of claim 35 wherein the connectivity chunks are defined in terms of allowed data volume.

37. The access terminal of claim 35 wherein the connectivity chunks are defined in terms of allowed connectivity time.

38. The access terminal of claim 35 wherein the price of the connectivity chunks is based on characteristics of the connectivity chunks.

39. The access terminal of claim 35 wherein a connectivity agent comprises information regarding a payment method for purchasing the connectivity chunks.

40. The access terminal of claim 35 wherein at least one connectivity chunk of the connectivity chunks is used for executing the service associated with the software application.

41. The access terminal of claim 35 wherein the inbuilt connectivity management comprises information regarding a payment method.

42. The access terminal of claim 41 wherein the payment method is one of the following:

a token accepted by a connectivity network selling chunks of connectivity, identity of a payment agent, information to be delivered to the payment agent to pay the connectivity network on behalf of the software application, payment executed via a payment agent, a credit card number or a pre-established credit or debit amount.

43. An apparatus for bundling application services with inbuilt connectivity management comprising:

means for launching a software application;

means for detecting a need for connectivity to use the service associated with the software application;

means for establishing connectivity; and

means for executing the service associated with the software application utilizing the established connectivity.

44. The apparatus of claim 43 further comprising means for determining whether connectivity is established.

45. The apparatus of claim 43 wherein the software application comprises at least one parameter for connectivity.

46. The apparatus of claim 45 wherein the means of establishing uses at least one parameter associated with the software application.

47. The apparatus of claim 43 wherein the inbuilt connectivity management comprises information necessary to establish connectivity.

48. The apparatus of claim 47 wherein the information identifies a connectivity agent that negotiates connectivity on behalf of the software application.

49. The apparatus of claim 48 wherein the connectivity agent is reachable via a connectivity network and is identified by one of the following:

a fully qualified domain name (FQDN), a service address, or an Internet protocol (IP) address.

50. The apparatus of claim 47 wherein the information comprises connectivity negotiation instructions.

51. The apparatus of claim 43 wherein the inbuilt connectivity management further comprises information provided to an entity within a user device to execute a connectivity establishment signal via a connectivity network.

52. The apparatus of claim 51 wherein the information is provided through an application programming interface (API) between the software application and the entity.

53. The apparatus of claim 51 wherein the information comprises connectivity negotiation instructions.

54. The apparatus of claim 51 wherein the inbuilt connectivity management further comprises specific information to be passed to a connectivity agent wherein the specific information pertains either to the software application or to the connectivity agent.

55. The apparatus of claim 43 wherein connectivity is available for purchase in connectivity chunks.

56. The apparatus of claim 55 wherein the connectivity chunks are defined in terms of allowed data volume.

57. The apparatus of claim 55 wherein the connectivity chunks are defined in terms of allowed connectivity time.

58. The apparatus of claim 55 wherein the price of the connectivity chunks is based on characteristics of the connectivity chunks.

59. The apparatus of claim 55 wherein a connectivity agent comprises information regarding a payment method for purchasing the connectivity chunks.

60. The apparatus of claim 55 wherein at least one connectivity chunk of the connectivity chunks is used for executing the service associated with the software application.

61. The apparatus of claim 55 wherein the inbuilt connectivity management comprises information regarding a payment method.

62. The apparatus of claim 61 wherein the payment method is one of the following:

a token accepted by a connectivity network selling chunks of connectivity, identity of a payment agent, information to be delivered to the payment agent to pay the connectivity network on behalf of the software application, payment executed via a payment agent, a credit card number or a pre-established credit or debit amount.

63. A computer-readable medium storing a computer program, wherein execution of the computer program is for:

launching a software application;

detecting a need for connectivity to use the service associated with the software application;

establishing connectivity; and

executing the service associated with the software application utilizing the established connectivity.

64. The computer-readable medium of claim 63 wherein execution of the computer program is also for determining whether connectivity is established.

65. The computer-readable medium of claim 63 wherein the software application comprises at least one parameter for connectivity.

66. The computer-readable medium of claim 65 wherein the step of establishing uses at least one parameter associated with the software application.

67. The computer-readable medium of claim 63 wherein the inbuilt connectivity management comprises information necessary to establish connectivity.

68. The computer-readable medium of claim 67 wherein the information identifies a connectivity agent that negotiates connectivity on behalf of the software application.

69. The computer-readable medium of claim 68 wherein the connectivity agent is reachable via a connectivity network and is identified by one of the following:

a fully qualified domain name (FQDN), a service address, or an Internet protocol (IP) address.

70. The computer-readable medium of claim 67 wherein the information comprises connectivity negotiation instructions.

71. The computer-readable medium of claim 63 wherein the inbuilt connectivity management further comprises information provided to an entity within a user device to execute a connectivity establishment signal via a connectivity network.

72. The computer-readable medium of claim 71 wherein the information is provided through an application programming interface (API) between the software application and the entity.

73. The computer-readable medium of claim 71 wherein the information comprises connectivity negotiation instructions.

74. The computer-readable medium of claim 71 wherein the inbuilt connectivity management further comprises specific information to be passed to a connectivity agent wherein the specific information pertains either to the software application or to the connectivity agent.

75. The computer-readable medium of claim 63 wherein connectivity is available for purchase in connectivity chunks.

76. The computer-readable medium of claim 75 wherein the connectivity chunks are defined in terms of allowed data volume.

77. The computer-readable medium of claim 75 wherein the connectivity chunks are defined in terms of allowed connectivity time.

78. The computer-readable medium of claim 75 wherein the price of the connectivity chunks is based on characteristics of the connectivity chunks.

79. The computer-readable medium of claim 75 wherein a connectivity agent comprises information regarding a payment method for purchasing the connectivity chunks.

80. The computer-readable medium of claim 75 wherein at least one connectivity chunk of the connectivity chunks is used for executing the service associated with the software application.

81. The computer-readable medium of claim 75 wherein the inbuilt connectivity management comprises information regarding a payment method.

82. The computer-readable medium of claim 81 wherein the payment method is one of the following:

a token accepted by a connectivity network selling chunks of connectivity, identity of a payment agent, information to be delivered to the payment agent to pay the connectivity network on behalf of the software application, payment executed via a payment agent, a credit card number or a pre-established credit or debit amount.

83. A method for providing connectivity service by a connectivity network comprising:

providing connectivity service by a connectivity network wherein the connectivity service is available for purchase in connectivity chunks.

84. The method of claim 83 wherein the connectivity chunks are defined in units of connectivity.

85. The method of claim 83 wherein the connectivity chunks are defined at least in terms of allowed data volume.

86. The method of claim 83 wherein the connectivity chunks are defined at least in terms of allowed connectivity time.

87. The method of claim 83 wherein the connectivity chunks are associated with specific connectivity.

88. The method of claim 87 wherein the specific connectivity is defined at least in terms of allowed connectivity peers

89. The method of claim 88 wherein the connectivity peers are defined at least in terms of their IP address or fully qualified domain name (FQDN).

90. The method of claim 83 wherein the price of the connectivity chunks is based on characteristics of the associated connectivity.

91. The method of claim 90 wherein the characteristics of the associated connectivity are defined at least in terms of the relative priority, quality of service (QoS) or other specific connectivity treatment.

92. The method of claim 83 wherein the connectivity service expires when the purchased connectivity chunks are consumed.

93. The method of claim 92 wherein a connectivity server informs a connectivity agent about the expiration of the connectivity service.

94. The method of claim 92 wherein a connectivity agent extends the connectivity service by purchasing additional connectivity chunks.

95. A connectivity server for providing connectivity service by a connectivity network comprising a processor and a memory, the memory containing program code executable by the processor for performing the following:

providing connectivity service by the connectivity network wherein the connectivity service is available for purchase in connectivity chunks.

96. The connectivity server of claim 95 wherein the connectivity chunks are defined in units of connectivity.

97. The connectivity server of claim 95 wherein the connectivity chunks are defined at least in terms of allowed data volume.

98. The connectivity server of claim 95 wherein the connectivity chunks are defined at least in terms of allowed connectivity time.

99. The connectivity server of claim 95 wherein the connectivity chunks are associated with specific connectivity.

100. The connectivity server of claim 99 wherein the specific connectivity is defined at least in terms of allowed connectivity peers

101. The connectivity server of claim 100 wherein the connectivity peers are defined at least in terms of their IP address or fully qualified domain name (FQDN).

102. The connectivity server of claim 95 wherein the price of the connectivity chunks is based on characteristics of the associated connectivity.

103. The connectivity server of claim 102 wherein the characteristics of the associated connectivity are defined at least in terms of the relative priority, quality of service (QoS) or other specific connectivity treatment.

104. The connectivity server of claim 95 wherein the connectivity service expires when the purchased connectivity chunks are consumed.

105. The connectivity server of claim 104 wherein the memory further comprising program code for informing a connectivity agent about the expiration of the connectivity service.

106. The connectivity server of claim 104 wherein a connectivity agent extends the connectivity service by purchasing additional connectivity chunks.

107. The connectivity server of claim 95 wherein the memory further comprising program code for receiving a query regarding the characteristics of the connectivity chunks that are available for purchase.

108. The connectivity server of claim 107 wherein the characteristics include pricing information.

109. A connectivity agent for obtaining connectivity service for a user equipment comprising a processor and a memory, the memory containing program code executable by the processor for performing the following:

purchasing connectivity service through a connectivity network wherein the connectivity service is available for purchase in connectivity chunks.

110. The connectivity agent of claim 109 wherein the connectivity chunks are defined in units of connectivity.

111. The connectivity agent of claim 109 wherein the connectivity chunks are defined at least in terms of allowed data volume.

112. The connectivity agent of claim 109 wherein the connectivity chunks are defined at least in terms of allowed connectivity time.

113. The connectivity agent of claim 109 wherein the connectivity chunks are associated with specific connectivity.

114. The connectivity agent of claim 113 wherein the specific connectivity is defined at least in terms of allowed connectivity peers

115. The connectivity agent of claim 114 wherein the connectivity peers are defined at least in terms of their IP address or fully qualified domain name (FQDN).

116. The connectivity agent of claim 109 wherein the price of the connectivity chunks is based on characteristics of the associated connectivity.

117. The connectivity agent of claim 116 wherein the characteristics of the associated connectivity are defined at least in terms of the relative priority, quality of service (QoS) or other specific connectivity treatment.

118. The connectivity agent of claim 109 wherein the connectivity service expires when the purchased connectivity chunks are consumed.

119. The connectivity agent of claim 118 wherein the memory further comprising program code for receiving information about the expiration of the connectivity service.

120. The connectivity agent of claim 118 wherein the memory further comprising program code for extending the connectivity service by purchasing additional connectivity chunks.

121. The connectivity agent of claim 109 wherein the memory further comprising program code for sending a query regarding the characteristics of the connectivity chunks that are available for purchase.

122. The connectivity agent of claim 121 wherein the characteristics include pricing information.