Patent Description:
The present disclosure generally relates to portable storage devices, and more particularly to portable storage devices with modular components.

Communication between devices is typically performed over a network, such as the internet or a local area network. However, networks may not always be available for communication between devices and additionally may expose communications to security breaches on the network. Devices enabled with Bluetooth® may communicate directly. However, Bluetooth® enabled devices must be within a limited range, and communication speeds may be relatively slow. Consumers may have files stored on one device and wish to access the files from another device. It may be difficult to transfer the file without an internet connection or using data on a data plan. Additionally, transferring the information may expose the information to hackers and security breaches.

Carrying storage devices can also be cumbersome even without concerns regarding data transfer. Most people are conditioned to check for a few items such as their keys, wallets, and phones when leaving a location. But USB sticks, for example, are easily misplaced and left behind. Losing storage devices is a security risk in addition to being inconvenient. Physical copies of data retained on a storage device get exposed when the device is recovered by a third party.

<CIT> describes a portable storage device.

A modular portable storage system is disclosed herein. The modular portable storage system includes a portable storage device with a housing having a cuboid geometry. The housing retains a processor, a storage module in electronic communication with the processor, and a wireless communication module. A circuit communicates electronically with the portable storage device. The portable storage device is removably coupled to the circuit board. A power supply is in electronic communication with the circuit board. The power supply is also removably coupled to the circuit board. The portable storage device and the power supply are removably retained within the external housing. The circuit board is mechanically coupled to the external housing.

In various embodiments, the portable storage device may further include a data port exposed from a first surface of the portable storage device. The portable storage device may also include conductive pads exposed from the first surface of the portable storage device. The data port may be disposed between at least two of the conductive pads. A case for a mobile device may define a cavity configured to retain the portable storage device. The case may further include an interface disposed in the cavity and configured for electronic coupling to at least one of the conductive pads or the data port. The case may also comprise a data plug in electronic communication with the interface and configured to engage a plug on the mobile device. The case may have a protrusion configured to house the cavity and/or the power supply.

A modular portable storage system may also include a portable storage device comprising a housing having a cuboid geometry. The housing may retain a processor, a storage module in electronic communication with the processor, and a wireless communication module. An electronic interface panel may be located on a surface of the portable storage device. The electronic interface panel may include a data port and/or a conductive pad. A case for a mobile device may include a cavity to retain the portable storage device.

In various embodiments, the cavity may have five orthogonal surfaces. The portable storage device may lay flush with an interior surface of the case in response to the portable storage device being inserted into the cavity. The case may further include an interface disposed in the cavity and electronically coupled to the electronic interface panel. The case may include a data plug in electronic communication with the interface and configured to engage a plug on the mobile device. The case may also comprise a protrusion disposed at an external surface and configured to house the cavity. The protrusion may be configured to house a power supply.

A portable storage device may include a processor, a circuit board coupled to the processor and in electronic communication with the processor, a non-transitory memory coupled to the circuit board and in electronic communication with the circuit board, a first wireless chip coupled to the circuit board and in electronic communication with the circuit board, wherein the first wireless chip may transmit data directly to a mobile device, a housing retaining the processor, the circuit board, the non-transitory memory, and the first wireless chip, wherein the housing is a cuboid defined by a height, a width, and a length.

In various embodiments, the height may be substantially <NUM> inches, the length may be substantially <NUM> inches, and the width may be substantially <NUM> inches. An electronic interface panel may be in electronic communication with the circuit board and disposed on a first surface of the portable storage device. The first surface may be defined by the height and the length of the portable storage device. A human interface panel may also be defined in a second surface with a button and/or a light source. The second surface may be defined by the length and the width of the portable storage device.

A more complete understanding may be derived by referring to the detailed description and claims when considered in connection with the Figures, wherein like reference numbers refer to similar elements throughout the Figures.

The detailed description of exemplary embodiments herein makes reference to the accompanying drawings and pictures, which show various embodiments by way of illustration. While these various embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.

The present disclosure relates to systems, methods, and computer program products. In the detailed description herein, references to "various embodiments," "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Systems and methods are disclosed herein for communication between a portable content repository and computing devices. A portable storage device may serve as a content repository by retaining content for access by other devices. Various computing devices may read, write, and/or execute content stored on the portable storage device. Although the portable storage device may "permanently" store the content, the various computing devices accessing content on the portable storage device retain the content temporarily and/or with access controls in place. The portable storage device may thus be described as a content repository device. Content repository devices of the present disclosure may use a standardized communication system ("SCS") as described herein. The portable storage device may also be reconfigurable relative to various components.

The systems and methods disclosed herein may enable communication between devices without connection to the Internet or other networks using an SCS. An SCS may be operable on the computing devices of the present disclosure. The SCS may comprise any combination of hardware and/or software. The SCS may utilize existing physical components of the device, such as <NUM> or <NUM>(<NUM>) wireless chips and Bluetooth® systems in order to communicate with other devices. The SCS may be suitable for any communication protocol, such as IP, TCP/UDP, Bluetooth®, raw Manchester encoding, and any other form of wireless communication.

The SCS may allow communication between devices of varying types and platforms. Additionally, as communication may happen directly between devices without transmitting data across a network, communication may be available when networks are unavailable, and communications may be protected from eavesdroppers on a network. Furthermore, direct communication between devices may avoid data charges on cellular data plans.

Referring to <FIG>, a system <NUM> for transmitting messages is illustrated according to various embodiments. A first device <NUM> comprising an SCS <NUM> and a second device <NUM> comprising an SCS <NUM> are illustrated according to various embodiments. In various embodiments, SCS <NUM> and SCS <NUM> may be aftermarket software programs installed on first device <NUM> and second device <NUM>. For example, a user may download an SCS app onto a smartphone or other device. However, in various embodiments, SCS <NUM> and SCS <NUM> may be embedded into a chip, such as an <NUM> wireless chip, in first device <NUM> and/or second device <NUM>.

