WO2022126174A1

WO2022126174A1 - A private communication system

Info

Publication number: WO2022126174A1
Application number: PCT/AU2021/051412
Authority: WO
Inventors: Dmitri Davies; Helen SCOTT
Original assignee: Dmitri Davies
Priority date: 2020-12-16
Filing date: 2021-11-26
Publication date: 2022-06-23
Also published as: AU2021104647A4; AU2021401995A1

Abstract

A communication system which allows for the sending and receiving of private communications has a server is configured for controlling communications (such as messaging and/or audio and/or video communications between the electronic devices) between caller and recipient client devices. Each communication is initiated by the communication controller of the software application of the caller device in ways that, should the recipient client device be accessed, it would not be possible to identify the identity of the caller.

Description

A private communication system

Field of the Invention

[0001 ] This invention relates generally to a communication system for the sending of private communications.

Background of the Invention

[0002] Electronic communication devices are used for making of audio and/or video calls and sending of messages.

[0003] However, message and call log data retained by the recipient and/or sender devices or the communication network are vulnerable to unauthorised access.

[0004] The present invention seeks to provide way to will overcome or substantially ameliorate at least some of the deficiencies of the prior art, or to at least provide an alternative.

[0005] It is to be understood that, if any prior art information is referred to herein, such reference does not constitute an admission that the information forms part of the common general knowledge in the art, in Australia or any other country.

Summary of the Disclosure

[0006] There is provided herein a communication system allowing for the sending and receiving of private communications.

[0007] Specifically, the system comprises a server in operable communication with a plurality of electronic client devices across a communication network. The server comprises a communication controller and each client device comprises a communication application installed thereon, the communication application comprising a client communication controller.

[0008] The server is configured for controlling communications (such as messaging and/or audio and/or video communications between the electronic devices) between caller and recipient client devices. Each communication is initiated by the communication controller of the software application of the caller device. [0009] The caller ID of the caller device is not transmitted to the recipient client device. As such, should the recipient client device be accessed, it would not be possible to identify the identity of the caller.

[0010] The client ID may comprise a mobile phone number, MAC address and/or IP address. Furthermore, the server may substitute the client ID with fixed or recycling client IDs of the server which therefore could only generically identify the server, but not the associated caller IDs.

[001 1 ] When sending messages, the server may hold the message data and send a notification thereof to the recipient client device. The recipient client device may thereafter retrieve the message data from the server.

[0012] The server may be configured for purging the message data after the expiration of a time period (including a time period which may be specified by the client device) or upon successful retrieval of the message data.

[0013] The recipient caller device may be configured for authenticating with the server and exchanging cryptographic keys for accessing the message data.

[0014] The client communication controller may be configured for purging of call log data of the client devices. Where operating system security prevents automatic purging of call log data, the system may prompt for the user purging of call log data, either after each communication or at set time periods.

[0015] Other aspects of the invention are also disclosed.

Brief Description of the Drawings

[0016] Notwithstanding any other forms which may fall within the scope of the present invention, preferred embodiments of the disclosure will now be described, by way of example only, with reference to the accompanying drawings in which:

[0017] Figure 1 shows a private communication system in accordance with an embodiment;

[0018] Figures 2 - 7 show exemplary graphical user interfaces displayed by the electronic client devices of Figure 1 ;

[0019] Figure 8 shows instantiation control of calls between electronic devices in accordance with an embodiment; and [0020] Figure 9 shows sending of messages between electronic devices in accordance with an embodiment.

Description of Embodiments

[0021 ] A communication system 100 comprises a server 101 in operable communication with a plurality of electronic client devices 102 across a communication network 103.

[0022] The server 101 comprises a processor 104 for processing digital data. In operable communication with the processor 104 across a system bus 105 is a memory device 106. The memory device 106 is configured for storing computer program code instructions and associated data 107. The computer program code instructions may be logically divided into a plurality of computer program code instruction controllers 108. In use, the processor 104 fetches these computer program code instructions and associated data 107 for interpretation and execution for the implementation of the functionality described herein.

[0023] The server 104 comprises a data interface 109 for sending and receiving data across the communication network 103.

