AU2007294464B2

AU2007294464B2 - Improvements in transmitting and relaying messages

Info

Publication number: AU2007294464B2
Application number: AU2007294464A
Authority: AU
Inventors: Grant Andrew Stepa
Original assignee: Individual
Current assignee: Individual
Priority date: 2006-09-04
Filing date: 2007-09-04
Publication date: 2012-01-19
Anticipated expiration: 2027-09-04
Also published as: AU2007294464A1; WO2008028227A1

Abstract

The present invention relates generally to improving transmission and relaying messages between devices. The method includes transmitting a message between a first device configured to send a message and a second like device, the first and second devices having first and second device identifiers respectively, the method including the steps of cloaking the first device identifier with a first alias, interrogating an encrypted data store to ascertain the second device identifier and sending the message to the second device via a communications network in such a fashion that the first device identifier is inhibited from display to a user of the first device.

Description

C .4RPortbl\DCC\HFS\3945789_1 DOC-20/10/2011 IMPROVEMENTS IN TRANSMITTING AND RELAYING MESSAGES Field of the Invention 5 The present invention relates to apparatus for, and method of facilitating communications using message data, such as for example SMS and MMS over communications networks which themselves include landlines, radio frequency devices as well as other types of network and protocol. 10 Definitions Throughout this specification and the claims that follow, the following definitions apply: Message: A plurality of ASCII characters, one or more images, or other data such as sound files, video files and other kinds of data. Where the message is sent by the SMS or MMS protocol, the term "message" is to be understood to include message details, as 15 well as a message field itself. Device Identifier Number: A telephone number such as for example a mobile phone number of land line number, or an IP address or like identifier. 20 Background to the Invention The reference to any prior art in this specification is not, and should not be taken as, an acknowledgment or any form of suggestion that that prior art forms part of the common general knowledge in Australia or elsewhere. 25 It is known to send message data by SMS and MMS protocol by telephone network, say, landline or GSM or the like. However, to send a message to a recipient, a sender must know a device identifier number associated with a recipient's device. Even though this kind of communication is associated with a certain degree of disinhibition by 30 virtue of remote positions of the first and second devices, greater degrees of disinhibition C:\NR"orbl\DCC\HFS\39457K9-lDOC-20/10/2011 -2 are sought to encourage free exchange of ideas by message data. The present invention seeks to alleviate one or more of the abovementioned disadvantages. 5 Summary of the Invention In a first aspect there is provided a method of relaying a message between a first device configured to send messages and a second like device, the devices having respective device identifiers associated therewith, the method including the steps of, in a server 10 processing system: receiving a message and an alias from the first device, the alias associated with the second device number identifier; cloaking the device number identifier associated with the first device with a first alias to create a cloaked or aliased message; 15 ascertaining a device identifier of the second device associated with the second alias; and sending the cloaked or aliased message, with the first alias, to the second device over a communications network. 20 In certain forms, the method includes the step of, in the server processing system: receiving a message and the first alias from the second device; cloaking the second device identifier with the second alias; ascertaining the first device identifier associated with the first alias; and sending the message, with the, second alias, to the first device over a 25 communications network. In particular forms, the cloaking step includes the steps of, in the server processing system, removing the first device identifier from the message and associating or including the first alias with the message. 30 In certain embodiments, the ascertaining step includes the step of, in the server processing C \NRPrtbl\DCC\IFSU9479_ I DOC-ZO10/201 I -3 system interrogating an encrypted data store in order to ascertain the device identifier or alias associated with a device. In particular embodiments, the interrogation step includes, in the server processing system, 5 the step of consulting lookup tables to ascertain the device identifier or alias associated with a device. In an optional embodiment, the message is one of: an SMS message; and 10 an MMS message. In a second aspect there is provided a server processing system for relaying a message between a first device configured to send messages and a second like device, the devices having respective device identifiers, the server processing system being configured to: 15 receive a sent message and an alias from the first device, the alias associated with the second device identifier; cloak a device identifier associated with the first device with a first alias to create a cloaked or aliased message; ascertain a device identifier of the second device associated with the second alias; 20 and send the cloaked or aliased message to the second device over a communications network. In certain forms, the server processing system is configured to: 25 receive a return message and the first alias from the second device; cloak the second device identifier with the second alias; ascertain the first device identifier associated with the first alias; and send the message to the first device over a communications network. 30 In particular forms, the server processing system is configured to ascertain the device identifier or alias associated with a device by interrogating an encrypted data store.

