Programming interface layer of a service provider for data service delivery

• US 20040142683A1
• Filed: 11/10/2003
• Published: 07/22/2004
• Est. Priority Date: 11/08/2002
• Status: Abandoned Application

• Current Assignee: Action Engine Corp. (MobUI, Inc.)
• Original Assignee: Action Engine Corp. (MobUI, Inc.)
• Inventors: Clark, Matt, Romanzin, Chris, Meyer, Shane, Roundtree, Brian C.
• Application Number:
  US10/705,456
• Publication Number:
  US 20040142683A1
• Time in Patent Office: Days
• US Class Current: 455/418
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 15/745 Customizing according to wishes of subscriber, e.g. friends or family
• CPC Class Codes: H04M 15/83 Notification aspects
• CPC Class Codes: H04M 15/84 Types of notifications
• CPC Class Codes: H04M 2215/0108 Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
• CPC Class Codes: H04M 2215/0168 On line or real-time flexible customization or negotiation according to wishes of subscriber
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
• CPC Class Codes: H04M 2215/2026 Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/81 Notifying aspects, e.g. notifications or displays to the user
• CPC Class Codes: H04M 2215/8129 Type of notification
• CPC Class Codes: H04W 4/24 Accounting or billing

Abstract

A programming interface layer and associated method, computer readable medium and apparatus are provided for service provider delivery of solutions to wireless mobile devices. The programming interface layer including solution delivery functions usable by any of a plurality of vendors to deliver solutions via the service provider.

Claims

1. A computer implemented method for accessing a wireless mobile device service provider server via a programming interface layer, the method comprising:

encapsulating a function call encapsulation of a function-specific parameter identified a associated with an executable programming interface layer function;

generating a programming interface function call directed to said executable programming interface layer function, wherein said programming interface function call includes said function call encapsulation of data; and

obtaining an indication of an programming interface response from said executable programming interface layer function.

2. The method of claim 1, further comprising directing said programming interface response to a specific wireless mobile device.

3. A computer system comprising:

a processor; and

memory coupled to the processor having a plurality of programming instructions implementing a programming interface layer for service provider delivery of data services to client devices, the programming interface layer including solution delivery functions usable by any of a plurality of vendors to deliver solutions via the service provider, the programming interface layer including

a plurality of executable service functions;

a parameter processing module for processing function-specific parameters, including device information for the wireless mobile device, for one of said plurality of executable service functions wherein said function-specific parameters are associated with one of said executable service functions; and

a response generating module for generating a function-specific response from one of said executable service functions, wherein said function-specific response is associated with one of said executable service functions and includes said device information.

4. The computer system of claim 3, wherein the programming interface layer further comprises a scheduling module for scheduling tasks via said executable service functions.

5. The computer system of claim 3, wherein said programming interface layer defines a plurality of classes including at least a selected one of AnswersResponse, BinaryResource, BooleanResponse, ClientInfo, CodeResponse, Concepts, ConceptsResponse, ConceptValues, ConfigFile, DeckResponse, Device, Devices, Identity, ImageResource, InfoRequest, InfoRequestResponse, InfoResponse, Message, MessageResponse, Resource, ResourceReference, ResourcesResponse, Response, Result, User, and UserDataResponse.

6. The computer system of claim 3, wherein said programming interface layer defines a plurality of methods including at least a selected one of AddMessage, Equals, AddData, GetString, GetEnumerator, CreateUser, DeleteUser, DoesUserExist, GetSignupConcepts, GetSupportedData, GetUserData, LogOn, ModifyUserData, SetIdentity, SetPassword, SetPrimaryUserData, AppendResource, AppendResourceReference, DoFeatureCommand, DoSolutionCommand, GetDeck, GetResources, SubmitConcepts, GetInfo, and GetInfoRequest.

7. A programming interface layer for service provider delivery of data services to wireless mobile devices, the programming interface layer including solution delivery functions usable by any of a plurality of vendors to deliver solutions via the service provider, the programming interface layer comprising:

a plurality of executable service functions;

a parameter processing module for processing function-specific parameters, including device information for the wireless mobile device, for one of said plurality of executable service functions wherein said function-specific parameters are associated with one of said executable service functions; and

a response generating module for generating a function-specific response from one of said executable service functions, wherein said function-specific response is associated with one of said executable service functions and includes said device information.

8. The programming interface layer of claim 7, further comprising a scheduling module for scheduling tasks via said executable service functions.

9. The programming interface layer of claim 7, further defining a plurality of classes including at least a selected one of AnswersResponse, BinaryResource, BooleanResponse, ClientInfo, CodeResponse, Concepts, ConceptsResponse, ConceptValues, ConfigFile, DeckResponse, Device, Devices, Identity, ImageResource, InfoRequest, InfoRequestResponse, InfoResponse, Message, MessageResponse, Resource, ResourceReference, ResourcesResponse, Response, Result, User, and UserDataResponse.

10. The programming interface layer of claim 7, further defining a plurality of methods including at least a selected one of AddMessage, Equals, AddData, GetString, GetEnumerator, CreateUser, DeleteUser, DoesUserExist, GetSignupConcepts, GetSupportedData, GetUserData, LogOn, ModifyUserData, SetIdentity, SetPassword, SetPrimaryUserData, AppendResource, AppendResourceReference, DoFeatureCommand, DoSolutionCommand, GetDeck, GetResources, SubmitConcepts, GetInfo, and GetInfoRequest.

11. A computer readable medium containing computer executable instructions for a programming interface layer for service provider delivery of data services to client devices, the programming interface layer including solution delivery functions usable by any of a plurality of vendors to deliver solutions via the service provider, the programming interface layer including

a plurality of executable service functions;

a parameter processing module for processing function-specific parameters, including device information for the wireless mobile device, for one of said plurality of executable service functions wherein said function-specific parameters are associated with one of said executable service functions; and

a response generating module for generating a function-specific response from one of said executable service functions, wherein said function-specific response is associated with one of said executable service functions and includes said device information.

12. The computer readable medium of claim 11, wherein the programming interface layer further comprises a scheduling module for scheduling tasks via said executable service functions.

13. The computer readable medium of claim 11, wherein said programming interface layer defines a plurality of classes including at least a selected one of AnswersResponse, BinaryResource, BooleanResponse, ClientInfo, CodeResponse, Concepts, ConceptsResponse, ConceptValues, ConfigFile, DeckResponse, Device, Devices, Identity, ImageResource, InfoRequest, InfoRequestResponse, InfoResponse, Message, MessageResponse, Resource, ResourceReference, ResourcesResponse, Response, Result, User, and UserDataResponse.

14. The computer readable medium of claim 11, wherein said programming interface layer defines a plurality of methods including at least a selected one of AddMessage, Equals, AddData, GetString, GetEnumerator, CreateUser, DeleteUser, DoesUserExist, GetSignupConcepts, GetSupportedData, GetUserData, LogOn, ModifyUserData, SetIdentity, SetPassword, SetPrimaryUserData, AppendResource, AppendResourceReference, DoFeatureCommand, DoSolutionCommand, GetDeck, GetResources, SubmitConcepts, GetInfo, and GetInfoRequest.