Patent Description:
Certain files/documents may need to be sent securely so that they files/documents are not seen in the open, are not intercepted, and/or cannot be misappropriated by users who are not authorized to view the files/documents.

<CIT> relates to data processing and transmission, and describes a method where an original data object is segmented, and reordered into discrete and separate encrypted data objects, none of which contain a complete representation of the original data object, and whereby these discrete data objects are transmitted via separate means so as to limit acquisition and decryption of the original data object.

<CIT> describes managing data by dividing the data into a first file and a second file, storing the first file in the memory, and transmitting the second file to an external electronic device for storing.

Claim <NUM> defines an apparatus and claim <NUM> defines a method. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

Apparatuses, methods, systems, and program products are disclosed for secure file distribution. An apparatus, in one embodiment, includes a processor and a memory that stores code executable by the processor. In certain embodiments, the code is executable by the processor to divide a file that is intended for a recipient into a plurality of portions. In one embodiment, the code is executable by the processor to associate each of the plurality of portions with a different one of the recipient's electronic devices. In some embodiments, the code is executable by the processor to assemble the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file.

A method for secure file distribution, in one embodiment, includes dividing, by a processor, a file that is intended for a recipient into a plurality of portions. The method, in further embodiments, includes associating each of the plurality of portions with a different one of the recipient's electronic devices. In certain embodiments, the method includes assembling the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file.

A computer program product for secure file distribution, in one embodiment, includes a computer readable storage medium having program instructions embodied therewith. In certain embodiments, the program instructions are executable by a processor to cause the processor to divide a file that is intended for a recipient into a plurality of portions. In some embodiments, the program instructions are executable by a processor to cause the processor to associate each of the plurality of portions with a different one of the recipient's electronic devices. In further embodiments, the program instructions are executable by a processor to cause the processor to assemble the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file.

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, method or program product.

Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.

An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Code for carrying out operations for embodiments may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.

This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the code for implementing the specified logical function(s).

An apparatus, in one embodiment, includes a processor and a memory that stores code executable by the processor. In certain embodiments, the code is executable by the processor to divide a file that is intended for a recipient into a plurality of portions. In one embodiment, the code is executable by the processor to associate each of the plurality of portions with a different one of the recipient's electronic devices. In some embodiments, the code is executable by the processor to assemble the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file.

In one embodiment, the code is executable by the processor to authenticate the recipient on the recipient's electronic device that is used to view the assembled file prior to providing access to the assembled file. In certain embodiments, the code is executable by the processor to verify that the recipient successfully authenticated at each of the recipient's electronic devices that are associated with each portion of the plurality of portions prior to assembling the plurality of portions of the file for the recipient.

In one embodiment, the code is executable by the processor to delete the assembled file after a period of time, which is triggered in response to the recipient first viewing the file. In certain embodiments, the code is executable by the processor to delete a portion of the plurality of portions of the file in response to the portion being accessed to assemble the file. In some embodiments, the code is executable by the processor to determine a predefined order for accessing the plurality of portions for assembling the file such that one portion of the plurality of portions is not accessible until a previous portion of the plurality of portions in the predefined order has been accessed.

In one embodiment, the code is executable by the processor to begin a timer for expiring one or more portions of the plurality of portions in response to one portion of the plurality of portions being accessed for assembling the file. In certain embodiments, the code is executable by the processor to randomly select the recipient's electronic devices that are associated with the plurality of portions and randomly associate each of the plurality of portions with the different one of the randomly selected recipient's electronic devices.

In one embodiment, the code is executable by the processor to authenticate the recipient on each of the recipient's electronic devices in response to the recipient using credentials to one or more of unlock the electronic device and log into an application on the electronic device that verifies the recipient's identity. In various embodiments, the code is executable by the processor to assemble and make available the file on one of the recipient's electronic devices that is not associated with a portion of the plurality of portions of the file.

In one embodiment, the code is executable by the processor to store the assembled file in volatile memory of one of the recipient's electronic devices that used to view the file. In some embodiments, the code is executable by the processor to store the plurality of portions on one or more of a device that is remote to the recipient's electronic devices and on the recipient's electronic devices that are associated with the portions.

