CA2406568A1 - Method and apparatus for a universal encoding template for sms ecommerce messaging - Google Patents
Method and apparatus for a universal encoding template for sms ecommerce messaging Download PDFInfo
- Publication number
- CA2406568A1 CA2406568A1 CA002406568A CA2406568A CA2406568A1 CA 2406568 A1 CA2406568 A1 CA 2406568A1 CA 002406568 A CA002406568 A CA 002406568A CA 2406568 A CA2406568 A CA 2406568A CA 2406568 A1 CA2406568 A1 CA 2406568A1
- Authority
- CA
- Canada
- Prior art keywords
- message
- sms
- messages
- encoding
- template
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims description 56
- 238000012545 processing Methods 0.000 claims abstract description 58
- 230000005540 biological transmission Effects 0.000 claims abstract description 26
- 230000004044 response Effects 0.000 claims description 181
- 238000012790 confirmation Methods 0.000 claims description 27
- 238000012384 transportation and delivery Methods 0.000 claims description 18
- 238000003780 insertion Methods 0.000 claims description 8
- 230000037431 insertion Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 5
- 238000013500 data storage Methods 0.000 claims description 4
- 230000003287 optical effect Effects 0.000 claims description 3
- 230000009471 action Effects 0.000 description 27
- 230000008569 process Effects 0.000 description 26
- 238000013480 data collection Methods 0.000 description 22
- 238000010586 diagram Methods 0.000 description 18
- 230000007246 mechanism Effects 0.000 description 14
- 238000013479 data entry Methods 0.000 description 13
- 239000000284 extract Substances 0.000 description 13
- 238000004891 communication Methods 0.000 description 11
- 238000013507 mapping Methods 0.000 description 11
- 239000008186 active pharmaceutical agent Substances 0.000 description 8
- 230000008901 benefit Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000010200 validation analysis Methods 0.000 description 4
- 230000006872 improvement Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000005267 amalgamation Methods 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000035515 penetration Effects 0.000 description 2
- XRIWLEWQNCECEP-UHFFFAOYSA-N 3-methyl-3-nitrososulfanyl-2-(propanoylamino)butanoic acid Chemical compound CCC(=O)NC(C(O)=O)C(C)(C)SN=O XRIWLEWQNCECEP-UHFFFAOYSA-N 0.000 description 1
- 101100060915 Haemophilus influenzae (strain ATCC 51907 / DSM 11121 / KW20 / Rd) comF gene Proteins 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013502 data validation Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000005755 formation reaction Methods 0.000 description 1
- 239000003112 inhibitor Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- JILPJDVXYVTZDQ-UHFFFAOYSA-N lithium methoxide Chemical compound [Li+].[O-]C JILPJDVXYVTZDQ-UHFFFAOYSA-N 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 238000012367 process mapping Methods 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 108090000623 proteins and genes Proteins 0.000 description 1
- 235000002020 sage Nutrition 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Economics (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a SMS universal encoding template for encoding outbound SMS business messages for a data processing system for transmission over a network; including the categorization meta data defining a categorization of outbound SMS messages; the categorization representing a specific business intended usage; the categorization meta data providing definitions of messages and instructions that are parsable by the data processing system for generating SMS business messages.
Description
METHOD AND APPARATUS FOR A UNIVERSAL ENCODING TEMPLATE FOR
SMS ECOMMERCE MESSAGING
Background of the Invention Field of the Invention This invention relates to the field of wireless ecommerce communication, more particularly to methods and apparatus for applying Short Message Services and other messaging s~;,rvices used in mobile wireless communication to commercial messaging.
General Background Mobile commerce offers convenience to users such that they can perform business transaction, anytime, anywhere. Though Wireless Application Protocol (W.AP) has been around for several years, the market penetration of WAP enabled cell phones, and other such web enabled vrireless devices still remains quite low. The most established technology in the space of mobile commerce today is Short Message Services (SMS) on mobile wireless devices.
With SMS's high penetration and adoption rate in the market, it has been a prime target for mobile commerce usage.
Examples of SMS notification with commerce functions contemplated by the present invention include the following:
2o marketing driven message to user: e.g. discount information, promotion and other commerce campaign information;
notification for business events: e.g. order received confirmation, shipping confirmation; and, notification for operational efficiency like payment due, or other deadline driven type reminders.
However, various intrinsic technical hurdles and limitations exist in SMS
today, thus making its application and usage in commerce web application difficult and impractical.
We have determined a number of limitations of prior art technology and determined a number of useful requirements for the use of SMS messaging in business environments. A
discussion of these limitations and requirements follow.
1. Limitations of Using SMS in Commerce Transactions T'he absence of the concept of semantics in SMS make SMS usage in commerce application difficult. The difficulty lies in:
C'A9-2002-0074 the encoding of the SMS message to accurately implement a given business purpose; and, the corresponding run time handling of the SMS message as the business purpose requires.
1.1 Encoding Barriers SMS messages, by nature are typeless, stateless, sessionless and meaningless to data processing systems. Currently the main purpose of SMS messaging is person to person communication between mobile devices.
However, for SMS messages to be viable as means of business transactions, SMS
cannot be just a casual exchange of two parties. Business transaction requirements include: traceability, confirmation, and non-repudiation. It also has to be understood by any web application or other to data processor that handles it. We collectively define these requirements as the 'semantics' of SMS
messaging.
For example:
~ A given set of business rules may require that a subset of SMS messages be confirmed on delivery for non-repudiation of transactions such as:
i. confirmed arrival ii recorded timestamp of arrival for non-repudiation iii acknowledgment of reception of SMS messages ~ It may also be a business requirement that a given set of SMS messages are to be regularly delivered based on a given schedule. Examples include:
i monthly reminders of invoices ii scheduled promotions via SMS messages ~ Broadcasti~YType SMS messages may be required by businesses to reach multiple users without the need of checking or confirming message arrival. Examples include:
i. Store wide promotional broadcasts.
In this case acknowledgment would likely not be required.
~ When a user wants to send in a SMS message to make a transaction, the intent of the user (e.g. to buy an given item) as encoded in the SMS message text has to be unambiguously understood by a web application or other application that handles the user's incoming SMS
message.
C'A9-2002-0055 2 Cowectly encoding SMS messages to accurately represent business intent is a technically complex and difficult task and is highly prone to human error. Human errors in encoding are often very expensive and difficult to debug and correct. Business users want efficiency and reliability in s using SMS to achieve their business objectives. They require sheltering from such technical complexity when using SMS messages in their business processes. Business users typically only want to focus on:
i. Determining the business intent of a given SMS message;
ii. Forming the correct wording of the message (without worrying to about the different technical details of encoding); and, iii. Being informed of error if the message sent does not meet the intent of that message classification.
Business users who initiate these business transactions now face the significant technical 1s challenge of manually encoding all of these SMS messages correctly so that they map accurately to the particular different business objectives that they set out to achieve.
1.2 Difficulty in Semantic Handling at Run Time Apart from the manual, technical challenge in SMS message encoding, semantic handling 2o at run time to meet business process requirements is also a major problem.
For example, a SMS message notifying a user of an outstanding payment typically requires the acknowledgment of the user, as stipulated by a business process that defines "a completed customer touch point".
The lack of acknowledgment by the user upon receiving the SMS message in this case will 2s be handled differently than other SMS message.
However, the concept of semantics and categorization does not presently exist in the space of SMS today.
1.3 The Absence of Syntax in SMS Messages makes Its Usage in Commerce Business 3o Processes Difficult and Impractical 1.4 Lack of Mapping of SMS Text Stream to a Commerce Business Action SMS messages are simple text messages without any encoding scheme. Thus, a simple C'A9-2002-0074 3 plain text SMS message is unsuitable for commerce transactions for the following reasons in addition to the ones mentioned above:
It's not currently possible for a simple SMS message to indicate the type of commerce transaction to be carried out;
ii. Additional parameters required by a particular transaction cannot be encoded in a standard manner and hence, cannot be parsed by the backend commerce application;
iii. Additional details like user authentication and authorization can not be taken care of in a standard manner;
to iv. Lack of state information means request-response model required by commerce transactions can not be applied to commerce SMS messages; and, v. Free form composing of 160 characters as responses by human users makes the adoption impossible and impractical.
The above problem creates a serious usability issue for SMS users (both human and web application) who need to respond to business messages originated from a Web Application or other data processing application.
1.5 Lack of Notation for Parameters Encoded as Part of the SMS message All inbound SMS messages carrying transaction information are required to be validated 2o for data completeness and data validity. Not only that, users sending SMS
messages to a given web application are required to encode enough information in the inbound SMS
messages for proper authentication.
For example, using SMS in online auction requires that the backend web application used to communicate to bidders notify the subscribed bidders whenever an auction bidder has been outbid by someone else. Bidders, upon notification, should be given a mechanism to respond in order to raise their bids.
In this example, the SMS message is required to be sent in a non-repudiated manner so that the subscribed bidders can't deny receipt of auction override notices. Also such messages must be sent out via a high priority channel, if available, so that they can reach the bidders as soon as 3o possible. In addition, the auction bidders are required to have a mechanism to call back the backend commerce application being used in the auction to submit a new bid using a standard SMS message template acceptable to the backend commerce application. These SMS
messages must be parsed correctly by the backend commerce application in order for the backend web C'A9-2002-(1074 application to perform the appropriate semantics.
As an example, one of the required parameters in an auction scenario would be an SKU
number for the identification of item under bid. Both back end server and bidder authentication is required for non-repudiation purposes.
The lack of syntax in SMS messaging makes application to the following business processes extremely difficult:
commerce process mapping;
user authentication;
parameter passing;
to data validation.
1.6 Technical Complexities in encoding SMS deter Business Users from adopting its usage The originators of business SMS messages are business users who have business needs to send business messages. Their prime concern is to focus on the business logistics of the message (like the timing of sending, to whom to send the message to etc.) and the message itself (like the choice of wordings etc.). They do not want to be (and typically cannot afford to be) burdened with the technology of the delivery medium. For example, the technical knowledge of how to send a SMS message is something that the business users do not want to deal with and expect to be handled for them. Transparency and user friendliness is important to a business user.
1.7 The Requirement of Confirmation in Commerce Usage A key requirement of to use SMS in commerce is the need for confirmation from SMS
message recipients. The following is a list of examples for such critical requirements in SMS usage in commerce:
- Upon receiving a SMS notification from the commerce server, often the recipient needs to respond by sending an SMS message back to the commerce server. For example:
the recipient may send an SMS message back to the commerce server to buy an item advertised by an SMS promotion message.
- '7,o fulfill the non-repudiation requirement, for example: all customer touch points need to be recorded.
- C'.onfirmation also requires the confirmation of user ID in an inbound message.
C',A9-2002-0074 5 L.8 The Requirement of Security in Commerce Usage Another key requirement for using SMS in commerce is the need for security in carrying out a business transaction. This requirement includes:
~ User ID authentication by a web application like WebSphere when a user initiates a transaction using SMS message ~ Web application authentication by the user so that the user knows for sure that the correct Web application is handling the user's request ~ User authentication to condinn that no unauthorized mobile device is used for the o transaction; a PIN could preferably be used as an additional layer of user confirmation.
1.9 The Requirement of Session in Commerce Usage Another key requirement of using SMS in commerce is that of the session.
Often, when a web application sends out an outbound message to its users (e.g. campaign message like 'all electronics 50% off if purchased in the next 6 hours), the web application used expects the user to respond back in SMS to the corresponding outbound message within the specified time period.
Typically, this requirement of session includes:
~ A request and response model mapping to outbound and inbound SMS messages;
~ A time out mechanism; and, ~ A Session Data sharing mechanism.
One of the major inhibitor of using SMS in commerce application, is the difficulty in encoding SMS message to accurately implement a given business purpose with the corresponding run time handling matching the intended semantics. Examples of various semantics in SMS
usage in 2s commerce application includes scheduled sent message; confirmation for non-repudiation;
response required message etc.
The fundamental short coming of using Short Message Services in commerce application is the difficulty in encoding with the complexity accurately matching the business intend of the SMS
message sent / received by the commerce web application.
Summary of the Invention The various embodiments and features of the invention herein address shortcomings and requirements outlined above, with particular embodiments having specific features addressing selected shortcomings or requirements as will be appreciated liom the summary of the invention which follows.
One embodiment of the invention provides a universal encoding template that could be used in SMS for encoding outbound business messages for a data processing system for transmission over a network; including the categorization meta data defining a categorization of outbound messages; the categorization representing a specific business intended usage; the categorization meta data providing definitions of messages and instructions that are parsable by t0 the data processing system for generating business messages.
Another embodiment of the invention provides extensible syntactic rules for encoding and decoding SMS message. It also provides extensible semantics for the interpretation and handling of the encoded SMS messages in accordance with encading characteristics in corresponding message types.
Another embodiment of the invention of the SMS universal encoding template provides a message entry field for insertion of a message entry; with the template providing an additional field in the SMS message for categorization of meta data; the meta data providing instructions for encoding a business intent for an commerce SMS message. The meta data may preferably include instructions for dispatching the SMS message including instructions selected from message priority; delivery time; number of recipients; delivery channel etc. The meta data preferably includes instructions for identifying the web application to handle the response.
Another embodiment of the invention of the SMS universal encoding template is adapted to create a typed SMS message instance indicating that a response is required.
The encoded inbound message template enables the unambiguous interpretation of an inbound SIVIS message, leading to unambiguous mapping to a selected business action of a web application of the messaging system.
The predefined categorization of the invention serves as a contract between the user and the web application of the business process so that the interpretation of a given SMS message is unambiguous.
The inclusion of the inbound message template in the outbound message so a user does not need to formulate an inbound message is new to SMS. With this embodiment of the invention, a user only needs to fill in specific required parameters.
C'A9-2002-0074 Another embodiment of the invention provides a SMS commerce message format for use in sending a commerce message over a network to a recipient, which includes a message text entry field for alerting a recipient about a commerce event; an encryption string entry field; a response indicator label; a recipient data entxy field associated with the response indicator label; a recipient authentication indicator label; and, a recipient authentication data entry field associated with the recipient authentication indicator label.
Preferably the encryption string entry field is adapted to accept communication session identification data.
The encryption string entry field may be adapted to accept security information.
l0 The recipient authentication data entry field may be adapted to accept a PIN number from the recipient.
Another embodiment of the invention provides a SMS commerce message format for use in sending an ecommerce message over a network to a recipient including a message text entry field for alerting a recipient about an ecommerce event; an encryption string entry field for security and session control; a response indicator label; a recipient data entry field associated with the rcaponse indicator label; a recipient authentication indicator label; and, a recipient authentication data entry field associated with the recipient authentication indicator label.
Another embodiment of the invention provides a SMS commerce message format for use in sending a commerce message over a network to a recipient including a message text entry field for alerting a recipient about a commerce event; and, an encryption string entry field.
The encryption suing entxy field may be adapted to accept communication session identification data. The encryption string entry field may be adapted to accept security data.
The recipient authentication data entry field may be adapted to accept a PIN
number from the recipient.
Another aspect of the invention provides a SMS commerce message format for use in sc,nding an ecommerce message over a network to a recipient including a message text entry field for alerting a recipient about an ecommerce event; and, an encryption string entry field for security a~zd session control.
Preferably the session identification data may be used to associate a response to the sent message.
The session identification data may be used to identify a software application to process a response to the sent message.
Another embodiment of the invention provides a SMS commerce message for transmission CA9-2002-0074 s over a network to a recipient including a message text for alerting a recipient about a commerce event; an encryption string entry; a response indicator label; a recipient data entry associated with the response indicator label; a recipient authentication indicator label; and, a recipient authentication data entry associated with the recipient authentication indicator label.
The encryption string entry may include communication session identification data.
Preferably the encryption string entry includes security information.
The recipient authentication data entry may include a PIN number from the recipient.
Another embodiment of the invention provides a SMS commerce message for use in sending an ecommerce message over a network to a recipient including a message text entry for l0 alerting a recipient about an ecommerce event; an encryption string entry for security and session control; a response indicator label; a recipient data entry associated with the response indicator label; a recipient authentication indicator label; and, a recipient authentication data entry associated with the recipient authentication indicator label.
Another embodiment of the invention provides a SMS commerce message for use in sending a commerce message over a network to a recipient including a message text entry for alerting a recipient about a commerce event; and, an encryption string entry.
The encryption string entry may include communication session identification data.
The encryption string entry may advantageously include security data.
The recipient authentication data entry may include a P1N number from the recipient.
Another embodiment of the invention provides a SMS commerce message for use in sending an ecommerce message over a network to a recipient including a message text entry for alerting a recipient about an ecommerce event; a.nd, an encryption string entry for security and session control.
The ,session identification data may be used to associate a response to the message with the message.
The session identification data may be used to identify a software application to process a response to the message.
Another embodiment of the invention provides a method for processing an incoming ecommerce SMS response message received by a server from a recipient responding to an outgoing ecommerce SMS message, including receiving the SMS response message;
decoding an encryption string within the SMS response message with an appropriate key to verify that: the response message is directed to the server; extracting identification from the SMS
response message for processing information in the response; identifying and obtaining a corresponding inbound template for the response message from the server;
parsing the response message with the inbound template to extract data and instructions contained in the response message, if any, for processing the data and instructions.
Still another embodiment of the invention provides a method for processing an incoming ecommerce SMS response message received by a server from a recipient responding to an outgoing ecommerce SMS message, including receiving the SMS response message;
decoding an encryption string within the SMS response message with an appropriate key used to encode the outgoing ecommerce SMS message to verify that the response message is directed to the server; extracting identification from the SMS response message for processing information in the response; identifying and obtaining a corresponding inbound template for the response message from the server; parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message;
and forwarding the data and instructions to an application server for processing.
Anc>ther embodiment of the invention provides a method for handling an incoming ecommerce SMS response message received by a ecommerce server from a recipient responding to an outgoing ecommerce SMS message; wherein the response message includes:
an encryption string encoded with an encoding key, identification of a software application capable of processing the response, and user authentication information; tile method including receiving the SMS
message; decoding an encryption string within the SMS message with an encoding key previously 2o used to encode the corresponding outgoing ecommerce message to verify that the response message is directed to the ecommerce server; extract identification from thf:
SMS response for a software application intended to process information in the response; identify and obtain a corresponding inbound template for the response message from the ecommerce server;
parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message; and forwarding the data and instructions to the software application for processing.
Yet another embodiment of the invention provides a method for handling an incoming ecommerce SMS response message received by a ecommerce server from a recipient responding to an outgoing ecommerce SMS message, wherein the response message includes an encryption 3o string encoded with an encoding key used to encode the corresponding outgoing ecommerce rr~essage, identification of a software application capable of processing the response, and user authentication information, and wherein the ecommerce server has access to the encoding key, and an inbound template for processing an incoming SMS response message;; the method CA9-2002-0074 t o including:
receiving the SMS message; decoding an encryption string within the SMS
message with the encoding key to verify that the response message is directed to the ecommerce server;
extract identification from the SMS response for a software application intended to process information in the response; identify and obtain a corresponding inbound template for the response message from the ecommerce server: parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message;
amd forwarding the data and instructions to the software application for processing.
Another embodiment of the invention provides a method for handling an incoming 1o ecommerce SMS response message received by a ecommerce server from a responding recipient, including receiving the S1VIS message; decoding an encryption string within the SMS message vvith a systemwide encoding key previously used to encode the corresponding outgoing ecommerce message to verify that the response message is directed to the ecommerce server;
extracting identification from the SMS response for a software application intended to process information in the response; identifying and obtaining a corresponding inbound template for the response message from the ecommerce server; parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message; and forwarding the data and instructions to the software application for processing.
2o Yet another embodiment of the invention provides a method for handling an incoming ecommerce SMS response message received by a ecommerce server from a recipient responding to an outgoing ecommerce SMS message; wherein the response message includes:
an encryption string encoded with session id, and identification of a software application capable of processing the response; the method including receiving the SMS message; decoding an encryption string within the SMS message to verify that the response message is directed to the ecommerce server;
extracting identification from the SMS response for a software application intended to process information in the response;
identifying and obtaining a corresponding inbound template for the response message from the ecommerce server; parsing the response message with the inbound template to extract data and 3o instructions including user authentication information from the response message; and forwarding the data and instructions to the software application for processing.
In another embodiment of the method of the invention the encryption string is encoded with an encoding key, identification of a software application capable of processing the response, CA9-2002-0074 t 1 and user authentication information; the method including receiving the SMS
message; decoding an encryption string within the SMS message with an encoding key previously used to encode the corresponding outgoing ecommerce message to verify that the response message is directed to the ecommerce server; extract identification from the SMS response for a software application intended to process information in the response;
identify and obtain a corresponding inbound template for the response message from the ecommerce server; parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message; and forwarding vthe data and instructions to the software application for processing.
Preferably the processing of the software application includes using the session id to match the response with a outbound SMS message.
Another embodiment of the invention provides a SMS universal encoding template for encoding outbound SMS business messages for a data processing system for transmission over a network; including categorization meta data defining a categorization of outbound SMS messages;
the categorization representing a specific businesses intended usage;
the categorization meta data providing definitions of messages and instructions that are parsable by the data processing system for generating SMS business messages.
Another embodiment of the invention provides a SMS universal encoding template for use by a message encoding engine of an ecommerce server for encoding outbound SMS
messages from a web application to a SMS dispatcher (runtime processor) for transmission over a wireless network; including categorization meta data defining categorizations of outbound SMS messages;
each of the categorizations representing a specific businesses intended usage;
the categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding SMS business messages for handling by the SMS dispatcher for transmission over the wireless network.
In another embodiment of the invention the SMS universal encoding template provides a message entry field for insertion of a message entry of full SMS message length for access by a recipient; with the template providing an additional field in the SMS message for categorization meta data; the meta data providing instructions for encoding a business intent of an ecommerce 3o SMS message.
The meta data may preferably include instructions for dispatching the SMS
message including instructions selected from the following set pertaining message priority, delivery time, number of recipients, delivery channel, confirmation, authentication, encryption, intended web CA9-2002-0074 ~ 2 application to handle a response.
The meta data preferably includes instructions for identifying a software application intended to handle the response.
Another embodiment of the invention provides apparatus for generation of a SMS
business message processable by a software application, including a data collection interface for accepting instructions and data from the software application;
a rr~essage encoding engine; an encoding template accessible by the message encoding engine; the message encoding engine being adapted to encode the instructions and data from the software application using the encoding template to generate categorized SMS
messages 1o formatted for processing by a data processing system; and, a dispatcher runtime processor linked 1:o the message encoding engine for accepting the categorized SMS messages and processing the categorized SMS messages for transmission over a network to a recipient.
Yet another embodiment of the invention provides apparatus for generation of a SMS
business message for a software application, including a data collection interface for accepting instructions and data from the software application; a message encoding engine; a universal encoding template accessible by the message encoding engine;
the message encoding engine being adapted to encode the instructions and data from the software application using the universal encoding template to generate typed (categorized) SMS
messages that can be processed by a data processing system;
2o a runtime dispatcher processor linked to the message encoding engine for accepting the typed SMS messages and adapted to process the typed SMS messages for dispatch over a network to a recipient.
Another embodiment of the invention provides apparatus for generation of a SMS
business message for a software application, including: data interface means for accepting instructions and data from the software application; message encoding means;
encoding template means accessible by the message encoding means; the message encoding means being adapted to encode the instructions and data from the software application using the encoding template means to generate categorized SMS messages that can be processed by a data processing system; and, a processor linked to the message encoding means for accepting 3o the categorized SMS messages and adapted to process the categorized SMS
messages for transmission to a recipient.
The apparatus of this embodiment may advantageously provide a response tracking database associated with the dispatcher for tracking incoming responses from recipients receiving C.A9-2002-0074 t 3 the SMS business messages.
The apparatus may further include an inbound template database associated with the runtime dispatcher for identifying and parsing an inbound response from a SMS
message recipient for processing by the dispatcher and forwarding to the software application originating the SMS
business message for processing by the software application.
In another embodiment of the invention, the apparatus further includes a commerce user interface including a message composing user interface having: labeled fields for insertion of messages by a user to a recipient and instructions processable by the message encoding engine and runtime processor to generate a SMS business message for transmission to a recipient.
to The apparatus may further include a commerce user interface for creating a new SMS
message type derived fiom the universal encoding template; the corrunerce user interface including labeled fields describing a parent message type; providing labeled fields for defining variations on the parent message type; means for labeling the derived message type; and, apparatus or software for saving the labeled derived message type and adding to the universal template.
Preferably the universal encoding template is adapted to create a typed SMS
message instance indicating that a response is required; the runtime processor being adapted to create an outbound SMS message with a confirmation indicator label with a confirmation field for a recipient to enter a response in a response SMS business message; the runtime dispatcher being adapted to store a response from the recipient in the response tracking database, and forward 2o response message data and instructions to the software application indicating that a response was received.
The runtime dispatcher may be adapted to store data in the response tracking database upon elapse of a predetermined response time without receiving a response, indicating absence of a response; and to send an alert to the software application indicating absence of a response.
An encryption processor may be provided for generating an encryption string for the SMS
business message.
The encryption processor is preferably adapted to generate an encryption string including entries for at least one of the following: session identification, security, a software application for processing a response to the message.
An application key generator may be provided to use an encryption key for generating the encryption string.
Another embodiment of the invention provides an SMS commerce message response including an encryption string field for security and session control; a response indicator label; a C.A9-2002-0074 recipient data entry field associated with the response indicator label in which a response can be inserted by a responding recipient; recipient authentication indicator label;
and, a recipient data entry field associated with the authentication indicator label in which a response can be inserted by a responding recipient.
The SMS commerce message response may further include a short message text field for alerting a recipient about a commerce event.
The encryption string field may preferably be adapted to include security information.
The encryption string field may be adapted to include session control information.
The SMS commerce message response encryption string may include session control information.
Yet other aspects of the invention provide a computer programming for implementing the methods and apparatus of the embodiments of the invention described above.
Other aspects of the invention provide an article including:
a computer readable signal bearing medium; with computer program code means recorded on the medium adapted to perform the methods of the embodiments of the invention and implement the apparatus of the embodiments of the invention.
The medium may be selected from the group consisting of magnetic, optical, biological, and atomic data storage media. The medium may be a modulated carrier signal.
The signal may be a transmission over a network such as a computer network, telecommunication network, or the 2o Internet.
Description of the Drawings Embodiments of the present invention will be described by way of example, referring to the accompanying drawings in which:
Figure 1 depicts an SMS enabled Commerce: Highlighting improvement over pre-existing system;
Figure 2 depicts a Structure Mapping of the SMS commerce Infrastructure Components;
Figure 3 depicts using SMS Message Composing Wizard To Create New SMS Type In S1VIS Universal Encoding Template;
3o Figure 4 depicts using The SMS Message Composing GUI To create new SMS
type;
Figure 5 depicts an SMS Encoding Flow Diagram;
Figure 6 depicts an SMS Message Encoding Engine DCI Structure Diagram;
Figure 7 depicts an SMS Message Encoding Engine Flow Diagram;
CA9-2002-0074 ~ 5 Figure 8 depicts an actual Outbound SM:S message example as seen by a recipient user;
Figure 9 depicts an SMS Inbound Message with user response filled in;
Figure 10 depicts a GUI to compose a SMS message;
Figure 11 depicts adding SMS Inbound Template to the message type;
Figure 12 depicts an inbound Template Manager Structure Diagram:
Figure 13 depicts the Flow For the Inbound Template Management;
Figure 14 depicts Structure Diagram For Business User Sending SMS Message;
Figure 15 depicts a Flow chart for Figure 16;
Figure 16 depicts Confirmation Response Run Time Flow;
1 o Figure 17a depicts an Outbound F low Diagram 1;
Figure 17b depicts an Outbound Flow Diagram 2;
Figure 17c depicts an Outbound Flow Diagram 3;
Figure 18a depicts an Inbound flow Diagram 1;
Figure 18b depicts an Inbound Flow Diagram 2; and Figure 18c depicts an Inbound Flow Diagram 3.
Detailed Description of Preferred Embodiments of the Invention The following description is presented to enable those skilled in the art to understand and apply the invention. Various modifications to the embodiment or embodiments described will be 2o apparent to those skilled in the art. The invention may be applied to other embodiments without departing from the scope of the invention. The present invention is not intended to be limited to the embodiment or embodiments shown.
Figure 1 illustrates an SMS enabled eCommerce system highlighting the improvements of the invention over pre-existing systems. The improvements contributed by the invention herein are indicated by shading.
As indicated previously SMS is not new. Referring to Figure 1, which depicts an SMS
enabled Commerce communication system in accordance with the invention, it can be seen that existing technology lies in space labeled prior art. In the past there were attempts to solve the issue of routing SMS messages to appropriate applications running on the mobile devices (e.g. cell phones).
The space labeled 'New Invention' in Figure 1 is new with the exception of a few basic building blocks that exist today. Although some of the basic building blocks may exist the invention herein allows enhancement of them as appropriate to take into account new capabilities CA9-2002-Ot)74 offered by the invention. New elements contributed by the invention are highlighted in gray while prior art elements are the not highlighted.
Referring to the embodiment of the invention illustrated in Fig. 1, it can be seen that c;Commerce Server 104 is comprised of a number of components:
Application Components 108: Application components 108 form the business subsystems of a given commerce server. Each business subsystem is an implementation of a given business processes. Examples of business subsystems include: Order Management; User Management;
1'~Iarketing and Campaign subsystems, among others.
Common Message Subsystem 107: The Common Message Subsystem 107 is a generic message handling system to handle (and process) messages generated by the application components 108. The common message subsystem handles emails, file transport and other matters pertaining to handling and processing messages.
The embodiment of the invention illustrated in Fig. 1 makes use of a number of existing futures or processes including:
SMS messages: An SMS message is limited to a maximum 160 character long simple text message. It can be sent through many wireless networks. Most cellular phones are capable of sanding and receiving SMS messages.
Wireless Message Gateway: A wireless message gateway can be implemented by a computer which can route SMS messages between a wireless network and the eCommerce server 104.
SMS Center: The SMS Center 102 is typically operated by the telecommunication company to handle the delivery of SMS messages to selected mobile devices.
Data Collection Interface (#1): The Data Collection Interface 117 is comprised of a set of interfaces that collect i. user input via SMS Message Composing Wizard 112; and, ii, data generated by the Application Components 108 forwarded by the 3o Common Message Subsystem 107 to generate an SMS input data collection to be used by the Message Encoding Engine 111.
C.A9-2002-0074 17 Message Encoding Engine (#2): The message encoding engine 111, takes an input data collection, as generated by the Data Collection Interface 117, as input.
The message encoding engine 111 then uses the data in the SMS input data collection to generate the encoding of an SMS message with attributes appropriate to the user selected SMS
type. It further validates the user input against the SMS Universal Encoding template 113 for error checking.
This automatic generation capability in the engine 111 eliminates encoding errors, likely due to human mistakes. This also hides the technical complexity of the encoding of attributes for the implementation of message intent from business users. The Message Encoding Engine 111 produces a 'Typed SMS Message instance 114 as output.
Runtime Processor (#3): The SMS Message Runtime Processor 110 handles business semantics as defined in SMS categorization at run time Basic Functions of the run time processor 110:
- If an SMS message requires confirmation of delivery, or expected response, the SMS
Message Runtime Processor 110 will keep track on the confirmation.
- T he SMS Runtime Processor 110 is also responsible for taking the response returned from an end user and locating the corresponding inbound message template from the inbound template database I 1 ~.
- If the SMS message is a scheduled message, the SMS Message Runtime Processor will handle the scheduling of the SMS message sent.
- Further semantic action can be taken in the absence of user confirmation.
- The runtime processor also does runtime error checking and error handling.
S1VIS Message Composing Wizard (#4): Referring to Fig. 2 which illustrates the structural mapping of an SMS Commerce Infrastructure system in accordance with an embodiment of the invention the SMS Message Composing Vdizard 112 guides a user to articulate the intended usage of the message. SMS Message Encoding Engine 111 uses the user input to generate an SMS
message by mapping the user input into a selected predefined type in a SMS
categorization template 113 as follows:
The Message Composing Wizard 112 takes the user input and invokes the Data Collection Interface 117 which in turn produces an appropriate SMS input data collection.
ii. In the event that user has defined a new SMS categorization via the Message Composing Wizard 112, the Message Composing Wizard 112 will then also update the SMS Universal Encoding Template 113.
iii. 1:n the event that the business user defines an SMS message that has the associated required response from the end user, the business user will define the required response to as required and understood by the application components 108 in the form of template via the Message Composing Wizard 112. I'he Message Composing Wizard 112 will take this input and update the Inbound Template Database (part #9) 115 (see Fig. l ).
SMS Universal Encoding Template (#5): The SMS Universal Encoding template 113 contains the meta data that defines the categorization (or 'type') of outbound and inbound SMS messages.
Each SMS categorization represents a given business intended usage. It provides definition of semantics for encoding as well as for run time.
With. this well defined SMS message categorization, automatic SMS generation with proper encoding reflecting the intended usage is now made possible. Additional SMS message categorization can be further derived from the existing types.
2o This entity provides an important aspect of this invention as it provides the mechanism for semantic definition and handling, making proper semantic handling in SMS now possible.
With the SMS Universal Encoding Template 113, a business user can define a new SMS
message type without any code changes in the Message Encoding Engine 111 and the Run Time Processor 110, making both components generic.
Typed SMS Message Instances (#6): Typed SMS Message Instances 114 are generated by the Message Encoding engine 111, to be used by the Run Time Processor 110.
Am example of a Typed SMS Message Instance follows:
CA9-2002-0074 t 9 <GenericSMSMessage>
<short message text>SOmething</short message text>
<ReceiverProfile>
<userid>steve</userid>
<cellphonenumber>416123456'7@cellphone.com</cellphonenumber>
<deliverychannel>SMTP<%del.iverychannel>
</Re:ceiverProfile>
</GenericSMSMessage>
S~MS Response Tracking DB (#7): The SMS Response Tracking Database 116 captures all Response Required messages as required by their encoded type. This enables the runtime processor 110 to ensure that required response messages receive expected responses and perform proper run time processing. This also enables the base mechanism to handle system expected user initiated inbound messages.
Inbound Template Database (#8): Inbound Template Database 115 stores all business user specified inbound message templates.
Flow Annotation from Figure 1: The formation, processing, and communication of SMS
messages in accordance with the embodiment of the invention depicted are indicated by z0 alphanumerically labeled arrows indicated in Fig. 1. Fig. 2 presents a structural mapping of an SIvIS commerce system in accordance with Fig. 1. An appreciation of the invention can be achieved by reading the description below while referring to Figures 1 and 2.
A1: A business user 105 making use of common user interface 106 invokes the SMS Message Composing Wizard (#4) 112 in order to prepare a message B1: The business user uses the Message Composing Wizard 112 to send a SMS
message based on existing type as defined in the SMS Universal Encoding Template ~#5) 113.
A2: The Wizard 1 I2 captures all the user input and calls the Data Collection Interface (#1 ) 117.
B2: The business user uses the SMS Message Composing Wizard 112 to define a new SMS
message type.
A3: The business user uses the Wizard 112 to define a pre-set user response by creating a new s inbound template. The Wizard I 12 updates the Inbound Template DB (#8) I 15.
C1: Message Encoding Engine (#2) 111 - retrieves (C 1 ) the SMS (Jniversal Encoding Template (#5) I I 3;
validates data captured by Data Collection Interface (#1) 117 against the SMS
Universal Encoding Template 113 and performs error checking.
C2: Message Encoding Engine 111 generates a Typed SMS Message Instance (#6) 114 as output. Referring to Fig. 2 the message can be an XML encoded massage 201.
D2: Message Encoding Engine 111 invokes the Runtime Processor (#3) I 10 which retrieves the generated Typed SMS Message Instance 114 generated in C2.
D3: If a user response is required in this SMS message type, the Run Time Processor 110 will is register this message as one which required user response by updating the SMS Response Tracking DB (#7) 116.
D4: The Run Time Processor 110 transmits this Typed SMS Message Instance 114 to the Wireless Message Gateway 103, referred to as the everyplace wireless gateway 203 in Fig.
SMS ECOMMERCE MESSAGING
Background of the Invention Field of the Invention This invention relates to the field of wireless ecommerce communication, more particularly to methods and apparatus for applying Short Message Services and other messaging s~;,rvices used in mobile wireless communication to commercial messaging.
General Background Mobile commerce offers convenience to users such that they can perform business transaction, anytime, anywhere. Though Wireless Application Protocol (W.AP) has been around for several years, the market penetration of WAP enabled cell phones, and other such web enabled vrireless devices still remains quite low. The most established technology in the space of mobile commerce today is Short Message Services (SMS) on mobile wireless devices.
With SMS's high penetration and adoption rate in the market, it has been a prime target for mobile commerce usage.
Examples of SMS notification with commerce functions contemplated by the present invention include the following:
2o marketing driven message to user: e.g. discount information, promotion and other commerce campaign information;
notification for business events: e.g. order received confirmation, shipping confirmation; and, notification for operational efficiency like payment due, or other deadline driven type reminders.
However, various intrinsic technical hurdles and limitations exist in SMS
today, thus making its application and usage in commerce web application difficult and impractical.
We have determined a number of limitations of prior art technology and determined a number of useful requirements for the use of SMS messaging in business environments. A
discussion of these limitations and requirements follow.
1. Limitations of Using SMS in Commerce Transactions T'he absence of the concept of semantics in SMS make SMS usage in commerce application difficult. The difficulty lies in:
C'A9-2002-0074 the encoding of the SMS message to accurately implement a given business purpose; and, the corresponding run time handling of the SMS message as the business purpose requires.
1.1 Encoding Barriers SMS messages, by nature are typeless, stateless, sessionless and meaningless to data processing systems. Currently the main purpose of SMS messaging is person to person communication between mobile devices.
However, for SMS messages to be viable as means of business transactions, SMS
cannot be just a casual exchange of two parties. Business transaction requirements include: traceability, confirmation, and non-repudiation. It also has to be understood by any web application or other to data processor that handles it. We collectively define these requirements as the 'semantics' of SMS
messaging.
For example:
~ A given set of business rules may require that a subset of SMS messages be confirmed on delivery for non-repudiation of transactions such as:
i. confirmed arrival ii recorded timestamp of arrival for non-repudiation iii acknowledgment of reception of SMS messages ~ It may also be a business requirement that a given set of SMS messages are to be regularly delivered based on a given schedule. Examples include:
i monthly reminders of invoices ii scheduled promotions via SMS messages ~ Broadcasti~YType SMS messages may be required by businesses to reach multiple users without the need of checking or confirming message arrival. Examples include:
i. Store wide promotional broadcasts.
In this case acknowledgment would likely not be required.
~ When a user wants to send in a SMS message to make a transaction, the intent of the user (e.g. to buy an given item) as encoded in the SMS message text has to be unambiguously understood by a web application or other application that handles the user's incoming SMS
message.
C'A9-2002-0055 2 Cowectly encoding SMS messages to accurately represent business intent is a technically complex and difficult task and is highly prone to human error. Human errors in encoding are often very expensive and difficult to debug and correct. Business users want efficiency and reliability in s using SMS to achieve their business objectives. They require sheltering from such technical complexity when using SMS messages in their business processes. Business users typically only want to focus on:
i. Determining the business intent of a given SMS message;
ii. Forming the correct wording of the message (without worrying to about the different technical details of encoding); and, iii. Being informed of error if the message sent does not meet the intent of that message classification.
Business users who initiate these business transactions now face the significant technical 1s challenge of manually encoding all of these SMS messages correctly so that they map accurately to the particular different business objectives that they set out to achieve.
1.2 Difficulty in Semantic Handling at Run Time Apart from the manual, technical challenge in SMS message encoding, semantic handling 2o at run time to meet business process requirements is also a major problem.
For example, a SMS message notifying a user of an outstanding payment typically requires the acknowledgment of the user, as stipulated by a business process that defines "a completed customer touch point".
The lack of acknowledgment by the user upon receiving the SMS message in this case will 2s be handled differently than other SMS message.
However, the concept of semantics and categorization does not presently exist in the space of SMS today.
1.3 The Absence of Syntax in SMS Messages makes Its Usage in Commerce Business 3o Processes Difficult and Impractical 1.4 Lack of Mapping of SMS Text Stream to a Commerce Business Action SMS messages are simple text messages without any encoding scheme. Thus, a simple C'A9-2002-0074 3 plain text SMS message is unsuitable for commerce transactions for the following reasons in addition to the ones mentioned above:
It's not currently possible for a simple SMS message to indicate the type of commerce transaction to be carried out;
ii. Additional parameters required by a particular transaction cannot be encoded in a standard manner and hence, cannot be parsed by the backend commerce application;
iii. Additional details like user authentication and authorization can not be taken care of in a standard manner;
to iv. Lack of state information means request-response model required by commerce transactions can not be applied to commerce SMS messages; and, v. Free form composing of 160 characters as responses by human users makes the adoption impossible and impractical.
The above problem creates a serious usability issue for SMS users (both human and web application) who need to respond to business messages originated from a Web Application or other data processing application.
1.5 Lack of Notation for Parameters Encoded as Part of the SMS message All inbound SMS messages carrying transaction information are required to be validated 2o for data completeness and data validity. Not only that, users sending SMS
messages to a given web application are required to encode enough information in the inbound SMS
messages for proper authentication.
For example, using SMS in online auction requires that the backend web application used to communicate to bidders notify the subscribed bidders whenever an auction bidder has been outbid by someone else. Bidders, upon notification, should be given a mechanism to respond in order to raise their bids.
In this example, the SMS message is required to be sent in a non-repudiated manner so that the subscribed bidders can't deny receipt of auction override notices. Also such messages must be sent out via a high priority channel, if available, so that they can reach the bidders as soon as 3o possible. In addition, the auction bidders are required to have a mechanism to call back the backend commerce application being used in the auction to submit a new bid using a standard SMS message template acceptable to the backend commerce application. These SMS
messages must be parsed correctly by the backend commerce application in order for the backend web C'A9-2002-(1074 application to perform the appropriate semantics.
As an example, one of the required parameters in an auction scenario would be an SKU
number for the identification of item under bid. Both back end server and bidder authentication is required for non-repudiation purposes.
The lack of syntax in SMS messaging makes application to the following business processes extremely difficult:
commerce process mapping;
user authentication;
parameter passing;
to data validation.
1.6 Technical Complexities in encoding SMS deter Business Users from adopting its usage The originators of business SMS messages are business users who have business needs to send business messages. Their prime concern is to focus on the business logistics of the message (like the timing of sending, to whom to send the message to etc.) and the message itself (like the choice of wordings etc.). They do not want to be (and typically cannot afford to be) burdened with the technology of the delivery medium. For example, the technical knowledge of how to send a SMS message is something that the business users do not want to deal with and expect to be handled for them. Transparency and user friendliness is important to a business user.
1.7 The Requirement of Confirmation in Commerce Usage A key requirement of to use SMS in commerce is the need for confirmation from SMS
message recipients. The following is a list of examples for such critical requirements in SMS usage in commerce:
- Upon receiving a SMS notification from the commerce server, often the recipient needs to respond by sending an SMS message back to the commerce server. For example:
the recipient may send an SMS message back to the commerce server to buy an item advertised by an SMS promotion message.
- '7,o fulfill the non-repudiation requirement, for example: all customer touch points need to be recorded.
- C'.onfirmation also requires the confirmation of user ID in an inbound message.
C',A9-2002-0074 5 L.8 The Requirement of Security in Commerce Usage Another key requirement for using SMS in commerce is the need for security in carrying out a business transaction. This requirement includes:
~ User ID authentication by a web application like WebSphere when a user initiates a transaction using SMS message ~ Web application authentication by the user so that the user knows for sure that the correct Web application is handling the user's request ~ User authentication to condinn that no unauthorized mobile device is used for the o transaction; a PIN could preferably be used as an additional layer of user confirmation.
1.9 The Requirement of Session in Commerce Usage Another key requirement of using SMS in commerce is that of the session.
Often, when a web application sends out an outbound message to its users (e.g. campaign message like 'all electronics 50% off if purchased in the next 6 hours), the web application used expects the user to respond back in SMS to the corresponding outbound message within the specified time period.
Typically, this requirement of session includes:
~ A request and response model mapping to outbound and inbound SMS messages;
~ A time out mechanism; and, ~ A Session Data sharing mechanism.
One of the major inhibitor of using SMS in commerce application, is the difficulty in encoding SMS message to accurately implement a given business purpose with the corresponding run time handling matching the intended semantics. Examples of various semantics in SMS
usage in 2s commerce application includes scheduled sent message; confirmation for non-repudiation;
response required message etc.
The fundamental short coming of using Short Message Services in commerce application is the difficulty in encoding with the complexity accurately matching the business intend of the SMS
message sent / received by the commerce web application.
Summary of the Invention The various embodiments and features of the invention herein address shortcomings and requirements outlined above, with particular embodiments having specific features addressing selected shortcomings or requirements as will be appreciated liom the summary of the invention which follows.
One embodiment of the invention provides a universal encoding template that could be used in SMS for encoding outbound business messages for a data processing system for transmission over a network; including the categorization meta data defining a categorization of outbound messages; the categorization representing a specific business intended usage; the categorization meta data providing definitions of messages and instructions that are parsable by t0 the data processing system for generating business messages.
Another embodiment of the invention provides extensible syntactic rules for encoding and decoding SMS message. It also provides extensible semantics for the interpretation and handling of the encoded SMS messages in accordance with encading characteristics in corresponding message types.
Another embodiment of the invention of the SMS universal encoding template provides a message entry field for insertion of a message entry; with the template providing an additional field in the SMS message for categorization of meta data; the meta data providing instructions for encoding a business intent for an commerce SMS message. The meta data may preferably include instructions for dispatching the SMS message including instructions selected from message priority; delivery time; number of recipients; delivery channel etc. The meta data preferably includes instructions for identifying the web application to handle the response.
Another embodiment of the invention of the SMS universal encoding template is adapted to create a typed SMS message instance indicating that a response is required.
The encoded inbound message template enables the unambiguous interpretation of an inbound SIVIS message, leading to unambiguous mapping to a selected business action of a web application of the messaging system.
The predefined categorization of the invention serves as a contract between the user and the web application of the business process so that the interpretation of a given SMS message is unambiguous.
The inclusion of the inbound message template in the outbound message so a user does not need to formulate an inbound message is new to SMS. With this embodiment of the invention, a user only needs to fill in specific required parameters.
C'A9-2002-0074 Another embodiment of the invention provides a SMS commerce message format for use in sending a commerce message over a network to a recipient, which includes a message text entry field for alerting a recipient about a commerce event; an encryption string entry field; a response indicator label; a recipient data entxy field associated with the response indicator label; a recipient authentication indicator label; and, a recipient authentication data entry field associated with the recipient authentication indicator label.
Preferably the encryption string entry field is adapted to accept communication session identification data.
The encryption string entry field may be adapted to accept security information.
l0 The recipient authentication data entry field may be adapted to accept a PIN number from the recipient.
Another embodiment of the invention provides a SMS commerce message format for use in sending an ecommerce message over a network to a recipient including a message text entry field for alerting a recipient about an ecommerce event; an encryption string entry field for security and session control; a response indicator label; a recipient data entry field associated with the rcaponse indicator label; a recipient authentication indicator label; and, a recipient authentication data entry field associated with the recipient authentication indicator label.
Another embodiment of the invention provides a SMS commerce message format for use in sending a commerce message over a network to a recipient including a message text entry field for alerting a recipient about a commerce event; and, an encryption string entry field.
The encryption suing entxy field may be adapted to accept communication session identification data. The encryption string entry field may be adapted to accept security data.
The recipient authentication data entry field may be adapted to accept a PIN
number from the recipient.
Another aspect of the invention provides a SMS commerce message format for use in sc,nding an ecommerce message over a network to a recipient including a message text entry field for alerting a recipient about an ecommerce event; and, an encryption string entry field for security a~zd session control.
Preferably the session identification data may be used to associate a response to the sent message.
The session identification data may be used to identify a software application to process a response to the sent message.
Another embodiment of the invention provides a SMS commerce message for transmission CA9-2002-0074 s over a network to a recipient including a message text for alerting a recipient about a commerce event; an encryption string entry; a response indicator label; a recipient data entry associated with the response indicator label; a recipient authentication indicator label; and, a recipient authentication data entry associated with the recipient authentication indicator label.
The encryption string entry may include communication session identification data.
Preferably the encryption string entry includes security information.
The recipient authentication data entry may include a PIN number from the recipient.
Another embodiment of the invention provides a SMS commerce message for use in sending an ecommerce message over a network to a recipient including a message text entry for l0 alerting a recipient about an ecommerce event; an encryption string entry for security and session control; a response indicator label; a recipient data entry associated with the response indicator label; a recipient authentication indicator label; and, a recipient authentication data entry associated with the recipient authentication indicator label.
Another embodiment of the invention provides a SMS commerce message for use in sending a commerce message over a network to a recipient including a message text entry for alerting a recipient about a commerce event; and, an encryption string entry.
The encryption string entry may include communication session identification data.
The encryption string entry may advantageously include security data.
The recipient authentication data entry may include a P1N number from the recipient.
Another embodiment of the invention provides a SMS commerce message for use in sending an ecommerce message over a network to a recipient including a message text entry for alerting a recipient about an ecommerce event; a.nd, an encryption string entry for security and session control.
The ,session identification data may be used to associate a response to the message with the message.
The session identification data may be used to identify a software application to process a response to the message.
Another embodiment of the invention provides a method for processing an incoming ecommerce SMS response message received by a server from a recipient responding to an outgoing ecommerce SMS message, including receiving the SMS response message;
decoding an encryption string within the SMS response message with an appropriate key to verify that: the response message is directed to the server; extracting identification from the SMS
response message for processing information in the response; identifying and obtaining a corresponding inbound template for the response message from the server;
parsing the response message with the inbound template to extract data and instructions contained in the response message, if any, for processing the data and instructions.
Still another embodiment of the invention provides a method for processing an incoming ecommerce SMS response message received by a server from a recipient responding to an outgoing ecommerce SMS message, including receiving the SMS response message;
decoding an encryption string within the SMS response message with an appropriate key used to encode the outgoing ecommerce SMS message to verify that the response message is directed to the server; extracting identification from the SMS response message for processing information in the response; identifying and obtaining a corresponding inbound template for the response message from the server; parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message;
and forwarding the data and instructions to an application server for processing.
Anc>ther embodiment of the invention provides a method for handling an incoming ecommerce SMS response message received by a ecommerce server from a recipient responding to an outgoing ecommerce SMS message; wherein the response message includes:
an encryption string encoded with an encoding key, identification of a software application capable of processing the response, and user authentication information; tile method including receiving the SMS
message; decoding an encryption string within the SMS message with an encoding key previously 2o used to encode the corresponding outgoing ecommerce message to verify that the response message is directed to the ecommerce server; extract identification from thf:
SMS response for a software application intended to process information in the response; identify and obtain a corresponding inbound template for the response message from the ecommerce server;
parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message; and forwarding the data and instructions to the software application for processing.
Yet another embodiment of the invention provides a method for handling an incoming ecommerce SMS response message received by a ecommerce server from a recipient responding to an outgoing ecommerce SMS message, wherein the response message includes an encryption 3o string encoded with an encoding key used to encode the corresponding outgoing ecommerce rr~essage, identification of a software application capable of processing the response, and user authentication information, and wherein the ecommerce server has access to the encoding key, and an inbound template for processing an incoming SMS response message;; the method CA9-2002-0074 t o including:
receiving the SMS message; decoding an encryption string within the SMS
message with the encoding key to verify that the response message is directed to the ecommerce server;
extract identification from the SMS response for a software application intended to process information in the response; identify and obtain a corresponding inbound template for the response message from the ecommerce server: parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message;
amd forwarding the data and instructions to the software application for processing.
Another embodiment of the invention provides a method for handling an incoming 1o ecommerce SMS response message received by a ecommerce server from a responding recipient, including receiving the S1VIS message; decoding an encryption string within the SMS message vvith a systemwide encoding key previously used to encode the corresponding outgoing ecommerce message to verify that the response message is directed to the ecommerce server;
extracting identification from the SMS response for a software application intended to process information in the response; identifying and obtaining a corresponding inbound template for the response message from the ecommerce server; parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message; and forwarding the data and instructions to the software application for processing.
2o Yet another embodiment of the invention provides a method for handling an incoming ecommerce SMS response message received by a ecommerce server from a recipient responding to an outgoing ecommerce SMS message; wherein the response message includes:
an encryption string encoded with session id, and identification of a software application capable of processing the response; the method including receiving the SMS message; decoding an encryption string within the SMS message to verify that the response message is directed to the ecommerce server;
extracting identification from the SMS response for a software application intended to process information in the response;
identifying and obtaining a corresponding inbound template for the response message from the ecommerce server; parsing the response message with the inbound template to extract data and 3o instructions including user authentication information from the response message; and forwarding the data and instructions to the software application for processing.
In another embodiment of the method of the invention the encryption string is encoded with an encoding key, identification of a software application capable of processing the response, CA9-2002-0074 t 1 and user authentication information; the method including receiving the SMS
message; decoding an encryption string within the SMS message with an encoding key previously used to encode the corresponding outgoing ecommerce message to verify that the response message is directed to the ecommerce server; extract identification from the SMS response for a software application intended to process information in the response;
identify and obtain a corresponding inbound template for the response message from the ecommerce server; parsing the response message with the inbound template to extract data and instructions including user authentication information from the response message; and forwarding vthe data and instructions to the software application for processing.
Preferably the processing of the software application includes using the session id to match the response with a outbound SMS message.
Another embodiment of the invention provides a SMS universal encoding template for encoding outbound SMS business messages for a data processing system for transmission over a network; including categorization meta data defining a categorization of outbound SMS messages;
the categorization representing a specific businesses intended usage;
the categorization meta data providing definitions of messages and instructions that are parsable by the data processing system for generating SMS business messages.
Another embodiment of the invention provides a SMS universal encoding template for use by a message encoding engine of an ecommerce server for encoding outbound SMS
messages from a web application to a SMS dispatcher (runtime processor) for transmission over a wireless network; including categorization meta data defining categorizations of outbound SMS messages;
each of the categorizations representing a specific businesses intended usage;
the categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding SMS business messages for handling by the SMS dispatcher for transmission over the wireless network.
In another embodiment of the invention the SMS universal encoding template provides a message entry field for insertion of a message entry of full SMS message length for access by a recipient; with the template providing an additional field in the SMS message for categorization meta data; the meta data providing instructions for encoding a business intent of an ecommerce 3o SMS message.
The meta data may preferably include instructions for dispatching the SMS
message including instructions selected from the following set pertaining message priority, delivery time, number of recipients, delivery channel, confirmation, authentication, encryption, intended web CA9-2002-0074 ~ 2 application to handle a response.
The meta data preferably includes instructions for identifying a software application intended to handle the response.
Another embodiment of the invention provides apparatus for generation of a SMS
business message processable by a software application, including a data collection interface for accepting instructions and data from the software application;
a rr~essage encoding engine; an encoding template accessible by the message encoding engine; the message encoding engine being adapted to encode the instructions and data from the software application using the encoding template to generate categorized SMS
messages 1o formatted for processing by a data processing system; and, a dispatcher runtime processor linked 1:o the message encoding engine for accepting the categorized SMS messages and processing the categorized SMS messages for transmission over a network to a recipient.
Yet another embodiment of the invention provides apparatus for generation of a SMS
business message for a software application, including a data collection interface for accepting instructions and data from the software application; a message encoding engine; a universal encoding template accessible by the message encoding engine;
the message encoding engine being adapted to encode the instructions and data from the software application using the universal encoding template to generate typed (categorized) SMS
messages that can be processed by a data processing system;
2o a runtime dispatcher processor linked to the message encoding engine for accepting the typed SMS messages and adapted to process the typed SMS messages for dispatch over a network to a recipient.
Another embodiment of the invention provides apparatus for generation of a SMS
business message for a software application, including: data interface means for accepting instructions and data from the software application; message encoding means;
encoding template means accessible by the message encoding means; the message encoding means being adapted to encode the instructions and data from the software application using the encoding template means to generate categorized SMS messages that can be processed by a data processing system; and, a processor linked to the message encoding means for accepting 3o the categorized SMS messages and adapted to process the categorized SMS
messages for transmission to a recipient.
The apparatus of this embodiment may advantageously provide a response tracking database associated with the dispatcher for tracking incoming responses from recipients receiving C.A9-2002-0074 t 3 the SMS business messages.
The apparatus may further include an inbound template database associated with the runtime dispatcher for identifying and parsing an inbound response from a SMS
message recipient for processing by the dispatcher and forwarding to the software application originating the SMS
business message for processing by the software application.
In another embodiment of the invention, the apparatus further includes a commerce user interface including a message composing user interface having: labeled fields for insertion of messages by a user to a recipient and instructions processable by the message encoding engine and runtime processor to generate a SMS business message for transmission to a recipient.
to The apparatus may further include a commerce user interface for creating a new SMS
message type derived fiom the universal encoding template; the corrunerce user interface including labeled fields describing a parent message type; providing labeled fields for defining variations on the parent message type; means for labeling the derived message type; and, apparatus or software for saving the labeled derived message type and adding to the universal template.
Preferably the universal encoding template is adapted to create a typed SMS
message instance indicating that a response is required; the runtime processor being adapted to create an outbound SMS message with a confirmation indicator label with a confirmation field for a recipient to enter a response in a response SMS business message; the runtime dispatcher being adapted to store a response from the recipient in the response tracking database, and forward 2o response message data and instructions to the software application indicating that a response was received.
The runtime dispatcher may be adapted to store data in the response tracking database upon elapse of a predetermined response time without receiving a response, indicating absence of a response; and to send an alert to the software application indicating absence of a response.
An encryption processor may be provided for generating an encryption string for the SMS
business message.
The encryption processor is preferably adapted to generate an encryption string including entries for at least one of the following: session identification, security, a software application for processing a response to the message.
An application key generator may be provided to use an encryption key for generating the encryption string.
Another embodiment of the invention provides an SMS commerce message response including an encryption string field for security and session control; a response indicator label; a C.A9-2002-0074 recipient data entry field associated with the response indicator label in which a response can be inserted by a responding recipient; recipient authentication indicator label;
and, a recipient data entry field associated with the authentication indicator label in which a response can be inserted by a responding recipient.
The SMS commerce message response may further include a short message text field for alerting a recipient about a commerce event.
The encryption string field may preferably be adapted to include security information.
The encryption string field may be adapted to include session control information.
The SMS commerce message response encryption string may include session control information.
Yet other aspects of the invention provide a computer programming for implementing the methods and apparatus of the embodiments of the invention described above.
Other aspects of the invention provide an article including:
a computer readable signal bearing medium; with computer program code means recorded on the medium adapted to perform the methods of the embodiments of the invention and implement the apparatus of the embodiments of the invention.
The medium may be selected from the group consisting of magnetic, optical, biological, and atomic data storage media. The medium may be a modulated carrier signal.
The signal may be a transmission over a network such as a computer network, telecommunication network, or the 2o Internet.
Description of the Drawings Embodiments of the present invention will be described by way of example, referring to the accompanying drawings in which:
Figure 1 depicts an SMS enabled Commerce: Highlighting improvement over pre-existing system;
Figure 2 depicts a Structure Mapping of the SMS commerce Infrastructure Components;
Figure 3 depicts using SMS Message Composing Wizard To Create New SMS Type In S1VIS Universal Encoding Template;
3o Figure 4 depicts using The SMS Message Composing GUI To create new SMS
type;
Figure 5 depicts an SMS Encoding Flow Diagram;
Figure 6 depicts an SMS Message Encoding Engine DCI Structure Diagram;
Figure 7 depicts an SMS Message Encoding Engine Flow Diagram;
CA9-2002-0074 ~ 5 Figure 8 depicts an actual Outbound SM:S message example as seen by a recipient user;
Figure 9 depicts an SMS Inbound Message with user response filled in;
Figure 10 depicts a GUI to compose a SMS message;
Figure 11 depicts adding SMS Inbound Template to the message type;
Figure 12 depicts an inbound Template Manager Structure Diagram:
Figure 13 depicts the Flow For the Inbound Template Management;
Figure 14 depicts Structure Diagram For Business User Sending SMS Message;
Figure 15 depicts a Flow chart for Figure 16;
Figure 16 depicts Confirmation Response Run Time Flow;
1 o Figure 17a depicts an Outbound F low Diagram 1;
Figure 17b depicts an Outbound Flow Diagram 2;
Figure 17c depicts an Outbound Flow Diagram 3;
Figure 18a depicts an Inbound flow Diagram 1;
Figure 18b depicts an Inbound Flow Diagram 2; and Figure 18c depicts an Inbound Flow Diagram 3.
Detailed Description of Preferred Embodiments of the Invention The following description is presented to enable those skilled in the art to understand and apply the invention. Various modifications to the embodiment or embodiments described will be 2o apparent to those skilled in the art. The invention may be applied to other embodiments without departing from the scope of the invention. The present invention is not intended to be limited to the embodiment or embodiments shown.
Figure 1 illustrates an SMS enabled eCommerce system highlighting the improvements of the invention over pre-existing systems. The improvements contributed by the invention herein are indicated by shading.
As indicated previously SMS is not new. Referring to Figure 1, which depicts an SMS
enabled Commerce communication system in accordance with the invention, it can be seen that existing technology lies in space labeled prior art. In the past there were attempts to solve the issue of routing SMS messages to appropriate applications running on the mobile devices (e.g. cell phones).
The space labeled 'New Invention' in Figure 1 is new with the exception of a few basic building blocks that exist today. Although some of the basic building blocks may exist the invention herein allows enhancement of them as appropriate to take into account new capabilities CA9-2002-Ot)74 offered by the invention. New elements contributed by the invention are highlighted in gray while prior art elements are the not highlighted.
Referring to the embodiment of the invention illustrated in Fig. 1, it can be seen that c;Commerce Server 104 is comprised of a number of components:
Application Components 108: Application components 108 form the business subsystems of a given commerce server. Each business subsystem is an implementation of a given business processes. Examples of business subsystems include: Order Management; User Management;
1'~Iarketing and Campaign subsystems, among others.
Common Message Subsystem 107: The Common Message Subsystem 107 is a generic message handling system to handle (and process) messages generated by the application components 108. The common message subsystem handles emails, file transport and other matters pertaining to handling and processing messages.
The embodiment of the invention illustrated in Fig. 1 makes use of a number of existing futures or processes including:
SMS messages: An SMS message is limited to a maximum 160 character long simple text message. It can be sent through many wireless networks. Most cellular phones are capable of sanding and receiving SMS messages.
Wireless Message Gateway: A wireless message gateway can be implemented by a computer which can route SMS messages between a wireless network and the eCommerce server 104.
SMS Center: The SMS Center 102 is typically operated by the telecommunication company to handle the delivery of SMS messages to selected mobile devices.
Data Collection Interface (#1): The Data Collection Interface 117 is comprised of a set of interfaces that collect i. user input via SMS Message Composing Wizard 112; and, ii, data generated by the Application Components 108 forwarded by the 3o Common Message Subsystem 107 to generate an SMS input data collection to be used by the Message Encoding Engine 111.
C.A9-2002-0074 17 Message Encoding Engine (#2): The message encoding engine 111, takes an input data collection, as generated by the Data Collection Interface 117, as input.
The message encoding engine 111 then uses the data in the SMS input data collection to generate the encoding of an SMS message with attributes appropriate to the user selected SMS
type. It further validates the user input against the SMS Universal Encoding template 113 for error checking.
This automatic generation capability in the engine 111 eliminates encoding errors, likely due to human mistakes. This also hides the technical complexity of the encoding of attributes for the implementation of message intent from business users. The Message Encoding Engine 111 produces a 'Typed SMS Message instance 114 as output.
Runtime Processor (#3): The SMS Message Runtime Processor 110 handles business semantics as defined in SMS categorization at run time Basic Functions of the run time processor 110:
- If an SMS message requires confirmation of delivery, or expected response, the SMS
Message Runtime Processor 110 will keep track on the confirmation.
- T he SMS Runtime Processor 110 is also responsible for taking the response returned from an end user and locating the corresponding inbound message template from the inbound template database I 1 ~.
- If the SMS message is a scheduled message, the SMS Message Runtime Processor will handle the scheduling of the SMS message sent.
- Further semantic action can be taken in the absence of user confirmation.
- The runtime processor also does runtime error checking and error handling.
S1VIS Message Composing Wizard (#4): Referring to Fig. 2 which illustrates the structural mapping of an SMS Commerce Infrastructure system in accordance with an embodiment of the invention the SMS Message Composing Vdizard 112 guides a user to articulate the intended usage of the message. SMS Message Encoding Engine 111 uses the user input to generate an SMS
message by mapping the user input into a selected predefined type in a SMS
categorization template 113 as follows:
The Message Composing Wizard 112 takes the user input and invokes the Data Collection Interface 117 which in turn produces an appropriate SMS input data collection.
ii. In the event that user has defined a new SMS categorization via the Message Composing Wizard 112, the Message Composing Wizard 112 will then also update the SMS Universal Encoding Template 113.
iii. 1:n the event that the business user defines an SMS message that has the associated required response from the end user, the business user will define the required response to as required and understood by the application components 108 in the form of template via the Message Composing Wizard 112. I'he Message Composing Wizard 112 will take this input and update the Inbound Template Database (part #9) 115 (see Fig. l ).
SMS Universal Encoding Template (#5): The SMS Universal Encoding template 113 contains the meta data that defines the categorization (or 'type') of outbound and inbound SMS messages.
Each SMS categorization represents a given business intended usage. It provides definition of semantics for encoding as well as for run time.
With. this well defined SMS message categorization, automatic SMS generation with proper encoding reflecting the intended usage is now made possible. Additional SMS message categorization can be further derived from the existing types.
2o This entity provides an important aspect of this invention as it provides the mechanism for semantic definition and handling, making proper semantic handling in SMS now possible.
With the SMS Universal Encoding Template 113, a business user can define a new SMS
message type without any code changes in the Message Encoding Engine 111 and the Run Time Processor 110, making both components generic.
Typed SMS Message Instances (#6): Typed SMS Message Instances 114 are generated by the Message Encoding engine 111, to be used by the Run Time Processor 110.
Am example of a Typed SMS Message Instance follows:
CA9-2002-0074 t 9 <GenericSMSMessage>
<short message text>SOmething</short message text>
<ReceiverProfile>
<userid>steve</userid>
<cellphonenumber>416123456'7@cellphone.com</cellphonenumber>
<deliverychannel>SMTP<%del.iverychannel>
</Re:ceiverProfile>
</GenericSMSMessage>
S~MS Response Tracking DB (#7): The SMS Response Tracking Database 116 captures all Response Required messages as required by their encoded type. This enables the runtime processor 110 to ensure that required response messages receive expected responses and perform proper run time processing. This also enables the base mechanism to handle system expected user initiated inbound messages.
Inbound Template Database (#8): Inbound Template Database 115 stores all business user specified inbound message templates.
Flow Annotation from Figure 1: The formation, processing, and communication of SMS
messages in accordance with the embodiment of the invention depicted are indicated by z0 alphanumerically labeled arrows indicated in Fig. 1. Fig. 2 presents a structural mapping of an SIvIS commerce system in accordance with Fig. 1. An appreciation of the invention can be achieved by reading the description below while referring to Figures 1 and 2.
A1: A business user 105 making use of common user interface 106 invokes the SMS Message Composing Wizard (#4) 112 in order to prepare a message B1: The business user uses the Message Composing Wizard 112 to send a SMS
message based on existing type as defined in the SMS Universal Encoding Template ~#5) 113.
A2: The Wizard 1 I2 captures all the user input and calls the Data Collection Interface (#1 ) 117.
B2: The business user uses the SMS Message Composing Wizard 112 to define a new SMS
message type.
A3: The business user uses the Wizard 112 to define a pre-set user response by creating a new s inbound template. The Wizard I 12 updates the Inbound Template DB (#8) I 15.
C1: Message Encoding Engine (#2) 111 - retrieves (C 1 ) the SMS (Jniversal Encoding Template (#5) I I 3;
validates data captured by Data Collection Interface (#1) 117 against the SMS
Universal Encoding Template 113 and performs error checking.
C2: Message Encoding Engine 111 generates a Typed SMS Message Instance (#6) 114 as output. Referring to Fig. 2 the message can be an XML encoded massage 201.
D2: Message Encoding Engine 111 invokes the Runtime Processor (#3) I 10 which retrieves the generated Typed SMS Message Instance 114 generated in C2.
D3: If a user response is required in this SMS message type, the Run Time Processor 110 will is register this message as one which required user response by updating the SMS Response Tracking DB (#7) 116.
D4: The Run Time Processor 110 transmits this Typed SMS Message Instance 114 to the Wireless Message Gateway 103, referred to as the everyplace wireless gateway 203 in Fig.
2.
2o D5: When an incoming SMS message is sent to the Wireless Message Gateway 103, it routes the incoming message to the Run Time Processor I 10, which in turn extracts the inbound template ID from the incoming SMS message.
D1: The Run Time Processor 110 reads in the SMS Universal Encoding Template 113 to handle type appropriate semantics for outbound run time processing and that the instances 25 are correct.
D6: The Run Time Processor 110 then extracts the corresponding Inbound Template from the Inbound Template DB (#8) 1 I S and parses the inbound SMS message using the inbound template. The Run Time Processor 110 decodes the inbound SMS message and routes it to the corresponding Application Component 108 for handling.
3o Communication of SMS between a user's SMS device 120 (Fig. 2) such as a cell phone 101 (.Fig. 1) is handled by the telephone company's cell phone interface 102 with which wireless gateway 103 is in communication as required to send and receive messages.
Dx The runtime processor I 10 reports run time error back to the application component 108 CA9-2002-0(174 2 ~
1. SMS Message Categorization (Type) Method and Apparatus for defining SMS message Categorization The SMS Universal Encoding 'template 113 provides the mechanism of defining SMS
s message categorization. It is preferably implemented as a XMI. schema in which the meta data of an SMS message (e.g. attributes and characteristics of a given message) that constitutes a SMS
message category is specified.
The Commerce SMS Message Template is preferably designed to provide commerce Typing (categorization) of SMS messages. The SMS Universal Encoding Template 113 provides a to mechanism for a user to extend and define new SMS message types by inheritance from preexisting defined types. Users can thereby extend the SMS Message type in the original SMS
categorization template to define new SMS types.
Business user can use an existing SMS type and extend it to create new message types.
Business User only need to specify the new attributes in the extended type.
All attributes of the 15 base message type (that this new message type extends from) will be set and the business user does not need to respecify them.
Mechanism of Defining Semantics Associated With A Given SMS Category In a preferred embodiment of the invention, when an SMS Message needs to be encoded, 20 the Message Encoding Engine (#2) 111 calls an XML parser to translate the SMS Universal Encoding Template 113 into Java runtime objects. The XMI. parser may be part of the Message Encoding Engine or available to it as may be understood by those skilled in the art. These runtime objects provide the necessary semantic information for the Message Encoding engine 111 to generate SMS messages.
25 Under these circumstances the Message Encoding Engine 111 can now use the XML
parser to parse a given instance of a message against the SMS Universal Encoding Template 113.
This provides the automatic mechanism for error checking. Any missing or unexpected information in a given SMS message not appropriate with to the Type Definition of the SMS
message will result in an error during message parsing.
30 At run time, the SMS Run Time Processor (#3) 110 also reads in the categorization information as provided by the SMS Universal Encoding Template 113 in order to handle different run time semantics as well as error checking based on the SMS Message Type.
C.A9-2002-0074 22 The runtirr~e processing of SMS messages covers the following aspects:
1. Parsing of outbound SMS messages.
2. Error checking outbound messages,
2o D5: When an incoming SMS message is sent to the Wireless Message Gateway 103, it routes the incoming message to the Run Time Processor I 10, which in turn extracts the inbound template ID from the incoming SMS message.
D1: The Run Time Processor 110 reads in the SMS Universal Encoding Template 113 to handle type appropriate semantics for outbound run time processing and that the instances 25 are correct.
D6: The Run Time Processor 110 then extracts the corresponding Inbound Template from the Inbound Template DB (#8) 1 I S and parses the inbound SMS message using the inbound template. The Run Time Processor 110 decodes the inbound SMS message and routes it to the corresponding Application Component 108 for handling.
3o Communication of SMS between a user's SMS device 120 (Fig. 2) such as a cell phone 101 (.Fig. 1) is handled by the telephone company's cell phone interface 102 with which wireless gateway 103 is in communication as required to send and receive messages.
Dx The runtime processor I 10 reports run time error back to the application component 108 CA9-2002-0(174 2 ~
1. SMS Message Categorization (Type) Method and Apparatus for defining SMS message Categorization The SMS Universal Encoding 'template 113 provides the mechanism of defining SMS
s message categorization. It is preferably implemented as a XMI. schema in which the meta data of an SMS message (e.g. attributes and characteristics of a given message) that constitutes a SMS
message category is specified.
The Commerce SMS Message Template is preferably designed to provide commerce Typing (categorization) of SMS messages. The SMS Universal Encoding Template 113 provides a to mechanism for a user to extend and define new SMS message types by inheritance from preexisting defined types. Users can thereby extend the SMS Message type in the original SMS
categorization template to define new SMS types.
Business user can use an existing SMS type and extend it to create new message types.
Business User only need to specify the new attributes in the extended type.
All attributes of the 15 base message type (that this new message type extends from) will be set and the business user does not need to respecify them.
Mechanism of Defining Semantics Associated With A Given SMS Category In a preferred embodiment of the invention, when an SMS Message needs to be encoded, 20 the Message Encoding Engine (#2) 111 calls an XML parser to translate the SMS Universal Encoding Template 113 into Java runtime objects. The XMI. parser may be part of the Message Encoding Engine or available to it as may be understood by those skilled in the art. These runtime objects provide the necessary semantic information for the Message Encoding engine 111 to generate SMS messages.
25 Under these circumstances the Message Encoding Engine 111 can now use the XML
parser to parse a given instance of a message against the SMS Universal Encoding Template 113.
This provides the automatic mechanism for error checking. Any missing or unexpected information in a given SMS message not appropriate with to the Type Definition of the SMS
message will result in an error during message parsing.
30 At run time, the SMS Run Time Processor (#3) 110 also reads in the categorization information as provided by the SMS Universal Encoding Template 113 in order to handle different run time semantics as well as error checking based on the SMS Message Type.
C.A9-2002-0074 22 The runtirr~e processing of SMS messages covers the following aspects:
1. Parsing of outbound SMS messages.
2. Error checking outbound messages,
3. Message tracking and scheduling capabilities.
4. Generation of outbound SMS template messages.
5. Error checking inbound messages.
6. Translation of inbound templates into XML SMS messages.
7. Mapping of outbound types to their corresponding inbound SMS messages.
1 o Runtime parsing of outbound SMS messages is possible as they are now encoded in accordance with the templates we have introduced. During this parsing stage information about message type, transmission medium, send priority etc. is parsed out.
Error checking is an added benefit of this runtime parsing of outbound messages. Since the outbound SMS messages are now strictly type encoded, various errors like missing parameters etc.
Can be detected and handled at this stage. This ensures that the final outbound message is correct.
A sample source code listing that can be used to implement an SMS Universal Encoding 'll'emplate in accordance with one embodiment of the invention follows:
<:xsd: schema xmlns:xsd="http:/lwww.w3.org/200i/XML;3chema"
xmlns:cep=
"htt:p://www.ibm.com/WebsphereCommerceEnab.iedPortal/SMSCommerceDefinition Schema">
<annot:ation>
<doc:umentation xml:lang="en">
Schema for Websphere Commerce Enabled ~o.r~ai SMS Commerce Type Definition Copyright 2002 IBM Corporation <documentation>
</annotation>
<!-Dynamic Context Group Instance -->
<xsd:element name="Schedulec~GenericSMSMessaqe"
CA9-2002-0074 ? 3 type="SCheduledGene ricSMSMessageType", minOccurs="0"/>
<xsd: element name="ResponseRequiredGerieric:~M~~Message"
type=" ResponseReq~.ziredGeneric:SMSMessa~eType ", minOccurs="0"/>
<xsd:element name=" HighPriorityGenericSMSMessage"
type=" HighPriorityGenericSMSMe;;sage'Type", minOccurs="0"/>
<xsd:element name="GenericSMSMessa<~e"
type="GenericSMSMessage'rype", minOccurs="0"/>
<xsd:element name="BroadcastSMSMessage"
type="BroadcastSMSI~lessageType", minOccurs="0"/>
<xsd:comp=LexType name="ScheduledGenericSMSMessageType">
<xsd:sequence>
<xsd:element name="GenericSMSMessage"
type="GenE:ricSMSMessageType"/>
<xsd:attribute name="DateToBeSentOn" type="xs:date"/>
<xsd:attribute name="Ti~eToBeSentOn" type="xs:time"/>
</x~sd:sequence>
</xsd:comx>lexType>
<xsd:complexType name="ResponseRequiredGeneri.cSMSMessageType">
<xsd:sequence>
<xsd:element name="GenericSMSMessage"
type="GenericSMSMessageType"/>
<xsd:attribute name---"Inboi:ndTemplateld" type="xs:string"!>
</xsd:sequence>
</xsd:complexType>
<xsd:comF>lexType name="HighPrio rityGenericSMSMessageType">
<xsd:sequence>
<xsd:element name="GenericSMSMessage" type="GenericSMSMessageType"/>
<xsd:attribute name=°'DeliveryPriority"
type="DeliveryPriorityType" fixed="HIGH"/>
</xsd:sequence>
</xsd:complexType>
<:xsd:complexType name="GenericSMSMessageType">
<xsd:sequence>
<xsd;element name="short message text" type="xsd:string"
maxLength="160"/>
<xs~3:attribute name="ReceiverProf.ile" type="ReceiverProfileType"
minoccurs-="1" maxOccurs="1"/>
</xad:sequence>
</xsd:complexType>
<xsd: comp)_exType na:ne="Broad~~astSMSMessageType":>
<xsd:sequence>
<xsd:element name="short message text" type="xsd:string"
maxLength=="160"/>
<xsd:attribute name="ReceiverProfi~..e" type="ReceiverProfileType"
C'A9-2002-0074 25 minoccur:>="1" maxOccurs="unbounded" />
</xsd: sequence>
</xsd: cornplexType>
<xsd: simpleType name="Deliver?:riorityType"
<xsd:restriction base="xsd:string"~~
<~:sd:enumeration value="HIGH"/>
<~a d:enumeration value="MEDIUM"/>
<xa d:enumeration value="LOW"/>
</x:sd:restriction>
</xsd: sirr.pleType>
~:xsd:complexType name="ReceiverTransmissionF'rcfileType">
<xsd:sequence>
<xsd:element name="userid" type="xsd:string"/.
<xsd:element name="cellphonenumber" type="xsd:string"/ >
<xsd:element name="deliverychannel" type="DeliveryChannelType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="DeliveryChannelType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="SMTP"/>
<xsd:enumeration value="GSM"/~>
<xsd:enumeration value="SNPP"/>
<xsd:enumeration value="Mobitex"/>
<xsd:enumeration value=="DataTAC"/>
</xsd:restriction>
</xsd:simpleType>
</xsd: schema>
The following source code listing provides an illustration of a Typed (Categorized) SMS
Message Instance XSD Schema Definition of Commerce Payment Exception SMS Message <xsd:complexType name="Payment~~xceptionSMSMessage"=
<xsd:sequence>
<xsd:elementname="Re:>ponseRequiredSMSMess.age"
type="ResponseRequiredSMSMessageType"%>
</xsd:sequence>
l5 </xsd:c:omplexType >
Message Instance of a Payment Exception SMS Message <PaymentExceptionSMSMessage>
<Re;~ponseRequiredSMSMessag~~>
<HighPriorityGenericSMSMessage>
<GenericSMSMessage>
<short message text>
Your cheque bounced!
</short message text>
2S <ReceiverPro.file>
<userid>steve<iuserid>
<cellphone:number>
116123456?@ce ll~izcne , c:.om </cellphonenumber>
<deliverychannel>SMTP</deliverychanne'~>
</ReceiverProfile>
</GenericSMSMessage>
<DeliveryPrior-ity>HIGH</Deliveryl'riori.ty>
CA9-2002-0074 2~
</HighPriorityGenericSMSMessage>
<ConfirmationOfDelivery>CONFIPMED<%:~onfirmationOfDelivery>
<lRc~sponseRequiredSMSMessa;~e>
</PaymentExceptionSMSMessage>
XSD Schema Definition of Campaign Started Broadcast SMS Message <xsd:complexType name="CampaignStartedSMSMessage">
<xsd:sequence>
<xsd:elementname="BroadcastSM:~Message"
type="Broadcas-SMSMessageType"%>
</xsd:sequence>
</xsd:complexType >
Message Instance of a Campaign Started SMS Message 1$ <CampaignStartedSMSMessage>
<BroadcastSMSMessage>
<short message text>
New campaign has been started, visit our website </short message text:' <Receive=Profile>
<userid>steve<,/vserid>
<cellphonenumber>
91012395c: ;iacellphone. co~r.
</cellphonenumoer>
<deliverychannel>SMTP</deliverychannel>
</ReceiverProfile>
<ReceiverProfile>
<userid>joe</userid>
<cellphonenumber:>
4161~3456B~cel~hone. c'~m </cellphonenumb2r>
<deliverychannel>SMTP<ldelivery<:hannel>
</ReceiverProfile>
</BroadcastSMSMessage>
</CampaignStartedSMSMessage>
The SMS Encoding engine 11 I can automatically generate an SMS Message instance based on th.e SMS message type selected. The SMS Message Runtime Processor 110 is adapted to handle the semantics of a given predefined type. At runtime, if a SMS message sent is a ResponseRequiredSMSMessageType, the SMS Message Runtime Processor 110 waits a preset wait time for user confirmation. If confirmation is not received after the preset wait time, the to runtime processor 110 will sent the error to the corresponding application component 108 so that action can be performed according to that stipulated in the business process represented by that application component. For example, application component 108 may provide for resending, or rollbacking the transaction and marking this transaction as having failed completion. (Dx of Figure 1 Runtime processor 110 reports run time error to the application component for handling) How a User Creates a New SMS Type By Extending From an Existing Type Referring to Figure 3, which depicts a process for Using SMS Message Composing Wizard T'o Create a. New SMS Type In the SMS Universal Encoding Template, and Figure 1, which depicts a SKIS Message Composing GI~I for creating a new SMS type it will be readily understood 2o how a new SMS type can be created using a preferred embodiment of the invention.
In order the start 300 the process a business user clicks a button provided on the Message Composing Wizard 112 (see Fig. 1, 2) to instruct the system of the invention to create a new message type 301. The message composing wizard then reads in the SMS universal encoding template 11; (Fig. 1, 2) to present a selectable parent SMS type 405 for the user to create a new type in step 302. In step 303 the user enters a new message type name (see 404) and specifies all new attributes indicated by provided descriptions, 406, 407, 408, 409, 410, 41 t, 414, 415, 416, and the base (parent) type 405, to generate a new SMS type. Add and Delete buttons, 412, and 413 respectively allow insertion and deletion of items in the reply section, while buttons 402 and 403 are used to save or cancel the new message type as will be appreciated.
3o If a new response template is required for the new message type, 304, the response template manager is invoked by the business user to create the inbound template required, 305 and the inbound template database 11 S is updated, 306. if a new response template is not needed the new message type is saved, 307, int the SMS universal encoding template 113, reaching the end 308 of the process depicted in Figure 3.
2. Encoding End to End Flow Referring to Figure 5, which illustrates SMS message encoding flow following will be understood:
A: Business User invokes New Message Type Creator to create a new Message Type.
B: Business User invokes Inbound Template Manager to create a new Inbound Template for the rlew Message Type (thru the Inbound Template Manager).
C: Inbound Template Manager retrieves a list of predefined command list from the Inbound to Template DB. The command list is defined by the Application Component owners.
P: Inbound Template Manager inserts a new row into the Inbound Template DB
with the Response Action and Command selected by the Business User from the GUI.
E: Inbound Template Manager returns the newly created Inbound Template ID
(generated by the Inbound Template DB) to the New Message Type Creator.
1 s F: New Message Type Creator then saves the newly created message type (imbedded with the Inbound Template ID) into the SMS Universal Encoding Template (part #5).
2.1 Encoding An Outbound Message only message The SMS Composing Wizard allows business user to send a message to any registered 2o users in the e-Commerce system. All the complexity of transferring the message is handled by this invention. T'he business user just has to select a type of message, enter the message text and click the Submit button.
Micro Flow: Data Collection Interface, SMS Input Data Collection and Message Encoding 25 Engine Message processing by the encoding engine is shown by alphabetically labeled arrows in Figure 6 as discussed below.
A: Common Message Subsystem 107 or the SMS Message GL.1I Wizard (part #4) 112 calls the Data Collection Interface's 117 APIs (part #1 ) 510-516 to pass data collected from the message 30 originator.
B: The Data Collection Interface's APIs 510-516 pass the data to the Data Collection Object 518.
For example, calling the setTextMessage API 514 with the message text as parameter, the API 514 will save the text in the Data Collectian Object 518.
C: The sendMessage API 516 invokes the Typed SMS message encoder 701. It retrieves the message type name from the Data Collection Object 518. The message type name is captured by the messageInstanceCreation API 510. In this step, the Typed SMS message encoder 701 also collects other information from the Data Collection Object 518; such as: send time, send priority, f~esponseTemplate Id, text message, receiver info.
1D: Using the message type name, the Typed SMS message encoder 701 retrieves the SMS
Universal )=?ncoding template 113 for this message type.
>H:: The Typed SMS message encoder 701 creates a Temporary Typed SMS Message Instance 702 by converting the SMS Universal Encoding template 113 into a temporary Typed SMS message instance 70:? expressed in Document Object Model (which is an internal structure for XML) and fills in the information collected from the Data Collection Object 518 in C.
F': The Temporary Typed SMS Message Instance 702 is then passed to the SMS
Message Validator 703 to perform validation. The validation process involves checking of mandatory data, data semantic, data syntax, data range.
G: If validation is successful, the SMS Message Validator will copy the Temporary Typed SMS
2o Message Instance 702 into the final Typed SMS Message Instance (part #6) 114.
Steps 801 to 808 of Figure 8 depict the process above in a graphical flow diagram.
2.2 Encoding A ResponseRequired Message For a SMS message that requires a response, an Inbound Template should be included in the original outbound SMS message to a recipient. 'rhe Inbound Template provides a form based input mechanism for the recipient; it is adapted to encode the expected response of the recipient of a SMS message. The Inbound Template eases the burden of the recipient user trying to formulate a response back to the Application Component 108 that originated the outbound SMS message to the recipient. The response template serves to constrain the user's response by indicating the format of the response required to the user. As a result the user's response will be in a form that c;an be processed automatically by the web application server on its return.
Inbound Template: The structure of an inbound template is illustrated below:
<Short Message Text>
<Encrypted String>
<response action 1>
<response action 2>
<response action n>
2o PIN:<mobile user personal identification>
The Inbound Template structure depicted above supports multiple response actions.
Depending on the type of transaction, the recipient, likely a mobile user, will pick one of the response actions.
Figure 8 depicts the appearance of an outbound SMS message with indications of a required response to a recipient user as it would appear on the user's digital cell phone screen 901.
The SMS Message string to achieve this would resemble: Your cheque bounced!-lust-CONFIRMED: PIN:
2.2.1 SMS response message encoding template elements As may be seen from Fig. 9 the SMS response message encoding template elements for the inbound template include the following:
~ Short Message Text, 902 ~ Encrypted String, 903 ~ <response action, 904>:<response data, 906 >
~ PIN, 905 Figure 10 illustrates an SMS inbound message with a user response entered before being sent.
'?.2.1.1 Short Message Text 902 This is the message that the message originator intended to send to the receiver.
2 .2.1.2 Encrypted String 903 Encrypted String is a four character hashed string delimited by a pair of '-' The encrypted string is built upon the amalgamation of the following information:
- web application id (predefined by web app administrator, e.g. store ID) - userid (login id of the receiver of this store) - inbound template id (that includes command and expected parameter) as per database entry. This can be obtained from the Inbound Template DB (part #8) - Action id (id representing the response actions allowed in this message) - Hash Key - the user can change anytime to make the key expire. This can be saved in 2o a file in restricted directory.
The Runtime Processor 110 is responsible for generating this encrypted string using the above information as input. The Runtime Processor is also responsible for generating the Inbound Template before transferring the SMS message to the Wireless Message Gateway 103.
Advantage of using the encrypted string:
- the encrypted string can be limited to 4 bytes to save space from the 160 character limit - Encrypted string is unintelligible - Hash Key can be changed anytime by the business user to impose an arbitrary time out - Runtime Processor 110 can filter out unwanted incoming messages. An invalid or a missing encrypted string indicates the message is unwanted.
- Users can store the inbound template in their mobile devices so that they can initiate transactions with the designated web application any time at their own volition. This advantage will be discussed in detail in section 2.3.
2.2.1.3 <response action>:<response data>
Response action 904 is a keyword to identify allowable response actions and the corresponding parameters. In the example, the allowable response 904 is CONFIRMED. In this example, Fig. 10 the user has entered the response 906 Y. There can be more than one allowable responses for different transactions. There are three sub-elements in this response:
1. Response Action - the keyword representing the action. E.G. CONFIRMED
l0 2. Command - a web application program or command which the Runtime Processor will invoke These response actions and commands are saved in the Inbound Template DB (part #8) indexed by unique Inbound Template ID. Business user can use the SMS Message Composing Wizard (part #4) to manage these response actions. Refer to section 2.2.3 How to manage Inbound Template using the SMS Message Composing Wizard.
The runtime processor will invoke the command with the <response data 906>
when the responding SMS message is received.
2.2.1.4 PIN
2o The PIN element 905 provides for a user to enter a PIN number 904 specified by the user at user registration ( the user entered 1234 in this example). With the PIN and the userid (encrypted in the Encrypted string) the Runtime processor 110 can authenticate the originality of the inbound message.
2.'x.2. SMS response showing what a user would have input in the response Figure 9 illustrates the screen 1001 of a digital cell phone with a user response.
When the mobile cell phone user responded to the SMS message, the user would just have to select "forward message" to a designated phone number for the web application; enter the response data 3o for one of the response actions, enter the PIN number and hit the "send"
button.
In this example, the mobile cell phone user entered Y 906 beside CONFIRMED:
904 to indicate that lrelshe acknowledged the message.
CA9-2002-0074 3~
The SMS Message that would be received by the web application would resemble:
Your cheque bounced!-kis2-CONFIRMED:Y PIN:1234 For t:he processing of an inbound SMS message, please refer to section 3.2 "Response Required Message and Inbound Message End To End Flow".
2.2.3 How to manage Inbound Template using the SMS Message Composing Wizard.
Inbound Template Manager 502 (see Fig. 5) , a sub-component of the SMS Message Composing Wizard (part #4) (see Fig. 4) , is responsible for managing inbound templates. This l0 includes creation and deletion of the mapping between the response actions and the web application commands.
2.2.3.1 GUI
Figure 10 illustrates a GUI 1101 that could be used to compose a SMS message that would be sent by the web application server to a mobile user. In this instance it is illustrating a GUI for a payment exception message that could have been used to produce the message of Figure 8.
If a business user wanted to create a new SMS message type derived from this pressing NEW button 1102 would invoke the Create a new SMS Message Type panel 400 as illustrated in Figure 4. This panel could then be used to create a new message type.
Click on "Add" button 412 will invoke Add SMS (Reply) Inbound Template panel illustrated in Figure 11:
2.2.3.2 Inbound Template Manager Structure Diagram Figure 12 illustrates the structure of the inbound template manager 202.
The flow annotation for the inbound template manager follows:
A; Business User 900 invokes New Message Type Creator 201 to create a new Message Type.
B: Business User 900 invokes Inbound 'Cemplate Manager 202 to create a new Inbound Template for the new Message Type.
3o C.. Inbound Template Manager retrieves a list of predefined commands from the Inbound Template DB 115. The command list is defined by Application Component 108 (Fig. 1).
D: Inbound 'Template Manager 202 collects the information from GUI and update the Inbound Template DB 115.
E: Inbound Template Manager 202 returns the newly created Inbound Template ID
(generated by the Inbound Template DB 115) to the New Message Type Creator 201.
F: New Message Type Creator 201 then saves the newly created message type (imbedded with the Inbound Template ID) into the SMS Universal Encoding Template (part #5) 113.
2.2.3.3 Managing Inbound Template Flow Chart Figure 13 illustrates a flow chart depicting the steps I50 to 158 of how an SMS Message C'.omposing Wizard would be used to manage the response actions described above:
2.3 Encoding An Inbound Message For User's consumption Another useful application of the Inbound template is to allow mobile users to submit requests to the web application. For example, a user can send to the web application a request for account balance. Using a saved Inbound template far account balance request in the mobile device, the user can send this inbound template as an inbound SMS message. In response to this request, the web application will send the account balance as an outbound SMS
message assuming the incoming message passed validation and authentication.
2.3.1 Steps to implement this feature:
Stepl: Business User defines a list of inbound templates. This can be done using similar procedures in creating a new message type. A new message type called "InboundReduestGenericMsg" must be defined first. The Business user can then derive another inbound request message type with inbound template attached.
Step 2: An Application component called "Customer Services" publishes a list of defined Inbound Templates in the store web site.
Step 3: Users logon on to the store web site and select the inbound templates they wish to download.
Step 4: The (Justomer Service Application Component sends the selected Inbound Templates to the mobile device. The transmission can be completed by using the Common Message Subsystem which calls the Data Collection Interface's APIs (part #1 ).
2,.3.1 Structure Diagram Figure 14 depicts a Structure Diagram of a SMS system in accordance with a preferred embodiment of this invention depicting the process of a Business User Sending an SMS Message.
The flow annotation follows:
A: Business user 900 defines new message types and corresponded inbound templates. This is done by using the SMS Message Composing Wizard I 12 (hig. 1 ).
>g: SMS Message Composing Wizard I 12 stores these new message types and inbound templates in the SMS Universal Encoding Template (part #5) 113 and Inbound Template DB
(part #8) 115 respectively, C': Mobile user 901 logons to the web site for the system and requests a list of inbound templates.
D: The Customer Service Application Component 161 obtains the Inbound Template IDs from the SMS Universal Encoding Template 113. Using the IDs, the Customer Service Application Component 161 retrieves the available inbound templates from the Inbound Template DB 115 using the IDs.
E: The Customer Service Application Component 161 displays the list of inbound templates to the mobile user 901.
F: The mobile user 901 selects the inbound templates desired and requests them to be sent to his/her mobile device.
G: The Customer Service Application Component 161 sends a request to the Common Message Subsystem 107 to send the selected inbound templates as generic SMS messages.
3o H: The Common Message Subsystem 107 calls the Data Collection Interface's APIs (part #1) 117 to transmit the inbound templates as generic SMS messages I: The SMS Message Encoding Engine (part #2) 111 encodes the SMS messages containing the CA9-2002-0074 3'l inbound templates and sends them to the Runtime Processor (part #3) 110.
J: The Runtime Processor 110 inserts an encrypted string into the SMS
messages. This encrypted :string preferably should not have an expiration time since the templates will be used for input requests. The SMS messages are sent to the Wireless Message Gateway 162.
K: Wireless Message Gateway 162 delivers these messages to the mobile user 901.
L: Mobile user 901 saves these inbound templates in the storage of his/her mobile device. Mobile user 901 can now use these inbound templates to submit a request or requests to the application component 108.
M: The Wireless Gateway 162 transfers inbound SMS messages from mobile users to the Runtime Processor 110.
N: The Runtime Processor 110 examines the encrypted string in an inbound SMS
message to determined if this is an inbound request. If the message is authenticated, the Runtime Processor 110 will invoke the corresponding command owned by the relevant Application Component 108 of the SMS enabled commerce system.
2.3.2 Flow Chart Figure 15 illustrates a flow chart of a business user obtaining selected inbound templates in accordance with a preferred embodiment of the invention similar to that depicted in Figure 13.
3. Run Time End To End Flow This section outlines runtime processing of an embodiment of the invention, cover outbound mcasage generation and inbound response message processing.
3.1 Outbound Message End to End Message Processing Flow Figure 5 outbound flow diagram depicting outbound message handling flow of an SMS
ecommerce system of one embodiment of the invention.
CA9-2002-0074 3 s F figure 17 depicts an outbound flow diagram of the environment of the invention. Referring to Fig.
17, it can be seen that:
~ Typed SMS Message Instance I 14 generated by Message Encoding Engine 111 is checked to see if it is a scheduled message.
~ If it is a scheduled message to be sent later, save the message into the SMS
Message Tracking DB 195. Scheduler 182 will periodically read the SMS Message Tracking DB
195 to retrieve messages which are due to send.
If the message is due to send, it will be checked for type error by comparing to the type saved in the Universal Encoding Template 113.
~ If there is a type error, generate and return error.
~ If there is no type error, parse the message using the XML parser 1918 with the input of the Universal Encoding Template 113 The XML parser 1918 parses the Typed SMS Message Instance which is in a DOM
tree format 1912.
~ Check to see if the message requires a response ~ If response is not required, dispatch the message using the wireless gateway 103, then stop ~ If response is required, extract the message template id from the parsed message.
~ Find the inbound template1916 using the message template id from Inbound Template DB
115.
~ Using the Typed SMS Message Instance 1 I 4 and inbound template I 916, generate the final SMS message ~ Create the session object 1927 ~ Using the session object, WebAppID 1928, UserID 1929, Template ID 1930 and Encoding Key 1931, generate the encrypted string 1924 ~ Insert the encrypted string 1924 into the final SMS message ~ Dispatch the final SMS message using the wireless gateway 103, then stop.
3.2 ResponseRequiredMessage and Inbound Message End To End Message Processing Flow.
Figure 18 depicts inbound flow diagram. It can been seen that:
~ Wireless Gateway 103 received an Inbound SMS message 2003 ~ Runtime Processor 110 extracts the four character encrypted string 2005 from the Inbound SMS message 2003 ~ With the encoding key 1931, the encrypted string 2005 is decoded ~ If decoding is not successful, then stop.
~ If decoding is successful, extract the WebApp ID from the encrypted string 2005.
If the WebApp ID does not match the current WebApp ID, then stop ~ If the WebApp ID does match the current WebApp ID, extract the template ID
from the to encrypted string 2005.
~ Using the template ID extracted from the above, get the inbound template 2014 from the Inbound Template DB 115.
~ Extract the parameter names, command and values 2017 from the Inbound SMS
message 2003.
~ Extract the User ID from the encrypted string 2005 ~ Create the message for the Commerce Server (Command Context Object 2020) using the command name, parameters and Llser ID extracted above.
~ Dispatch the said message to the Commerce Server I 08 ~ All is completed Figure 16 illustrates a detailed example of the runtime processor 110 of an embodiment of the invention depicting details sufficient for a description of the confirmation response run time processing flow. An explanation of the elements of runtime processor I 10 and their interaction follows:
2s Typed Message Instance: The typed message instance 114, is the actual outbound SMS message as received from the Encoding Engine (or the Scheduler for a scheduled message) by the runtime.
In the current implementation scheme this message is encoded in XML in accordance with the Universal Encoding Template schema.
CA9-2002-0074 ao Typed Message Parsing Subsystem: The typed message parsing subsystem 181, consists of a parser for the typed XML message. Its job is to verify that the incoming message is correctly encoded in accordance with the schema and also to parse this message into a DOM tree (for the current implementation).
The output of this subsystem is a parsed object that contains the entire contents of the outbound SMS message in computer readable memory object format.
Message Tracking Subsystem: The message tracking subsystem 183 updates the SMS
tracking to DB with statistics about message sent time, message receipt time etc.
Scheduler: The scheduler subsystem 182 is responsible for timed relaying of SMS messages. If an SMS message requires to be sent at some scheduled time then this subsystem is responsible for caching the message in the message tracking DB.
I5 Also this subsystem is responsible for polling the message tracking DB at intervals decided upon by the business mmager and picking up messages that are ready for dispatch and forwarding to the typed message parsing subsystem for delivery.
Application Key Generator Subsystem: The application key generator subsystem 184 is 2o responsible for generating the encrypted string that goes out with SMS
messages that require user response. This subsystem uses a system wide, time sensitive encoding/decoding key to encode this session string;.
The encrypted string itself consists of the following:
z5 1. WebApp ID
2. User ID
3. Inbound Template ID
4. Session Object ID
3o As this encrypted string is based on the time sensitive encoding and decoding key, this invention provides the break through in SMS to achieve the effect of a session in SMS, which was not able to be done before.
With the notion of session being introduced in SMS now, we can now create session object CA9-2002-00'74 which can be used for SMS based session data storage.
After the encrypted string is decoded by the time sensitive decoding key, each element (the WebApp ID, the UserID, the inbound TemplateID, and the sessionID) c<tn be decoded at the second stage by its own corresponding decoding key (WebAppIDKey, UseridKey, inboundTemplateKey, sessionIDKey).
Thus, the final encoding is a two stage encoding scheme that can only be decoded successfully if both the system wide encoding key and the WebApp ID are correct. This leads to added security for the outbound session string.
Outbound Message Generator: The outbound message generator subsystem 185 encodes the 1o final 160 character outbound message by using the parsed outbound SMS
message generated by the typed message parsing subsystem and the session string generated by the Application Key Generator Subsystem. After creating this SMS message it forwards it to the wireless gateway 103 far final delivery to the end user.
Inbound Message Parsing Subsystem: The inbound message parsing subsystem 186 has the task of first, decoding each incoming message using the encrypted string and the system wide encoding key and the WebApp ID. After verifying that this message can be decoded correctly, the subsystem extracts the Inbound Template ID and looks up the inbound template from the Inbound Template DB to parse the incoming message.
2o A successful parsing of the inbound message leads to extraction of incoming command and parameters. 'This subsystem then extracts the User ID from the encrypted string and creates the command context object for this incoming request. Before creating the command context object, this component also verifies the incoming PIN number for authentication using the application component 108 authentication mechanism.
The next step is to actually dispatch this message to the relevant application component.
It co-operates with the Message 'Tracking Subsystem to track incoming SMS
messages for receipt time and other statistics.
3o CONCLUSION
The embodiments of the invention described herein provide a number of advantages and distinctions over prior SMS messaging systems:
1. Confirmation the inbound template being park of the outbound SMS message text body provides a system for confirmation that would readily processable by a web application.
- The SMS Response Database provides enablement of run time confirmation as required by the message type.
- The absence of confirmation in previous SMS systems hinders the application of SMS
in commerce. This invention provides a solution to this limitation with encrypted string such as userid and PIN, making the confirmation of a user possible.
2. Security - The inbound SMS message can preferably include an encrypted string with two levels of encryption. This ensures that the relevant web application only handles incoming sms messages that are directed towards that web application.
- The userid is obtained by a second level userid key, together with a user specified PIN
number, providing additional layers of security protection.
~ 5 - A 4 byte security mechanism can make sms application in commerce possible.
- The two level encoding is as used herein is new as is the amalgamation of 4 elements (web app id, userid, inbound template id, session object id) into 4 bytes and decoded with two level of keys.
3. Session Control If the Session ID is encrypted in the SMS string this will provide a timeout control for typical http sessions.
- The matching of the encrypted string with the outbound message provides a request and response model, making the formation of~ a session possible.
- With this session, cohesive requests and responses between the user and the web application are now possible, making commerce applications in SMS practical.
- The 4 byte encrypted string in the message is new - The timestamp and the system key added to the encrypted string is new - The SMS response DB together with the Run Time Process to manage the session effect of request / response SMS messages at run time is new to SMS messaging.
4. Extensible Syntax: Rules for Encoding and Decoding a SMS Message - . The encoded inbound message template enables the unambiguous interpretation of an inbound SMS message leading to unambiguous mapping to a selected business action of a web application of the messaging system.
- This syntax is extensible to create new inbound message templates.
- Including the inbound message template in the outbound message so user does not need to formulate their own inbound message is new to SMS. Now the user only needs to fill in specific required parameters 7~he extensibility of the syntax to create other syntax in new message types is new.
5.1 Extensible Semantics: Interpretation Of Encoding Mapped To unambiguous Business to Actions T'he predefined categorization of the invention serves as a contract between the user and the web application of the business pracess so that the interpretation of a given sins message is unambiguous and maps to a definite business action of a predefined business process, making commerce application of SMS possible.
- The base categorization is extensible to define new categorization for new mapping of business actions.
- The application of xml schema (with inherent characteristics including categorization and deriving new categorization) as a SMS Universal Encoding Template in the space of SMS is new.
5.2 Extensible Semantics: Handling of SMS Messages at runtime in accordance with encoding characteristics in corresponding message types - The SMS Universal Encoding Template enables extra information about the SMS
messages to be shared between the Web Application and the message Run Time Processor. The Run Time Processor can now (based on the extra semantic characteristics as defined in the SMS type) perform type-appropriate run time tasks consistent with the intent of the sender (business user) as understood by the web application.
6. Enhanced Usability - Business users axe now spared from the technical complexity of encoding a SMS
message to match their business intents. Business user can now focus on the content of the message without being distracted by SMS message encoding.
- The SMS commerce solution of this invention reduces the possibility of encoding error (as SMS encoding errors are difficult and expensive to solve at run time). The mechanism of encoding ensures error checking and provides early identification of encoding errors.
CA.9-2002-0074 45
1 o Runtime parsing of outbound SMS messages is possible as they are now encoded in accordance with the templates we have introduced. During this parsing stage information about message type, transmission medium, send priority etc. is parsed out.
Error checking is an added benefit of this runtime parsing of outbound messages. Since the outbound SMS messages are now strictly type encoded, various errors like missing parameters etc.
Can be detected and handled at this stage. This ensures that the final outbound message is correct.
A sample source code listing that can be used to implement an SMS Universal Encoding 'll'emplate in accordance with one embodiment of the invention follows:
<:xsd: schema xmlns:xsd="http:/lwww.w3.org/200i/XML;3chema"
xmlns:cep=
"htt:p://www.ibm.com/WebsphereCommerceEnab.iedPortal/SMSCommerceDefinition Schema">
<annot:ation>
<doc:umentation xml:lang="en">
Schema for Websphere Commerce Enabled ~o.r~ai SMS Commerce Type Definition Copyright 2002 IBM Corporation <documentation>
</annotation>
<!-Dynamic Context Group Instance -->
<xsd:element name="Schedulec~GenericSMSMessaqe"
CA9-2002-0074 ? 3 type="SCheduledGene ricSMSMessageType", minOccurs="0"/>
<xsd: element name="ResponseRequiredGerieric:~M~~Message"
type=" ResponseReq~.ziredGeneric:SMSMessa~eType ", minOccurs="0"/>
<xsd:element name=" HighPriorityGenericSMSMessage"
type=" HighPriorityGenericSMSMe;;sage'Type", minOccurs="0"/>
<xsd:element name="GenericSMSMessa<~e"
type="GenericSMSMessage'rype", minOccurs="0"/>
<xsd:element name="BroadcastSMSMessage"
type="BroadcastSMSI~lessageType", minOccurs="0"/>
<xsd:comp=LexType name="ScheduledGenericSMSMessageType">
<xsd:sequence>
<xsd:element name="GenericSMSMessage"
type="GenE:ricSMSMessageType"/>
<xsd:attribute name="DateToBeSentOn" type="xs:date"/>
<xsd:attribute name="Ti~eToBeSentOn" type="xs:time"/>
</x~sd:sequence>
</xsd:comx>lexType>
<xsd:complexType name="ResponseRequiredGeneri.cSMSMessageType">
<xsd:sequence>
<xsd:element name="GenericSMSMessage"
type="GenericSMSMessageType"/>
<xsd:attribute name---"Inboi:ndTemplateld" type="xs:string"!>
</xsd:sequence>
</xsd:complexType>
<xsd:comF>lexType name="HighPrio rityGenericSMSMessageType">
<xsd:sequence>
<xsd:element name="GenericSMSMessage" type="GenericSMSMessageType"/>
<xsd:attribute name=°'DeliveryPriority"
type="DeliveryPriorityType" fixed="HIGH"/>
</xsd:sequence>
</xsd:complexType>
<:xsd:complexType name="GenericSMSMessageType">
<xsd:sequence>
<xsd;element name="short message text" type="xsd:string"
maxLength="160"/>
<xs~3:attribute name="ReceiverProf.ile" type="ReceiverProfileType"
minoccurs-="1" maxOccurs="1"/>
</xad:sequence>
</xsd:complexType>
<xsd: comp)_exType na:ne="Broad~~astSMSMessageType":>
<xsd:sequence>
<xsd:element name="short message text" type="xsd:string"
maxLength=="160"/>
<xsd:attribute name="ReceiverProfi~..e" type="ReceiverProfileType"
C'A9-2002-0074 25 minoccur:>="1" maxOccurs="unbounded" />
</xsd: sequence>
</xsd: cornplexType>
<xsd: simpleType name="Deliver?:riorityType"
<xsd:restriction base="xsd:string"~~
<~:sd:enumeration value="HIGH"/>
<~a d:enumeration value="MEDIUM"/>
<xa d:enumeration value="LOW"/>
</x:sd:restriction>
</xsd: sirr.pleType>
~:xsd:complexType name="ReceiverTransmissionF'rcfileType">
<xsd:sequence>
<xsd:element name="userid" type="xsd:string"/.
<xsd:element name="cellphonenumber" type="xsd:string"/ >
<xsd:element name="deliverychannel" type="DeliveryChannelType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="DeliveryChannelType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="SMTP"/>
<xsd:enumeration value="GSM"/~>
<xsd:enumeration value="SNPP"/>
<xsd:enumeration value="Mobitex"/>
<xsd:enumeration value=="DataTAC"/>
</xsd:restriction>
</xsd:simpleType>
</xsd: schema>
The following source code listing provides an illustration of a Typed (Categorized) SMS
Message Instance XSD Schema Definition of Commerce Payment Exception SMS Message <xsd:complexType name="Payment~~xceptionSMSMessage"=
<xsd:sequence>
<xsd:elementname="Re:>ponseRequiredSMSMess.age"
type="ResponseRequiredSMSMessageType"%>
</xsd:sequence>
l5 </xsd:c:omplexType >
Message Instance of a Payment Exception SMS Message <PaymentExceptionSMSMessage>
<Re;~ponseRequiredSMSMessag~~>
<HighPriorityGenericSMSMessage>
<GenericSMSMessage>
<short message text>
Your cheque bounced!
</short message text>
2S <ReceiverPro.file>
<userid>steve<iuserid>
<cellphone:number>
116123456?@ce ll~izcne , c:.om </cellphonenumber>
<deliverychannel>SMTP</deliverychanne'~>
</ReceiverProfile>
</GenericSMSMessage>
<DeliveryPrior-ity>HIGH</Deliveryl'riori.ty>
CA9-2002-0074 2~
</HighPriorityGenericSMSMessage>
<ConfirmationOfDelivery>CONFIPMED<%:~onfirmationOfDelivery>
<lRc~sponseRequiredSMSMessa;~e>
</PaymentExceptionSMSMessage>
XSD Schema Definition of Campaign Started Broadcast SMS Message <xsd:complexType name="CampaignStartedSMSMessage">
<xsd:sequence>
<xsd:elementname="BroadcastSM:~Message"
type="Broadcas-SMSMessageType"%>
</xsd:sequence>
</xsd:complexType >
Message Instance of a Campaign Started SMS Message 1$ <CampaignStartedSMSMessage>
<BroadcastSMSMessage>
<short message text>
New campaign has been started, visit our website </short message text:' <Receive=Profile>
<userid>steve<,/vserid>
<cellphonenumber>
91012395c: ;iacellphone. co~r.
</cellphonenumoer>
<deliverychannel>SMTP</deliverychannel>
</ReceiverProfile>
<ReceiverProfile>
<userid>joe</userid>
<cellphonenumber:>
4161~3456B~cel~hone. c'~m </cellphonenumb2r>
<deliverychannel>SMTP<ldelivery<:hannel>
</ReceiverProfile>
</BroadcastSMSMessage>
</CampaignStartedSMSMessage>
The SMS Encoding engine 11 I can automatically generate an SMS Message instance based on th.e SMS message type selected. The SMS Message Runtime Processor 110 is adapted to handle the semantics of a given predefined type. At runtime, if a SMS message sent is a ResponseRequiredSMSMessageType, the SMS Message Runtime Processor 110 waits a preset wait time for user confirmation. If confirmation is not received after the preset wait time, the to runtime processor 110 will sent the error to the corresponding application component 108 so that action can be performed according to that stipulated in the business process represented by that application component. For example, application component 108 may provide for resending, or rollbacking the transaction and marking this transaction as having failed completion. (Dx of Figure 1 Runtime processor 110 reports run time error to the application component for handling) How a User Creates a New SMS Type By Extending From an Existing Type Referring to Figure 3, which depicts a process for Using SMS Message Composing Wizard T'o Create a. New SMS Type In the SMS Universal Encoding Template, and Figure 1, which depicts a SKIS Message Composing GI~I for creating a new SMS type it will be readily understood 2o how a new SMS type can be created using a preferred embodiment of the invention.
In order the start 300 the process a business user clicks a button provided on the Message Composing Wizard 112 (see Fig. 1, 2) to instruct the system of the invention to create a new message type 301. The message composing wizard then reads in the SMS universal encoding template 11; (Fig. 1, 2) to present a selectable parent SMS type 405 for the user to create a new type in step 302. In step 303 the user enters a new message type name (see 404) and specifies all new attributes indicated by provided descriptions, 406, 407, 408, 409, 410, 41 t, 414, 415, 416, and the base (parent) type 405, to generate a new SMS type. Add and Delete buttons, 412, and 413 respectively allow insertion and deletion of items in the reply section, while buttons 402 and 403 are used to save or cancel the new message type as will be appreciated.
3o If a new response template is required for the new message type, 304, the response template manager is invoked by the business user to create the inbound template required, 305 and the inbound template database 11 S is updated, 306. if a new response template is not needed the new message type is saved, 307, int the SMS universal encoding template 113, reaching the end 308 of the process depicted in Figure 3.
2. Encoding End to End Flow Referring to Figure 5, which illustrates SMS message encoding flow following will be understood:
A: Business User invokes New Message Type Creator to create a new Message Type.
B: Business User invokes Inbound Template Manager to create a new Inbound Template for the rlew Message Type (thru the Inbound Template Manager).
C: Inbound Template Manager retrieves a list of predefined command list from the Inbound to Template DB. The command list is defined by the Application Component owners.
P: Inbound Template Manager inserts a new row into the Inbound Template DB
with the Response Action and Command selected by the Business User from the GUI.
E: Inbound Template Manager returns the newly created Inbound Template ID
(generated by the Inbound Template DB) to the New Message Type Creator.
1 s F: New Message Type Creator then saves the newly created message type (imbedded with the Inbound Template ID) into the SMS Universal Encoding Template (part #5).
2.1 Encoding An Outbound Message only message The SMS Composing Wizard allows business user to send a message to any registered 2o users in the e-Commerce system. All the complexity of transferring the message is handled by this invention. T'he business user just has to select a type of message, enter the message text and click the Submit button.
Micro Flow: Data Collection Interface, SMS Input Data Collection and Message Encoding 25 Engine Message processing by the encoding engine is shown by alphabetically labeled arrows in Figure 6 as discussed below.
A: Common Message Subsystem 107 or the SMS Message GL.1I Wizard (part #4) 112 calls the Data Collection Interface's 117 APIs (part #1 ) 510-516 to pass data collected from the message 30 originator.
B: The Data Collection Interface's APIs 510-516 pass the data to the Data Collection Object 518.
For example, calling the setTextMessage API 514 with the message text as parameter, the API 514 will save the text in the Data Collectian Object 518.
C: The sendMessage API 516 invokes the Typed SMS message encoder 701. It retrieves the message type name from the Data Collection Object 518. The message type name is captured by the messageInstanceCreation API 510. In this step, the Typed SMS message encoder 701 also collects other information from the Data Collection Object 518; such as: send time, send priority, f~esponseTemplate Id, text message, receiver info.
1D: Using the message type name, the Typed SMS message encoder 701 retrieves the SMS
Universal )=?ncoding template 113 for this message type.
>H:: The Typed SMS message encoder 701 creates a Temporary Typed SMS Message Instance 702 by converting the SMS Universal Encoding template 113 into a temporary Typed SMS message instance 70:? expressed in Document Object Model (which is an internal structure for XML) and fills in the information collected from the Data Collection Object 518 in C.
F': The Temporary Typed SMS Message Instance 702 is then passed to the SMS
Message Validator 703 to perform validation. The validation process involves checking of mandatory data, data semantic, data syntax, data range.
G: If validation is successful, the SMS Message Validator will copy the Temporary Typed SMS
2o Message Instance 702 into the final Typed SMS Message Instance (part #6) 114.
Steps 801 to 808 of Figure 8 depict the process above in a graphical flow diagram.
2.2 Encoding A ResponseRequired Message For a SMS message that requires a response, an Inbound Template should be included in the original outbound SMS message to a recipient. 'rhe Inbound Template provides a form based input mechanism for the recipient; it is adapted to encode the expected response of the recipient of a SMS message. The Inbound Template eases the burden of the recipient user trying to formulate a response back to the Application Component 108 that originated the outbound SMS message to the recipient. The response template serves to constrain the user's response by indicating the format of the response required to the user. As a result the user's response will be in a form that c;an be processed automatically by the web application server on its return.
Inbound Template: The structure of an inbound template is illustrated below:
<Short Message Text>
<Encrypted String>
<response action 1>
<response action 2>
<response action n>
2o PIN:<mobile user personal identification>
The Inbound Template structure depicted above supports multiple response actions.
Depending on the type of transaction, the recipient, likely a mobile user, will pick one of the response actions.
Figure 8 depicts the appearance of an outbound SMS message with indications of a required response to a recipient user as it would appear on the user's digital cell phone screen 901.
The SMS Message string to achieve this would resemble: Your cheque bounced!-lust-CONFIRMED: PIN:
2.2.1 SMS response message encoding template elements As may be seen from Fig. 9 the SMS response message encoding template elements for the inbound template include the following:
~ Short Message Text, 902 ~ Encrypted String, 903 ~ <response action, 904>:<response data, 906 >
~ PIN, 905 Figure 10 illustrates an SMS inbound message with a user response entered before being sent.
'?.2.1.1 Short Message Text 902 This is the message that the message originator intended to send to the receiver.
2 .2.1.2 Encrypted String 903 Encrypted String is a four character hashed string delimited by a pair of '-' The encrypted string is built upon the amalgamation of the following information:
- web application id (predefined by web app administrator, e.g. store ID) - userid (login id of the receiver of this store) - inbound template id (that includes command and expected parameter) as per database entry. This can be obtained from the Inbound Template DB (part #8) - Action id (id representing the response actions allowed in this message) - Hash Key - the user can change anytime to make the key expire. This can be saved in 2o a file in restricted directory.
The Runtime Processor 110 is responsible for generating this encrypted string using the above information as input. The Runtime Processor is also responsible for generating the Inbound Template before transferring the SMS message to the Wireless Message Gateway 103.
Advantage of using the encrypted string:
- the encrypted string can be limited to 4 bytes to save space from the 160 character limit - Encrypted string is unintelligible - Hash Key can be changed anytime by the business user to impose an arbitrary time out - Runtime Processor 110 can filter out unwanted incoming messages. An invalid or a missing encrypted string indicates the message is unwanted.
- Users can store the inbound template in their mobile devices so that they can initiate transactions with the designated web application any time at their own volition. This advantage will be discussed in detail in section 2.3.
2.2.1.3 <response action>:<response data>
Response action 904 is a keyword to identify allowable response actions and the corresponding parameters. In the example, the allowable response 904 is CONFIRMED. In this example, Fig. 10 the user has entered the response 906 Y. There can be more than one allowable responses for different transactions. There are three sub-elements in this response:
1. Response Action - the keyword representing the action. E.G. CONFIRMED
l0 2. Command - a web application program or command which the Runtime Processor will invoke These response actions and commands are saved in the Inbound Template DB (part #8) indexed by unique Inbound Template ID. Business user can use the SMS Message Composing Wizard (part #4) to manage these response actions. Refer to section 2.2.3 How to manage Inbound Template using the SMS Message Composing Wizard.
The runtime processor will invoke the command with the <response data 906>
when the responding SMS message is received.
2.2.1.4 PIN
2o The PIN element 905 provides for a user to enter a PIN number 904 specified by the user at user registration ( the user entered 1234 in this example). With the PIN and the userid (encrypted in the Encrypted string) the Runtime processor 110 can authenticate the originality of the inbound message.
2.'x.2. SMS response showing what a user would have input in the response Figure 9 illustrates the screen 1001 of a digital cell phone with a user response.
When the mobile cell phone user responded to the SMS message, the user would just have to select "forward message" to a designated phone number for the web application; enter the response data 3o for one of the response actions, enter the PIN number and hit the "send"
button.
In this example, the mobile cell phone user entered Y 906 beside CONFIRMED:
904 to indicate that lrelshe acknowledged the message.
CA9-2002-0074 3~
The SMS Message that would be received by the web application would resemble:
Your cheque bounced!-kis2-CONFIRMED:Y PIN:1234 For t:he processing of an inbound SMS message, please refer to section 3.2 "Response Required Message and Inbound Message End To End Flow".
2.2.3 How to manage Inbound Template using the SMS Message Composing Wizard.
Inbound Template Manager 502 (see Fig. 5) , a sub-component of the SMS Message Composing Wizard (part #4) (see Fig. 4) , is responsible for managing inbound templates. This l0 includes creation and deletion of the mapping between the response actions and the web application commands.
2.2.3.1 GUI
Figure 10 illustrates a GUI 1101 that could be used to compose a SMS message that would be sent by the web application server to a mobile user. In this instance it is illustrating a GUI for a payment exception message that could have been used to produce the message of Figure 8.
If a business user wanted to create a new SMS message type derived from this pressing NEW button 1102 would invoke the Create a new SMS Message Type panel 400 as illustrated in Figure 4. This panel could then be used to create a new message type.
Click on "Add" button 412 will invoke Add SMS (Reply) Inbound Template panel illustrated in Figure 11:
2.2.3.2 Inbound Template Manager Structure Diagram Figure 12 illustrates the structure of the inbound template manager 202.
The flow annotation for the inbound template manager follows:
A; Business User 900 invokes New Message Type Creator 201 to create a new Message Type.
B: Business User 900 invokes Inbound 'Cemplate Manager 202 to create a new Inbound Template for the new Message Type.
3o C.. Inbound Template Manager retrieves a list of predefined commands from the Inbound Template DB 115. The command list is defined by Application Component 108 (Fig. 1).
D: Inbound 'Template Manager 202 collects the information from GUI and update the Inbound Template DB 115.
E: Inbound Template Manager 202 returns the newly created Inbound Template ID
(generated by the Inbound Template DB 115) to the New Message Type Creator 201.
F: New Message Type Creator 201 then saves the newly created message type (imbedded with the Inbound Template ID) into the SMS Universal Encoding Template (part #5) 113.
2.2.3.3 Managing Inbound Template Flow Chart Figure 13 illustrates a flow chart depicting the steps I50 to 158 of how an SMS Message C'.omposing Wizard would be used to manage the response actions described above:
2.3 Encoding An Inbound Message For User's consumption Another useful application of the Inbound template is to allow mobile users to submit requests to the web application. For example, a user can send to the web application a request for account balance. Using a saved Inbound template far account balance request in the mobile device, the user can send this inbound template as an inbound SMS message. In response to this request, the web application will send the account balance as an outbound SMS
message assuming the incoming message passed validation and authentication.
2.3.1 Steps to implement this feature:
Stepl: Business User defines a list of inbound templates. This can be done using similar procedures in creating a new message type. A new message type called "InboundReduestGenericMsg" must be defined first. The Business user can then derive another inbound request message type with inbound template attached.
Step 2: An Application component called "Customer Services" publishes a list of defined Inbound Templates in the store web site.
Step 3: Users logon on to the store web site and select the inbound templates they wish to download.
Step 4: The (Justomer Service Application Component sends the selected Inbound Templates to the mobile device. The transmission can be completed by using the Common Message Subsystem which calls the Data Collection Interface's APIs (part #1 ).
2,.3.1 Structure Diagram Figure 14 depicts a Structure Diagram of a SMS system in accordance with a preferred embodiment of this invention depicting the process of a Business User Sending an SMS Message.
The flow annotation follows:
A: Business user 900 defines new message types and corresponded inbound templates. This is done by using the SMS Message Composing Wizard I 12 (hig. 1 ).
>g: SMS Message Composing Wizard I 12 stores these new message types and inbound templates in the SMS Universal Encoding Template (part #5) 113 and Inbound Template DB
(part #8) 115 respectively, C': Mobile user 901 logons to the web site for the system and requests a list of inbound templates.
D: The Customer Service Application Component 161 obtains the Inbound Template IDs from the SMS Universal Encoding Template 113. Using the IDs, the Customer Service Application Component 161 retrieves the available inbound templates from the Inbound Template DB 115 using the IDs.
E: The Customer Service Application Component 161 displays the list of inbound templates to the mobile user 901.
F: The mobile user 901 selects the inbound templates desired and requests them to be sent to his/her mobile device.
G: The Customer Service Application Component 161 sends a request to the Common Message Subsystem 107 to send the selected inbound templates as generic SMS messages.
3o H: The Common Message Subsystem 107 calls the Data Collection Interface's APIs (part #1) 117 to transmit the inbound templates as generic SMS messages I: The SMS Message Encoding Engine (part #2) 111 encodes the SMS messages containing the CA9-2002-0074 3'l inbound templates and sends them to the Runtime Processor (part #3) 110.
J: The Runtime Processor 110 inserts an encrypted string into the SMS
messages. This encrypted :string preferably should not have an expiration time since the templates will be used for input requests. The SMS messages are sent to the Wireless Message Gateway 162.
K: Wireless Message Gateway 162 delivers these messages to the mobile user 901.
L: Mobile user 901 saves these inbound templates in the storage of his/her mobile device. Mobile user 901 can now use these inbound templates to submit a request or requests to the application component 108.
M: The Wireless Gateway 162 transfers inbound SMS messages from mobile users to the Runtime Processor 110.
N: The Runtime Processor 110 examines the encrypted string in an inbound SMS
message to determined if this is an inbound request. If the message is authenticated, the Runtime Processor 110 will invoke the corresponding command owned by the relevant Application Component 108 of the SMS enabled commerce system.
2.3.2 Flow Chart Figure 15 illustrates a flow chart of a business user obtaining selected inbound templates in accordance with a preferred embodiment of the invention similar to that depicted in Figure 13.
3. Run Time End To End Flow This section outlines runtime processing of an embodiment of the invention, cover outbound mcasage generation and inbound response message processing.
3.1 Outbound Message End to End Message Processing Flow Figure 5 outbound flow diagram depicting outbound message handling flow of an SMS
ecommerce system of one embodiment of the invention.
CA9-2002-0074 3 s F figure 17 depicts an outbound flow diagram of the environment of the invention. Referring to Fig.
17, it can be seen that:
~ Typed SMS Message Instance I 14 generated by Message Encoding Engine 111 is checked to see if it is a scheduled message.
~ If it is a scheduled message to be sent later, save the message into the SMS
Message Tracking DB 195. Scheduler 182 will periodically read the SMS Message Tracking DB
195 to retrieve messages which are due to send.
If the message is due to send, it will be checked for type error by comparing to the type saved in the Universal Encoding Template 113.
~ If there is a type error, generate and return error.
~ If there is no type error, parse the message using the XML parser 1918 with the input of the Universal Encoding Template 113 The XML parser 1918 parses the Typed SMS Message Instance which is in a DOM
tree format 1912.
~ Check to see if the message requires a response ~ If response is not required, dispatch the message using the wireless gateway 103, then stop ~ If response is required, extract the message template id from the parsed message.
~ Find the inbound template1916 using the message template id from Inbound Template DB
115.
~ Using the Typed SMS Message Instance 1 I 4 and inbound template I 916, generate the final SMS message ~ Create the session object 1927 ~ Using the session object, WebAppID 1928, UserID 1929, Template ID 1930 and Encoding Key 1931, generate the encrypted string 1924 ~ Insert the encrypted string 1924 into the final SMS message ~ Dispatch the final SMS message using the wireless gateway 103, then stop.
3.2 ResponseRequiredMessage and Inbound Message End To End Message Processing Flow.
Figure 18 depicts inbound flow diagram. It can been seen that:
~ Wireless Gateway 103 received an Inbound SMS message 2003 ~ Runtime Processor 110 extracts the four character encrypted string 2005 from the Inbound SMS message 2003 ~ With the encoding key 1931, the encrypted string 2005 is decoded ~ If decoding is not successful, then stop.
~ If decoding is successful, extract the WebApp ID from the encrypted string 2005.
If the WebApp ID does not match the current WebApp ID, then stop ~ If the WebApp ID does match the current WebApp ID, extract the template ID
from the to encrypted string 2005.
~ Using the template ID extracted from the above, get the inbound template 2014 from the Inbound Template DB 115.
~ Extract the parameter names, command and values 2017 from the Inbound SMS
message 2003.
~ Extract the User ID from the encrypted string 2005 ~ Create the message for the Commerce Server (Command Context Object 2020) using the command name, parameters and Llser ID extracted above.
~ Dispatch the said message to the Commerce Server I 08 ~ All is completed Figure 16 illustrates a detailed example of the runtime processor 110 of an embodiment of the invention depicting details sufficient for a description of the confirmation response run time processing flow. An explanation of the elements of runtime processor I 10 and their interaction follows:
2s Typed Message Instance: The typed message instance 114, is the actual outbound SMS message as received from the Encoding Engine (or the Scheduler for a scheduled message) by the runtime.
In the current implementation scheme this message is encoded in XML in accordance with the Universal Encoding Template schema.
CA9-2002-0074 ao Typed Message Parsing Subsystem: The typed message parsing subsystem 181, consists of a parser for the typed XML message. Its job is to verify that the incoming message is correctly encoded in accordance with the schema and also to parse this message into a DOM tree (for the current implementation).
The output of this subsystem is a parsed object that contains the entire contents of the outbound SMS message in computer readable memory object format.
Message Tracking Subsystem: The message tracking subsystem 183 updates the SMS
tracking to DB with statistics about message sent time, message receipt time etc.
Scheduler: The scheduler subsystem 182 is responsible for timed relaying of SMS messages. If an SMS message requires to be sent at some scheduled time then this subsystem is responsible for caching the message in the message tracking DB.
I5 Also this subsystem is responsible for polling the message tracking DB at intervals decided upon by the business mmager and picking up messages that are ready for dispatch and forwarding to the typed message parsing subsystem for delivery.
Application Key Generator Subsystem: The application key generator subsystem 184 is 2o responsible for generating the encrypted string that goes out with SMS
messages that require user response. This subsystem uses a system wide, time sensitive encoding/decoding key to encode this session string;.
The encrypted string itself consists of the following:
z5 1. WebApp ID
2. User ID
3. Inbound Template ID
4. Session Object ID
3o As this encrypted string is based on the time sensitive encoding and decoding key, this invention provides the break through in SMS to achieve the effect of a session in SMS, which was not able to be done before.
With the notion of session being introduced in SMS now, we can now create session object CA9-2002-00'74 which can be used for SMS based session data storage.
After the encrypted string is decoded by the time sensitive decoding key, each element (the WebApp ID, the UserID, the inbound TemplateID, and the sessionID) c<tn be decoded at the second stage by its own corresponding decoding key (WebAppIDKey, UseridKey, inboundTemplateKey, sessionIDKey).
Thus, the final encoding is a two stage encoding scheme that can only be decoded successfully if both the system wide encoding key and the WebApp ID are correct. This leads to added security for the outbound session string.
Outbound Message Generator: The outbound message generator subsystem 185 encodes the 1o final 160 character outbound message by using the parsed outbound SMS
message generated by the typed message parsing subsystem and the session string generated by the Application Key Generator Subsystem. After creating this SMS message it forwards it to the wireless gateway 103 far final delivery to the end user.
Inbound Message Parsing Subsystem: The inbound message parsing subsystem 186 has the task of first, decoding each incoming message using the encrypted string and the system wide encoding key and the WebApp ID. After verifying that this message can be decoded correctly, the subsystem extracts the Inbound Template ID and looks up the inbound template from the Inbound Template DB to parse the incoming message.
2o A successful parsing of the inbound message leads to extraction of incoming command and parameters. 'This subsystem then extracts the User ID from the encrypted string and creates the command context object for this incoming request. Before creating the command context object, this component also verifies the incoming PIN number for authentication using the application component 108 authentication mechanism.
The next step is to actually dispatch this message to the relevant application component.
It co-operates with the Message 'Tracking Subsystem to track incoming SMS
messages for receipt time and other statistics.
3o CONCLUSION
The embodiments of the invention described herein provide a number of advantages and distinctions over prior SMS messaging systems:
1. Confirmation the inbound template being park of the outbound SMS message text body provides a system for confirmation that would readily processable by a web application.
- The SMS Response Database provides enablement of run time confirmation as required by the message type.
- The absence of confirmation in previous SMS systems hinders the application of SMS
in commerce. This invention provides a solution to this limitation with encrypted string such as userid and PIN, making the confirmation of a user possible.
2. Security - The inbound SMS message can preferably include an encrypted string with two levels of encryption. This ensures that the relevant web application only handles incoming sms messages that are directed towards that web application.
- The userid is obtained by a second level userid key, together with a user specified PIN
number, providing additional layers of security protection.
~ 5 - A 4 byte security mechanism can make sms application in commerce possible.
- The two level encoding is as used herein is new as is the amalgamation of 4 elements (web app id, userid, inbound template id, session object id) into 4 bytes and decoded with two level of keys.
3. Session Control If the Session ID is encrypted in the SMS string this will provide a timeout control for typical http sessions.
- The matching of the encrypted string with the outbound message provides a request and response model, making the formation of~ a session possible.
- With this session, cohesive requests and responses between the user and the web application are now possible, making commerce applications in SMS practical.
- The 4 byte encrypted string in the message is new - The timestamp and the system key added to the encrypted string is new - The SMS response DB together with the Run Time Process to manage the session effect of request / response SMS messages at run time is new to SMS messaging.
4. Extensible Syntax: Rules for Encoding and Decoding a SMS Message - . The encoded inbound message template enables the unambiguous interpretation of an inbound SMS message leading to unambiguous mapping to a selected business action of a web application of the messaging system.
- This syntax is extensible to create new inbound message templates.
- Including the inbound message template in the outbound message so user does not need to formulate their own inbound message is new to SMS. Now the user only needs to fill in specific required parameters 7~he extensibility of the syntax to create other syntax in new message types is new.
5.1 Extensible Semantics: Interpretation Of Encoding Mapped To unambiguous Business to Actions T'he predefined categorization of the invention serves as a contract between the user and the web application of the business pracess so that the interpretation of a given sins message is unambiguous and maps to a definite business action of a predefined business process, making commerce application of SMS possible.
- The base categorization is extensible to define new categorization for new mapping of business actions.
- The application of xml schema (with inherent characteristics including categorization and deriving new categorization) as a SMS Universal Encoding Template in the space of SMS is new.
5.2 Extensible Semantics: Handling of SMS Messages at runtime in accordance with encoding characteristics in corresponding message types - The SMS Universal Encoding Template enables extra information about the SMS
messages to be shared between the Web Application and the message Run Time Processor. The Run Time Processor can now (based on the extra semantic characteristics as defined in the SMS type) perform type-appropriate run time tasks consistent with the intent of the sender (business user) as understood by the web application.
6. Enhanced Usability - Business users axe now spared from the technical complexity of encoding a SMS
message to match their business intents. Business user can now focus on the content of the message without being distracted by SMS message encoding.
- The SMS commerce solution of this invention reduces the possibility of encoding error (as SMS encoding errors are difficult and expensive to solve at run time). The mechanism of encoding ensures error checking and provides early identification of encoding errors.
CA.9-2002-0074 45
Claims (30)
1. An SMS universal encoding template for encoding outbound SMS business messages for a data processing system for transmission over a network; comprising:
categorization meta data defining a categorization of outbound SMS messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating SMS business messages.
categorization meta data defining a categorization of outbound SMS messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating SMS business messages.
2. An SMS universal encoding template for use by a message encoding engine of an ecommerce server for encoding outbound SMS messages from a web application to an SMS
dispatcher (runtime processor) for transmission over a wireless network, comprising:
categorization meta data defining categorizations of outbound SMS messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding SMS business messages for handling by said SMS dispatcher for transmission over said wireless network.
dispatcher (runtime processor) for transmission over a wireless network, comprising:
categorization meta data defining categorizations of outbound SMS messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding SMS business messages for handling by said SMS dispatcher for transmission over said wireless network.
3. The SMS universal encoding template of claim 1 providing a message entry field for insertion of a message entry of full SMS message length for access by a recipient;
said template providing an additional field in said SMS message for categorization meta data; and said meta data providing instructions for encoding a business intent of an ecommerce SMS
message.
said template providing an additional field in said SMS message for categorization meta data; and said meta data providing instructions for encoding a business intent of an ecommerce SMS
message.
4. The SMS universal encoding template of claim 3 wherein said meta data includes instructions fir dispatching said SMS message including instructions selected from the following set pertaining message priority, delivery time, number of recipients, delivery channel, confirmation, authentication, encryption, intended web application to handle a response.
5. The SMS universal encoding template of claim 3 wherein said meta data includes instructions for identifying a software application intended to handle said response.
6 A method of implementing an SMS universal encoding template for encoding outbound SMS business messages for a data processing system for transmission over a network; comprising providing:
categorization meta data defining a categorization of outbound SMS messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating SMS business messages.
categorization meta data defining a categorization of outbound SMS messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating SMS business messages.
7. A method of implementing an SMS universal encoding template for use by a message encoding engine of an ecommerce server for encoding outbound SMS messages from a web application to an SMS dispatcher (runtime processor) for transmission over a wireless network, comprising providing:
categorization meta data defining categorizations of outbound SMS messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding SMS business messages for handling by said SMS dispatcher for transmission over said wireless network.
categorization meta data defining categorizations of outbound SMS messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding SMS business messages for handling by said SMS dispatcher for transmission over said wireless network.
8. The method of implementing an SMS universal encoding template of claim 6 providing a message entry field for insertion of a message entry of full SMS message length for access by a recipient;
said template providing an additional field in said SMS message for categorization meta data; and said meta data providing instructions for encoding a business intent of an ecommerce SMS
message.
said template providing an additional field in said SMS message for categorization meta data; and said meta data providing instructions for encoding a business intent of an ecommerce SMS
message.
9. The method of implementing an SMS universal encoding template of claim 8 wherein said meta data includes instructions for dispatching said SMS message including instructions selected from the following set pertaining message priority, delivery time, number of recipients, delivery channel, confirmation, authentication, encryption, intended web application to handle a response.
10. The method of implementing an SMS universal encoding template of claim 8 wherein said meta data includes instructions for identifying a software application intended to handle said response.
11. An article comprising:
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to perform the method of any of claims 6 to 10.
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to perform the method of any of claims 6 to 10.
12. An article comprising:
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to implement the apparatus of any of claims 1 to 5.
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to implement the apparatus of any of claims 1 to 5.
13. The article of claims 11 or 12 wherein said medium is selected from the group consisting of magnetic, optical, biological, and atomic data storage media.
14. The article of claims 11 or 12 wherein said medium is a modulated carrier signal.
15. The article of claim 13 wherein said signal is a transmission over a network.
16. A universal encoding template for encoding outbound business messages for a data processing system for transmission over a network; comprising:
categorization meta data defining a categorization of outbound messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating business messages.
categorization meta data defining a categorization of outbound messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating business messages.
17. A universal encoding template for use by a message encoding engine of an ecommerce server fir encoding outbound messages from a web application to an dispatcher (runtime processor) for transmission over a wireless network, comprising:
categorization meta data defining categorizations of outbound messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding business messages for handling by said dispatcher for transmission over said wireless network.
categorization meta data defining categorizations of outbound messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding business messages for handling by said dispatcher for transmission over said wireless network.
18. The universal encoding template of claim 16 providing a message entry field for insertion of a message entry of full message length for access by a recipient;
said template providing an additional field in said message for categorization meta data;
and said meta data providing instructions for encoding a business intent of an ecommerce message.
said template providing an additional field in said message for categorization meta data;
and said meta data providing instructions for encoding a business intent of an ecommerce message.
19. The universal encoding template of claim 18 wherein said meta data includes instructions for dispatching said message including instructions selected from the following set pertaining message priority, delivery time, number of recipients, delivery channel, confirmation, authentication, encryption, intended web application to handle a response.
20. The universal encoding template of claim 18 wherein said meta data includes instructions for identifying a software application intended to handle said response.
21. A method of implementing a universal encoding template for encoding outbound business messages for a data processing system for transmission over a network;
comprising providing:
categorization meta data defining a categorization of outbound messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating business messages.
comprising providing:
categorization meta data defining a categorization of outbound messages;
said categorization representing a specific businesses intended usage; and said categorization meta data providing definitions of messages and instructions that are parsable by said data processing system for generating business messages.
22. A method of implementing a universal encoding template for use by a message encoding engine of an ecommerce server for encoding outbound messages from a web application to an SMS dispatcher (runtime processor) for transmission over a wireless network, comprising providing:
categorization meta data defining categorizations of outbound messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding business messages for handling by said dispatcher for transmission over said wireless network.
categorization meta data defining categorizations of outbound messages;
each of said categorizations representing a specific businesses intended usage;
said categorization meta data providing definitions of messages and instructions that are parsable by data processing systems for encoding business messages for handling by said dispatcher for transmission over said wireless network.
23. The method of implementing a universal encoding template of claim 21 providing a message entry field for insertion of a message entry of full message length for access by a recipient;
said template providing an additional field in said message for categorization meta data;
and said meta data providing instructions for encoding a business intent of an ecommerce message.
said template providing an additional field in said message for categorization meta data;
and said meta data providing instructions for encoding a business intent of an ecommerce message.
24. The method of implementing a universal encoding template of claim 23 wherein said meta data includes instructions for dispatching said message including instructions selected from the following set pertaining message priority, delivery time, number of recipients, delivery channel, confirmation, authentication, encryption, intended web application to handle a response.
25. The method of implementing a universal encoding template of claim 23 wherein said meta data includes instructions for identifying a software application intended to handle said response.
26. An article comprising:
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to perform the method of any of claims 21 to 25.
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to perform the method of any of claims 21 to 25.
27. An article comprising:
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to implement the apparatus of any of claims 16 to 20.
a computer readable signal bearing medium;
computer program code means recorded on said medium adapted to implement the apparatus of any of claims 16 to 20.
28. The article of claims 26 or 27 wherein said medium is selected from the group consisting of magnetic, optical, biological, and atomic data storage media.
29. The article of claims 26 or 27 wherein said medium is a modulated carrier signal.
30. The article of claim 28 wherein said signal is a transmission over a network.
Priority Applications (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002406568A CA2406568A1 (en) | 2002-10-04 | 2002-10-04 | Method and apparatus for a universal encoding template for sms ecommerce messaging |
| PCT/GB2003/004336 WO2004032542A2 (en) | 2002-10-04 | 2003-10-03 | Method and apparatus for an e-commerce message using sms |
| KR1020057004425A KR100861740B1 (en) | 2002-10-04 | 2003-10-03 | Method and apparatus for an e-commerce message using sms |
| JP2004540999A JP4345893B2 (en) | 2002-10-04 | 2003-10-03 | Method and apparatus for e-commerce message using short message service |
| AU2003269255A AU2003269255A1 (en) | 2002-10-04 | 2003-10-03 | Method and apparatus for an e-commerce message using sms |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002406568A CA2406568A1 (en) | 2002-10-04 | 2002-10-04 | Method and apparatus for a universal encoding template for sms ecommerce messaging |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2406568A1 true CA2406568A1 (en) | 2004-04-04 |
Family
ID=32331615
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002406568A Abandoned CA2406568A1 (en) | 2002-10-04 | 2002-10-04 | Method and apparatus for a universal encoding template for sms ecommerce messaging |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2406568A1 (en) |
-
2002
- 2002-10-04 CA CA002406568A patent/CA2406568A1/en not_active Abandoned
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10810623B2 (en) | E-commerce messaging using SMS | |
| US8364711B2 (en) | Contact management system and method | |
| US8002178B2 (en) | Virtual membership card system and providing method, and virtual membership card reading method | |
| CN100514320C (en) | Message screening system and method | |
| US20050198124A1 (en) | System and method for embedded instant messaging collaboration | |
| US20100153407A1 (en) | Method and system for automated document registration | |
| CN104333599A (en) | Application sharing method and system and application service platform | |
| CN101689210A (en) | Gathering and search are from the profile data of a plurality of services | |
| CN101652967A (en) | Be used to reduce the method and system of the propagation of electronic information | |
| WO2012113253A1 (en) | Method and system for downloading content | |
| CN111177597B (en) | Method for collecting electronic invoice through code scanning, electronic equipment and storage medium | |
| US20040128524A1 (en) | Delivery system for delivery items, delivery agency server apparatus, cryptogram reader, delivery method for delivery items, program, and recording medium | |
| WO2007076698A1 (en) | A information collection,transmission and processing system and method based on short messages of mobile telephone | |
| KR100861740B1 (en) | Method and apparatus for an e-commerce message using sms | |
| FI118832B (en) | Method and apparatus for providing service in a computer network | |
| US20070050371A1 (en) | Interacting with an online database through a variety of communications media | |
| CN1941778B (en) | Third party access gateway for telecommunications services | |
| KR20010103240A (en) | certification of contents/attestation method using internet | |
| US20080176587A1 (en) | System and a method for sending digital content to a mobile device | |
| CA2406568A1 (en) | Method and apparatus for a universal encoding template for sms ecommerce messaging | |
| CA2406711A1 (en) | Method and apparatus for generation and processing of sms ecommerce messages | |
| CA2406869A1 (en) | Method and apparatus for processing an incoming ecommerce sms message | |
| KR20040009343A (en) | A system and method for providing multi-media messaging service | |
| JP2004318442A (en) | Authentication support method and its system | |
| KR100904386B1 (en) | Method and system for providing information change service by using hub relay |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued | ||
| FZDE | Discontinued |
Effective date: 20080623 |