Email-based software delivery

A method, apparatus, and program product are disclosed for dividing, by a processor, a code segment into one or more portions that together form the code segment, generating a plurality of email messages, combining one or more portions of the code segment into an email message of the plurality of email messages, and sending the plurality of email messages to a client to be reassembled on the client.

BACKGROUND

Field

The subject matter disclosed herein relates to software and more particularly relates to delivering software using email.

Description of the Related Art

In general, software may be downloaded from a server by a client over a data network. The downloaded software may include software programs and updates, such as feature updates, security updates, patches, etc. However, downloading software programs and updates over a data network can be ineffective in situations where a client does not have a consistent connection to a data network. In some circumstances, a client may be required to restart an interrupted download if the connection to the network is lost, which may be inefficient and frustrating.

BRIEF SUMMARY

An apparatus for email-based software delivery is disclosed. A method and computer program product also perform the functions of the apparatus. In one embodiment, an apparatus provides a server that includes a processor, which communicates with a client. An apparatus may also include a partition module that divides, by the processor, a code segment into one or more portions that together form the code segment. In another embodiment, an apparatus includes an email module that generates a plurality of email messages and combines one or more portions of the code segment into an email message of the plurality of email messages. In a further embodiment, an apparatus includes a communication module that sends the plurality of email messages to the client to be reassembled on the client.

In certain embodiments, the apparatus includes an action module that confirms an action related to the code segment. In some embodiments, the action is selected from the group consisting of a reassembly on the client and an execution on the client. In another embodiment, the email module combines one or more portions of the code segment into an email message by attaching the one or more portions to the email message. An apparatus, in one embodiment, further includes a sequence module that determines an order to send the plurality of email messages to the client.

In certain embodiments, the communication module sends an email message of the plurality of email messages in response to receiving an acknowledgement email message from the client. In some embodiments, the acknowledgement email message confirms reception of a sent email message. In another embodiment, an email message of the plurality of email messages includes instructions for reassembling the one or more portions of the code segment.

In a further embodiment, the communication module pauses sending email messages of the plurality of email messages in response to communication with the client being interrupted. In another embodiment, the communication module continues sending email messages of the plurality of email messages in response to communication with the client being restored.

In one embodiment, an apparatus includes an integrity module that resends one or more email messages in response to receiving an integrity email from the client. In some embodiments, the integrity email indicates that one or more portions of the code segment lacks integrity. An apparatus, in one embodiment, includes a security module that encrypts each email message of the plurality of email messages. An apparatus, in a further embodiment, includes a status module that determines the status of one or more code segments sent to a client. In certain embodiments, the status of the one or more code segments is presented to a user. In one embodiment, the code segment includes either a software update, a patch, or a software application.

In one embodiment, a method includes dividing, by a processor, a code segment into one or more portions that together form the code segment. A method, in another embodiment, includes generating a plurality of email messages and combining one or more portions of the code segment into an email message of the plurality of email messages. In certain embodiments, a method includes sending the plurality of email messages to a client to be reassembled on the client.

A method, in another embodiment, includes confirming an action related to the code segment wherein the action is selected from the group consisting of a reassembly on the client and an execution on the client. In one embodiment, combining one or more portions of the code segment into an email message comprises attaching the one or more portions to the email message. In some embodiments, a method includes determining an order to send the plurality of email messages to the client. A method, in a further embodiment, includes sending an email message of the plurality of email messages in response to receiving an acknowledgement email message from the client. In some embodiments, the acknowledgement email message confirms reception of a sent email message.

A method, in one embodiment, includes resending one or more email messages in response to receiving an integrity email from the client. In some embodiments, an integrity email indicates that one or more portions of the code segment lacks integrity. In another embodiment, a method includes encrypting each email message of the plurality of email messages. A method, in a further embodiment, includes determining the status of one or more code segments sent to a client. In one embodiment, the status of the one or more code segments is presented to a user.

A computer program product is provided that includes a computer readable storage medium that stores code executable by a processor to perform operations. In one embodiment, the operations include dividing a code segment into one or more portions that together form the code segment. In a further embodiment, the operations include generating a plurality of email messages and combining one or more portions of the code segment into an email message of the plurality of email messages. The operations, in another embodiment, include sending the plurality of email messages to a client to be reassembled on the client.

DETAILED DESCRIPTION

FIG. 1depicts one embodiment of a system100for email-based software delivery. In one embodiment, the system100includes servers102, data networks104, clients106, and update apparatuses108, which are described below in more detail.

