Connection architecture for a mobile network
DCFirst Claim
1. A server that manages transactions between first and second devices, the server comprising:
- a communication interface;
a processor communicatively coupled to the communication interface; and
a memory communicatively coupled to the processor, the memory containing instructions executable by the processor whereby the server is operable to;
receive a first connection from a first device;
authenticate the first device over the first connection;
receive a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction;
generate a trigger for a second device based on the first transaction from the first device, wherein the trigger is pushed to the second device;
after the generation of the trigger for the second device, receive a second connection from the second device while the first connection is maintained;
authenticate the second device over the second connection,wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user; and
send a second transaction to the second device using the second connection, wherein the second transaction contains the new data,wherein the trigger is pushed over a connection different from the second connection,wherein a third transaction is received by the server in response to user input at the second device.
2 Assignments
Litigations
2 Petitions
Accused Products
Abstract
A mobile device for accessing content stored on a remote server over a mobile network is provided. The mobile device includes a processor configured to direct the mobile device to receive at least a portion of a list initiated by the remote server, the list identifying folders or files stored on the remote server, process a selection to identify one of the folders or files on the list having the content on the remote server, and send a request directing a management server to initiate a transaction including an identifier indicating the one of the folders or files having the content on the remote server that is to be sent as the attachment to the destination.
-
Citations
38 Claims
-
1. A server that manages transactions between first and second devices, the server comprising:
-
a communication interface; a processor communicatively coupled to the communication interface; and a memory communicatively coupled to the processor, the memory containing instructions executable by the processor whereby the server is operable to; receive a first connection from a first device; authenticate the first device over the first connection; receive a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction; generate a trigger for a second device based on the first transaction from the first device, wherein the trigger is pushed to the second device; after the generation of the trigger for the second device, receive a second connection from the second device while the first connection is maintained; authenticate the second device over the second connection, wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user; and send a second transaction to the second device using the second connection, wherein the second transaction contains the new data, wherein the trigger is pushed over a connection different from the second connection, wherein a third transaction is received by the server in response to user input at the second device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A method of operating a server to manage transactions between first and second devices, the method comprising:
- receiving a first connection from a first device;
authenticating the first device over the first connection; receiving a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction; generating a trigger for a second device based on the first transaction from the first device, wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user, wherein the trigger is pushed to the second device; after the generation of the trigger for the second device, receiving a second connection from the second device while the first connection is maintained; authenticating the second device over the second connection; and sending a second transaction to the second device using the second connection, wherein the second transaction contains the new data, wherein the trigger is pushed over a connection different from the second connection, wherein a third transaction is received by the server in response to user input at the second device. - View Dependent Claims (21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38)
- receiving a first connection from a first device;
Specification