[0024] The server controllers 108 may comprise a communication controller 1 10 for controlling communications between electronic client devices 102. The communication controller 1 10 may comprise a call session controller 1 1 1 and associated audio and video codecs 1 12 therefor.

[0025] The data 107 may comprise user profile data 1 13. Cryptographic keys 1 14 may be stored in relation to each profile 1 13. Cryptographic keys 1 14 may comprise public/private key pairs. The data 107 may hold short-term duration communication messages 1 15 or longer term duration data in a secure vault 1 16.

[0026] Each electronic client device 102 may similarly comprise a processor 104, memory device 106 and a data interface 109.

[0027] A communication application 1 17 may be installed within memory 106 of each client device 102. The communication application 1 17 may further comprise controllers 108 including a client communication controller 1 18. [0028] The client device memory 106 may further store data 107 including cryptographic keys 1 14.

[0029] The client device 102 may comprise a microphone 1 19 capturing of audio data and a camera 120 for capturing of image and/or video data. The electronic device 102 may further comprise a digital display 121 for the display of digital data thereon. A haptic overlay may receive user input gestures in relation data displayed on the digital display 121 . The client device 102 may further comprise an audio output 122 for the output of audio.

[0030] Exemplary call instantiation and control 123 implemented by the system 100 will now be described with reference to Figure 8.

[0031 ] As alluded to above, a plurality of system users, each having an associated client device 102 will install the communication application 1 17 thereon. Once installed, the user may register with the server 101 wherein a user profile 1 13 is created accordingly. The server 101 may generate cryptographic keys 1 14 for the user profile 1 13.

[0032] For the making of a voice or video call to a user of a caller client device 102A, at step 124, a contact search query may be input into a contact search field 132 of a user interface 133 displayed on the digital display 121 of the caller client device 102A. Matching contacts 134 may be selected. The application 1 17 may retrieve contact details from the operating system contacts database of the client device 102.

[0033] With reference to Figure 3, contact details 135 may be displayed along with the call button 136 to instantiate a voice or video call with a recipient client device 102B at step 126.

[0034] During call instantiation, the recipient ID is transmitted to the server 101 . The recipient ID is used to look up and identify a recipient electronic client device 102B.

[0035] The recipient ID may be a mobile phone number wherein the server 101 searches the profiles 1 13 for a matching mobile phone number. If a matching mobile phone number is found, the server 101 may instantiate the call.

[0036] If a matching mobile phone number is not found, the server 101 they return a notification to the caller client device 102A that a recipient client device cannot be located. Additionally, or alternatively, the server 101 may send an invitational SMS communication to the recipient electronic client device 102B comprising a URL for the downloading of installation of the software application 1 17.

[0037] In further embodiments, the recipient ID may be a unique recipient name, nickname, numeric ID and/or the like.

[0038] When instantiating the call at step 126, the server 101 may send a push notification to the recipient client device 102B indicating an incoming call. If the call is picked up at step 128, the call is instantiated at step 129 wherein the session controller 1 1 1 of the server 101 controls the communication between the phone devices 102 until the call ends at step 130.

[0039] As shown in Figure 3, the interface 133 may comprise an option 137 to place an anonymous call.

[0040] As such, when instantiating the call at step 126, the server 101 does not transmit the ID of the caller client device 102A to the recipient client device 102B. The caller ID may comprise any one of a user identity, mobile phone number, IP address and/or MAC address.

[0041 ] In embodiments, at step 127, the server 101 may substitute the caller ID with a substitute ID. The server 101 may substitute the caller ID with a fixed or recycling ID relating only to the server 101.

[0042] At step 131 , the communication application 1 17 of the caller client device 102A or the recipient client device 102B may purge a call log thereof.

[0043] In embodiments, the communication application 1 17 automatically purges the call log after the communication. In further embodiments, the communication application 1 17 prompts the user by way of a notification to manually purge the call log of the client device 102.

[0044] In embodiments, the communication application 1 17 runs a call log purge timer wherein, upon expiration of the call log purge timer, the software application 1 17 either automatically purges the call log or alternatively prompts the user to purge the call log.

[0045] Figure 9 shows sending of messages 138 using the system 100. [0046] With reference to Figure 2, the user of the caller client device 102 may similarly select a contact at step 139.

[0047] With reference to figure 4, at step 140, the user may use an option input 137 of the interface 133 to transmit the message anonymously.

