Method and System for Extending the Use and/or Application of Messaging Systems

• US 20080305774A1
• Filed: 05/19/2006
• Published: 12/11/2008
• Est. Priority Date: 05/19/2005
• Status: Active Grant

• Current Assignee: Affle India Pvt Ltd.
• Original Assignee: Affle (India) Limited (Affle Global Pte Ltd.)
• Inventors: Ramakrishna, Madhusudana
• Granted Patent: US 8,050,694 B2
• Time in Patent Office: Days
• US Class Current: 455/412.1
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G07B 17/00 Franking apparatus printing aspects B41
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/65 Environment-dependent, e.g. using captured environmental data
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/185 by embedding added-value information into content, e.g. geo-tagging
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

A method for extending the use and/or application of messaging systems is disclosed. The method includes embedding non-standard data within a first portion of a header of a message, transmitting the message via the messaging system, and identifying the embedded non-standard data in the first portion of the header of the message and processing the message differently to messages without the non-standard data.

Claims

1. A method for extending the use and/or application of messaging systems including:

embedding non-standard data within a first portion of a header of a message;

transmitting the message via the messaging system; and

, identifying the embedded non-standard data in the first portion of the header of the message and processing the message differently to messages without the non-standard data.

2. A method as claimed in claim 1, wherein the messaging system comprises an SMS, MMS or EMS messaging system.

3. A method according to claim 1, further comprising setting a further portion of the header to a value causing at least part of said first portion of said header to be ignored by the messaging system.

4. A method according to claim 3, wherein said first portion of said header comprises a validity period field.

5. A method according to any claim 4, wherein said non-standard data comprises one or more of:

data operative to cause application of a different charging tariff to the message;

a charge to be raised against the account associated with the originating terminal of the message;

instructions for performance of an action authorized by the originator of the message;

a request for provision of a service to the originating terminal of the message.

6. A method as claimed in claim 4, wherein said non-standard data comprises a link to a record in a remote repository, the method further comprising accessing the remote repository via said link and determining said processing required in dependence on the record.

7. A method according to claim 6, wherein identifying the embedded non-standard data in the first portion of the header of the message and processing the message differently to messages without the non-standard data includes one of:

dropping the message;

replying to the originating terminal with an acknowledgement message; and

, performing an action with reference to the stated recipient of the message.

8. A method as claimed in claim 1, further comprising sending the message from a merchant, the non-standard data comprising a request for payment of a transaction and the transaction being at the request of the recipient of the message, wherein the step of identifying the embedded non-standard data in the first portion of the header of the message and processing the message differently to messages without the non-standard data further comprises identifying the request for payment of a transaction and prompting the recipient to authorize payment.

9. A method as claimed in claim 8, further comprising entering data via a secure terminal enabling the merchant to send the message.

10. A messaging system arranged to receive messages and monitor for non-standard data embedded within a predetermined first portion of headers of said messages, wherein upon detection of non-standard data in said first portion of a header, the messaging system is arranged to process said message differently to messages without said non-standard data.

11. A messaging system as claimed in claim 10, wherein the messaging system comprises an SMS, MMS or EMS messaging system.

12. A messaging system according to claim 10, further comprising setting a further portion of the header to a value causing at least part of said first portion of said header to be ignored by the messaging system.

13. A messaging system according to claim 12, wherein said first portion of said header comprises a validity period field.

14. A messaging system according to claim 13, wherein said non-standard data comprises one or more of:

data operative to cause said messaging system to apply a different charging tariff to the message;

data operative to cause said messaging system to raise a charge against the account associated with the originating terminal of the message;

instructions arranged to cause said messaging system to perform an action authorized by the originator of the message;

instructions arranged to cause said messaging system to provide a service to the originating terminal of the message.

15. A messaging system as claimed in claim 13, further comprising a remote repository, wherein said non-standard data comprises a link to a record in said remote repository, the messaging system being arranged to access the remote repository via said link and determine said processing required in dependence on the record.

16. A messaging system as claimed in claim 10, further comprising a merchant terminal and a user terminal, wherein upon performance of a transaction for said user, the merchant terminal is arranged to embed non-standard data comprising a request for payment of the transaction into the first portion of a header of a message and transmit said message to the user terminal, the messaging system being arranged to identify the embedded non-standard data in the first portion of the header of the message and prompt the user terminal for authorization to pay said transaction, wherein upon receipt of authorization to pay said transaction from said user terminal, the messaging system is arranged to charge an account associated with the user terminal.

17. A messaging system as claimed in claim 16, wherein said user terminal comprises a mobile telephone.

18. A messaging system as claimed in claim 16, wherein said merchant terminal further comprises a secure terminal arranged to accept an identifier identifying said user terminal, wherein the merchant terminal is arranged to transmit the message in dependence on the identifier.

19. A messaging system as claimed in claim 16, further comprising a remote profile system and a client application, wherein upon installation of the client application on the user terminal, the client application is arranged to obtain profile data and populate a profile record in said remote profile system for the user.

20. A messaging system as claimed in claim 19, wherein if said user terminal includes an image capture device, the client application is arranged to obtain an image of the user for said profile record, the merchant terminal being arranged to access said profile record and display an image of said user for authentication of the user during payment of said transaction