In various embodiments, the SCS may implement a standardized communication protocol ("SCP") on a device. The SCP may attach an SCP header <NUM> to a packet in order to identify a datagram <NUM> as an SCP datagram. First device <NUM> may communicate with second device <NUM> via SCP. The SCS may recognize the SCP header and may follow the SCP. The SCP may define the ability for devices to discover one another, to request the transfer of raw data, to transmit confirmations on receipt of data, and to perform any other steps involved with transmitting data.

In various embodiments, the SCS may be implemented at the network layer in the Open Systems Interconnection ("OSI") model (or the Internet layer in the TCP/IP model). Regardless of the protocol being used at the transport layer (e.g. TCP, UDP, SCTP, DCCP), the SCP header may allow devices comprising an SCS to communicate via SCP.

In various embodiments, at least one of first device <NUM> and second device <NUM> may comprise a smartphone. However, in various embodiments, first device <NUM> and second device <NUM> may comprise any type of device capable of transmitting and/or receiving data.

Referring to <FIG>, a process <NUM> for transmitting data between devices is illustrated according to various embodiments. In various embodiments, a first user may wish to transmit data from first device <NUM> to second device <NUM>. The data may comprise any type of data, such as a text message, image, video, text document, or any other type of file.

First device <NUM> may discover available devices (step <NUM>). First device <NUM> may attempt to discover other devices by a variety of methods. In various embodiments, first device <NUM> may discover other devices via a camera or other optical device. In various embodiments, second device <NUM> may display a symbol, such as a QR-code, a barcode, or text. The symbol may comprise identifying characteristics about second device <NUM>. For example, in various embodiments the identifying characteristics may comprise at least one of a device name, an IP address of the device, an owner name, an endpoint of the device, and the available transport layers on the device. First device <NUM> may scan the symbol using a camera. First device <NUM> may obtain the identifying characteristics from the symbol and use the identifying characteristics in order to transmit data to second device <NUM>.

In various embodiments, the SCS on first device <NUM> may search for other devices using a wireless chip in first device <NUM>. Devices comprising an SCS may transmit a broadcast message. The broadcast message may comprise the identifying characteristics of the device. In various embodiments, first device <NUM> may be within transmission range of second device <NUM>. The transmission range may depend on the specific type of wireless chips in first device <NUM> and second device <NUM>. However, in various embodiments, the transmission range may be up to about <NUM> feet - <NUM> feet. The SCS may open a socket on first device <NUM> to listen for broadcast messages. The broadcast message may be sent by a variety of hardware. For example, the broadcast message may be transmitted via an <NUM> wireless chip, Bluetooth® chip, or NFC.

In various embodiments, first device <NUM> and second device <NUM> may not be within transmission range of each other. However, an intermediary device, such as a smartphone equipped with hotspot technology, may be within transmission range of first device <NUM>. First device <NUM> may search for available devices by transmitting a message to intermediary device, instructing intermediary device to look for available devices. Intermediary device may receive a broadcast message from second device <NUM>, and intermediary device may transmit the broadcast message to first device <NUM>. Thus, first device <NUM> may discover second device <NUM> without connecting to the internet or a cellular network even though first device <NUM> may not be within transmission range of second device <NUM>. In various embodiments, any number of intermediary devices may be daisy-chained, such that first device <NUM> may discover second device <NUM> from miles apart by transmitting data via a series of intermediary devices.

First device <NUM> may display a list of all discovered devices to the user. The user may select second device <NUM> in order to transmit data to second device <NUM>. The user may select a file or message to be transmitted to second device <NUM>.

The SCS <NUM> on first device <NUM> may determine the transmission hardware to utilize for the transmission (step <NUM>). In various embodiments, first device <NUM> and second device <NUM> may each have only one type of transmission hardware, such as an <NUM> wireless chip, and the SCS <NUM> may thus select the <NUM> wireless chip to transmit the data. However, in various embodiments, multiple transmission paths may be available between first device <NUM> and second device <NUM>. For example, first device <NUM> and second device <NUM> may each comprise an <NUM> wireless chip and a Bluetooth® chip. In various embodiments, the SCS <NUM> may determine the fastest transmission path, and may select the fastest transmission path to transmit the data. In various embodiments, the transmission path may be selected by default settings. For example, SCS <NUM> may always select an <NUM> wireless path for transmission when available, and if the <NUM> wireless path is not available, SCS <NUM> may select a Bluetooth® path. However, in various embodiments, the SCS <NUM> on first device <NUM> may transmit a speed test message to second device <NUM> via each available transmission path, and the SCS <NUM> may select the fastest transmission path based on the speed test results.

In various embodiments, the SCS <NUM> may instruct first device <NUM> to send the data to second device <NUM> via multiple transmission paths. A message may be divided into multiple packets. SCS <NUM> may analyze the available transmissions paths, and send the message over multiple transmission paths in order to expedite transmission of the entire message. For example, SCS <NUM> may determine that the fastest method of transmitting the message may be to transmit <NUM>% of the packets via an <NUM> wireless path, and <NUM>% of the packets over a Bluetooth® path. SCS <NUM> may attach an SCP header to each packet being transmitted to second device <NUM>, whether via <NUM> wireless or Bluetooth®. Thus, SCS <NUM> on second device <NUM> may recognize the packets as being received by SCP, and SCS <NUM> may reassemble the packets in order to recreate the entire message. In various embodiments, SCS <NUM> may analyze all transmission paths available, including but not limited to multiple <NUM> wireless chips, Bluetooth® chips, NFC, PDQ, or any other transmission paths in order to select the fastest transmission method. The SCS on first device <NUM> may initiate a file send protocol and transmit the data to second device <NUM> (step <NUM>).