C.\NRPortblDCC\-FSU 945789 _lDOC-2/1 0/2011 -4 In certain embodiments, the encrypted data store is in the form of a file or one or more lookup tables. 5 In particular embodiments, the server processing system is configured to relay the message data to the second device, so that a user of the first device is inhibited from obtaining the second device identifier, and so that cloaked or aliased messages is able to be relayed by the server processing system between the two devices. 10 In optional forms, the server processing system is configured to cloak the first device identifier from view by the second device by deleting the first device identifier from the message and appending the first alias to the message, so that the second device is inhibited from obtaining the device identifier of the first device and so that the second device can reply to the first device. 15 In optional embodiments, the server processing system is configured to cloak the second device identifier from display or other unauthorised use by the first device by deleting the second device identifier from the message and appending the second alias to the message, so that the first device can reply to the second device. 20 In certain optional forms, the server processing system is configured to transmit the data store over a communications network to at least one of the first device and the second device for storage and local access thereon. 25 In certain optional embodiments, the server processing system is configured to send and receive at least one of: SMS messages; and MMS messages. 30 In a third aspect there is provided a system for transmitting messages between a first device and a second device, the devices having respective device identifiers, the system C.\NRorblCC\HS\394579_ I DOC-20/102011 -5 including: a first device configured to send messages over a communications network; a second device configured to send messages over the communications network; and 5 a server processing system configured according to the second aspect. In a fourth aspect there is provided method of transmitting a message between a first device configured to send a message and a second like device, the first and second devices having first and second device identifiers respectively associated therewith, the method 10 including the steps of, in the first device: cloaking the first device identifier with a first alias to create a cloaked or aliased message; associating a second alias with the message; interrogating an encrypted data store associated with the first device to ascertain the 15 second device identifier associated with the second alias; and sending cloaked or aliased message to the second device via a communications network in such a fashion that the first device identifier is inhibited from display to a user of the first device. 20 In a fifth aspect there is provided a device suitable for transmitting messages to a second device, the devices having respective device identifiers associated therewith, the device being configured to: cloak the device identifier with a first alias to create a cloaked or aliased message; associate a second alias with the message; 25 interrogate an encrypted data store associated with the device to ascertain a second device identifier associated with the second alias; and send the message to a second device associated with the second device identifier via a communications network wherein display or other use of the second device identifier to a user of the device is inhibited. 30 In a sixth aspect there is provided a computer program product to configure a device to transmit messages from a first device to a second like device, the devices having respective C \NRPrblDCC\HFS\3945789_I.DOC-2/1O2OI -6 device identifiers associated therewith, wherein the computer program product configures the device to: cloak the device number identifier with a first alias to create a cloaked or aliased message; 5 associate or include a second alias with the message; interrogate an encrypted data store associated with the device to ascertain a second device identifier associated with the second alias; and send the message, with the first alias, to a second device associated with the second device number identifier via a communications network. 10 Other embodiments will be appreciated throughout the description.

C:\NRPortlDCC\HFS\3945789_ .DOC-20/10I2011 -7 Brief Description of the Drawings In order to enable a clearer understanding, a non-limiting example of the present invention 5 will now be described with reference to the accompanying drawings, in which: Figure 1 is a schematic of an example of apparatus for facilitating communication; Figures 2A and 2B are schematic diagrams of examples of the processing system and end stations of Figure 1; and Figure 3 is a flowchart of an example process for facilitating communication. 10 Detailed Description of the Preferred Embodiments An architecture for transmission and relay of messages via a network is shown by way of non-limiting example in Figures 1 and 2. 15 As shown in the Figures the architecture includes a base station 1 coupled to a number of different types of end stations or devices 3, 5, 6, via communications networks 2, 4. End station or device 3 is a computer processing system, end station or device 5 is a wireless PDA, and end station or device 6 is a phone, in particular, a mobile phone. A first mobile phone 6 is shown at 7 and a second mobile phone is shown at 8. 20 The communications networks 2, 4 may be communications networks such as for example telephone lines, the Internet, one or more Local Area Networks (LANs) one or more Wide Area Networks (WANs), Wireless Networks such as the GSM, 3G or GPRS Network, or the like. The base station I includes a server processing system 10. End stations or device 3, 5 and 6 also include one or more server processing systems 30. The server processing 25 system 10 and processing systems 30 may be coupled to a data store 11 (or I10), or the like, as shown. In use, the end stations or devices 3, 5, 6 are configured to communicate with other end stations or devices 3, 5, and 6. It will be appreciated that each of the end stations or C :\RPonbl\DCC\HFS\39457H9_ .DOC 20/10/2011 -8 devices 3, 5 and 6 and the base station 1 are typically configured to communicate with other devices via the communications networks 2 and 4, whilst the base station 1 is typically also configured to provide routing and relaying type functionality. Accordingly, it will be appreciated that the end stations and base stations may be in any suitable form. 5 In preferred embodiments of the invention, though, mobile phones 6 will be the end station used to send SMS, MMS and like message data to other end stations. An example of a server processing system 10 is shown in Figure 2A. As shown the server processing system 10 includes a processor 20, a memory 21, an input/output device 22, such as a keyboard and display or the like, and an external interface 10 23, coupled together via a bus 24. In use the external interface 23 may be coupled to the data store 11, as well as providing connections to the communications networks 2, 4. Base station I may be contained within and be owned by a Network Operator or may be a stand alone Device such as a Computer with an encrypted data store 11 in the form of a file or lookup table which may be designated an SMS server and has a unique device Number 15 associated with it that allows an SMS message to be sent to it. Base station 1, in this example, has a pre-assigned Phone Number for the reception of SMS or MMS message data. Accordingly, the server processing system 10 may be any form of processing system, such as a computer server, a network server, a web server, a desktop computer, a lap-top, PDA, 20 mobile phone or the like. Alternative specialised hardware may be used. Similarly, as shown in Figure 2B, the end stations or devices 3, 5 and 6 may be formed from a processor 30, a memory 31, an input/output device 32 and an external interface 33, coupled together via a bus 34. A data store 110 is connected to the end station or device 3, 5 or 6. Again the external interface 33 may be used to provide a connection to the 25 communications networks 2, 4. Accordingly the end station or device 3, 5 and 6 may be any form of computer system such as a desktop computer, lap-top, mobile phone, PDA, or other suitable specialised hardware.