[0048] At step 141 , the user may use a message expiration input 151 to input a date and/or time period after which the message expires.

[0049] At step 142, the user may input the message using message input field 152. The message may comprise text, embedded audio and/or video multimedia and/or attachments.

[0050] The user may transmit the message using a send button 153 which causes the communication application 172 transmit the message to the server 101. The server 101 stores the message 1 15.

[0051 ] With reference to Figure 5, at step 144, the server 101 may send a push notification to the recipient phone device 102 which may be displayed as an on-screen notification 154.

[0052] The notification 154 may display the caller ID unless the message has been transmitted anonymously. The notification 154 may comprise a button 155 to access the message and may further display the time remaining 156 during which the message is accessible.

[0053] At step 149, if the timer expires, the server 101 may delete the message 1 15 from memory 107.

[0054] Alternatively, the recipient may access the message at step 145.

[0055] As shown in Figure 6, at step 146, the recipient may be required to input username 156 and password 158 credentials.

[0056] Provided the appropriate authentication credentials are provided, the server 101 may retrieve the message 1 15 and transmit the message to the recipient client device 102B which are displayed on the digital display 121 thereof at step 147. Figure 7 shows the message content 159 displayed by the recipient client device 102B. [0057] Additionally, or alternatively, the server 101 may inspect a cryptographic key 1 14 transmitted by the recipient client device 102B when requesting retrieval of the message.

[0058] Once the message is displayed, the message is deleted at step 150.

[0059] In embodiments, a user may request that message data be stored within the vault 1 16. For example, prior the deletion of the message at step 150, the user may elect to save the message wherein the message data including the text and/or associated multimedia is stored within the vault 1 16. A method that may be encrypted, including using the cryptographic keys 1 14 associated with the respective client device 102.

[0060] The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that specific details are not required in order to practise the invention. Thus, the foregoing descriptions of specific embodiments of the invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed as obviously many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, thereby enabling others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following claims and their equivalents define the scope of the invention.

Claims

1 . A private communication system comprising a server in operable communication with a plurality of electronic client devices across a communication network, the server comprising a communication controller, each client device comprising a communication application installed thereon, the communication application comprising a client communication controller wherein the server is configured for controlling a communication between a caller and recipient client device initiated by the client communication controller of the software application of the caller device wherein a caller ID of the caller device is not transmitted to the recipient client device.

2. The system as claimed in claim 1 , wherein the server substitutes the caller ID of the caller device with a substitute ID.

3. The system as claimed in claim 1 , wherein the caller ID comprises a phone number.

4. The system as claimed in claim 1 , wherein the caller ID comprises a MAC address.

5. The system as claimed in claim 1 , wherein the caller ID comprises an IP address.

6. The system as claimed in claim 1 , wherein the communication is voice communication.

7. The system as claimed in claim 1 , wherein the communication is video communication.

8. The system as claimed in claim 1 , wherein the server stores message data of the communication, pushes a notification to the recipient client device and wherein the message data is retrievable by the recipient client device from the server.

9. The system as claimed in claim 8, wherein the server confirms authentication credentials received from the recipient client device prior retrieving the communication data from the recipient client device.

10. The system as claimed in claim 8, wherein the server confirms cryptographic key data from the recipient client device.

1 1 . The system as claimed in claim 8, wherein, if the message data is not retrieved, the server deletes the message data.

12. The system as claimed in claim 1 1 , wherein the server deletes the message data after a time period.

13. The system as claimed in claim 12, wherein the time period is specified by the client communication controller of the caller device.

14. The system as claimed in claim 12, wherein the notification displays time remaining of the time period.

15. The system as claimed in claim 8, wherein, if the message data is retrieved, the server deletes the message data.

16. The system as claimed in claim 1 , wherein the recipient client device purges a call log.

17. The system as claimed in claim 16, wherein the recipient client device purges a call log after the communication.

18. The system as claimed in claim 16, wherein the software application comprises a call log purge timer.

19. The system as claimed in claim 18, wherein upon expiration of the call log purge timer, the software application purges the call log.

20. The system as claimed in claim 18, wherein upon expiration of the call log purge timer, the software application prompts to purge the call log.

9