In various embodiments, first device <NUM> and second device <NUM> may be connected to the same local network. First device <NUM> may transmit a link, such as a QR-code, over a cellular network or the local network to second device <NUM>. In various embodiments, the link may comprise 10kb or less of data. Second device <NUM> may use the link to request or accept a file transfer. First device <NUM> may transmit a file over the local network. In various embodiments, the file may be transferred using TCP/IP directly over the local network.

In various embodiments, second device <NUM> may have access to an internet connection. First device <NUM> may transmit a link over a cellular transmission path to second device <NUM>, and second device <NUM> may use the link to download a file stored on the cloud and/or on a server over the internet. In various embodiments, second device <NUM> may download the file using TCP/IP.

In various embodiments, first device <NUM> may sync its contents with a cloud database. In various embodiments, first device <NUM> may comprise an SCS folder, and only files stored in the SCS folder may be synced with the database. First device <NUM> may transmit a link over a cellular transmission path to second device <NUM> identifying a file stored on the database. In various embodiments, second device <NUM> may not have access to an <NUM> wireless network at the time second device <NUM> receives the link. Second device <NUM> may use the link to access the file whenever second device <NUM> gains access to an <NUM> wireless network in order to prevent cellular data charges. In various embodiments, second device <NUM> may use the link to access the file over the cellular network. In various embodiments, second device <NUM> may stream all or part of the file over either the cellular network or an <NUM> wireless network.

In various embodiments, first device <NUM> may share an online folder with second device <NUM>. First device <NUM> may indicate that second device <NUM> may have access to an online folder. First device <NUM> may sync with the online folder to upload files stored on first device <NUM> to the online folder. Second device <NUM> may sync with the online folder to download files stored in the online folder to second device <NUM>.

Referring to <FIG>, a process <NUM> for a file send protocol is illustrated according to various embodiments. First device <NUM> may transmit a request to establish a connection with second device <NUM> (step <NUM>). In various embodiments the connection may comprise a TCP connection. However, in various embodiments, the connection may comprise any type of connection for transmitting data between devices. Second device <NUM> may accept the connection request (step <NUM>). In various embodiments, the connection may be between secure sockets on first device <NUM> and second device <NUM>.

In various embodiments, first device <NUM> may transmit a message comprising a cypher book to second device <NUM> (step <NUM>). The cypher book may comprise a list of one-time cyphers, and may allow second device <NUM> to decrypt data sent to second device <NUM> over the secure socket connection using one time cyphers. In various embodiments, first device <NUM> may encrypt the message comprising the cypher book using known encryption methods, such as Advanced Encryption Standard ("AES") or RSA encryption. However, subsequent messages during the transfer session may be encrypted using the one-time cyphers contained in the cypher book. The messages encrypted using the one-time cyphers may be encrypted and decrypted using significantly less processing power and time than messages encrypted with AES or RSA. Additionally, the messages sent using the one-time cyphers may be indecipherable to parties not containing the cypher book.

First device <NUM> may send a file transfer request (step <NUM>). For an example of a file transfer request, refer to <FIG>. Second device <NUM> may accept the file transfer request (step <NUM>). In response to second device <NUM> accepting the file transfer request, first device <NUM> may break the file into segments, and begin transmitting the segments to second device <NUM> (step <NUM>). After first device <NUM> has transmitted all segments of the file, first device <NUM> may wait for confirmation that second device <NUM> has received all segments. Second device <NUM> may transmit a confirmation message to first device <NUM> indicating that all segments have been received (step <NUM>). Second device <NUM> may decrypt and reassemble the segments according to SCP in order to recreate the file (step <NUM>).

Referring to <FIG>, an example of a discovery protocol <NUM> is illustrated according to various embodiments. Discovery protocol <NUM> may be implemented on the transport layer using TCP/UDP. However, in various embodiments, discovery protocols may be implemented using a Bluetooth® serial port, RS-<NUM>, or may be sent entirely over datagrams or a Windows® Socket API ("WSA"). The LocalClient in the illustrated embodiment may be a new instance of an IDiscoveredClient (defined in <FIG>) class filled in with the device's identifying characteristics, such as device name, user name, preview image, and endpoint (in this case an IP address and port). First device <NUM> may open a new socket for a broadcast message (<NUM>). First device <NUM> may transmit the IP address that first device <NUM> is listening on for a response to the broadcast message (<NUM>). First device <NUM> may open a new datagram socket to listen for a response message (<NUM>). After receiving a response message, first device <NUM> may decipher the response message into the original IDiscoveredClient message that first device <NUM> sent (<NUM>).

Referring to <FIG>, a definition for an example discovery protocol <NUM> is illustrated according to various embodiments. The definition may be a single common class called IDiscoveredClient that may be implemented by a transmitting device and a receiving device. In various embodiments, the definition may be expanded to include custom fields and any other information that users may desire. In various embodiments, the definition may comprise a name of the device (<NUM>), an IP address of the device (<NUM>), an owner of the device (<NUM>), an endpoint of the device (<NUM>), and a transport layer on which the device was discovered (<NUM>). However, one skilled in the art will appreciate that the particular fields used may be altered to any desired fields.

Referring to <FIG>, a definition for an example file transfer request protocol <NUM> is illustrated according to various embodiments. The definition may be called "IFileTransferRequest. " In various embodiments, the definition may comprise the name of the device transmitting a file (<NUM>), the filename to be sent (<NUM>), the size of the file (<NUM>), the device receiving the file (<NUM>), a unique identification for the file transfer (<NUM>), and the transport layer associated with the file transfer (<NUM>).