In one embodiment, the recipient's electronic device that is used to view the assembled file comprises a head-mounted display executing a mixed reality environment comprising one or more of a virtual reality environment and an augmented reality environment. In some embodiments, the code is executable by the processor to authenticate the recipient wearing the head-mounted display using biometric information captured from the recipient's eyes.

In one embodiment, the method includes authenticating the recipient on the recipient's electronic device that is used to view the assembled file prior to providing access to the assembled file. In some embodiments, the method includes verifying that the recipient successfully authenticated at each of the recipient's electronic devices that are associated with each portion of the plurality of portions prior to assembling the plurality of portions of the file for the recipient.

In one embodiment, the method includes deleting the assembled file after a period of time, which is triggered in response to the recipient first viewing the file. In some embodiments, the method includes deleting a portion of the plurality of portions of the file in response to the portion being accessed to assemble the file.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for secure file distribution. In one embodiment, the system <NUM> includes one or more information handling devices <NUM>, one or more file management apparatuses <NUM>, one or more data networks <NUM>, and one or more servers <NUM>. In certain embodiments, even though a specific number of information handling devices <NUM>, file management apparatuses <NUM>, data networks <NUM>, and servers <NUM> are depicted in <FIG>, one of skill in the art will recognize, in light of this disclosure, that any number of information handling devices <NUM>, file management apparatuses <NUM>, data networks <NUM>, and servers <NUM> may be included in the system <NUM>.

In one embodiment, the system <NUM> includes one or more information handling devices <NUM>. The information handling devices <NUM> may be embodied as one or more of a desktop computer, a laptop computer, a tablet computer, a smart phone, a smart speaker (e.g., Amazon Echo®, Google Home®, Apple HomePod®), an Internet of Things device, a security system, a set-top box, a gaming console, a smart TV, a smart watch, a fitness band or other wearable activity tracking device, an optical head-mounted display (e.g., a virtual reality headset, smart glasses, or the like), a High-Definition Multimedia Interface ("HDMI") or other electronic display dongle, a personal digital assistant, a digital camera, a video camera, or another computing device comprising a processor (e.g., a central processing unit ("CPU"), a processor core, a field programmable gate array ("FPGA") or other programmable logic, an application specific integrated circuit ("ASIC"), a controller, a microcontroller, and/or another semiconductor integrated circuit device), a volatile memory, and/or a non-volatile storage medium, a display, a connection to a display, and/or the like.

In one embodiment, the file management apparatus <NUM> is configured to securely distribute or send a file by a file that is intended for a recipient into a plurality of portions, associating each of the plurality of portions with a different one of the recipient's electronic devices, and assembling the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file. The file management apparatus <NUM>, including its various sub-modules, may be located on one or more information handling devices <NUM> in the system <NUM>, one or more servers <NUM>, one or more network devices, and/or the like. The file management apparatus <NUM> is described in more detail below with reference to <FIG> and <FIG>.

In various embodiments, the file management apparatus <NUM> may be embodied as part of an information handling device <NUM> such as a smart device, a network device, an Internet of Things device, a computing device, or as a hardware appliance that can be installed or deployed on an information handling device <NUM>, on a server <NUM>, on a user's mobile device, on a display, or elsewhere on the data network <NUM>. In certain embodiments, the file management apparatus <NUM> may include a hardware device such as a secure hardware dongle or other hardware appliance device (e.g., a set-top box, a network appliance, or the like) that attaches to a device such as a laptop computer, a server <NUM>, a tablet computer, a smart phone, a security system, a network router or switch, or the like, either by a wired connection (e.g., a universal serial bus ("USB") connection) or a wireless connection (e.g., Bluetooth®, Wi-Fi, near-field communication ("NFC"), or the like); that attaches to an electronic display device (e.g., a television or monitor using an HDMI port, a DisplayPort port, a Mini DisplayPort port, VGA port, DVI port, or the like); and/or the like. A hardware appliance of the file management apparatus <NUM> may include a power interface, a wired and/or wireless network interface, a graphical interface that attaches to a display, and/or a semiconductor integrated circuit device as described below, configured to perform the functions described herein with regard to the file management apparatus <NUM>.

