Device based telecommunications initiated data fulfillment system

• US 8,626,145 B2
• Filed: 08/30/2012
• Issued: 01/07/2014
• Est. Priority Date: 12/05/2007
• Status: Active Grant

• Current Assignee: VHT Starstar LLC
• Original Assignee: Zoove Corporation (Medallia, Inc.)
• Inventors: Han, Wen Khang
• Primary Examiner(s): Ajibade Akonai, Olumide T
• Application Number:
  US13/599,239
• Publication Number:
  US 20130090107A1
• Time in Patent Office: 495 Days
• Field of Search: 455/414.1, 455/414.2, 455/418, 455/518, 455/519, 455/521, 455/552.1, 455/553.1
• US Class Current: 455/418
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

A system and method for service fulfillment is based on service invocation with a preprogrammed communication device. The communication device recognizes special multi-function code digit sequences to cause service invocation. The preprogrammed communication device, upon recognition of a multi-function code, selects a communication channel or messaging protocol and forwards information related to the service invocation to a service fulfillment platform. The communication channel or messaging protocol may be selected based on availability, optimization, preprogrammed logic associated with the multi-function code, or other parameters related to the service invocation, such as user, subscription, registration, location or device ID. The preprogrammed communication device permits service invocation without reconfiguration of a communication network to which the communication device is coupled. The communication device can be reconfigured or reprogrammed to recognize and respond to different multi-function codes.

Claims

1. A communications device comprising:

at least one function-identifier table for storing one or more of a non-numeric code prefix or a service code programmed for identifying a service invocation;

an interface in the communication device configured to receive an input sequence that includes an input function code that identifies a service invocation;

a processing engine in the communication device, the processing engine being communicatively coupled to the interface and being operative to determine if the input function code identifies a service invocation corresponding to a function identifier stored in the function-identifier table;

wherein;

the processing engine is operable, in response to determining that the input function code identifies the service invocation, to transmit information related to the service invocation; and

the communication device is operable to establish a connection with a service-fulfillment center and to receive therefrom, during a communication between the communication device and the service-fulfillment center, dynamic reprogramming operative to alter contents of the function-identifier table.

2. The system according to claim 1, wherein the altered contents of the function-identifier table permit the communication device to respond to newly available services.

3. The system according to claim 1, wherein the altered contents of the function-identifier table modify a size of a multi-function code namespace.

4. The system according to claim 1, wherein the altered contents of the function-identifier table include additional non-numeric code prefixes.

5. The system according to claim 1, wherein one or more of the function identifier tables further comprises additional parameters associated with the type of service invocation.

6. The system according to claim 1, wherein the input sequence further comprises an input service code for identifying a service to be invoked with the service invocation.

7. The system according to claim 1, wherein the information transmission further comprises one or more of a function identifier, the input sequence, a mobile directory number (MDN), communication device brand, model type, electronic serial number (ESN), international mobile equipment identity (IMEI), screen size, location, owner or user subscription profile or user subscriptions.

8. A method for permitting a user to invoke a service with a communication device in a communication network, comprising:

programming the communication device with at least one function-identifier table containing one or more of a non-numeric code prefix or a service code for triggering service invocation;

receiving an input sequence at the communication device to identify a service invocation;

determining that a function identifier in the input sequence that includes a non-numeric code prefix identifies a service invocation corresponding to a function identifier stored in the function-identifier table;

in response to determining that the function identifier identifies the service invocation, transmitting information related to the service invocation to a service-fulfillment center,

wherein, during a communication between the communication device and the service-fulfillment center, the communication device receives dynamic reprogramming operative to alter contents of the function-identifier table.

9. The method according to claim 8, wherein the altered contents of the function-identifier table permit the communication device to respond to newly available services.

10. The method according to claim 8, wherein the altered contents of the function-identifier table modify a size of a multi-function code namespace.

11. The method according to claim 8, wherein the altered contents of the function-identifier table include additional non-numeric code prefixes.

12. The method according to claim 8, wherein one or more of the function identifier tables further comprises additional parameters associated with the type of service invocation.

13. The method according to claim 8, wherein the input sequence further comprises an input service code for identifying a service to be invoked with the service invocation.

14. The method according to claim 8, wherein the information transmission further comprises one or more of a function identifier, the input sequence, a mobile directory number (MDN), communication device brand, model type, electronic serial number (ESN), international mobile equipment identity (IMEI), screen size, location, owner or user subscription profile or user subscriptions.