Referring to <FIG>, a definition for a response to a file transfer request <NUM> is illustrated according to various embodiments. The receiving device may respond with a definition called IFileTransferResponse to indicate that the receiving device is willing to accept the file transfer. In various embodiments, IFileTransferResponse may comprise the response from the user (<NUM>) and the unique identification for the file transfer (<NUM>). The transmitting device may receive the response from the receiving device, and the transmitting device may proceed to transmit the file to the receiving device. Once a complete file transfer has occurred, the receiving device may transmit a confirmation to the transmitting device (<NUM>).

Referring to <FIG>, a portable storage device ("PSD") <NUM> is illustrated according to various embodiments. The PSD <NUM> may be a wearable device, such as a wrist band or bracelet as illustrated in <FIG>. However, PSDs may be any type of portable device which is capable of storing information. For example, a PSD may comprise a watch, necklace, phone case, smartphone, implanted chips, clothing item, wallet, etc..

The PSD <NUM> may comprise a storage module <NUM>, a communication module <NUM>, a processor <NUM>, and a battery <NUM>. The storage module <NUM> may comprise a memory card. For example, the storage module <NUM> may comprise an SD card, an xD card, a CompactFlash card, or any other suitable memory card. The storage module <NUM> may comprise an internal memory, such as iSSD, SSD, iNAND, or flash SD. The communication module <NUM> may comprise one or more components capable of wireless communication. For example, the communication module may comprise an <NUM> or <NUM>(<NUM>) wireless chip, a Bluetooth® chip, an NFC chip, etc. The processor <NUM> may comprise any combination of hardware and/or software capable of providing instructions to the storage module <NUM> and the communication module <NUM>. In various embodiments, the storage module <NUM>, the communication module <NUM>, and the processor <NUM> may be embedded within the PSD <NUM>, such that the PSD <NUM> does not have any visible electronic components. In various embodiments, the PSD <NUM> may comprise a waterproof coating, such as rubber or silicone.

The PSD <NUM> may comprise a standard communication system ("SCS") as previously described herein. The SCS may be any combination of hardware and/or software which is capable of communicating via a standard communication protocol ("SCP") as previously described herein. In various embodiments, the SCS may be implemented on at least one of the storage module <NUM>, the communication module <NUM>, or the processor <NUM>.

The PSD <NUM> may wirelessly receive and transmit files and communications from other devices, such as smartphones, televisions, game consoles, tablets, personal computers, printers, etc. Due to the SCS, the PSD <NUM> may not be limited to communicating with any particular brand or manufacturer of device. In contrast, the PSD <NUM> may communicate across platforms, such as with Apple® devices, Android® devices, Windows® devices, UNIX® devices, or any other suitable devices.

In various embodiments, the PSD <NUM> may allow a user to access their files wherever the user goes. For example, a user may have a document stored on a laptop computer. The user may transmit the document from the laptop computer to the PSD <NUM> using the SCS. The PSD <NUM> may store the document in the storage module <NUM>. The user may then transmit the document from the PSD <NUM> to another device, such as a smartphone, using the SCS.

In various embodiments, the PSD <NUM> may communicate directly with other devices without using a network. Thus, information may be transmitted securely between the PSD <NUM> and other devices. However, in various embodiments, the PSD <NUM> may communicate over a network using a wireless chip in the communication module <NUM>. The communication module <NUM> may comprise two wireless chips, allowing the PSD <NUM> to simultaneously communicate over a network on a first wireless chip and directly to another device on a second wireless chip.

In various embodiments, the PSD <NUM> may allow data to be transferred from a device to the PSD <NUM> without storing the data on the device. For example, a smartphone may capture a picture and transmit the picture directly to the PSD <NUM> using the smartphone's RAM without storing the picture on the hard drive of the smartphone. Thus, the smartphone may be lost, stolen, sold, or donated without risk of a third-party obtaining the picture, or other data which is stored on the PSD <NUM> and not the smartphone. Similarly, a user may initiate an SCS on a device, such as a laptop, and open a file stored on the PSD <NUM> using the device. The user may edit the file on the device and save the edited file directly on the PSD <NUM> without saving the edited file on the device.

A user may use the PSD <NUM> to store all of the user's files. Regardless of what device a user is using to access the files on the PSD <NUM>, the user may create, edit, and delete files directly on the PSD <NUM> using another device, such as a personal computer.

In various embodiments, the PSD <NUM> may emulate a network drive. Thus, the PSD <NUM> may be able to communicate with devices which are not capable of downloading or installing custom software. For example, the PSD <NUM> may emulate a DLNA media service, or a Windows® network. The PSD <NUM> may require a password to be entered on the device, and the device may then access files stored on the PSD <NUM>.

Referring to <FIG>, a PSD <NUM> and a device <NUM> comprising an SCS <NUM> are illustrated according to various embodiments. In various embodiments, the device <NUM> may be the first device <NUM> described with reference to <FIG>. However, the device <NUM> may comprise any device capable of communicating with the PSD <NUM> using an SCP. A user may login to the SCS <NUM>, and the device <NUM> may request an access key. In various embodiments, the device <NUM> may request the access key from a server over an internet or cellular connection. However, in various embodiments, the PSD <NUM> may have one or more stored access keys on the PSD <NUM>, and the device <NUM> may request the stored access key from the PSD <NUM>. The PSD <NUM> may transmit the stored access key to the device <NUM>, and the device <NUM> may use the stored access key to encrypt and/or decrypt data transmitted between the device <NUM> and the PSD <NUM>. In various embodiments, the access key may be a temporary key which may expire after a set amount of time. The user may view the files stored on the PSD <NUM>, and the user may upload or download files between the PSD <NUM> and the device <NUM>. In various embodiments, the PSD <NUM> may stream a file, such as an audio or video file, to the device <NUM>. Once a file is stored on the PSD <NUM>, the user may access the file with any device within communication range of the PSD <NUM>. In various embodiments, a file may be streamed cross-platform. For example, a user may purchase an audio file via iTunes® on an Apple® device. The user may transmit the audio file to the PSD <NUM> using the SCP. The PSD <NUM> may stream the audio file from the PSD <NUM> to a non-Apple® device, regardless of the operating system, using the SCP.

