1. A method for establishing communications with a secure network using a non-secure mobile device operating in a non-secure network, the method comprising:
communicating a mobile device identifier to the secure network;
validating, with a mobile device manager in the secure network, the mobile device identifier; and
establishing a secure connection between the mobile device and the secure network.
2. The method of claim 1, wherein the mobile device identifier is communicated to the secure network via at least one of a cellular network, a Wi-Fi network, and an out-of-band network.
3. The method of claim 1, wherein the method further comprises sending, with the mobile device manager, a request for the mobile device identifier.
4. The method of claim 1, wherein the mobile device identifier is an Internet protocol (IP) address.
5. The method of claim 1, wherein the mobile device identifier is a unique identification (ID) code.
6. The method of claim 1, wherein the method further comprises validating, with the mobile device manager, a user of the mobile device.
7. The method of claim 6, wherein the user of the mobile device is validated by using biometrics of the user.
8. The method of claim 1, wherein the mobile device is validated by determining a location of the mobile device.
9. The method of claim 1, wherein the method further comprises:
receiving, with the mobile device, encrypted secure data from the secure network; and
decrypting, with the mobile device, the received encrypted secure data using mobile device security software.
10. The method of claim 1, wherein the method further comprises:
encrypting, with the mobile device, non-secure data using mobile device security software; and
transmitting, with the mobile device, the encrypted data to the secure network.
11. A non-secure mobile device operating in a non-secure network used for establishing communications with a secure network, the mobile device comprising:
a transmitter, wherein the transmitter is configured for communicating a mobile device identifier to the secure network;
a receiver, wherein the receiver is configured for receiving encrypted secure data from the secure network; and
a processor, wherein the processor is configured for decrypting the received encrypted secure data using mobile device security software.
12. The mobile device of claim 11, wherein the mobile device security software comprises at least one of encryption software, decryption software, and forced fixed destination addressing software.
13. The mobile device of claim 11, wherein the transmitter communicates the mobile device identifier to the secure network via at least one of a cellular network, a Wi-Fi network, and an out-of-band network.
14. The mobile device of claim 11, wherein the mobile device identifier is an Internet protocol (IP) address.
15. The mobile device of claim 11, wherein the mobile device identifier is a unique identification (ID) code.
16. The mobile device of claim 11, wherein the processor is further configured for encrypting non-secure data using the previously downloaded mobile device security software, and
wherein the transmitter is further configured for transmitting the encrypted data to the secure network.
17. A method for establishing communications with a secure network using a non-secure mobile device operating in a non-secure network, the method comprising:
communicating a mobile device identifier to the secure network to establish a secure connection between the mobile device and the secure network; and
establishing a secure connection between the mobile device and the secure network.
18. A method for establishing communications with a secure network using a non-secure mobile device operating in a non-secure network, the method comprising:
receiving a request with a mobile device identifier to establish a secure connection between the mobile device and the secure network;
validating, with a mobile device manager in the secure network, the mobile device identifier; and
establishing a secure connection between the mobile device and the secure network.
19. The method of claim 18, wherein the mobile device is operating in at least one of a cellular network and a Wi-Fi network.
20. The method of claim 18, wherein the method further comprises sending, with the mobile device manager, a request for the mobile device identifier.
21. The method of claim 18, wherein the mobile device identifier is an Internet protocol (IP) address.
22. The method of claim 18, wherein the mobile device identifier is a unique identification (ID) code.
23. The method of claim 18, wherein the method further comprises validating, with the mobile device manager, a user of the mobile device.
24. The method of claim 18, wherein the method further comprises:
transmitting, with a transmitter, encrypted secure data from the secure network to the mobile device.
25. The method of claim 18, wherein the method further comprises:
receiving, with the receiver, encrypted data transmitted from the mobile device; and
decrypting, with a processor, the received encrypted data.
26. The method of claim 23, wherein the user of the mobile device is validated by using biometrics of the user.
27. The method of claim 18, wherein the mobile device is validated by determining a location of the mobile device.
28. A method for allowing for the establishment of communications with a secure network using a non-secure mobile device operating in a non-secure network, the method comprising:
communicating a request to the secure network to download mobile device security software;
downloading and installing, by the mobile device, the mobile device security software from the secure network;
activating, by the mobile device, the mobile device security software;
transmitting, with the mobile device, a mobile device manager enrollment request to the secure network;
validating, with the mobile device manager, the mobile device based on a unique data item description (UDID) of the mobile device; and
transmitting, by the mobile device manager, a mobile device identifier to the mobile device,
wherein the mobile device identifier allows for the mobile device to establish communications with the secure network.
29. The method of claim 28, wherein the method further comprises:
including, with the mobile device manager, a phone number of the mobile device on a carrier access list,
wherein subsequent encrypted data transmissions from mobile devices having their phone numbers on the carrier access list will be automatically routed to the secure network.
30. A system for establishing communications with a secure network using a non-secure mobile device operating in a non-secure network, the system comprising:
the mobile device configured to communicate a mobile device identifier to an authentication server;
the authentication server configured to receive the mobile device identifier, to transmit the mobile device identifier to a mobile device manager in the secure network, and to validate the mobile device identifier with the mobile device manager; and
the mobile device manager configured to validate the mobile device identifier with the authentication server,
wherein a secure connection between the mobile device and the secure network is established when the mobile device identifier is validated.
31. The system of claim 30, wherein the mobile device is configured to communicate the mobile device identifier to the authentication server via at least one of a cellular network, a Wi-Fi network, and an out-of-band network.
32. The system of claim 30, wherein the mobile device manager is further configured to send a request to the mobile device for the mobile device identifier.
33. The system of claim 30, wherein the mobile device identifier is an Internet protocol (IP) address.
34. The system of claim 30, wherein the mobile device identifier is a unique identification (ID) code.
35. The system of claim 30, wherein mobile device manager is further configured to validate, with the authentication sever, a user of the mobile device.
36. The system of claim 35, wherein mobile device manager is further configured to validate, with the authentication sever, the user of the mobile device by using biometrics of the user.
37. The system of claim 30, wherein the mobile device manager is further configured to validate, with the authentication sever, the mobile device by determining a location of the mobile device.
38. The system of claim 30, wherein the mobile device is further configured to receive encrypted secure data from the secure network, and to decrypt the received encrypted secure data using mobile device security software.
39. The system of claim 30, wherein the mobile device is further configured to encrypt non-secure data using mobile device security software, and to transmit the encrypted data to the secure network.
40. A system for establishing communications with a secure network using a non-secure mobile device operating in a non-secure network, the system comprising:
the mobile device configured to communicate a request with a mobile device identifier to an authentication sever to establish a secure connection between the mobile device and the secure network;
the authentication sever configured to receive the request with the mobile device identifier, to transmit the mobile device identifier to a mobile device manager in the secure network, and to validate the mobile device identifier with the mobile device manager; and
the mobile device manager configured to validate the mobile device identifier with the authentication server;
wherein a secure connection between the mobile device and the secure network is established when the mobile device identifier is validated.
41. The system of claim 40, wherein the mobile device is configured to operate in at least one of a cellular network and a Wi-Fi network.
42. The system of claim 40, wherein the mobile device manager is further configured to send a request for the mobile device identifier.
43. The system of claim 40, wherein the mobile device identifier is an Internet protocol (IP) address.
44. The system of claim 40, wherein the mobile device identifier is a unique identification (ID) code.
45. The system of claim 40, wherein the mobile device manager is further configured to validate, with the authentication server, a user of the mobile device.
46. The system of claim 45, wherein the mobile device manager is further configured to validate, with the authentication server, the user by using biometrics of the user.
47. The system of claim 40, wherein the system further comprises:
a transmitter configured to transmit encrypted secure data from the secure network to the mobile device.
48. The system of claim 40, wherein the system further comprises:
a receiver configured to receive encrypted data transmitted from the mobile device; and
a processor configured to decrypt the received encrypted data.
49. The system of claim 40, wherein the mobile device manager is further configured to validate, with the authentication sever, the mobile device by determining a location of the mobile device.
50. A system for allowing for the establishment of communications with a secure network using a non-secure mobile device operating in a non-secure network, the system comprising:
the mobile device configured to communicate a request to a mobile device manager in the secure network via an authentication server to download mobile device security software, configured to download and install the mobile device security software received from the mobile device manager, configured to activate the mobile device security software, and configured to transmit a mobile device manager enrollment request to the mobile device manager via the authentication server; and
the mobile device manager configured to validate the mobile device based on a unique data item description (UDID) of the mobile device, and configured to transmit a mobile device identifier to the mobile device,
wherein the mobile device identifier allows for the mobile device to establish communications with the secure network.
51. The system of claim 50, wherein the mobile device manager is further configured to include a phone number of the mobile device on a carrier access list,
wherein subsequent encrypted data transmissions from mobile devices having their phone numbers on the carrier access list will be automatically routed to the secure network.
52. A system for establishing communications with a secure network using a non-secure mobile device operating in a non-secure network, the system comprising:
a mobile device manager in the secure network,
wherein the mobile device manager is configured to validate, with an authentication server, a mobile device identifier associated with the mobile device, and
wherein a secure connection between the mobile device and the secure network is established when the mobile device identifier is validated.
53. The system of claim 52, wherein the mobile device manager is further configured to send a request to the mobile device for the mobile device identifier.
54. The system of claim 52, wherein the mobile device identifier is an Internet protocol (IP) address.
55. The system of claim 52, wherein the mobile device identifier is a unique identification (ID) code.
56. The system of claim 52, wherein mobile device manager is further configured to validate, with the authentication sever, a user of the mobile device.
57. The system of claim 56, wherein mobile device manager is further configured to validate, with the authentication sever, the user of the mobile device by using biometrics of the user.
58. The system of claim 52, wherein the mobile device manager is further configured to validate, with the authentication sever, the mobile device by determining a location of the mobile device.
59. A secure network used for establishing communications with a non-secure mobile device operating in a non-secure network, the secure network comprising:
a mobile device manager configured to validate, with an authentication server, a mobile device identifier associated with the mobile device,
wherein a secure connection between the mobile device and the secure network is established when the mobile device identifier is validated; and
application and database systems.
60. The secure network of claim 59, wherein the mobile device manager is further configured to send a request to the mobile device for the mobile device identifier.
61. The secure network of claim 59, wherein the mobile device identifier is an Internet protocol (IP) address.
62. The secure network of claim 59, wherein the mobile device identifier is a unique identification (ID) code.
63. The secure network of claim 59, wherein mobile device manager is further configured to validate, with the authentication sever, a user of the mobile device.
64. The secure network of claim 63, wherein mobile device manager is further configured to validate, with the authentication sever, the user of the mobile device by using biometrics of the user.
65. The secure network of claim 59, wherein the mobile device manager is further configured to validate, with the authentication sever, the mobile device by determining a location of the mobile device.
66. The secure network of claim 59, wherein the secure network further comprises at least one of a secure data storage, a remote desktop access system, a mobile web application system, a mobile application database system, and a web single sign-on system.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method comprising:
receiving at a bus interface a request for access to a resource;
employing a first counter to assign a value to the request;
buffering the request for access to the resource at the bus interface while waiting for the granting of the request; and
granting the requested access to the resource when a second counter reaches a value equal to the value assigned by the first counter to the request, wherein the bus interface can take action regarding the request while the request waits for access to the resource.
2. The method of claim 1, wherein the bus interface includes multiple types of buffers, and the method further comprises buffering the request in one type of buffer of the multiple types of buffers based on a request type of the request.
3. The method of claim 2, wherein the request type comprises one of a write transaction and a read transaction.
4. The method of claim 1, wherein buffering the request comprises buffering the request in one buffer of a plurality of buffers of the bus interface, and wherein each buffer of the plurality of buffers includes an associated request state machine, and wherein the associated request state machine of the one buffer takes action regarding the request while the request waits for access to the resource.
5. The method of claim 1, further comprising maintaining request coherency at the bus interface employing snooping, and wherein the first counter assigns the value to the request during a snoop phase of the request.
6. The method of claim 5, further comprising repeating the method for a plurality of requests, and wherein the values assigned to the plurality of requests by the first counter maintain a snoop response ordering of the plurality of requests for access to the resource, while the bus interface takes action regarding at least one request of the plurality of requests.
7. The method of claim 6, wherein the bus interface comprises a bus bridge coupled between a first bus and a second bus, the first bus and the second bus comprising different bus types.
8. The method of claim 1, wherein the first counter and the second counter have offset values, and count in the same order.
9. A system comprising:
means for receiving at a bus interface a request for access to a resource, the bus interface including multiple types of buffers;
means for employing a first counter to assign a value to the request;
means for buffering the request in one type of buffer of the multiple types of buffers based on a request type of the request; and
means for granting the requested access to the resource when a second counter reaches a value equal to the value assigned by the first counter to the request, wherein the bus interface can take action regarding the request while the request waits for access to the resource.
10. The system of claim 9, wherein the request type comprises one of a write transaction and a read transaction.
11. The system of claim 9, wherein each buffer of the multiple types of buffers includes an associated request state machine, and wherein the associated request state machine of the one type of buffer buffering the request takes action regarding the request while the request waits for access to the resource.
12. The system of claim 9, further comprising means for maintaining request coherency at the bus interface employing snooping, and wherein the first counter is employed to assign the value to the request during a snoop phase of the request.
13. The system of claim 12, wherein the means for receiving, the means for employing and the means for granting are repeated for a plurality of requests, and wherein the values assigned to the plurality of requests by the first counter maintain a snoop response ordering of the plurality of requests for access to the resource, while the bus interface takes action regarding at least one request of the plurality of requests.
14. The system of claim 13, wherein the bus interface comprises a bus bridge coupled between a first bus and a second bus, the first bus and the second bus comprising different bus types.
15. The system of claim 9, wherein the first counter comprises a ticket dispenser counter for dispensing a ticket value to the request, and the second counter comprises a ticket call counter for providing ticket call values, wherein the request is granted access to the resource when a ticket call value equals the ticket value dispensed to the request by the ticket dispenser counter, wherein the bus interface can takes action regarding the request while the bus interface waits for the ticket call value to equal the dispensed ticket value.
16. A system comprising:
a bus bridge for coupling between a first bus and a second bus, the bus bridge including:
multiple ticket registers;
a ticket dispenser counter for dispensing a ticket value to a request received at the bus bridge from the first bus for access to the second bus, the ticket value being held in one ticket register of the multiple ticket registers; and
a ticket call counter for providing ticket call values, wherein the request is granted access to the second bus when a ticket call value equals the ticket value dispensed to the request by the ticket dispenser counter, and wherein the bus bridge can take action regarding the request while the request waits for access to the second bus.
17. The system of claim 16, further comprising multiple request state machines, each request state machine being associated with a respective ticket register of the multiple ticket registers, and wherein the request state machine associated with the one ticket register holding the ticket value for the request can take action regarding the request while the request waits for access to the second bus.
18. The system of claim 17, further comprising multiple buffers, each buffer comprising a ticket register of the multiple ticket registers and an associated request state machine of the multiple request state machines, and wherein each buffer further comprises a comparator for determining when the ticket call value provided by the ticket call counter equals the ticket value dispensed to the request by the ticket dispenser counter.
19. The system of claim 18, wherein the multiple buffers comprise at least two types of buffers, and wherein the request is buffered in one type of buffer of the at least two types of buffers based on a request type of the request.
20. The system of claim 19, wherein the request type comprises one of a write transaction and a read transaction.
21. The system of claim 16, further comprising a processor coupled to the first bus, and a transaction dispatcher coupled to the second bus, and wherein the request received at the bus bridge is from the processor.
22. The system of claim 16, wherein the first bus and the second bus comprise different bus types.
23. The system of claim 22, wherein the first bus and the second bus comprise at least one of an application programming interface (API) bus and a message passing interface (MPI) bus.
24. The system of claim 16, wherein coherency is maintained within the bus bridge via snooping, and wherein the ticket dispenser counter dispenses the ticket value to the request during a snoop phase of the request.
25. The system of claim 24, wherein the ticket dispenser counter dispenses a plurality of ticket values to a plurality of requests received at the bus bridge, and wherein the ticket values assigned to the plurality of requests by the ticket dispenser counter maintain a snoop response ordering of the plurality of requests for access to the second bus, while the bus interface takes action regarding at least one request of the plurality of requests.