System and method for administration and operation of one or more mobile electronic communications devices

• US 9,936,387 B2
• Filed: 01/30/2017
• Issued: 04/03/2018
• Est. Priority Date: 04/22/2010
• Status: Active Grant

• Current Assignee: Zipit Wireless, Inc.
• Original Assignee: Zipit Wireless, Inc.
• Inventors: Heredia, Rafael, Crowe, Michael W., Greer, IV, Frank U., Ellis, Joseph A., Upham, Jordan, Matson, William R.
• Primary Examiner(s): DOAN, KIET M
• Application Number:
  US15/419,060
• Publication Number:
  US 20170142585A1
• Time in Patent Office: 428 Days
• Field of Search: 455466, 455458, 4554351, 4554565, 455521, 455411, 455433, 455436, 4554321, 370329, 370338
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: H04B 1/401 for selecting or indicating operating mode
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04M 1/67 by electronic means
• CPC Class Codes: H04M 1/72457 according to geographic location
• CPC Class Codes: H04M 2250/06 including a wireless LAN interface
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 48/18 Selecting a network or a communication service
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

A system for managing mobile electronic communications devices includes a user directory database configured to hold authentication data associated with at least one user, an authentication authority communicatively connected to the user directory database, an administration server configured to send and receive command messages with at least one mobile electronic communications device, a messaging server configured to send and receive communications messages with at least one mobile electronic communications device, and the authentication authority, administration server, and messaging server are configured to send and receive data via a data communications network. The authentication authority accepts or denies authentication data for a user received from at least one mobile electronic communications device, stores status information corresponding to authenticated users in the user directory database, and stores an association between each authenticated user and each mobile electronic device that sent authentication data for an authenticated user in the user directory database.

Claims

1. A method for delivering data from a first network computing device to a subscriber computing device comprising:

establishing at least one publisher node in a network computing device;

configuring a subscriber computing device with a subscription to the at least one publisher node;

generating a first data message for publication by the at least one publisher node;

generating with the publisher node a version number for the first data message generated by the publisher node;

storing the first data message and the version number for the first data message in a memory in the publisher node;

identifying at the publisher node a version number stored in the subscriber computing device;

transmitting the first data message from the at least one publisher node to the subscriber computing device with the subscription in response to the version number for the first data message being greater than the version number stored in the subscriber computing device;

generating a receipt message in the subscriber computing device that indicates receipt of the first data message at the subscriber computing device;

transmitting the receipt message from the subscriber computing device to the network computing device; and

removing a second data message having a second version number from the memory at the publisher node in response to the network computing device receiving the receipt message from the subscriber computing device and the version number for the first data message being greater than the second version number;

transmitting the first data message from the at least one publisher node to the subscriber computing device a predetermined number of times; and

generating a record that indicates that the subscriber computing device failed to receive the first data message in response to the subscriber computing device failing to send a receipt message to the network computing device in response to any one of the transmitted first data messages.

2. The method of claim 1 further comprising:

receiving the version number and the first data message generated by the publisher node at the subscriber computing device;

identifying with the subscriber computing device a version number stored in the subscriber computing device; and

deleting the first data message at the subscriber computing device in response to the version number for the first data message computing device being equal to or less than the version number stored at the subscriber computing device.

3. The method of claim 1 further comprising:

generating message verification data with the subscriber computing device, the message verification data indicating the subscriber computing device received the first data message without corruption or data errors; and

incorporating the message verification data in the receipt message when the subscriber computing device generates the receipt message.

4. The method of claim 3, the generation of the message verification data further comprising:

generating a checksum or a message digest of the first data message at the subscriber computing device to verify content of the first data message received by the subscriber computing device.

5. The method of claim 1 further comprising:

transmitting the first data message from the at least one publisher node to the subscriber computing device for a predetermined period of time; and

generating a record that indicates that the subscriber computing device failed to receive the first data message in response to the subscriber computing device failing to send a receipt message to the network computing device within the predetermined period of time.