The file management apparatus <NUM>, in such an embodiment, may include a semiconductor integrated circuit device (e.g., one or more chips, die, or other discrete logic hardware), or the like, such as a field-programmable gate array ("FPGA") or other programmable logic, firmware for an FPGA or other programmable logic, microcode for execution on a microcontroller, an application-specific integrated circuit ("ASIC"), a processor, a processor core, or the like. In one embodiment, the file management apparatus <NUM> may be mounted on a printed circuit board with one or more electrical lines or connections (e.g., to volatile memory, a non-volatile storage medium, a network interface, a peripheral device, a graphical/display interface, or the like). The hardware appliance may include one or more pins, pads, or other electrical connections configured to send and receive data (e.g., in communication with one or more electrical lines of a printed circuit board or the like), and one or more hardware circuits and/or other electrical circuits configured to perform various functions of the file management apparatus <NUM>.

The semiconductor integrated circuit device or other hardware appliance of the file management apparatus <NUM>, in certain embodiments, includes and/or is communicatively coupled to one or more volatile memory media, which may include but is not limited to random access memory ("RAM"), dynamic RAM ("DRAM"), cache, or the like. In one embodiment, the semiconductor integrated circuit device or other hardware appliance of the file management apparatus <NUM> includes and/or is communicatively coupled to one or more non-volatile memory media, which may include but is not limited to: NAND flash memory, NOR flash memory, nano random access memory (nano RAM or "NRAM"), nanocrystal wire-based memory, silicon-oxide based sub-<NUM> nanometer process memory, graphene memory, Silicon-Oxide-Nitride-Oxide-Silicon ("SONOS"), resistive RAM ("RRAM"), programmable metallization cell ("PMC"), conductive-bridging RAM ("CBRAM"), magneto-resistive RAM ("MRAM"), dynamic RAM ("DRAM"), phase change RAM ("PRAM" or "PCM"), magnetic storage media (e.g., hard disk, tape), optical storage media, or the like.

The data network <NUM>, in one embodiment, includes a digital communication network that transmits digital communications. The data network <NUM> may include a wireless network, such as a wireless cellular network, a local wireless network, such as a Wi-Fi network, a Bluetooth® network, a near-field communication ("NFC") network, an ad hoc network, and/or the like. The data network <NUM> may include a wide area network ("WAN"), a storage area network ("SAN"), a local area network ("LAN") (e.g., a home network), an optical fiber network, the internet, or other digital communication network. The data network <NUM> may include two or more networks. The data network <NUM> may include one or more servers, routers, switches, and/or other networking equipment. The data network <NUM> may also include one or more computer readable storage media, such as a hard disk drive, an optical drive, non-volatile memory, RAM, or the like.

The wireless connection may be a mobile telephone network. The wireless connection may also employ a Wi-Fi network based on any one of the Institute of Electrical and Electronics Engineers ("IEEE") <NUM> standards. Alternatively, the wireless connection may be a Bluetooth® connection. In addition, the wireless connection may employ a Radio Frequency Identification ("RFID") communication including RFID standards established by the International Organization for Standardization ("ISO"), the International Electrotechnical Commission ("IEC"), the American Society for Testing and Materials® (ASTM®), the DASH7™ Alliance, and EPCGlobal™.

Alternatively, the wireless connection may employ a ZigBee® connection based on the IEEE <NUM> standard. In one embodiment, the wireless connection employs a Z-Wave® connection as designed by Sigma Designs®. Alternatively, the wireless connection may employ an ANT® and/or ANT+® connection as defined by Dynastream® Innovations Inc. of Cochrane, Canada.

The wireless connection may be an infrared connection including connections conforming at least to the Infrared Physical Layer Specification ("IrPHY") as defined by the Infrared Data Association® ("IrDA"®). Alternatively, the wireless connection may be a cellular telephone network communication. All standards and/or connection types include the latest version and revision of the standard and/or connection type as of the filing date of this application.

