US2017366512A1PendingUtilityA1

System and Method for Machine-to-Machine Privacy and Security Brokered Transactions

Assignee: Mobile Search Security LLCPriority: Oct 11, 2012Filed: Sep 1, 2017Published: Dec 21, 2017
Est. expiryOct 11, 2032(~6.2 yrs left)· nominal 20-yr term from priority
H04W 4/70H04L 63/0421H04L 63/0407H04W 4/005
32
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A machine-to-machine secure messaging system permits a first machine to send a message to a second machine, despite not knowing the addressing information (e.g., telephone number, IP address or other identifier) associated with the second machine. The system comprises an intermediary server with access to a database with information linking addressing information with other information related to the device, e.g., owner name, operator name and job title, etc., and facilitates a secure communication without the need for either party to the communication to know the other party's addressing information.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 - 23 . (canceled) 
     
     
         24 . A method of sending a message from a first machine to a second machine, the second machine having second machine addressing information unknown to the first machine, the method comprising the steps of:
 a) storing in a database an association between sender information relating to the identity of the first machine and recipient information relating to the second machine, the database containing, for a plurality of machines, machine characteristic information, machine addressing information, and a security rule for each second machine;   b) without user action, composing the message based on a conditional rule, at the first machine, the message comprising the sender information and the recipient information, but not including second machine addressing information and not including recipient addressing information, and a message payload;   c) transmitting the message via a first private network to an intermediary server, the intermediary server in communication with the database;   d) authenticating the sender information relating to the identity of the first machine at the intermediary server;   e) querying the database and comparing the recipient information to the machine characteristic information to identify the second machine; and   f) transmitting the message payload to the identified second machine via a second private network, wherein the message payload is transmitted according to the security rule associated with the second machine.   
     
     
         25 . The method of  claim 24 , wherein the sender information comprises sender owner information. 
     
     
         26 . The method of  claim 24 , wherein the sender information comprises information relating to the geographic location of the first machine. 
     
     
         27 . The method of  claim 24 , wherein the recipient information comprises recipient owner name information. 
     
     
         28 . The method of  claim 24 , wherein the recipient information comprises recipient operator name information. 
     
     
         29 . The method of  claim 24 , wherein the recipient information comprises recipient job title information. 
     
     
         30 . The method of  claim 24 , wherein the machine addressing information is a telephone identifier. 
     
     
         31 . The method of  claim 24 , wherein the machine addressing information is from the group consisting of: an Internet Protocol address, a MAC address and a network name. 
     
     
         32 . The method of  claim 24 , wherein the intermediary server is controlled by a wireless telephone carrier. 
     
     
         33 . The method of  claim 24 , wherein the intermediary server is an industry clearinghouse. 
     
     
         34 . The method of  claim 33 , wherein the database is controlled by a clearinghouse provider. 
     
     
         35 . The method of  claim 33 , wherein the database is controlled by a wireless telephone carrier. 
     
     
         36 . The method of  claim 24 , wherein said sender information further comprises continuing contact information sufficient to enable the second machine to send a message to the first machine. 
     
     
         37 . The method of  claim 36 , wherein said continuing contact information is a permanent telephone identifier. 
     
     
         38 . The method of  claim 36 , wherein said continuing contact information is a temporary telephone number. 
     
     
         39 . The method of  claim 36 , wherein said continuing contact information identifies a proxy for further communication. 
     
     
         40 . The method of  claim 24 , wherein the security rule lists the sender information for approved senders authorized to send messages to the second machine. 
     
     
         41 . The method of  claim 24 , wherein the machine characteristic information relates to the owner of the second machine. 
     
     
         42 . The method of  claim 24 , wherein the machine characteristic information relates to the identity of the user of the second machine. 
     
     
         43 . The method of  claim 24 , wherein the machine characteristic information relates to work information relating to a user of the second machine. 
     
     
         44 . The method of  claim 24 , wherein the machine characteristic information relates to the geographic location of the second machine. 
     
     
         45 . The method of  claim 24 , wherein the security rule lists times when messages can be delivered. 
     
     
         46 . The method of  claim 24 , wherein the security rule lists one or more locations such that the second machine will only accept messages when at a listed location. 
     
     
         47 . The method of  claim 24 , wherein the first private network and the second private network are part of the same network.

Join the waitlist — get patent alerts

Track US2017366512A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.