The servers102, in certain embodiments, comprise a main frame computer, a desktop computer, a laptop computer, a cloud server, a smart phone, a tablet computer, and/or the like. In one embodiment, a server102is communicatively coupled to one or more clients106through the data network104. In some embodiments, a server102is an email server configured to send and/or receive email message data. For example, an email server102may send email messages that include software data to the clients106. In another embodiment, a server102executes an email server program, such as Exchange Server by Microsoft® of Redmond, Wash., or the like. An administrator, such as a network administrator, a database administrator, and/or the like, in certain embodiments, maintains and monitors the servers102.

The data networks104, in one embodiment, comprise a digital communication network104that transmits digital communications related to email-based software delivery. The digital communication network104may include a wireless network, such as a wireless telephone network, a local wireless network, such as a Wi-Fi network, a Bluetooth® network, and the like. The digital communication network104may include a wide area network (“WAN”), a storage area network (“SAN”), a local area network (“LAN”), an optical fiber network, the internet, or other digital communication network known in the art. The digital communication network104may include two or more networks. The digital communication network104may include one or more servers, routers, switches, and/or other networking equipment. The digital communication network104may also include computer readable storage media, such as a hard disk drive, an optical drive, non-volatile memory, random access memory (“RAM”), or the like.

The clients106, in certain embodiments, include one or more information handling devices. In one embodiment, the clients106include a desktop computer, a server, a main frame computer, a smart TV, and/or the like. In some embodiments, the clients106include mobile devices, such as a tablet computer, a smart phone, a PDA, an eBook reader, a smart watch, a head-mounted optical display, and/or the like.

In certain embodiments, the clients106are in communication with a server102and sends/receives data to/from the server102through the data network104. In some embodiments, the clients106receive email messages from the server102and send email messages to the server102. In one embodiment, the clients106run an email client program, such as Outlook® by Microsoft® of Redmond, Wash., or the like, which may communicate with an email server running on the server102. In another embodiment, the clients106access a web-based email client, such as Gmail® by Google® of Mountain View, Calif., or the like.

In some embodiments, the update apparatus108is configured to divide a code segment into one or more portions, combine the one or more portions into a plurality of generated email messages, and send the plurality of email messages to a client106such that the one or more portions may be reassembled and executed on the client106. In one embodiment, portions of the update apparatus108are located on a server102and a client106. The update apparatus108, in another embodiment, includes one or more modules that perform the operations of the apparatus108. The update apparatus108, and its accompanying modules, are described in more detail below.

FIG. 2depicts one embodiment of an apparatus200for email-based software delivery. In one embodiment, the apparatus200includes an update apparatus108. The update apparatus108, in some embodiments, includes a partition module202, an email module204, and a communication module206, which are described below in more detail.

In one embodiment, the partition module202divides a code segment into one or more portions that together form the code segment. In some embodiments, the code segment includes a software update, such as a patch, a service pack, a security update, a feature update, a bug fix, and/or the like. In another embodiment, the code segment includes a software installation package configured to install a new software application on a client106. In certain embodiments, the partition module202divides the code segment on the server102, which subsequently sends the one or more portions to clients106.

In some embodiments, the partition module202reassembles the one or more portions to reconstitute the code segment. In further embodiments, the partition module202reassembles the one or more portions on a client106in response to the client106receiving all the portions of the divided code segment. The partition module202, in some embodiments, divides the code segment into equal-sized portions. In another embodiment, the partition module202divides the code segment into one or more portions that each have a different size.

In a further embodiment, the partition module202divides the code segment into portions based on user input. For example, an IT administrator may specify the size of the portions of the code segment. In this manner, the IT administrator can tailor the portion sizes based on various factors, such as the constraints of the email server, the network connectivity history of a client106, and/or the like.

In another embodiment, the email module204generates a plurality of email messages and combines the one or more portions of the code segment into each email message of the plurality of email messages. In one embodiment, the email module204attaches each portion of the code segment as an attachment to an email message. In another example, the email module204combines the one or more portions into an archived file, such as .zip, .tar, and/or the like, and attached to an email message. In another embodiment, the email module204provides one or more portions in the body of an email message.

In some embodiments, the email module204provides secondary data associated with an email message, such as a message, a subject, and/or the like. The secondary data may include data that is used by a client106receiving an email message to reassemble the one or more portions. For example, the email module204may insert instructions for reassembling the one or more portions within the body of the last email message of the plurality of email messages. Similarly, in another example, the email module204may provide descriptive data to the client106in the subject line and/or the body of an email message, such as the total number of portions to be received, the size of an attached portion, the total size of the reassembled code segment, error-detection codes, and/or the like.