Referring to <FIG>, a system <NUM> for backing up data on a PSD <NUM> is illustrated according to various embodiments. The PSD <NUM> may establish a connection with a device <NUM>. In various embodiments, the device <NUM> may comprise any type of device capable of communicating with a server <NUM>. For example, the device <NUM> may comprise a personal computer, a smartphone, or a wireless router. The device <NUM> may communicate with the server <NUM> over a network. In various embodiments, the server <NUM> may comprise a cloud computing system.

The device <NUM> may comprise an SCS. The PSD <NUM> may communicate with the device <NUM> utilizing the SCS. A user may log into the SCS on the device <NUM>, and instruct the PSD <NUM> to sync with the server <NUM>. The PSD <NUM> may transmit any new or edited files to the server <NUM> via the device <NUM>. The files may be associated with a user account and stored on the server <NUM>. In various embodiments, any new or edited files associated with the user account may be downloaded from the server <NUM> and transmitted to the PSD <NUM> via the device <NUM>. Once the PSD <NUM> is synced with the server <NUM>, a user may access a file by either logging into the user account with any device over the internet, or the user may access the file by accessing the PSD <NUM> with a device.

In various embodiments, the PSD <NUM> may automatically sync when charging, and may charge wirelessly or on a charging cable. The PSD <NUM> may reach a predefined battery level prior to initiating the sync. For example, when placed on a charger, the PSD <NUM> may initiate a sync in response to the battery level reach at least <NUM>%, or at least <NUM>%. The PSD <NUM> may sync to any location specified by a user, such as the server <NUM>, a local device, or another PSD.

With reference to <FIG> a portable storage device <NUM> is shown with modular components, in accordance with various embodiments. Portable storage device <NUM> may include features and functionality described herein. Portable storage device <NUM> has a housing <NUM>. Housing <NUM> may be made from materials including metals, plastics, and/or rubbers. For example, housing <NUM> may be made from stamped and fused sheets of aluminum, molded plastic, or other suitable materials. Housing <NUM> may also be made from thermally conductive materials to enhance heat dissipation.

In various embodiments, housing <NUM> may have rectangular cuboid geometry or rhomboid geometry with <NUM> sides. Each side may have dimensions substantially congruent to the side opposite each side's internal surface. In that regard, housing <NUM> may comprise three pairs of sides having similar dimensions.

In various embodiments, the surfaces of housing <NUM> may leave exposed various interfaces and components. For example, surface <NUM> of housing <NUM> may include electronic interface panel <NUM>. Electronic interface panel <NUM> may further include conductive pads <NUM> disposed slightly proud from, flush with, or slightly recessed from surface <NUM>. Conductive pads <NUM> may form an electrical connection with conductive pins and/or conductive pads formed on an opposing surface in contact with or near to surface <NUM>.

In various embodiments, electronic interface panel <NUM> may further comprise a data port <NUM> exposed from housing <NUM>. Data port <NUM> may be configured to transmit power and/or signals over electronic connections in a predetermined format. For example, data port <NUM> may use a protocol such as USB, firewire, lightning cable, SATA, PCIe, or other suitable cable interface for data and/or power transfer. Data port <NUM> may also use a proprietary pin configuration and slot geometry.

In various embodiments, housing <NUM> may further include surface <NUM> having a rectangular geometry as depicted in a top view by <FIG>. Surface <NUM> may include human I/O interface <NUM> comprising a power button and/or light source <NUM> and an interface button and/or light source <NUM>. Lighting may come from a light emitting diode or other low energy consumption lighting source. Power button <NUM> and interface button <NUM> may comprise capacitive touch buttons, actuating buttons, or other input mechanisms suitable for touch control by a user. Housing <NUM> may also retain a microphone or other I/O device in various embodiments so that users may thus interact with portable storage device <NUM> using voice commands, for example.

In various embodiments, surface <NUM> may have a width W<NUM> and a Length L<NUM>. Width W<NUM> may be a length of substantially <NUM> inches, for example. Length L<NUM> may be a length of substantially <NUM> inches, for example. As used herein to describe a dimension, the term "substantially" describes a variance in the stated dimension of +/- <NUM>%, +/- <NUM>%, +/- <NUM>%, or +/-<NUM>%. Furthermore, the dimensions disclosed herein are given for exemplary purposes and are not intended to be limiting. The small dimensions of portable storage device <NUM> may lend it to use in a modular storage and power solution described in greater detail below. The perimeter of surface <NUM> as well as other surfaces of housing <NUM> may be bounded by rounded edges <NUM>.

Referring now to <FIG>, an elevation view of housing <NUM> is shown, in accordance with various embodiments. Surface <NUM> of housing <NUM> may have a height H<NUM>. Height H1 may have a length of substantially <NUM> inches, for example. Electronic interface panel <NUM> may also be defined in surface <NUM> with conductive pads <NUM> and data port <NUM> exposed from surface <NUM>. The components defined in surface <NUM> may be displaced from the edges of surface <NUM> at symmetric and/or asymmetric locations on surface <NUM>. For example, data port <NUM> may be offset from an edge of housing <NUM> by a distance D<NUM>. Distance D<NUM> may be substantially <NUM> inches, for example. Conductive pads may be offset from a first edge of housing <NUM> by a distance D<NUM>, and from a second edge of housing <NUM> by a distance D<NUM>. Distance D<NUM> and/or distance D<NUM> may be substantially <NUM> inches, for example. Distances D<NUM> and D<NUM> may also vary slightly such that D<NUM> is greater than or less than D<NUM>. Conductive pads <NUM> may have a pitch P<NUM>. Pitch as used herein is defined to be the distance between successive corresponding points on adjacent conductive pads <NUM>. Pitch may describe the distance between the midpoints of adjacent conductive pads <NUM>, for example.