The one or more servers <NUM>, in one embodiment, may be embodied as blade servers, mainframe servers, tower servers, rack servers, and/or the like. The one or more servers <NUM> may be configured as mail servers, web servers, application servers, FTP servers, media servers, data servers, web servers, file servers, virtual servers, and/or the like. The one or more servers <NUM> may be communicatively coupled (e.g., networked) over a data network <NUM> to one or more information handling devices <NUM> and may host, store, stream, or the like files and content to a different device such as documents, videos, music, podcasts, images, games, web pages, augmented and/or virtual reality environments, and/or the like.

<FIG> is a schematic block diagram illustrating one embodiment of an apparatus <NUM> for secure file distribution. In one embodiment, the apparatus <NUM> includes an instance of a file management apparatus <NUM>. In one embodiment, the file management apparatus <NUM> includes one or more of a file dividing module <NUM>, an association module <NUM>, and an assembly module <NUM>, which are described in more detail below.

In one embodiment, the file dividing module <NUM> is configured to divide a file that is intended for a recipient into a plurality of portions. The file, in one embodiment, may be a document, an image, a PDF file, a music file, a video file, a web page, and/or other digital files. The file may be uploaded to a storage location where it can be downloaded or accessed by other recipients. The file may be sent as an attachment to an electronic message sent to a recipient such as an email, instant message, social media message, push notification, text message, and/or the like. In such an embodiment, the file dividing module <NUM> may intercept or process the file prior to the electronic message being sent to the recipient.

As described in more detail below, instead of sending the complete original file to the recipient as a single file (or allowing a recipient to download the complete original file as a single file), the portions of the file are sent to different devices that belong to the recipient so that the complete file is not sent as a single file. The recipient then needs to access each of his/her devices to access the portions of the file so that the file can be reassembled from the portions. In this manner, a file can be sent securely over a data network because even if one portion is intercepted or misappropriated, the complete file cannot be viewed without having access to the other portions of the file.

The file dividing module <NUM> may divide the file into a plurality of different portions, segments, parts, and/or the like. For example, the file dividing module <NUM> may divide the file into different portions using a bitwise pattern (e.g., every other bit or every two bits, or the like); using a word pattern for a text file (e.g., every other word or every two words, or the like); using a pixel pattern for an image file (e.g., every other pixel or every two pixels, or the like); and/or the like. The file dividing module <NUM>, in certain embodiments, uses a completely random pattern for dividing the file.

The file dividing module <NUM>, in one embodiment, makes copies of the data that is divided from the original file so that the original file is not impacted by the division of the file. In other words, the original file maintains its original state and the data of the original file is divided and copied into different portions of data. The portions may comprise information or metadata for re-assembling the portions to arrive at the original file. The metadata may include an order for re-assembling the portions, a position in the file (e.g., a position in a bitmap for the file, a position for a pixel, a position of a word/sentence in the file, and/or the like), which is used to re-assemble the file from the plurality of portions.

In one embodiment, the association module <NUM> is configured to associate each of the plurality of portions of the file with a different one of the recipient's electronic devices. For example, the recipient may have a smart phone, a tablet computer, a desktop computer, a laptop computer, and a smart watch and the association module <NUM> may assign each of the plurality of portions to each of the recipient's devices. The association module <NUM> may assign or associate a portion of the file with a device by sending the portion to the device to be stored in a secure location on the device, or to be stored in an encrypted format, until the portion is accessed. In such an embodiment, the association module <NUM> may encrypt the portions prior to being sent to the devices. In certain embodiments, the portions may be stored and/or sent using different security measures, methods, and/or the like (e.g., using a different encryption scheme for each portion of the file).

In certain embodiments, the recipient registers or otherwise lists devices that he/she wants to use as devices to be associated with a portion of the file. In such an embodiment, the association module <NUM> may audit each of the registered devices to determine specifications of each device such as the authentication methods of each device, the applications available on the devices, how often the devices are used/accessed, and/or the like. The association module <NUM> may reference or check the recipient's registered devices to determine how many devices the recipient has registered, which devices the user has registered, a priority order for selecting the recipient's devices for storing portions of the file, and/or the like.