In a further embodiment, the communication module206sends the plurality of email messages to a client106, where the one or more received portions are subsequently reassembled. In certain embodiments, the communication module206initiates communication with a client106by sending an initiation email message. In some embodiments, the initiation email message comprises the first portion of the one or more portions of the code segment.

The communication module206, in certain embodiments, does not send the next email message containing the next portion of the code segment until an acknowledgement email message is received from the client106. The acknowledgement email message, in certain embodiments, confirms reception of an email message. Thus, in response to determining the client106successfully received an email message, and the portions combined in the message, the communication module206sends the next email message, including the next portions of the code segment.

In certain embodiments, the communication module206pauses sending email messages to a client106in response to communication with the client106being interrupted. For example, if a client106loses connection to the data network104, such as by going outside the range of a Wi-Fi connection, the communication module206will pause sending emails to the client106. The communication module206, in one embodiment, continues sending email messages to the client106in response to communication with the client106being reestablished. In this manner, the client106may receive a complete code segment, such as a software update, when connection to the data network104is intermittent.

In one embodiment, the communication module206sends one or more email messages to a plurality of clients106on a distribution list. In one embodiment, a user, such as an IT administrator, creates a list of clients106that may receive a code segment. The IT administrator may determine which code segments to partition and assign the code segments to one or more clients106on the distribution list.

For example, an IT administrator in a corporation may create a distribution list of one or more clients106associated with sales persons who travel, i.e., “road warriors.” The IT administrator may receive a status update of each client106associated with the “road warriors” to determine software updates that the clients106may need to receive. Because the “road warriors” travel, they may have intermittent connection to a data network104, which may make it difficult to receive traditional software updates. Thus, the IT administrator may create a distribution list of clients106and assign a code segment (e.g., a software update) to each client106, which may be partitioned and sent to the clients106via a plurality of email messages. In this manner, the “road warriors” may receive necessary software updates, patches, security updates, and/or the like, for their clients106even if a network104connection is intermittent.

In another embodiment, the email module204monitors reception of one or more email messages received from the communication module206on the client106. For example, the email module204may monitor an email client running on the client106for emails sent from the server102that contains at least a portion of a code segment. In response to an email being received by the client106, the email module204may receive the portion of the code segment combined in the received email message and store the portion on the client106. In some embodiments, the email module204removes the email from the client's106inbox in response to receiving the portions attached to the received email.

In another embodiment, the email module204queues one or more received portions until a final email message is received by the client106. In some embodiments, the final received email message includes instructions for reassembling the received portions. In response to a final email message being received, the one or more portions may be reassembled on the client106by the partition module202. In some embodiments, the integrity of each of the received portions may be verified during reassembly by the integrity module306. In another embodiment, the integrity of the reassembled code segment is verified by the integrity module306. The reassembled code segment may then be executed by the client106.

FIG. 3depicts another embodiment of an apparatus300for email-based software delivery. In one embodiment, the apparatus300includes an update apparatus108. The update apparatus108, in certain embodiments, includes a partition module202, an email module204, and a communication module206, which are substantially similar to the partition module202, email module204, and communication module206described above with reference toFIG. 2. The update apparatus108, in some embodiments, includes an action module302, a sequence module304, an integrity module306, a security module308, and a status module310, which are described in more detail below.

The action module302, in one embodiment, confirms an action related to the code segment. In certain embodiments, the action comprises reassembly on the client106, execution on the client106, and/or the like. In one embodiment, the action module302receives a confirmation email message from the client106in response to the client106reassembling the sent portions of the code segment. In another embodiment, the action module302receives a confirmation email message from the client106in response to the client106executing the reassembled code segment.

In some embodiments, the confirmation email message received by the action module302includes information describing the status of the reassembly of the code segment and/or the status of execution of the code segment. For example, the confirmation email message may include a message stating that the reassembly of the code segment was successful or unsuccessful. Similarly, the confirmation email message may include a message stating that the execution of the reassembled code segment was successful or unsuccessful. In some embodiments, as described below, the status module310presents the status of the reassembly of the code segment and/or the execution of the reassembled code segment to a user.

In another embodiment, the sequence module304determines an order to send the plurality of email messages to the client106. In some embodiments, the sequence module304arranges the email messages in random order. In another embodiment, the sequence module304arranges the email messages in a reassembly order, which may include the same order necessary to reassemble the code segment. In certain embodiments, the sequence module304arranges the email messages in order of attachment size. For example, in embodiments where the size of the attached portions of the code segment vary, the sequence module304may send the email messages in ascending or descending order of size.

In another embodiment, the sequence module304determines the order to send the plurality of email messages based on user input. For example, an IT administrator may specify the order, on a per email basis, to send the email messages. In another example, the IT administrator may select an order scheme, such as random, ascending/descending based on size, reassembly order and/or the like.