Referring now to <FIG>, examples of internal components of portable storage device <NUM> (of <FIG>) is shown, in accordance with various embodiments. <FIG> illustrates a printed circuit board (PCB) device <NUM> having a stacked configuration. PCB device <NUM> may include a main board <NUM> having an electronic interface panel <NUM> and various semiconductor chips suitable for wireless communication, processing, wired communication, storage access, or other otherwise providing functionality described herein. The semiconductor chips may be packaged as depicted using various packaging configurations such as ball grid array, flip chip, bumps-on-die, or other suitable techniques. One or more secondary PCBs <NUM> and <NUM> may be stacked with main board <NUM>. Secondary PCBs may include printed circuits, wires, and connections to various memory devices <NUM> capable of storing digital data. PCB device <NUM> may be retained partially or completely within housing <NUM> (of <FIG>).

With reference to <FIG>, PCB device <NUM> is shown, in accordance with various embodiments. PCB device <NUM> includes various semiconductor chips as described above with reference to PCB device <NUM>. PCB device <NUM> may have a smaller form-factor than PCB device <NUM> based in part on PCB device <NUM> using a single board construction. Electronic interface panel <NUM> may include conductive pads <NUM> and data port <NUM> soldered or otherwise connected to PCB device <NUM> to effect electronic communication with PCB device <NUM>. Similar to PCB device <NUM> described above, PCB device <NUM> may be retained within portable storage device <NUM> (of <FIG>) to enable the functionality of the portable storage device described herein. Housing <NUM> may thus removably or permanently enclose the PCB devices of <FIG> depending on the configuration of housing <NUM>.

With reference to <FIG>, a portable storage device assembly <NUM> that supports modular configurations including portable storage device <NUM> (of <FIG>) is shown, in accordance with various embodiments. Portable storage device assembly <NUM> comprises an external housing <NUM> that retains various components and protects the components from environmental hazards.

In various embodiments, components retained within external housing <NUM> include portable storage device <NUM> and/or power supply <NUM>. Portable storage device <NUM> and/or power supply <NUM> are removably coupled to external housing <NUM>. Power supply <NUM> may comprise a battery and/or a wireless power receiver suitable for powering portable storage device <NUM> and/or providing supplemental power to external devices via port <NUM>. Cap <NUM> of external housing may be pivotally coupled to external housing <NUM> by a pivot joint <NUM> comprising a pin in a circular sleeve, for example.

In various embodiments, external housing <NUM> has a rectangular cuboid or rhomboid geometry larger than that of a portable storage device <NUM> to be retained within the external housing. External housing <NUM> may comprise a height H<NUM>, a width W<NUM>, and a length L<NUM>. Height H<NUM> may be substantially <NUM> inch, for example. Width W<NUM> may be substantially <NUM> inches, for example. Length L<NUM> may be substantially <NUM> inches, for example.

In various embodiments, external housing may include an interface button <NUM> and/or lighting <NUM> in surface <NUM> to facilitate communication with internals. Surface <NUM>, surface <NUM>, and/or cap <NUM> may be finished with a variety of materials such as, for example, plastics, rubbers, synthetic materials, natural materials, or other suitable materials. For example, surface <NUM> may comprise a smooth plastic with translucent and/or transparent portions to allow light to pass through surface <NUM>. External housing may also define internal cavity <NUM> suitable for retaining portable storage device <NUM> and/or internal cavity <NUM> suitable for retaining a power supply <NUM>. A divider <NUM> may separate internal cavity <NUM> from internal cavity <NUM> in various embodiments.

Referring now to <FIG>, an internal assembly <NUM> is shown for electronic communication of power and/or data between power supply <NUM> and portable storage device <NUM> through PCB <NUM>. Internal assembly <NUM> may be at least partially mounted, molded, bonded, glued, adhered, fastened, press fit, or otherwise mechanically coupled to external housing <NUM> to form portable storage device assembly <NUM> (of <FIG>). Internal assembly <NUM> thus has dimensions suitable for retention within external housing <NUM>.

In various embodiments, power supply <NUM>, data port <NUM>, and PCB <NUM> of internal assembly <NUM> may have a combined length L<NUM>, while power supply <NUM> alone may have a shorter length L<NUM>. Length L<NUM> may be substantially <NUM> inches, for example. Length L<NUM> may be substantially <NUM> inches, for example. The length of PCB <NUM> and data port <NUM> may be the difference between L<NUM> and L<NUM>. Internal assembly <NUM> may also have a width W<NUM>, while PCB <NUM>, connector <NUM>, data adapter <NUM>, and conductive leads <NUM> stand off from portable storage device <NUM> by a width W<NUM>. Width W<NUM> may be, for example, substantially <NUM> inches. Width W<NUM> may be, for example, substantially <NUM> inches.

In various embodiments, data adapter <NUM> may engage, mate with, and/or form an electrical connection with data port <NUM> (of <FIG>). Conductive leads <NUM> may engage, mate with, and/or form an electronic connection with conductive pads <NUM> (of <FIG>). The electronic connections enable electronic communication between portable storage device <NUM> and PCB <NUM>. PCB <NUM> may communicate electronic signals between other physically connected devices such as, for example, a power supply <NUM> in the form of a battery or another external device in electronic communication with data port <NUM>.