C \NRPorbI\DCC\HFS\3945789_I DOC-20/10/201I1 -9 An example of a process for facilitating communication will now be described with reference to Figure 3. At step 300 a user of a first (in this case the sending) mobile phone 7 prepares message data in the form of an SMS or MMS or the like. 5 At step 310 the first (or sending) mobile phone 7 associates with the message, a second or destination alias which is associated with a second or destination device 8 and its device identifier. At step 320 the first (or sending) mobile phone 7 sends the SMS or MMS message to the base station I or server processing system. 10 At step 330 the base station I searches the message to identify the first mobile phone 7 device identifier. At step 340 base station 1 searches the Message to identify the second alias. At step 350 the base station 1 or server processing system searches data store 11, specifically in its file or Lookup Table, to march the first mobile phone 7 device identifier 15 with a first alias and to match the second alias to a second (or receiving) device identifier. Any suitable rules may be enacted for location of the second alias which is associated, with, included in or appended to the message. It may be that, for example, the aliases must be the first identifier in the SMS or MMS (i.e. string of characters followed by an ASCII Space). A first alias may be the sending alias, and the second alias may be the receiving 20 alias. Also, the entire message portion may be blank wherein only the details section has non-zero values and this kind of message may have special meaning when being processed by base station 1. For example, a blank message (no alias at all) may trigger an emergency message to be relayed to a predetermined group of aliases, which would be matched by the server processing system and sent to one or more devices. 25 At step 360 the base station forwards the message to the second end station or second device 8 which is associated with the device identifier number located in the lookup table C:\NRPobl\DCC\HFS\394S789_1 DOC-20/10/2011 - 10 search conducted at step 350, and appends or embeds the alias associated with the first device 7 so that the second device 8 may reply to the message. Of course, to reply to the message, the second device 8 undertakes the same steps as 5 undertaken by the first device, starting at 300. Accordingly, the abovedescribed method allows users of the end stations or devices 7 and 8 to communicate freely without divulging their end station identification number. In the above example, by having communication routed through the base station 1, this allows identities of end stations to remain anonymous. It will be appreciated that the only device 10 identifier known to each device 7 and 8 is that of the server processing system. Generally, the users of devices 7 and 8 will pre-register an alias with base station 1 before step 300. However, in the case where the user of device 7 has not registered an alias with base station I then a temporary alias may be issued by base station 1 as determined by the 15 rules assigned from time to time by the administrator of base station 1 to allow the message data to be delivered to second device 8. Under such a condition the process proceeds except that in order that the SMS message may be replied to, an alias is assigned automatically and associated uniquely to the first device identifier of first device 7. Base station I may also advise device 7 of the alias that has been assigned to it. 20 Under another example the method proceeds as described above except that base station 1 is specifically hosted by a third party and NOT the network carrier. This may be the case where base station 1 is operated as part of a subscription service. 25 An. example of another process for facilitating communication will now be described with reference to Figure 4. At step 400 a user of a first (in this case the sending) mobile phone 7 prepares message data in the form of an SMS or MMS or the like.