In one embodiment, the association module <NUM> randomly selects the recipient's electronic devices that are associated with the plurality of portions and randomly associates each of the plurality of portions with a different one of the randomly selected recipient's electronic devices. For instance, the association module <NUM> may randomly select devices from the list of the recipient's registered devices that can each store or access a portion of the file. In certain embodiment, the recipient devices are selected based on the authentication methods of the devices, e.g., one may require a username/password combination, one may require biometric information, and/or the like, so that different authentication methods are required to view the file. In such an embodiment, the desired authentication methods may be selected based on a sensitivity level of the file, e.g., more restrictive authentication methods may be preferred for "confidential" files.

In some embodiments, the association module <NUM> stores the plurality of portions separately at one or multiple secure, remote locations that are external to the recipient's devices. In such an embodiment, each portion is logically associated with a recipient's device and can only be accessed using the associated recipient's device. For example, each portion may be encrypted or otherwise securely stored, e.g., using an identifier for a recipient's device that is associated with the portion, such that the portion is only made available to the recipient's devices that are associated with or assigned to the portion, instead of storing the portions directly on the recipient devices.

In certain embodiments, the portions are stored directly on the recipient's devices in a secure location, e.g., in a trusted platform module portion of the device's storage, on an encrypted drive, in an encrypted folder, and/or the like, and may be stored in an encrypted form. In this manner, the recipient may need to login or otherwise provide credentials to authenticate with the device that the recipient is the real or actual owner/user of the device prior to the portion being accessible.

In one embodiment, the file dividing module <NUM> determines the number of portions of the file to generate based on the number of the recipient's devices that will be associated with the portions. For instance, the file dividing module <NUM> may query the association module <NUM> to determine how many of the recipient's devices will be associated with the portions of the file based on the recipient and the number of devices the recipient has registered to be associated with portions of the files prior to dividing the file into its various portions.

In one embodiment, the assembly module <NUM> is configured to assemble the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file. For example, if the file dividing module <NUM> divided the file into two different portions, and the association module <NUM> associated the first portion with the recipient's smart phone and the second portion with the recipient's smart watch, the assembly module <NUM> may access the first portion from the recipient's smart phone and the second portion from the recipient's smart watch in response to the recipient authenticating or logging into the smart phone and smart watch (e.g., the portions may be received via a wireless connection such as Wi-Fi, Bluetooth®, NFC, and/or the like).

In one embodiment, the assembly module <NUM> assembles and makes available the file on one of the recipient's electronic devices that is not associated with a portion of the plurality of portions of the file. For example, instead of making the assembled file available on the recipient's smart phone and smart watch that were associated with the portions of the file, the assembly module <NUM> may make the file available on the recipient's laptop or desktop computer, a smart television, a tablet computer, and/or the like, which the recipient may designate beforehand.

In one embodiment, the assembly module <NUM> checks the metadata for each of the portions to determine a predefined order for accessing the plurality of portions for assembling the file. For instance, the metadata may specify that the portion that is associated with the recipient's smart phone should be accessed before the portion associated with the recipient's smart watch. In certain embodiments, one portion of the plurality of portions is not accessible until a previous portion of the plurality of portions in the predefined order has been accessed. Thus, in the previous example, the portion that is associated with the recipient's smart watch may not be accessible until the portion that is associated with the recipient's smart phone has been accessed. Accordingly, in such an embodiment, when a portion is accessed in order, the assembly module <NUM> sets or sends a flag, bit, or the like to indicate that the portion has been accessed, which then unlocks the following portion for access.

In one embodiment, the assembly module <NUM> assembles the file on a recipient's device and stores the assembled file in volatile memory while the recipient views the file so that the assembled file is not persistently stored on the recipient's device. In some embodiments, the assembly module <NUM> may store the assembled file in an encrypted format and/or in a secure storage area of the recipient's device such as on an encrypted storage drive or volume.

In various embodiments, the recipient's electronic device that is used to view the assembled file comprises a head-mounted display executing a mixed reality environment comprising one or more of a virtual reality environment and an augmented reality environment. In such an embodiment, the assembly module <NUM> may present the assembled file as a three-dimensional object, or other graphical object, within the virtual reality and/or augmented reality environment and may present animations to visually illustrate assembly of the file from the various different portions.