Referring now to <FIG>, a case <NUM> for a mobile computing device is shown as a portable storage assembly <NUM>, in accordance with various embodiments. Case <NUM> may fit on a portable computing device such as, for example, a tablet, smartphone, smart watch, laptop, or other suitable computing device. Case <NUM> may have an interior contour matching that of a computing device to retain the computing device. Case <NUM> may define cavity <NUM> with a shape suitable to receive and retain with portable storage device <NUM>. In that regard, portable storage device <NUM> may be removably coupled to case <NUM>, and cavity <NUM> may have a geometry mirroring <NUM> sides of the portable storage device with an opening shaped like a surface of the portable storage device. The cavity may thus be defined by five orthogonal surfaces. The portable storage device may lie with a surface flush with the interior of case <NUM>.

In various embodiments, case <NUM> may include interface <NUM> suitable for communication with data port <NUM> or conductive pads <NUM> (of <FIG>). Interface <NUM> may by electronically coupled to a data plug <NUM> by an electrical conduit <NUM> such as a wire. Data plug <NUM> may interface with a corresponding data port on a computing device retained within case <NUM>. Data plug <NUM> may thus plug into the bottom port on a smartphone to electrically couple case <NUM> to the smartphone, for example. Case <NUM> may further include a protrusion <NUM> configured to house the PCBs and power supplies described herein as well as the cavity <NUM>.

In various embodiments, case <NUM> may enable physical electronic communication between portable storage device <NUM>, a power supply (e.g., power supply <NUM>), a PCB (e.g., PCB <NUM>), or other electronic devices retained within case <NUM>. Case <NUM> may further enable electronic communication of power and/or data to and/or from the mobile device retained within case <NUM>. Portable storage device <NUM> may also be in wireless communication with the mobile device retained within case <NUM> as described herein.

Referring briefly to <FIG>, a modular portable storage system <NUM> is shown, in accordance with various embodiments. Modular portable storage system <NUM> may include case <NUM>, portable storage device <NUM>, battery <NUM>, and/or external housing <NUM>. The various components described herein may be removable and interchangeably coupled to one another electronically and mechanically. In that regard, portable storage device <NUM> may be utilized in various configurations to augment functionality of computing devices in communication with portable storage device <NUM>.

In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.

For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein.

The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the system. As those skilled in the art will appreciate, user computers may include an operating system (e.g., Windows NT, Windows <NUM>/<NUM>/<NUM>, Windows XP, Windows Vista, Windows <NUM>, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers.

A network may include any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant), smart device (e.g., iPhone®, Palm Pilot®, Blackberry®, cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, Appletalk, IP-<NUM>, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network is in the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS AND PROTOCOLS (<NUM>); JAVA <NUM> COMPLETE, various authors, (Sybex <NUM>); DEBORAH RAY AND ERIC RAY, MASTERING HTML <NUM> (<NUM>); and LOSHIN, TCP/IP CLEARLY EXPLAINED (<NUM>) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THE DEFINITIVE GUIDE (<NUM>), the contents of which are hereby incorporated by reference.

The various system components may be independently, separately or collectively suitably coupled to the network via data links which includes, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods, see, e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (<NUM>), which is hereby incorporated by reference. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.

Any communication, transmission and/or channel discussed herein may include any system or method for delivering content (e.g. data, information, metadata, etc.), and/or the content itself. The content may be presented in any form or medium, and in various embodiments, the content may be delivered electronically and/or capable of being presented electronically. For example, a channel may comprise a website, a uniform resource locator ("URL"), a document (e.g., a Microsoft Word document, a Microsoft Excel document, an Adobe. pdf document, etc.), an "ebook," an "emagazine," an application or microapplication (as described below), an SMS or other type of text message, an email, Facebook, twitter, MMS and/or other type of communication technology. In various embodiments, a channel may be hosted or provided by a data partner. In various embodiments, the distribution channel may comprise at least one of a merchant website, a social media website, affiliate or partner websites, an external vendor, a mobile device communication, social media network and/or location based service. Distribution channels may include at least one of a merchant website, a social media site, affiliate or partner websites, an external vendor, and a mobile device communication. Examples of social media sites include Facebook®, foursquare®, Twitter®, MySpace®, LinkedIn®, and the like. Moreover, examples of mobile device communications include texting, email, and mobile applications for smartphones.

The present system or any part(s) or function(s) thereof may be implemented using hardware, software or a combination thereof and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed by embodiments were often referred to in terms, such as matching or selecting, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein. Rather, the operations may be machine operations. Useful machines for performing the various embodiments include general purpose digital computers or similar devices.

In fact, in various embodiments, the embodiments are directed toward one or more computer systems capable of carrying out the functionality described herein. The computer system includes one or more processors. The processor is connected to a communication infrastructure (e.g., a communications bus, cross over bar, or network). Various software embodiments are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement various embodiments using other computer systems and/or architectures. Computer system can include a display interface that forwards graphics, text, and other data from the communication infrastructure (or from a frame buffer not shown) for display on a display unit.

Computer system also includes a main memory, such as for example random access memory (RAM), and may also include a secondary memory. The secondary memory may include, for example, a hard disk drive and/or a removable storage drive, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive reads from and/or writes to a removable storage unit in a well-known manner. Removable storage unit represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by a removable storage unit. As will be appreciated, the removable storage unit includes a computer usable storage medium having stored therein computer software and/or data.

In various embodiments, secondary memory may include other similar devices for allowing computer programs or other instructions to be loaded into computer system. Such devices may include, for example, a removable storage unit and an interface. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read-only memory (EPROM), or programmable read-only memory (PROM)) and associated socket, and other removable storage units and interfaces, which allow software and data to be transferred from the removable storage unit to computer system.

Computer system may also include a communications interface. Communications interface allows software and data to be transferred between computer system and external devices. Examples of communications interface may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface are in the form of signals which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface. These signals are provided to communications interface via a communications path (e.g., channel). This channel carries signals and may be implemented using wire, cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, wireless, and other communications channels.