C \NRPortbj\DCC\HFS\3945789_ .DOC-20/10/2011 - 11 At step 405 the first (or sending) mobile phone 7 cloaks the device identifier by removing the first device identifier and including a first alias in the SMS message details. In this step, the first device 7 also associates a second or destination alias with the message, the 5 second or destination alias being associated with a second or destination device 8. At step 410 the first (or sending) mobile phone 7 interrogates the local, encrypted data store 110 so as to identify the device identifier associated with the second or destination alias. The data store 110 is encrypted so that access or other use of the device identifier of 10 the second or destination device 8 is inhibited. At step 415 the first device sends the SMS or MMS message to the second device 8 using the second device identifier from the data store 110. 15 At step 420 the mobile phone 8 receives the message. The mobile phone 8 displays the message and the message appears on the display to be from the alias, not the first device identifier. Another process for tranrmitting messages is described hereinbelow with reference to 20 Figure 5. At step 500 a user of a first (in this case the sending) mobile phone 7 prepares message data in the form of an SMS or MMS or the like. 25 At step 505 the first (or sending) mobile phone 7 associates a second or destination alias with the message, the second or destination alias being associated with a second or destination device 8. At step 510 the first (or sending) mobile phone 7 interrogates the local, encrypted data 30 store 110 so as to identify the device identifier associated with the second or destination alias. The data store 110 is encrypted so that access or other use of the device identifier of C \NRPrbl\DCC\HFS\3945789_1 DOC-20/102011 - 12 the second or destination device 8 is inhibited. The first device sends the SMS or MMS message to the second device 8 using the second device identifier from the data store 1 10. At step 520 the mobile phone 8 receives the message, and routes the message through the mobile phone 8 local data store 110. The mobile phone 8, the receiving or destintation 5 phone; interrogates its own local encrypted data store 110 so as to identify a first alias associated with the first device 7 identifier. The phone displays the message so as to appear to the user of the device to be from the alias and not the device identifier. The process is repeated if the mobile phone 8 replies to the first mobile phone 7. 10 In all processes and architectures for sending and relaying messages described herein, the following variations may apply: The local data stores or files or lookup tables 110 may be updated by the first mobile phone 7 sending a new file to the second mobile phone 8, or the server processing system 1 15 sending updates to each device 7 or 8. Further, if a user does not pay a registration fee periodically, the data store may be deleted from the local phone 7 or 8, and/or the phone 7 or 8 may not be granted access to the server processing system I database 11. 20 In addition, a phone 8 may request the server processing system 1 to block messages from a device having a selected alias. There may be several devices 6 associated with a selected alias. There may also be several 25 aliases for a single device 6. A number of specific features that can be implemented in some example situations will now be described.

C \NRPortbl\DCC\HFSU945789_1 DOC-20/10/2011 - 13 Base Station 1 The base station 1 can provide a central point for coordinating communication between the end stations 3, 5, 6 via the communications network, such as the Internet. In the above example, a single base station I is used, but in practice base station functionality may be 5 distributed amongst a number of mirror base stations to reduce traffic to the base station 1. Finally, it is to be understood that various alterations, modifications and/or additions may be incorporated into the various constructions and arrangements of parts without departing from the spirit or ambit of the invention. 10 The reference in this specification to any prior publication (or information derived from the prior publication), or to any matter which is known, is not, and should not be taken as an acknowledgment or admission or any form of suggestion that the prior publication (or information derived from the prior publication) or known matter forms part of the common 15 general knowledge in the field of endeavour to which this specification relates.

Claims

1. A method of relaying a message between a first device configured to send 5 messages and a second like device, the devices having respective device identifiers associated therewith, the method including the steps of, in a server processing system: receiving a message and an alias from the first device, the alias associated with the second device number identifier; cloaking the device number identifier associated with the first device with a first 10 alias to create a cloaked or aliased message; ascertaining a device identifier of the second device associated with the second alias; and sending the cloaked or aliased message, with the first alias, to the second device over a communications network. 15

2. The method according to claim 1, wherein the method includes the step of, in the server processing system: receiving a message and the first alias from the second device; cloaking the second device identifier with the second alias; 20 ascertaining the first device identifier associated with the first alias; and sending the message, with the, second alias, to the first device over a communications network.

3. The method according to claim I or 2, wherein the cloaking step includes the steps 25 of, in the server processing system, removing the first device identifier from the message and associating or including the first alias with the message.