The integrity module306, in a further embodiment, resends one or more email messages in response to receiving an integrity email from the client106. The integrity email, in certain embodiments, indicates that one or more portions of the code segment lacks integrity. In another embodiment, the integrity module306verifies an integrity of each portion of the code segment and/or the reassembled code segment. In some embodiments, the integrity module306is located on the server102and checks the integrity of the one or more portions being sent to the client106before they are sent to the client106. In response to determining the corruption in a portion being sent, the integrity module306, in one embodiment, notifies a user of the error. In another embodiment, the integrity module306notifies the partition module202of the corrupted portion, and the partition module202may repartition that portion of the code segment. In a further embodiment, the integrity module306notifies the email module204of the corrupted portion, which may recreate the email message associated with the corrupted portion of the code segment.

In another embodiment, the integrity module306is located on the client106. In such an embodiment, the integrity module306verifies the integrity of a received email message, a received portion of the code segment, and/or the integrity of the reassembled code segment. In some embodiments, if the integrity module306determines that a portion of the code segment and/or the reassembled code segment is corrupt, the integrity module306resends one or more email messages comprising portions of the code segment. The integrity module306may also notify a user of the corrupted portions and/or the corrupted reassembled code segment, which may be presented to the user by the status module310.

In one embodiment, the integrity module306verifies the integrity of the portions and/or the reassembled code segment by using an error-detection scheme. In one embodiment, the integrity module306uses a cyclic redundancy check (“CRC”) to determine the integrity of the portions and/or reassembled code segment. In another embodiment, the integrity module306uses a checksum algorithm to create a checksum associated with each portion and/or reassembled code segment, which may be used to determine whether a portion and/or reassembled code segment has been corrupted. One of skill in the art will recognize other methods to verify the integrity of a block of code.

The security module308, in another embodiment, encrypts each email message of the plurality of email messages on the server102. In one embodiment, the security module308decrypts the plurality of email messages on the client106. In certain embodiments, the security module308employs a public key/private key encryption scheme between the server102and client106. For example, the security module308may encrypt an email message with a public encryption key and decrypt an encrypted email message with a private decryption key, e.g., a key only known to the client106.

In another embodiment, the security module308employs a symmetric key encryption scheme between the server102and the client106, where the encryption and decryption keys are the same. One of skill in the art will recognize other encryption methods that may be utilized to encrypt and decrypt emails. In certain embodiments, if the client106cannot decrypt an encrypted email message, or if there are other errors in the encryption/decryption process, the security module308notifies the user of the errors.

In one embodiment, the status module310, determines the status of one or more code segments sent to a client106. In some embodiments, the status module310tracks the progress of one or more portions of a code segment sent by the email module204, and presents the status to a user. For example, the status module310may track how many email messages have been sent and how many emails are remaining to be sent. Alternatively, the status module310may report how many portions of the code segment have been sent and how many portions are remaining to be sent. Further, the status module310monitors and/or reports whether a code segment has been successfully reassembled and/or executed on the client106.

In another embodiment, the status module310presents to the user one or more notifications, such as error messages, informational messages, confirmation messages, and/or the like. For example, if a client106sends an error message that may require the user to take a certain action, the status module310may present the message to the user. In some embodiments, the status module310reports notifications and other information to a user through email, text message, desktop notifications, and/or the like. Alternatively, the status module310may present progress data, notifications, and/or the like in a graphical dashboard display, which provides an interface for a user to control and monitor the distribution of code segments and email messages.

In some embodiments, the dashboard presented by the status module310may allow a user to create and manage a distribution list of clients106and the code segments that are partitioned and sent to the clients106. For example, if clients106A-D require a service pack and clients106E-H require a security patch, the user may create a distribution list for clients106A-D and another list for clients106E-H. The user may then select the software to be partitioned and sent to each distribution list. Further, the user may also select the size of the portions of the partitioned software, the size of the email attachments sent to the clients106, the time to begin sending the emails, and/or the like. The status module310may then monitor the progress of the software sent to the clients106on a per client basis.

In one embodiment, the status module310generates a consolidated status report associated with distributions of one or more code segments. In some embodiments, the consolidated status report includes a status of one or more code segment distributions. For example, the status report may include a list of clients106, and the code segments distributed to each client106, with a status of the distribution, such as “successful,” “unsuccessful,” “in progress,” “paused,” and/or the like. In some embodiments, the status module310includes a completion percentage for distributions that are in progress in the status report. In certain embodiments, the status module310includes an estimated completion time for each distribution in progress and also a completion time for each distribution that is completed in the status report. In another embodiment, the status module310includes notifications, messages, error codes, and/or the like in the status report for each distribution.