The terms "computer program medium" and "computer usable medium" are used to generally refer to media such as a removable storage drive and a hard disk installed in a hard disk drive. These computer program products provide software to computer system.

Computer programs (also referred to as computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via a communications interface. Such computer programs, when executed, enable the computer system to perform the features as discussed herein. In particular, the computer programs, when executed, enable the processor to perform the features of various embodiments. Accordingly, such computer programs represent controllers of the computer system.

In various embodiments, software may be stored in a computer program product and loaded into computer system using removable storage drive, hard disk drive or communications interface. The control logic (software), when executed by the processor, causes the processor to perform the functions of various embodiments as described herein. In various embodiments, hardware components such as application specific integrated circuits (ASICs) are present. Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).

In various embodiments, the server may include application servers (e.g. WEB SPHERE, WEB LOGIC, JBOSS). In various embodiments, the server may include web servers (e.g. APACHE, IIS, GWS, SUN JAVA SYSTEM WEB SERVER).

As those skilled in the art will appreciate, a device may include but is not limited to an operating system (e.g., Windows NT, <NUM>/<NUM>/<NUM>/CE/Mobile, OS2, UNIX, Linux, Solaris, MacOS, PalmOS, etc.) as well as various conventional support software and drivers typically associated with computers. A device may include but is not limited to any suitable personal computer, network computer, workstation, personal digital assistant, cellular phone, smart phone, minicomputer, mainframe or the like. A device can be in a home or business environment with access to a network. In various embodiments, access is through a network or the Internet through a commercially available web-browser software package. A device may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). A device may implement several application layer protocols including http, https, ftp, and sftp.

In various embodiments, components, modules, and/or engines of system <NUM> may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a Palm mobile operating system, a Windows mobile operating system, an Android Operating System, Apple iOS, a Blackberry operating system and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.

"Cloud" or "Cloud computing" includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include locationindependent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing at http://csrc. gov/groups/SNS/cloud-computing/cloud-def-v15. doc (last visited February <NUM>, <NUM>), which is hereby incorporated by reference in its entirety.

As used herein, "transmit" may include sending electronic data from one system component to another. Additionally, as used herein, "data" may include encompassing information such as commands, queries, files, data for storage, and the like in digital or any other form.

The system contemplates uses in association with web services, utility computing, pervasive and individualized computing, security and identity solutions, autonomic computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing and/or mesh computing.

Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (Armonk, NY), various database products available from Oracle Corporation (Redwood Shores, CA), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Washington), MySQL by MySQL AB (Uppsala, Sweden), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a "key field" in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out ("I/O") bottlenecks.

One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.

Encryption may be performed by way of any of the techniques now available in the art or which may become available-e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), and symmetric and asymmetric cryptosystems.

The computing unit of the device may be further equipped with an Internet browser connected to the Internet or an intranet using standard dial-up, cable, DSL or any other Internet protocol known in the art. Transactions originating at a device may pass through a firewall in order to prevent unauthorized access from users of other networks. Further, additional firewalls may be deployed between the varying components of the system to further enhance security.

The computers discussed herein may provide a suitable website or other Internet-based graphical user interface which is accessible by users. In various embodiments, the Microsoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), and Microsoft SQL Server, are used in conjunction with the Microsoft operating system, Microsoft NT web server software, a Microsoft SQL Server database system, and a Microsoft Commerce Server. Additionally, components such as Access or Microsoft SQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In various embodiments, the Apache web server is used in conjunction with a Linux operating system, a MySQL database, and the Perl, PHP, and/or Python programming languages.

Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term "web page" as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, Java applets, JavaScript, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous Javascript And XML), helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL (http://yahoo. com/stockquotes/ge) and an IP address (<NUM>. The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communications means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art, and are covered in many standard texts. See, e.g., ALEX NGHIEM, IT WEB SERVICES: A ROADMAP FOR THE ENTERPRISE (<NUM>), hereby incorporated by reference.

Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WebSphere MQTM (formerly MQSeries) by IBM, Inc. (Armonk, NY) is an example of a commercially available middleware product. An Enterprise Service Bus ("ESB") application is another example of middleware.

Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.

The system and method may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, Java, JavaScript, VBScript, Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly, PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (<NUM>) "Applied Cryptography: Protocols, Algorithms, And Source Code In C," by Bruce Schneier, published by John Wiley & Sons (second edition, <NUM>); (<NUM>) "Java Cryptography" by Jonathan Knudson, published by O'Reilly & Associates (<NUM>); (<NUM>) "Cryptography & Network Security: Principles & Practice" by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.

As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, a processing apparatus executing upgraded software, a stand alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, any portion of the system or a module may take the form of a processing apparatus executing code, an internet based embodiment, an entirely hardware embodiment, or an embodiment combining aspects of the internet, software and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.

The system and method is described herein with reference to screen shots, block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various embodiments. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of windows, webpages, web forms, popup windows, prompts and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or windows but have been combined for simplicity.

The term "non-transitory" is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se.

Claim 1:
A modular portable storage system (<NUM>), comprising:
a portable storage device (<NUM>) comprising a housing (<NUM>) having a cuboid geometry, the housing (<NUM>) retaining a processor (<NUM>), a storage module (<NUM>) in electronic communication with the processor (<NUM>), and a wireless communication module (<NUM>);
a circuit board (<NUM>) in electronic communication with the portable storage device (<NUM>), wherein the portable storage device (<NUM>) is removably coupled to the circuit board (<NUM>);
a power supply (<NUM>) in electronic communication with the circuit board (<NUM>), wherein the power supply (<NUM>) is removably coupled to the circuit board (<NUM>); and
an external housing (<NUM>) with the portable storage device (<NUM>) and the power supply (<NUM>) removably retained within the external housing (<NUM>), wherein the circuit board (<NUM>) is mechanically coupled to the external housing (<NUM>).