In certain embodiments, the assembly module <NUM> assembles the file from the portions of the file and stores the file without allowing the recipient to screenshot the file, make a copy of the file, change the storage location of the file, forward a copy of the file, permanently save the file, and/or the like. In such an embodiment, the assembly module <NUM> may provide a simple file viewer for viewing the file without providing additional features, functions, or the like for manipulating the file. In one embodiment, the assembly module <NUM> notifies the sender that the recipient viewed/accessed the assembled file.

<FIG> is a schematic block diagram illustrating one embodiment of another apparatus <NUM> for secure file distribution. In one embodiment, the apparatus <NUM> includes an instance of a file management apparatus <NUM>. The file management apparatus <NUM>, in certain embodiments, includes a file dividing module <NUM>, an association module <NUM>, and an assembly module <NUM>, which may be substantially similar to the file dividing module <NUM>, the association module <NUM>, and the assembly module <NUM> described above with reference to <FIG>. The file management apparatus <NUM>, in further embodiments, includes one or more of an authentication module <NUM> and a deletion module <NUM>, which are described in more detail below.

The authentication module <NUM>, in one embodiment, is configured to authenticate the recipient on the recipient's electronic device that is used to view the assembled file prior to providing access to the assembled file. The authentication module <NUM> may receive confirmation that the recipient successfully logged into the device, may receive credentials (e.g., username/password, biometric data (e.g., retina scan, fingerprint reader, pulse reading, etc.), and/or the like) for authenticating the user, and/or the like.

In further embodiments, the authentication module <NUM> verifies that the recipient successfully authenticated at each of the recipient's electronic devices that are associated with each portion of the plurality of portions prior to assembling the plurality of portions of the file for the recipient. The recipient may be authenticated in response to the recipient using credentials to unlock the electronic device, log into an application on the electronic device that verifies the recipient's identity, log into an application for viewing the file, and/or the like. The authentication module <NUM>, for example, may receive a confirmation message when the recipient has logged into each of the devices that are associated with a portion of the file, may check a flag that is set when a recipient logs into a device associated with a portion of the file, and/or the like. In certain embodiments, the authentication module <NUM> may verify that the recipient is simultaneously logged into each of the devices that have associated portions of the file while viewing the assembled file.

In an embodiment where the viewing device is a head-mounted display, the authentication module <NUM> authenticates the recipient who is wearing the head-mounted display using biometric information that is captured using various sensors on the head-mounted display. For instance, the authentication module <NUM> may authenticate the user based on eye/retina information, facial structure/recognition/feature information, breath/odor information, and/or the like.

In one embodiment, the deletion module <NUM> is configured to delete the assembled file after a period of time. For example, the deletion module <NUM> may remove, delete, mark for deletion, mark as deleted, overwritten, removed from volatile storage, and/or the like the assembled file after a week, a day, an hour, thirty minutes, thirty seconds, and/or the like. The amount of time may be configurable by the user who sends or makes the file available to the recipient. In one embodiment, the period of time that the timer is set for is triggered or activated in response to the recipient first viewing the assembled file.

In one embodiment, the deletion module <NUM> is configured to delete a portion of the plurality of portions of the file in response to the portion being accessed to assemble the file. For example, when a portion is accessed from the user's smart phone, or from a remote location that is associated with the user's smart phone, the portion is deleted, removed, marked for deletion, marked as deleted, overwritten, and/or the like so that it is no longer accessible.

In one embodiment, the deletion module <NUM> begins a timer for expiring one or more portions of the plurality of portions in response to one portion of the plurality of portions being accessed for assembling the file. For instance, when a portion is accessed for assembling the single file, a timer may begin that indicates how much time the recipient has to access the other portions of the file to assemble the complete file before the portions expire and are deleted. In other words, once a portion is accessed on its associated device, the recipient has a certain amount of time to access the remaining portions on the other devices before the deletion module <NUM> deletes those portions.

