NZ527670A

NZ527670A - Intelligent wireless messaging system

Info

Publication number: NZ527670A
Application number: NZ527670A
Authority: NZ
Inventors: Mark Campitt Loveys; Maurice John Bryham
Original assignee: Datasquirt Ltd
Priority date: 2001-06-15
Filing date: 2002-06-14
Publication date: 2005-05-27

Abstract

A system for handling an order which is received from any 'text messaging" or other wireless data transmission protocol capable wireless communication device comprises: a means for receiving an order message from the wireless device; a means for extracting an indication of the identity of the wireless device from the order message a means for obtaining information associated with the indicated identity where the information comprises information on a wireless device user associated with the wireless device identity and a nominated method of payment for the order and a means for sending an order confirmation message using the identity to the wireless device.

Description

<div class="application article clearfix" id="description"> 5276 70 - 1 - INTELLIGENT WIRELESS MESSAGING SYSTEM FIELD OF INVENTION 5 The present invention relates to a system for data communications particularly though not solely for data communications using wireless communication protocols. BACKGROUND ART 10 In the delivery of cellular telephones it has recently become popular to provide as well as voice communications, the ability to communicate short text messages between users on the same network. In particular the currently favoured GSM digital protocol allows that any phone in the world connected to a GSM digital network in their particular country is able to send an "SMS" protocol text message directly to a phone in any other 15 country so long as it also is connected to a GSM digital network. Systems have been developed that allow communication between e-mail gateways and the SMS message system. The processing engine of said system translates the e-mail message into the format required by the secondary character protocol (SMS, facsimile, 20 courier, mail etc). Newer cellular phones allow connection directly to the Internet and allow access to E-mail. However even with these newer phones use of E-mail is labourious and sometimes slow. There are some cellular networks that determine the location of each cellular phone 25 eg: "Location Based Services". There are also systems that provide information based on desired criteria to the handset. Often this will include a range of information some of which may not be relevant of desired by the specific user. 30 Outlook and other organisation or scheduling packages have the ability to send Intellectual Propsi jy electronic meeting requests to the desired attendees. Similarly newer < ;ellular of N Z. 14 MAR 2005 RECEIVED -2- include a digital diary, from which meeting requests (Vcalender format) can be sent to other cellular phones. However since the emailed meeting requests are in a proprietary format the two systems are incompatible 5 SUMMARY OF THE INVENTION 10 It is therefore an object of the present invention to provide a data communication system which goes some way to overcoming the disadvantages in the above mentioned prior art or which will at least provide the public with a useful choice. In a first aspect the present invention may be broadly said to consist in a method for handling an order, said order received from any "text messaging" or other wireless data transmission protocol capable wireless communication device, comprising the steps of: receiving an order message from said wireless device; 15 extracting an indication of the identity of said wireless device from said order message; obtaining information associated with said indicated identity, said information comprising information on a wireless device user associated with said wireless device identity and a nominated method of payment for said order; and 20 sending an order confirmation message using said identity to said wireless device. In a second aspect the present invention may broadly consist in a system for handling an order, said order received from any "text messaging" or other wireless data transmission protocol capable wireless communication device, comprising: 25 means for receiving an order message from said wireless device; means for extracting an indication of the identity of said wireless device from said order message; means for obtaining information associated with said indicated identity, said information comprising information on a wireless device user associated with said wireless 30 device identity and a nominated method of payment for said order; and means for sending an order confirmation message using said identity to said Intellectual Propeiiy wireless device. Office of N.Z. 14 MAR 2005 RECEIVED -3- This invention may also be said broadly to consist in the parts, elements and features referred to or indicated in the specification of the application, individually or collectively, and any or all combinations of any two or more of said parts, elements or 5 features, and where specific integers are mentioned herein which have known equivalents in the art to which this invention relates, such known equivalents are deemed to be incorporated herein as if individually set forth. The invention consists in the foregoing and also envisages constructions of which 10 the following gives examples. BRIEF DESCRIPTION OF THE DRAWINGS Preferred forms of the present invention will now be described with reference to the 15 accompanying drawings in which: Figure 1 is a block diagram of the architecture according to the preferred embodiment of the present invention and Figure 2 is a block diagram of a SMS purchase system according to the present invention. 20 Figure 3 is a schematic diagram of the SMS purchase system according to the present invention. Figure 4 is a schematic diagram of the messaging engine system according to the present invention. 25 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring to Figure 1 the present invention is depicted with a number of users connected through various interfaces. In the preferred embodiment a system server 4 is connected by a data network, either the Internet 3 or other data communications to a 30 plurality of local user interfaces 1,2. Each local user interfaces 1,2 will typically include E-mail software preferably with organisational or scheduling capacity eg: Microsoft Outlook. As is known in the art E-mail messages including attachments may be sent fror l one l8teD®?*ua' PrcP- ;6 B 3 Office of N.Z. ;1 h MAR 2005 ;RECEI ;-4- ;user interface 1 to another local user interface 2 or in the preferred embodiment to the system server 4. Typically each of the local user interfaces 1, 2 will have a single E-mail address, whereas the system server 4 may have provision for a large number of E-mail addresses. ;5 In the preferred embodiment of the present invention each of the local user interfaces 1,2 are able to send an E-mail including a telephone number (of a cellular telephone connected to one of a certain number of approved cellular networks) as part of the address to the system server 4. The system server 4 includes a database 13 to store each received message for later actions and billing purposes. A relational database such as SQL 10 or others as are known in the art would be suitable for this purpose. ;The system server 4 is in turn connected to SMS gateway 7. The SMS gateway is capable of sending and receiving seven or eight bit data packets which often include short text messages or other data such as Calender or Vcard messages. Each SMS gateway 7 is 15 connected through a cellular network 9 eg: GSM or other protocols to each cellular telephone 10. Each SMS gateway 7 is connected to other SMS gateways eg: in other countries, thorough the Internet or other data communications network 8. In turn each cellular network 9 is interconnected to other cellular networks through similar data communications networks. ;20 ;Referring now to Figure 4 the present invention according to one preferred embodiment is illustrated with each step in the process implemented by the messenging engine or system server or text code server broken up to its requisite functional components. For example message origination 120 includes the sources such as mobile ;25 orginate ie SMS, application software, internet or database orginate, email orginate or heart beat (internal) which then is supplied to the inbound transport operation 122. The comunication protocol stack processes the message processing 124 into functions such as the inbound receptor, the application engine, the outbound queue, the messaging engine as well as interfacing with a SQL database and website reporting trend analysis and other etc. ;30 From there intelligent carrier and transport switching 126 interfaces with a number of ;GSM, CDMA and facsimile gateways which send messages to the extern^l_w£irkL_Em: ;Intellectual Property Office of N.Z. ;14 MAR 2005 ;RECEIVE ;example message delivery return 128 can be received by an SMS mobile application internet or database software, email, facsimile or internally routed messaging. ;Message Response System ;In the preferred embodiment a user sends an initiating E-mail to the system server 4. The E-mail will have an address eg: 6421631071@mysystem.com which includes the domain name of the system server 4 eg: mysystem.com and the full telephone number eg: 6421631071 of a cellular telephone 10. The E-mail itself may include a simple message to be conveyed to the cellular telephone or may be formatted as a response required question. Generally the question will only require a simple one key answer from the cellular telephone user. ;The system server 4 receives the E-mail and converts the content from E-mail format into SMS format. The initiating text message is then sent to the SMS gateway 7 addressed to the full telephone number of the cellular telephone 10. After sending, the system server 4 stores message key in association with the message in the database 13. The message key is received from the SMS gateway 7 as identification of the message. ;If the cellular telephone 10 replies to the system server 4 associates the response message back to the initiating message using the stored message key from the database. In one embodiment of the present invention on receipt of the response message the system server 4 sends a response E-mail back to the original sender, including the initiating message and the response message. For example if in the initiating E-mail included the question "Do you want to go to dinner tonight?" and the response message was "Y", the response E-mail might be: ;Or alternatively if the question was "What time do you want to go to dinner tonight?": ;You asked Ryan ;"Do you want to go to dinner tonight?" Ryan replied ;"Yes" ;You asked Ryan ;Intellectual Prope.jy Office of N.Z. ;1 4 MAR 2005 ;-6- ;"What time do you want to go to dinner tonight?" Ryan replied "9 pm" ;5 In a further embodiment the receipt of the response message above "17" ie: 9pm might then result in a booking request being emailed to a restaurant. This might for example be in the form of a meeting request if the restaurant in question was using Microsoft Outlook or other scheduling software. ;10 In an still further embodiment of the present invention the initiating E-mail could include the full facsimile number of a desired recipient by facsimile transmission. On receipt of the initiating E-mail the system server 4 would send an initiating facsimile to facsimile machine 5. ;15 Targeted Message alerts ;In another preferred embodiment of the present system the system server 4 would poll the SMS gateways 7 for the current location of the cellular telephone 10 of a registered user. Software on the system server tracks the location over time and using stored 20 geographical information predicts where the user might be in for example 10 min. The system server then looks through its database of updated information to see if it can locate information relevant to that predicted future location. If something of relevance is located a message is sent. ;25 The prediction of future location may be made using any number of intelligent algorithms as art known in the art. In the preferred embodiment the specific geographic location, the direction of travel and the speed of travel are tracked. This is matched against a set of rules to predict if the user falls within one of a number of known activities eg: travelling along the motorway, going to the gym etc. Once a prediction has been made 30 where the registered user has requested certain information eg: traffic updates on the motorway they are travelling they will be sent information only if the ormHitinnc are met ;Intellectual Property Office of N'.Z. ;2035 ;-7- ;Similarly the user may request that alerts be only sent in certain circumstances. For example only send the swell at the beach if its over a ceratin level; only send me information on a specific motorway if the user is travelling on that particular motorway; only send me weather information when the outlook changes and only between ceratin 5 hours. When the user registers they can chose from a range of alerts any conditions on when the alerts are sent or a combination of conditions to be met. ;Also when the alerts are sent part of the content could be depicted by logos, ;pictures or even tunes. The picture messages or logos could be chosen by software on the 10 system server 7 as being relevant or representative of information. For example if it was a overcast day with possibility of rain you might have a message sent with a picture of cloud with some rain coming out of it, if it was a sunny day you might have a sun. Also services of this type might be provided free if a simple advertisement were appended at the end each alert. The advertiser would benefit since by registering for that particular alert the user is 15 likely to fall within a particular target audience which the advertiser is targeting. ;Converting meeting requests ;As already mentioned Microsoft Outlook meeting requests are incompatible with 20 the Calender format used in GSM digital cellular telephones. In the preferred embodiment, the present invention converts meeting requests emailed to a cellular telephone to the Calender format. ;25 ;30 ;As previously described the system server 4 receives emails addressed in part to the telephone number of the cellular telephone 10. In this case the E-mail takes the form of a meeting request format. Software on the system server 4 recognises the format of the message and converts the content into the Calender format. An SMS Calender message is then sent to the cellular telephone 10 through the SMS gateway 7. Options to view, save and discard are available at time of receipt of the message. ;Similarly the system server 4 will recognise a contact informati( ;convert it to a Vcard message. This is sent through the SMS gateway 7 and reo ft1' < VI " I, F -fit-tii-anrl ;WeiTectus! Props; ;1 4 MAR 2005 ;receive ;the cellular telephone 10 as a Vcard whereby those contact details are entered into the local address book. If the present invention was not used the messages would not be recognised as Vcalendar or Vcard messages - the cellular telephone would interpret them as simple messages. ;SMS Gateway Switching ;In order to get a good balance between cost and performance of the system in the preferred embodiment, the present invention is able to dynamically switch between a range of SMS gateways based on a number of preset criteria. The criteria are arbitrary but in the preferred embodiment software on the system server 4 periodically tests each route 7 for speed of delivery. ;The system tests the performance of each route by sending loop back test messages. The loop back tests are conducted by generating test messages and sending the test messages using the targeted route. The system then monitors the length of time taken to receive the test message, rating the route's performance accordingly. ;To decide which route 7 to use for a given message the following criteria is tested by the system: ;1. Is a seven bit or eight bit route required eg: Calender messages require eight bit, text messages only requires seven bit; ;2. Has preferential service been requested- as to whether a higher quality of service ie: dependability etc and higher cost is incurred; ;3. What is the current time ie: some routes will be avoided in their recognised peak times; ;4. Of the remaining routes have all of them achieved a recent speed of delivery better than a threshold level of acceptable service; ;5. Of the remaining routes which is the least expensive. ;Once the preferred route is chosen the message is sent. If the message is not sent successfully the next most desirable route is used until the message is sent succes! ;Igfejdfftual Propeuy Office of N.Z. ;1 h MAR 2005 ;-9- ;In addition to testing the availability and performance of message routes, this system also checks the integrity of the entire system, alerting system administrators to possible problems anywhere across the system. The alert could include SMS, pager, facsimile, 5 automated telephone or other automatic messaging facilities. The additional tests check the availability of the application, database and web servers of the system. ;SMS Message Over-write ;10 In a further embodiment the present invention may be employed to send a string of messages to a cellular telephone. This may be useful in process which requires a number of questions answered, or a large amount of information. For example a purchase order by a customer, a job tracking process, buying a Lotto ticket, placing a bet, or booking a movie ticket. ;15 ;20 ;In order to prevent the message inbox of the cellular telephone becoming full and to prevent confusion regarding the current question to be answered, each subsequent message is sent with a message over-write (via the SMS carrier overwrite flag) so that the user only has one message in their inbox at any one time from the particular application. ;User Purchase Confirmation ;Referring to Figure 2 in a still further embodiment of the present invention, users may request or purchase goods or services using their cellular telephone 210. A user 25 requests a product or service by generating a MO (Mobile Originate - an SMS message that was created and sent FROM a cellular telephone) message, including for example a product code, and sending the message to the system server 22. ;30 ;When the MO is received, a software application running on the system server 22 matches the product code to the product or service in a product database. The product code is unique so it not only relates to a particular product or service but al >0 Propety running on the system server 22 contains the supplier of that particuk r producfi^^i^lc^- ;1 4 MAR 2005 ;RECElue ;-10- ;From the Caller Line Identification CLI (or other unique mobile phone caller ID) the software application matches the users cellular telephone number to the mobile users profile (Mobile) database record stored by the system. This mobile record contains the 5 name, delivery address(s), payment detail(s), cellular telephone number and other details relating to the user. Users create the mobile user profile record using a PC 23 and an on online interface served by a system server 22 or by calling a call centre. In the case of a call centre the call centre operator creates the profile. ;10 Users enter their desired payment methods and delivery destinations during the setup of their user profile on the supporting website. Once the user has entered the payment/delivery details they wish to use, they are directed to an 'assignment' section of the website, where they are instructed to assign preferred payment methods and delivery destinations to each available vendor. If no assignments are made by the user, defaults are 15 selected for the user. ;Caller Line Identification is included with every SMS message sent. It forms part of a compulsory SMS header which obtains the correct information directly from the SIM card of a GSM phones or from the information hard coded to the phone on 20 TDM A/CDMA/Analogue phones. ;An application on the system server 22 automatically generates a MT (Mobile Terminate - an SMS message that is sent TO a phone) message which displays the details of the product or service pricing and other details. The MT message includes a request to 25 reply with a "Y", "YES" or other short confirmation message to confirm the transaction. The application then generates an audit of transaction including the request and purchase confirmation and then passes the billing information onto the cellular provider's billing system for billing 27 so that the product/service can for example, appear on the users' next cellular telephone bill. ;30 ;The application server then creates an order by combining the Usei'i> pr0peijy ;information from the system database with information on the produqt or servi9^!SSd0^ N.Z. ;1 4 MAR 2005 ;RECEIVED ;information on the supplier. This information is then delivered to the supplier who delivers the product or service to the user. The information may be sent to the supplier by email 25, facsimile 26, data 27 or via the web browser 28. The MT message is sent back to the users mobile phone with the estimated time of delivery and/or order confirmation dialogue if required. ;The product or service is billed to the user via the method selected in the mobile for that particular supplier. Billing options include (but are not limited to) credit card, cash on delivery, charged to an account with the supplier, charged to the mobile carriers users bill, EFTPOS, or a third party account (i.e., added onto an electricity bill). ;When the user places their order via the system, the system matches their CLI against their user profile and selects the relevant payment method and delivery destination for each vendor included within the order, based on the decisions the user made at the assignments page of the website. ;Sensitive information, such as credit card numbers, are stored in an encrypted state within the system database. Such information is only available to merchants when a bonafide order exists for the given vendor. Immediately following the processing of the order, said information is no longer available for the merchant. ;When an order is created exists, notification of the order is sent to the relevant merchant(s), via email and/or SMS text message. If sent by email 25 the merchant will follow a hyperlink included within the content of the email and log on to the system webserver via a PC 28 to retrieve the details of the order for processing. In an alternative embodiment the system would charge the credit card and pay the merchant, requiring only product information, payment confirmation and delivery details to be sent to the merchant. ;Payments made using EFTPOS, account charging, carrier account charging or third party charging will be activated by the system and payment gateway 24 using known methods based on information supplied by the user in their mobile user profile. ;Intellectual Property Office of N.Z. ;1 h MAR 2005 ;10 ;15 ;-12- ;Customers purchasing using the system will be informed of the various merchants/product codes available for use through traditional media and such as newspapers, radio and television through the system website. Merchants will include product codes in their standard advertising, whether said advertising is destined for print, television, radio, billboards, the Internet or other. The product codes are small and unobtrusive, designed to support and complement existing merchant advertising. ;The customers may also visit the supporting website using a PC 23 to learn of new merchants and product codes. ;In an alterative embodiment the system would additionally allow for users to create their own product codes that may span several products or services and that, when matched with their mobile phone number through caller line identification, allow for the retrieval of the correct product/merchant information from the database. ;This is useful for users who order the same products on a regular basis. For example, ;a user may set up a code of PARTY to represent the purchase of a selection of pizzas, and a mixture of favourite bottles of wine, all selectable by the user and assigned to their specific code and user profile using the website system. Because the transaction is ultimately 20 matched back to the user's mobile phone number, there is no chance of errors occurring if multiple users create the same product codes. ;Personal codes of this nature are set up via the supporting system website, or alternatively via a supporting telephone helpdesk. ;25 ;A further enhanced feature of the system is the ability to advise an alternate preferred delivery address from within the content of the text message. Usually, the system refers back to the central database to ascertain which delivery address to use for a particular vendor. The user has the ability to override this feature by entering the product code, ;30 followed by a space, followed by a single character depicting the desired delivery address, ;(already existent in the database). For example, a user may enter '1234 W' to place an order ;Intellectual Property Office of N.Z. ;1 4 MAR 2005 ;receive ;- 13- ;for product '1234', to be delivered to WORK. Likewise, they may enter '5678 H' to place an order for product '5678', to be delivered to HOME. ;In a further embodiment the user would have the ability to enter a complete address, 5 which may be unknown to the database. This is achieved by entering the content of the order in the usual fashion, inserting a delimiting character and then entering the full desired delivery address. ;The ability to order quantities of products on the fly is a key feature of the system and 10 its capabilities. Users have the ability to order several products at once by simply separating each desired product code with a space. E.g.: '1234 5678 9876', would deliver one each of the products '1234', '5678' and '9876'. Ordering quantities of the same product is achieved by adding a multiplier immediately following the product code. E.g.: '1234x5' would deliver a quantity of five of product '1234'. A mix of these two features allows the 15 user to order any combination of the products and quantities of those products. ;Furthermore, products selected may all be from separate merchants, as the system server will break the order into components and forward the relevant details to each appropriate merchant. ;20 For the user's complete peace of mind, the confirmation message contains specific details of the order placed, the delivery destination and the total cost. Also included in the return message are any contact details for the merchant(s) so that the user may make voice contact if necessary. Confirmations for orders spanning multiple merchants are sent back in several distinct messages, indicating the individual product, cost and delivery details. ;25 ;In an alternative embodiment the user will be given the opportunity in those confirmation message to alter the address. ;Referring to Figure 3 the present invention is depicted according to one preferred ;30 embodiment showing a customer advert 100 displaying a text code whereby the user enters the text code into their SMS capable cellular telephone 102 which is transmitted via cellular network 106 to a SMSC 104. The messaging engine 108 r«eivestoMI«^£g%j^Tj" ;Office of lM,z. ;1 4 MAR 2005 ;R EC F a v £*- 1 - 14- from the SMSC 104 and together with user mobile profile 114 stored in the data centre secure server 112 the list of products and services held in the server farm 110 verifies whether or not the order can be dispatched. The messaging engine 108 then sends a confirmation to the user. The user may optionally confirm in a reply message to the 5 messaging engine 108. Once the order is confirmed an electronic autopatic 116 is forwarded to the merchant 118 who is turn delivers the product or service. Lottery Result Notification 10 The present invention comprises a further embodiment where users may register then- lottery entries and be notified of success using their cellular telephone 10. The user sends ticket numbers (eg: Kachingo or Lotto numbers) as a MO message to the system server 4. The system queries the database of available barcode numbers with the contents of the message. Upon obtaining the result of the database query, the system alerts the user to their 15 success (or failure) by return SMS message. An application on the system server 4 records the CLI (Caller Line Identification - the ability to see the phone number/mobile number of the person calling you) and ticket number information and stores them together in a database. 20 Multiple numbers could be sent by putting a space between the numbers in the message sent to the system by the user. The database information is then regularly checked against the ticket providers winning numbers database or engine to find matches. This database checking is performed immediately and based on the ticket number information, at future scheduled times (i.e. for 25 future weekly, monthly draws). Entry of ticket numbers would usually be by entering not the actual ticket number combinations but the ticket providers encrypted bar code number (normally found at the bottom of the ticket). Entry/maintenance of a user's ticket numbers could also be performed via a web site. 30 A mobile user is automatically sent a notification that they have won a prize based the ticket number entered in the database. This may have been for a dail r, weeiB^i&ctuaT"Propenv" Office of N.Z monthly draw that was either a past or future event when the ticket numl >er was entered. If 1 4 MAR 2005 Receive -15- the ticket number was entered as a MO SMS message then a threaded reply using the original SMS message serial number would be sent to the original sender of the message with winning number message. Included in this message could be the ticket providers encrypted bar code number so that prizes could be collected from existing ticketing outlets. 5 If the winning numbers were entered via the Internet then a SMS message would be sent to the user's cellular telephone as per their profile information. In order to collect prizes, users must, of course, be able to produce the actual winning ticket. Intellectual Property Office of N.Z. 14 MAR 2005 </div>

Claims

<div class="application article clearfix printTableText" id="claims"> CLAIMS:

1. A method for handling an order, said order received from any "text messaging" or other wireless data transmission protocol capable wireless communication device, comprising the steps of: receiving an order message from said wireless device; extracting an indication of the identity of said wireless device from said order message; obtaining information associated with said indicated identity, said information comprising information on a wireless device user associated with said wireless device identity and a nominated method of payment for said order; and sending an order confirmation message using said identity to said wireless device.

2. A method for handling an order as claimed in claim 1 further comprising the step of verifying the ability to fulfil said order prior to sending said order confirmation.

3. A method for handling an order as claimed in either claim 1 or claim 2 further comprising the step of receiving information on a wireless device user prior to receiving orders from the user, said information including an identity of a wireless device associated with said wireless device user, and storing said user information in a database; and said step of obtaining information associated with an indicated identity and comprises retrieving information from said database on the basis of said identity.

4. A method for handling an order as claimed in claim 3 wherein the step of receiving information on a wireless device user comprises the steps of: providing an information collecting interface for said wireless device user to provide said information; and receiving said information provided by said wireless device user from said information collecting interface.

5. A method for handling an order as claimed in anyone of claims 1 to 4 wherein said information on said wireless device user further comprises at least one 1 4 MAR 2005 - 17-

6. A method for handling an order as claimed in anyone of claims 1 to 5 further comprising the step of receiving a further message from said wireless device. 5

7. A method for handling an order as claimed in anyone of claims 1 to 6 further comprising the step of storing a plurality of codes, each said code being associated with one or more items and, for a received order message, the steps of extracting codes from said order message and matching extracted codes with stored codes to determine an order. 10

8. A method for handling an order as claimed in claim 7 wherein the said one or more items associated with a said received code in said order message depend on said indicated identity and said method further comprising the step of receiving information on items to be associated with a said received code for a said indicated identity. 15

9. A method for handling an order as claimed in claim 2 and either claim 7 or claim 8 wherein the step of verifying the ability to fulfil said order comprises checking if said received code is one of said stored codes.

10. A method for handling an order as claimed in anyone of claims 7 to 9 including the 20 step of extracting a quantity for each said code from said order message.

11. A method for handling an order as claimed in claim 3 and anyone of claims 4 to 10 wherein said method further comprising the steps of: receiving information on a delivery address to be associated with a delivery address 25 code for a wireless device user storing said association in said database, after receiving an order message, extracting a delivery address code from said message; and retrieving the delivery address associated with said delivery address code for said order. 30

12. A method for handling an order as claimed in any one of claims 1 to 11 including the step of extracting a delivery address from said order message. Intellectual Propeiiy Office of N.Z. 14 MAR 2305 RECEIVE - 18-

13. A method for handling an order as claimed in claim 12 wherein said confirmation message includes said extended delivery address.

14. A method for handling an order as claimed in anyone of claims 1 to 13 further 5 comprising the step of communicating said order and said confirmation to a third party for billing purposes.

15. A method for handling an order as claimed in anyone of claims 1 to 14 further comprising the step of communicating an order for at least one ordered item to an 10 appropriate supplier.

16. A method for handling an order as claimed in claim 15 wherein the step of communicating an order for at least one ordered item to an appropriate supplier includes communicating a delivery address. 15

17. A method for handling an order as claimed in either claim 15 or claim 16 wherein the step of communicating an order for at least one ordered item to an appropriate supplier further includes communicating a method of payment. 20

18. A method for handling an order as claimed in claim 2 and any one of claims 3 to 17 wherein the step of verifying the ability to fulfil said order comprises the steps of: communicating a request for fulfilment capability information on each ordered item to at least one appropriate supplier; and receiving fulfilment capability information from suppliers. 25

19. A method for handling an order as claimed in claim 4 wherein said information collecting interface is a web form.

20. A system for handling an order, said order received from any "text messaging" or other 30 wireless data transmission protocol capable wireless communication device, comprising: means for receiving an order message from said wireless device; means for extracting an indication of the identity of said wireless c evice^ Office of N.Z. 1 4 MAR 2005 i E 0 E I V F D - 19- order message; means for obtaining information associated with said indicated identity, said information comprising information on a wireless device user associated with said wireless device identity and a nominated method of payment for said order; and 5 means for sending an order confirmation message using said identity to said wireless device. 10 30

21. A system for handling an order as claimed in claim 20 further comprising the step of verifying the ability to fulfil said order prior to sending said order confirmation.

22. A system for handling an order as claimed in either claim 20 or claim 21 further comprising means for receiving information on a wireless device user prior to receiving orders from the user, said information including an identity of a wireless device associated with said wireless device user, and storing said user information in a database; and said 15 means for obtaining information associated with an indicated identity and includes means for retrieving information from said database on the basis of said identity.

23. A system for handling an order as claimed in claim 22 wherein said means for receiving information on a wireless device user comprises: 20 an information collecting interface for said wireless device user to provide said information; and means for receiving said information provided by said wireless device user from said information collecting interface. 25

24. A system for handling an order as claimed in anyone of claims 20 to 23 wherein said information on said wireless device user further comprises at least one delivery address.

25. A system for handling an order as claimed in anyone of claims 20 to 24 further comprising means for receiving a further message from said wireless device.

26. A system for handling an order as claimed in anyone of claims 20 to 25 further comprising means for storing a plurality of codes, each said code being at sociatbH^^MSA^P^?Pe'; lY 1 h MAR 2005 RECEIVED -20- or more items, and means for extracting codes from an order message and matching extracted codes with stored codes to determine an order.

27. A system for handling an order as claimed in claim 26 wherein the said one or more 5 items associated with a said received code in said order message depend on said indicated identity and said system further comprises means for receiving information on items to be associated with a said received code for a said indicated identity.

28. A system for handling an order as claimed in claim 21 and either claim 26 or claim 10 27 wherein said means for verifying the ability to fulfil said order comprises means for checking if said received code is one of said stored codes.

29. A system for handling an order as claimed in anyone of claims 26 to 28 including means for extracting a quantity for each said code from said order message.

30. A system for handling an order as claimed in claim 22 and anyone of claims 23 to 29 wherein said system further comprises: means for receiving information on a delivery address to be associated with a delivery address code for a wireless device user storing said association in said database; for said order.

31. A system for handling an order as claimed in anyone of claims 20 to 30 including 25 means for extracting a delivery address from said order message.

32. A system for handling an order as claimed in claim 31 wherein said confirmation message includes said extended delivery address. 30 33. A system for handling an order as claimed in anyone of claims 20 to 32 further comprising means for communicating said order and said confirmation to a third party for 15 20 means for extracting a delivery address code from an order message; and means for retrieving the delivery address associated with a said delivery address code billing purposes.

Intellectual Prope.iy Office of N.Z. 1 4 MAR 2005 -21 -

34. A system for handling an order as claimed in anyone of claims 20 to 33 further comprising means for communicating an order for at least one ordered item to an appropriate supplier. 5

35. A system for handling an order as claimed in claim 34 wherein said means for communicating an order for at least one ordered item to an appropriate supplier includes means for communicating a delivery address. 10

36. A system for handling an order as claimed in either claim 34 or claim 35 wherein the said means for communicating an order for at least one ordered item to an appropriate supplier further includes means for communicating a method of payment.

37. A system for handling an order as claimed in claim 21 and anyone of claims 22 to 36 15 wherein said means for verifying the ability to fulfil said order comprises: means for communicating a request for fulfilment capability information on each ordered item to at least one appropriate supplier; and means for receiving fulfilment capability information from suppliers. 20

38. A system for handling an order as claimed in claim 23 wherein said information collecting interface is a web form.

39. A method for handling an order as claimed in claim 1 and substantially as herein described with reference to the accompanying drawings. 25

40. A system for handling an order as claimed in claim 1 and substantially as herein described with reference to the accompanying drawings. HID Of CLAIM5 Intellectual Propesiy Office of N.Z. 14 MAR 2005 </div>