4. The method according to any one of claims I to 3, wherein the ascertaining step includes the step of, in the server processing system interrogating an encrypted data store 30 in order to ascertain the device identifier or alias associated with a device. C :RPonbl\DCC\HFSW945789 I DOC-20/10/2011 - 15

5. The method according to claim 16, wherein the interrogation step includes, in the server processing system, the step of consulting lookup tables to ascertain the device identifier or alias associated with a device. 5

6. The method according to any one of claims I to 5, wherein the message is one of: an SMS message; and an MMS message.

7. A server processing system for relaying a message between a first device 10 configured to send messages and a second like device, the devices having respective device identifiers, the server processing system being configured to: receive a sent message and an alias from the first device, the alias associated with the second device identifier; cloak a device identifier associated with the first device with a first alias to create a 15 cloaked or aliased message; ascertain a device identifier of the second device associated with the second alias; and send the cloaked or aliased message to the second device over a communications network. 20

8. The server processing system of claim 7, wherein the server processing system is configured to: receive a return message and the first alias from the second device; cloak the second device identifier with the second alias; 25 ascertain the first device identifier associated with the first alias; and send the message to the first device over a communications network.

9. The server processing system of claim 7 or 8, wherein the server processing system is configured to ascertain the device identifier or alias associated with a device by 30 interrogating an encrypted data store. C RPorI blDCC\HFS\3945789_I.DOC.20/10/201 1 -16

10. The server processing system of claim 9, wherein the encrypted data store is in the form of a file or one or more lookup tables.

11. The server processing system of any one of claims 7 to 10, wherein the server 5 processing system is configured to relay the message data to the second device, so that a user of the first device is inhibited from obtaining the second device identifier, and so that cloaked or aliased messages is able to be relayed by the server processing system between the two devices. 10

12. The server processing system of any one of claims 7 to 10, wherein the server processing system is configured to cloak the first device identifier from view by the second device by deleting the first device identifier from the message and appending the first alias to the message, so that the second device is inhibited from obtaining the device identifier of the first device and so that the second device can reply to the first device. 15

13. The server processing system of any one of claims 7 to 12, wherein the server processing system is configured to cloak the second device identifier from display or other unauthorised use by the first device by deleting the second device identifier from the message and appending the second alias to the message, so that the first device can reply to 20 the second device.

14. The server processing system of any one of claims 7 to 13, wherein the server processing system is configured to transmit the data store over a communications network to at least one of the first device and the second device for storage and local access 25 thereon.

15. The server processing system of any one of claims 7 to 14, wherein the server processing system is configured to send and receive at least one of: SMS messages; and 30 MMS messages. C \NRPortbIOlCC\RFS\3945789- DOC-20/10/2011 - 17

16. A system for transmitting messages between a first device and a second device, the devices having respective device identifiers, the system including: a first device configured to send messages over a communications network; a second device configured to send messages over the communications network; 5 and a server processing system configured according to any one of claims 7 to 15.

17. A method of transmitting a message between a first device configured to send a message and a second like device, the first and second devices having first and second 10 device identifiers respectively associated therewith, the method including the steps of, in the first device: cloaking the first device identifier with a first alias to create a cloaked or aliased message; associating a second alias with the message; 15 interrogating an encrypted data store associated with the first device to ascertain the second device identifier associated with the second alias; and sending cloaked or aliased message to the second device via a communications network in such a fashion that the first device identifier is inhibited from display to a user of the first device. 20

18. A device suitable for transmitting messages to a second device, the devices having respective device identifiers associated therewith, the device being configured to: cloak the device identifier with a first alias to create a cloaked or aliased message; associate a second alias with the message; 25 interrogate an encrypted data store associated with the device to ascertain a second device identifier associated with the second alias; and send the message to a second device associated with the second device identifier via a communications network wherein display or other use of the second device identifier to a user of the device is inhibited. 30

19. A computer program product to configure a device to transmit messages from a CAN rbl\DCC{FfS\3945789_ .DOC-2011 GI I - 18 first device to a second like device, the devices having respective device identifiers associated therewith, wherein the computer program product configures the device to: cloak the device number identifier with a first alias to create a cloaked or aliased message; 5 associate or include a second alias with the message; interrogate an encrypted data store associated with the device to ascertain a second device identifier associated with the second alias; and send the message, with the first alias, to a second device associated with the second device number identifier via a communications network. 10

20. A method performed by a server processing system for relaying a message between a first device and a second like device, a server processing system, a device, or a computer program product, substantially hereinbefore described with reference to the accompanying figures.