The status module310, in some embodiments, provides the status report in a printable format, such as a word processing document, a PDF, and/or the like. In certain embodiments, the status module310presents information in the status report based on user input. For example, a user (e.g., an IT administrator) may customize the information on the status report, such as the organization of the data, the types of data to be included in the report, and/or the like. In another embodiment, the status module310automatically creates a status report based on a schedule determined by a user. For example, an IT administrator may have a status report created every morning at 9:00 AM, or the like. Alternatively, the status module310creates a status report in response to user input.

FIG. 4depicts one embodiment of a system400for email-based software delivery. In one embodiment, the system400includes a plurality of portions410a-cof a code segment. In some embodiments, the code segment includes a software update, a security update, a patch, a software application, and/or the like. In certain embodiments, a partition module202segments the code segment into the one or more portions410a-c. In another embodiment, an email module204generates one or more email messages406a-cand combines the one or more portions410a-cof the code segment into the email messages.

In one embodiment, the server102initiates communication with the client106by sending an initiate email message402, which notifies the client106to expect one or more email messages that include one or more portions of a code segment. The email module204, in some embodiments, sends an acknowledgement (“ACK”) email message404afrom the client106to the server102to acknowledge receipt of the initiate email message402. In one embodiment, the communication module206sends the first email message406aof the plurality of email messages406a-cto the client106. In response to receiving an ACK email message404bin response to receiving the first email message406a, the communication module206sends another email message406bof the plurality of email message406a-c. The client106acknowledges reception of the second email message406bby sending an ACK email message404c. The server102continues to send email messages406a-c, which the client106acknowledges404a-euntil a final email message408is received.

In some embodiments, when the client106receives an email message406a-c, the email module204removes the one or more portions of the code segment from the received email406a-c. In some embodiments, the email module204stores the one or more portions until a final email message408is received and acknowledged404e. A partition module202, in some embodiments, reassembles the one or more received portions into the code segment412, which may be executed on the client106. In this manner, a client106may receive a software update, application, patch, or the like when the client106has intermittent network104connection to the server102.

FIG. 5depicts a flow chart illustrating one embodiment of a method500for email-based software delivery. In one embodiment, the method500begins and a partition module202divides502a code segment into one or more portions that together form the code segment. In another embodiment, an email module204generates504a plurality of email messages and combines506the one or more portions of the code segment into each email message of the plurality of email messages. In a further embodiment, a communication module206sends508the plurality of email messages to a client106, and the method500ends.

FIG. 6depicts a flow chart illustrating one embodiment of a method600for email-based software delivery. In one embodiment, the method600begins and a partition module202divides602a code segment into one or more portions that together form the code segment. In certain embodiments, the partition module202divides602the code segment into equal-sized portions, varying-sized portions, or user-defined portions.

In a further embodiment, an email module204generates604a plurality of email messages and combines606the one or more portions of the code segment into each email message of the plurality of email messages. In certain embodiments, the email module204attaches the each portion of the one or more portions to an email of the plurality of emails as an email attachment. In some embodiments, the email module204provides secondary data in an email message that describes one or more portions combined in the email message. The secondary data may include the size of a combined portion, the total size of the reassembled code segment, error-detection codes, and/or the like.

In one embodiment, a sequence module304determines608an order to send the plurality of email messages to the client106. In some embodiments, the sequence module304arranges the email messages in random order. In another embodiment, the sequence module304arranges the email messages in a reassembly order, which may include the same order necessary to reassemble the code segment. In certain embodiments, the sequence module304arranges the email messages in order of attachment size. In another embodiment, the sequence module304determines608the order to send the plurality of email messages based on user input.

In another embodiment, a communication module206sends610the plurality of email messages to a client106. In certain embodiments, after an email is sent, the communication module206determines612whether an acknowledgment email message has been received. If an acknowledgment email message has not been received, the communication module206may resend614the email message. In another embodiment, if an acknowledgment email message has been received, the communication module206determines616whether there are emails remaining to be sent. If there are emails remaining to be sent, in some embodiments, the communication module206sends610the next email message.

In one embodiment, if there are no more emails to be sent, an action module302confirms618an action related to the code segment. In certain embodiments, the action module302receives confirmation from the client106that all the portions have been received. In some embodiments, the action module302receives confirmation618that the integrity of the portions has been verified to ensure the portions have not been corrupted. In another embodiment, the action module302receives618confirmation that the portions have been reassembled into the code segment and/or executed on the client106, and the method600ends.