<FIG> depicts an example of a system <NUM> for secure file distribution. In one embodiment, the system <NUM> includes an original document <NUM>, e.g., a resume, a financial spreadsheet, a confidential slideshow presentation, and/or the like. A user may send the original document <NUM> to an intended recipient. The file management apparatus <NUM> may process the document <NUM> prior to it being delivered to the recipient.

In particular, the file dividing module <NUM> may divide the file into multiple different portions 404a-404b (collectively <NUM>). The association module <NUM> may associate each portion <NUM> with the recipient's devices 406a-406b (collectively <NUM>). As explained above, the association module <NUM> may send and store each of the portions <NUM> on their respective associated devices <NUM> or may logically associate the portions <NUM> with devices <NUM> while storing the portions in a different location such as a secure remote or cloud storage location.

The assembly module <NUM> may assemble the portions <NUM> into the assembled document <NUM> on another one of the recipient's devices <NUM> in response to the recipient being authenticated at each of the recipient's devices 406a-406b that has an associated portion <NUM> of the original document. In this manner, the original document can be securely sent to a recipient in parts such that if a part is intercepted or otherwise misappropriated, the entire document is not compromised because the other portions are needed to reassemble the original document. Furthermore, by associating the portions with the recipient's devices, the portions are only available to the recipient when the recipient is authenticated at the recipient's devices, e.g., by unlocking the device, logging into an application or webpage, using an authenticator application or two-factor authentication, and/or the like.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for secure file distribution. In one embodiment, the method <NUM> begins and divides <NUM> a file that is intended for a recipient into a plurality of portions. In further embodiments, the method <NUM> associates <NUM> each of the plurality of portions with a different one of the recipient's electronic devices.

In certain embodiments, the method <NUM> assembles <NUM> the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file, and the method <NUM> ends. In one embodiment, the file dividing module <NUM>, the association module <NUM>, and the assembly module <NUM> perform the various steps of the method <NUM>.

<FIG> is a schematic flow chart diagram illustrating one embodiment of another method <NUM> for secure file distribution. In one embodiment, the method <NUM> begins and divides <NUM> a file that is intended for a recipient into a plurality of portions. In further embodiments, the method <NUM> selects <NUM> recipient devices to associate with each of the plurality of portions, e.g., randomly or in some order from a predefined list.

In various embodiments, the method <NUM> associates <NUM> each of the plurality of portions with the selected recipient devices. In some embodiments, the method <NUM> associates <NUM> each of the plurality of portions of the file with a different one of the selected recipient devices. In further embodiments, if the method <NUM> determines <NUM> that the recipient has not authenticated with each of the devices associated with a portion of the file, the method <NUM> continues to check for the user's authentication.

Otherwise, in one embodiment, the method <NUM> retrieves <NUM> each portion of the file from each of the associated recipient devices and/or from a remote/cloud location and assembles <NUM> the file using the received portions. In certain embodiments, if the method <NUM> determines <NUM> that the recipient has not authenticated with the device that is being used to view the assembled file, the method <NUM> continues to check for the recipient's authentication.

Otherwise, in one embodiment, if the recipient has authenticated with the viewing device, e.g., by unlocking the viewing device, by providing credentials to login to the device or an application executing on the device, and/or the like, the method <NUM> presents <NUM> the assembled file on the viewing device. In further embodiments, the method <NUM> deletes <NUM> the portions of the file and/or the assembled file after a period of time, and the method <NUM> ends. In one embodiment, the file dividing module <NUM>, the association module <NUM>, the assembly module <NUM>, the authentication module <NUM>, and the deletion module <NUM> perform the various steps of the method <NUM>.

Claim 1:
An apparatus (<NUM>), comprising:
a processor; and
a memory arranged to store code executable by the processor to:
divide (<NUM>) a file that is intended for a recipient into a plurality of portions;
associate (<NUM>) each of the plurality of portions with a different one of the recipient's electronic devices;
assemble (<NUM>) the plurality of portions of the file for the recipient in response to authenticating the recipient on each of the recipient's electronic devices that is associated with a portion of the plurality of portions of the file; and
verify that the recipient successfully authenticated at each of the recipient's electronic devices that are associated with each portion of the plurality of portions prior to assembling the plurality of portions of the file for the recipient.