Photography Composition Service

The concepts and technologies disclosed herein are a photography composition service. According to one aspect disclosed herein, a requester device can create, on behalf of a requester user, a request for a photograph to be captured by a provider user via a provider device. The request can specify a composition template to be used by the provider user to capture the photograph. The request can further specify an offer to the provider user in compensation for capturing the photograph. The requester device can provide the request to the provider device. The requester device can determine if the offer was accepted. In response to determining that the offer was accepted, the requester device can notify the requester user that the offer was accepted. The requester device can receive the photograph and fulfill the offer to the provider user in compensation for the provider user capturing the photograph.

BACKGROUND

In 2019, 50 billion photographs were taken on smartphones, and according to some market research, approximately 90% of these interactions resulted in disappointment with the photograph or worse. While requesting a favor from a stranger to take a photograph has become a universal custom, it most often leads to awkward interactions, emotional rejection, and wasted time because it can be difficult to explain in words how the photograph should look. Other common, more quantifiable risks during this interaction involve damage to the smartphone (e.g., accidental dropping), theft, as well as virus transmission.

Photography composition applications currently exist, but these applications require handing over a smartphone to a stranger, so potential disappointment with the photograph is the only problem addressed. Some individuals may hire professional photographers for their expertise, but in addition to being prohibitively expensive, coordinating an on-demand photography service may be difficult or impossible.

SUMMARY

Concepts and technologies disclosed herein are directed to a photography composition service. According to one aspect disclosed herein, a requester device can create, on behalf of a requester user, a request for a photograph to be captured by a provider user via a provider device. The request can specify a composition template to be used by the provider user to capture the photograph. The request can further specify an offer to the provider user in compensation for capturing the photograph. The requester device can provide the request to the provider device. The requester device can determine if the offer was accepted. In response to determining that the offer was accepted, the requester device can notify the requester user that the offer was accepted. The requester device can receive the photograph and fulfill the offer to the provider user in compensation for the provider user capturing the photograph.

In some embodiments, the request can specify a plurality of parameters. The parameters can include a location parameter and the composition template. The composition template can include a pre-built composition template or a custom composition template created by the requester user. The location parameter can include a current location of the requester device or a custom location. The location parameter can include a photograph opportunity location, such as a landmark or user recommended location.

In some embodiments, the requester device can provide the request to the provider device by sending the request to the provider device. In addition or alternatively, the requester device can provide the request to the provider device by sending the request to a marketplace through which the provider user can accept the offer.

In some embodiments, the requester device can fulfill the offer to the provider user in compensation for the provider user capturing the photograph, which can include initiating monetary payment to be sent to an account associated the provider user. In some embodiments, payment can be arranged via one or more payment platforms (e.g., a mobile payment service such as VENMO, a bank or credit union, a credit card processor, or other financial entity) to complete the transaction. The exchange of physical currency is also contemplated. In some embodiments, the photograph can be transferred and/or stored, and/or payment (i.e., honoring the offer) can be completed on a distributed ledger such as a blockchain. The distributed ledger can implement smart contracts to ensure the requester user and the provider user perform tasks required of them for a successful transaction. In some embodiments, the photograph can be provided as or part of a non-fungible token (“NFT”) on the distributed ledger.

DETAILED DESCRIPTION

The concepts and technologies disclosed herein are directed to a photography composition service. More particularly, the concepts and technologies disclosed herein provide an application through which a user can submit a request for a photography composition service. A user (i.e., requester user) can select a pre-built composition template or create a custom composition template and offer what they think is a fair price for one or more photographs that utilize the composition template. Other application users (i.e., provider users) can be notified of the request and decide whether the offer is worth their time according to free market dynamics. Upon acceptance of the offer, the provider user(s) and the requester user can be connected via their respective devices (e.g., smartphone, tablet, or other mobile device). After the provider user captures the photograph and the requester user approves of the photograph, a digital payment in the amount of the offer can be transferred to an account associated with the provider user.

Turning now toFIG.1, an operating environment100in which embodiments of the concepts and technologies disclosed herein will be described. The operating environment100includes a requester user (hereinafter “requester”)102who desires to obtain one or more photographs104via a requester device106(e.g., a smartphone, tablet, or other mobile device). The photograph104can be of any subject, including any person, place, thing, or combination of photograph subjects. The concepts and technologies disclosed herein find particular application in scenarios where the requester102desires the photograph104to be of themselves alone or in a group with one or more other individuals, but does not want to or is unable to obtain the photograph104for some reason. Typically, the requester102would have to request a favor from a stranger nearby and ask them to take the photograph104with the requester device106. This most often leads to awkward interactions, emotional rejection, and wasted time because it can be difficult for the requester102to explain in words how the photograph104should look. Other common, more quantifiable risks during this interaction may involve damage to the requester device106(e.g., accidental dropping), theft, as well as virus transmission or other malicious activity. The concepts and technologies disclosed herein overcome these challenges through a photography composition service.

The photography composition service can be provided, at least in part, via a photography composition system108, a photography composition service requester application (hereinafter “requester application”)110executed by the requester device106, and one or more photography composition service provider applications (hereinafter “provider application” or “provider applications”)112A-112N executed by one or more provider devices (hereinafter “provider device” or “provider devices”)114A-114N (e.g., smartphone, tablet, or other mobile device with a camera component) associated with one or more provider users (hereinafter “provider” or “providers”)116A-116N. In some embodiments, the requester application110and/or the provider applications112A-112N are client applications for the photography composition system108. In other embodiments, the requester application110and/or the provider applications112A-112N can provide at least a portion of the functionality of the photography composition system108. Accordingly, any description of functionality being performed by the photography composition system108can be performed either locally by the requester device106via execution of the requester application110and/or by the provider device(s)114via execution of the provider application(s)112, or remotely by the photography composition system108at the request of the requester device106and/or the provider device(s)114.

The requester device106, the provider devices114A-114N, and the photography composition system108can communicate via one or more networks118. The network(s)118may include one or more wireless networks such as, but not limited to, a Wireless Local Area Network (“WLAN”) such as a WI-FI network, a Wireless Wide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”) such as BLUETOOTH, a Wireless Metropolitan Area Network (“WMAN”) such a WiMAX network, adhoc networks, peer-to-peer networks, any combination thereof, and the like. The networks118also may include one or more wired networks, including backhaul network(s) implemented, for example, using cable and/or fiber in support of one or more wireless networks. Data link cables for connecting two or more devices, such as the requester device106and the provider device114are also contemplated. For purposes of explanation, and not limitation, the network118will be described as a WWAN implemented via one or more wireless technologies that facilitate communications among the requester device106, the photography composition system108, and the provider devices114A-114N. It is contemplated that the requester device106and the provider devices114A-114N may communicate with each other via one network (e.g., WLAN or BLUETOOTH) and with the photography composition system108via another network (e.g., WWAN). An example network118is described herein with reference toFIG.9.

In the illustrated example, the requester102is positioned in an area120in which the requester102desires the photograph104to be taken. The area120can be any size or shape, but for purposes of explanation, the area120will be defined as a circle having a radius of approximately 50 feet, which is sufficient to encompass the providers116A-116N and their respective provider devices114A-114N. The requester102can utilize the requester application110to create photograph requests (hereinafter “photograph request” or “photograph requests”)122A-122N. The requester102can define, in the photograph requests122, one or more parameter(s)124and an offer126.

The parameters124may include a location of where the photograph104is to be taken. The location may be a current location of the requester102as determined, for example, via a Global Positioning System (“GPS”), cellular triangulation, or other location determining technique used by the requester device106. The location may be a custom location defined via latitude/longitude coordinates, address, or well-known named location (e.g., a national monument). The location may also be defined via a photograph opportunity. The photo opportunity locations may be provided by the photography composition system108, individuals (e.g., through the requester application110and/or social media), by a municipality, by a company, or by any other entity. In some embodiments, the photo opportunities change based upon time of day, date, weather, and/or other variable(s).

The parameters124may include a selection from one or more pre-built composition templates128that can define, at least in part, a desired composition of the photograph104. The pre-built composition template(s)128can be stored by the photography composition system108in a composition template repository130. The elements of composition that can be utilized to define, at least in part, the pre-built composition template128can include patterns, texture, symmetry, asymmetry, depth of field, lines, curves, frames, contrast, color, viewpoint, depth, negative space, filled space, foreground, background, visual tension, shapes, or any combination thereof. It is contemplated that one or more other parameters124may influence which pre-built composition templates128are available for selection. For example, a pre-built composition template128may be defined for a particular photo opportunity location and may only be available when the requester device106is located within the area120that includes the photo opportunity location. In addition to or as an alternative to the pre-built composition template128being particular to a photo opportunity location or other location, the pre-built composition template128may be generic such as to provide a basic composition for portraits, landscapes, or other photograph types.

The parameters124may include a custom template. The requester application110can provide tools, such as through a graphical user interface (“GUI”), that allow the requester102to define the custom template. In some embodiments, the requester application110can instruct the requester102to frame an image in a viewfinder and outline the elements they would like to include in the custom template. An example of this is best shown inFIG.2D, in which the location of a human subject and a background object are outlined.

The parameters124may include one or more other parameters. The other parameters can be any parameters other than location and template selection. For example, the other parameters may identify a particular time of day or a timeframe, weather preference (e.g., sunny, rainy, or overcast, image filter preference (if any), suggested exposure settings such as aperture (e.g., f-stop number), shutter speed, and ISO, any combination thereof, and the like. The other parameters may provide general guidance to the providers116such as a description of the style (e.g., dramatic, action, candid, etc.) the requester102would like expressed in the photograph104. This can inform the providers116with an idea of how the photograph104should look in addition to any specific guidance provided by way of a composition template.

The photograph request122also can include or can be associated with the offer126. The offer126can be a monetary offer, an item offer, a service offer, a custom offer (with conditions set by the requester102), or some other type of offer that the requester102agrees to honor in compensation to the provider116who accepts the photograph request122and successfully takes the desired photograph104. In some embodiments, the offer126functions as a reverse bid. In some embodiments, the offer126is a minimum offer, which may then be bid up by the providers116in an auction-style setup.

The requester device106can send the photograph request122to one or more of the provider devices114. In some embodiments, the requester device106can broadcast the photograph request122in the area120such that any provider device114in the area120can receive the photograph request122. The provider application112can provide an option to activate and deactivate provider status such that when provider status is active, the provider application112is capable of receiving the photograph request122. In the illustrated example, the requester device106can send a first photograph request122A to a first provider device114A associated with a first provider116A, a second photograph request122B to a second provider device114B associated with a second provider116B, and an nthphotograph request122N to an nthprovider device114N associated with an nthprovider116N. In some embodiments, the requester application110can post the photograph request122to a marketplace132, which can present photograph requests122from the requester102and optionally one or more other requesters (not shown) and associated offer(s)126. The providers116can view the marketplace132through the provider applications112and can accept photograph requests122from the requester102and/or other requesters (not shown).

After the photograph request122is accepted by the provider116, the provider application112can instruct the provider116to proceed to the location identified in the photograph request122and may provide directions and/or a map to assist. When the provider116is ready to capture the photograph104, the provider application112can load any parameters124, pre-built composition template128, or custom template identified in the photograph request122and allow the provider116to take the photograph104. After the photograph104is captured, the provider application112can send a preview of the photograph104to the requester application110for the requester102to view and either accept or decline. The preview may be a full fidelity or partial fidelity version of the photograph104. The requester102can accept the photograph104, in which case the photograph104can be transferred to the requester device106and the offer126can be fulfilled (e.g., the requester102pays an agreed upon monetary amount to the provider116). The photograph104may be stored locally on the requester device106and/or uploaded to a photograph repository134of the photograph composition system108. In addition to or as an alternative to the photograph repository134of the photograph composition system108, the requester device106can, at the discretion of the requester102, upload the photograph104to a photograph service, which may facilitate storage, editing, printing, and/or other functionality. The requester102can decline the photograph104, in which case the requester102may ask the provider116to retake the photograph104or decline further service from that provider116. In some embodiments, the marketplace132can include a review system through which requesters102can review providers116. The review system can include a score system (e.g., 1-10 or 5-star) and/or written reviews. The review system may also be a simple like/dislike system (e.g., thumbs up or thumbs down).

Payment can be arranged through the requester application110and the provider application112, which may be configured to execute one or more application programming interfaces (“APIs”) to access one or more payment platforms (e.g., a mobile payment service such as VENMO, a bank or credit union, a credit card processor, or other financial entity) to complete the transaction. The exchange of physical currency is also contemplated. In some embodiments, the photograph104can be transferred and/or stored, and/or payment (i.e., fulfilling the offer126) can be completed on a distributed ledger136such as a blockchain. The distributed ledger136can implement smart contracts to ensure the requester102and the provider116perform tasks required of them for a successful transaction. In some embodiments, the photograph104can be provided as or part of a non-fungible token (“NFT”)138on the distributed ledger.

Turning now toFIGS.2A-2I, user interface diagrams illustrating several aspects of an example requester application user interface200of the requester application110will be described, according to illustrative embodiments of the concepts and technologies disclosed herein. The requester application user interface200should not be construed as being limiting to the functionality that can be provided by the requester application110. Any soft buttons, menus, options, textboxes, prompts, and other user interface elements that are illustrated may have any shape, color, name, format, and/or other visual characteristics, and are not limited in any way to the examples shown. Moreover, the user interface elements can be interacted with via hardware buttons, touchscreen, touch pad, controllers, camera-based hardware, any combination thereof, and/or the like.

Turning first toFIG.2A, the requester application user interface200A is presented on a display (best shown inFIG.7) of the requester device106. The requester application user interface200A includes a “define parameters” soft button202and a “define offer” soft button204. In the illustrated example, the “define parameters” soft button202has been selected, and upon selection, a “location” drop-down menu206, a “select pre-built composition template” drop-down menu208, a “create custom composition template” soft button210, and a “define other parameters” soft button212are presented. The “location” drop-down menu206has been selected and a “current location” option214, an “enter location” option216, and a “find photo opportunity” option218are presented. Upon selection of the “current location” option214, the requester device106can use GPS, cellular triangulation, or other location determining technique to determine the current location of the requester device106. Upon selection of the “enter location” option216, the requester102can be prompted to enter a custom location via latitude/longitude coordinates, address, or well-known named location (e.g., a national monument. In the illustrated example, the find photo opportunity option218has been selected, which causes the requester application user interface200B shown inFIG.2Bto be presented on the display of the requester device106.

Turning toFIG.2B, the requester application user interface200B includes an expanded view of the “photo opportunities” option218that shows multiple landmark photo opportunities220A-220N and multiple user recommended photo opportunities222A-222N. The landmark photo opportunities220A-220N can identify the locations of famous landmarks. The user recommended photo opportunities222A-222N can identify photo opportunities that have been recommended by other users, including other requesters102, other providers116, and/or other individuals. The user recommended photo opportunities222A-222N can be defined via the requester application110and/or the provider application112, via social media, via a web interface, or other manner. It is contemplated that the landmark photo opportunities220A-220N and the user recommended photo opportunities222A-222N can be filtered based upon the current location of the requester device106. For example, all landmark photo opportunities220A-220N and user recommended photo opportunities222A-222N within a specified range (e.g., 100 feet or 5 miles) of the current location of the requester device106can be presented in the expanded view of the photo opportunities option218.

Turning now toFIG.2C, the requester application user interface200C includes an expanded view of the “select pre-built composition template” drop-down menu208that shows multiple pre-built template options224A-224N for using one or more pre-built composition templates128that can define, at least in part, a desired composition of the photograph104. The pre-built composition template(s)128can be stored by the photography composition system108in the composition template repository130. The elements of composition that can be utilized to define, at least in part, the pre-built composition template128can include patterns, texture, symmetry, asymmetry, depth of field, lines, curves, frames, contrast, color, viewpoint, depth, negative space, filled space, foreground, background, visual tension, shapes, or any combination thereof. It is contemplated that one or more other parameters124may influence which pre-built composition templates128are available for selection. For example, a pre-built composition template128may be defined for a particular photo opportunity location and may only be available when the requester device106is located within the area120that includes the photo opportunity location. In addition to or as an alternative to the pre-built composition template128being particular to a photo opportunity location or other location, the pre-built composition template128may be generic such as to provide a basic composition for portraits, landscapes, or other photograph types.

Turning now toFIG.2D, the requester application user interface200D shows that the “create custom composition template” soft button210has been selected. The requester application110can instruct the requester102to frame an image225in a viewfinder and to outline the elements they would like to include in the custom template. In the illustrated example, the requester102has outlined a background object226and a human subject228. In some embodiments, the requester application110can highlight elements of the image225that are likely to be desirable. For example, machine learning image recognition technology can be used to identify objects of interest and/or people and the requester102can confirm for inclusion in the custom template. Placeholders can be used for people, animals, and/or other subjects that are not present in the image225. For example, the requester application110may provide various size placeholders that can be positioned over the image225and tagged with the intended element (e.g., a person or object).

Turning now toFIG.2E, the requester application user interface200E shows that the “define other parameters” soft button212has been selected. The requester102can define one or more other parameters230A-230N. The other parameters230A-230N can be any parameters other than location and template selection. For example, the other parameters230A-230N may identify a particular time of day or a timeframe, weather preference (e.g., sunny, rainy, or overcast, image filter preference (if any), suggested exposure settings such as aperture (e.g., f-stop number), shutter speed, and ISO, any combination thereof, and the like. The other parameters230A-230N may provide general guidance to the providers116such as a description of the style (e.g., dramatic, action, candid, etc.) that the requester102would like expressed in the photograph104. This can inform the providers116with an idea of how the photograph104should look in addition to any specific guidance provided by way of a composition template.

Turning now toFIG.2F, the requester application user interface200F shows that the “define offer” soft button204has been selected. In response, a “select offer amount” drop-down menu232that includes pre-set offer amounts234A-234D can be presented. The requester102can select one of the pre-set offer amounts234A-234D, enter a custom amount in an “enter offer amount” textbox236, or set a pre-defined maximum offer via a “set maximum offer” soft button238. After an offer amount is specified, the requester102can submit the offer via a “submit offer” soft button240or cancel the offer via a “cancel offer” soft button242. In the illustrated example, the “submit offer” soft button240has been selected. In response, the requester application110can submit the offer126in the photograph request122to the provider devices114in the area120and/or to the marketplace132.

Turning now toFIG.2G, the requester application user interface200G shows a requester view map244that includes an estimated time of arrival246for the provider116to inform the requester102of when to expect the provider116, a provider location248, a requester location250, and a travel route252. The requester view map244, the estimated time of arrival246, the provider location248, the requester location250, and the travel route252can be updated as the provider116travels towards the requester location250.

Turning now toFIG.2H, the requester application user interface200H shows a photograph preview254received from the provider application112. The requester102can review the photograph preview254and accept the photograph preview254by selecting an “accept photograph” soft button256or decline the photograph preview254by selecting a “decline photograph” soft button258. In the illustrated example, the requester102has selected the “accept photograph” soft button256to accept the photograph preview254. Upon acceptance, payment in accordance with the offer126can be transferred to the provider116, the provider device114, or an account associated with the provider116.

Turning now toFIG.2I, the requester application user interface200I shows a payment confirmation260that payment has been provided to the provider116and a transfer status262indicating the status of the photograph104transferring from the provider device114or the photograph repository134to the requester device106. After the photograph104has been transferred, the transaction between the requester102and the provider116is complete.

Turning now toFIGS.3A-3I, user interface diagrams illustrating several aspects of an example provider application user interface300of the provider application112will be described, according to illustrative embodiments of the concepts and technologies disclosed herein. The provider application user interface300should not be construed as being limiting to the functionality that can be provided by the requester application110. Any soft buttons, menus, options, textboxes, prompts, and other user interface elements that are illustrated may have any shape, color, name, format, and/or other visual characteristics, and are not limited in any way to the examples shown. Moreover, the user interface elements can be interacted with via hardware buttons, touchscreen, touch pad, controllers, camera-based hardware, any combination thereof, and/or the like.

Turning first toFIG.3A, the provider application user interface300A is presented on a display (best shown inFIG.7) of the provider device114. The provider application user interface300A includes an “activate provider status” soft button302and a “marketplace” soft button304. In the illustrated example, the “activate provider status” soft button302has been selected to indicate that the provider116is available to receive photograph requests122. In some embodiments, provider status is automatically enabled. For example, a “select service area” drop-down menu306can allow the provider116to define one or more service areas308A-308N, which can be used to trigger provider status based on location using a geo-fence. The provider application user interface300A also includes a “set minimum offer” soft button310that allows the provider116to filter any potential incoming photograph requests122and corresponding offers126based upon a minimum amount. Turning toFIG.3B, the provider application user interface300B includes an expanded view of the “set minimum offer” soft button310that includes a minimum offer text box314in which the provider116can enter the minimum amount.

Turning now toFIG.3C, the provider application user interface300C shows the “marketplace” soft button304has been selected, and in response, a marketplace user interface316is presented. The marketplace user interface316shows a plurality of offer options318A-318N representative of offers126submitted by the requester102(and other requesters in this example). The provider116may actively search for offers through the marketplace user interface316and/or use the “activate provider status” soft button302to accept photograph requests122. In the illustrated example, one of the offers has been accepted.

Turning now toFIG.3D, the provider application user interface300D shows an “offer accepted” user interface320that includes a “navigate to accepted offer” option322and a “take photograph” option324. The “navigate to accepted offer” option322has been selected. Turning now toFIG.3E, the provider application user interface300E shows a provider view map326that includes the provider location248, the requester location250, and the travel route252. The provider application user interface300E also include directions328to assist the provider116in navigating to the requester102to take the photograph104. The provider view map326, the provider location248, the requester location140, the travel route252, and the directions328can be updated as the provider116travels towards the requester location250.

Turning now toFIG.3F, the provider application user interface300F shows the “take photograph” option324has been selected from the “offer accepted” user interface320, and in response, a camera viewfinder330can be presented as shown inFIG.3G. The provider116can use the camera viewfinder330to preview the image225and ensure the background object226and the human subject228are properly aligned according to the template. When the provider116is satisfied with the image225, they can select a camera shutter soft button332to capture the photograph104. The provider116can retake the photograph104if desired. As shown inFIG.3H, the provider116can select a “send photograph” option334when the provider116is ready to send the photograph104to the requester102.

Turning now toFIG.3I, the provider application user interface300I shows a “payment received” confirmation336that payment has been received from the requester102and a transfer status338indicating the status of the photograph104transferring from the provider device114or the photograph repository134to the requester device106. After the photograph104has been transferred, the transaction between the requester102and the provider116is complete.

Turning now toFIGS.4A-4B, flow diagrams illustrating aspects of a method400for utilizing a photography composition service from the perspective of a requester device106will be described, according to an illustrative embodiment of the concepts and technologies disclosed herein. It should be understood that the operations of the methods disclosed herein is not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be added, omitted, and/or performed simultaneously, without departing from the scope of the concepts and technologies disclosed herein.

Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These states, operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. As used herein, the phrase “cause a processor to perform operations” and variants thereof is used to refer to causing a processor of a computing system or device, or a portion thereof, to perform one or more operations, and/or causing the processor to direct other components of the computing system or device to perform one or more of the operations.

For purposes of illustrating and describing the concepts of the present disclosure, operations of the method disclosed herein are described as being performed alone or in combination via execution of one or more software modules, and/or other software/firmware components described herein. It should be understood that additional and/or alternative devices and/or network nodes can provide the functionality described herein via execution of one or more modules, applications, and/or other software. Thus, the illustrated embodiments are illustrative, and should not be viewed as being limiting in any way.

The method400begins and proceeds to operation402. At operation402, the requester device106launches the requester application110. From operation402, the method400proceeds to operation404. At operation404, the requester device106receives input that defines the parameters124for the desired photograph104. From operation404, the method400proceeds to operation406. At operation406, the requester device106receives further input that defines the offer126. From operation406, the method400proceeds to operation408. At operation408, the requester device106creates the photograph request122that includes the parameters124and the offer126. From operation408, the method400proceeds to operation410. At operation410, the requester device106sends the photograph request122to at least one of the provider devices114. Alternatively or additionally, the requester device106can send the photograph request122to the photography composition system108. The photography composition system108can include the photograph request122and the corresponding offer126in the marketplace132.

From operation410, the method400proceeds to operation412. At operation412, the requester device106determines if the offer126was accepted. If not, the method400returns to operation412and the method400repeats until the offer126is accepted. It is contemplated that an offer timeout may be triggered after a predetermined time has elapsed without the offer126being accepted. Alternatively, the requester application110may include an option to withdraw the offer126. If the offer126was accepted, the method400proceeds to operation414.

At operation414, the requester device106notifies the requester102that the offer126was accepted. After the offer126is accepted, the requester device106also can provide the requester view map244and/or the provider's ETA246, such as in the example shown inFIG.2G. From operation414, the method400proceeds to operation416. At operation416, the requester device106receives the photograph preview254, such as in the example shown inFIG.2H. From operation416, the method400proceeds to operation418. At operation418, the requester device106determines if the photograph preview254has been accepted. For example, the requester device106may receive an indication of acceptance, such as the “accept photograph” soft button256being selected in the example shown inFIG.2H. Alternatively, for example, the requester device106may receive an indication of rejection via a button press, such as the “decline photograph” soft button258being selected in the example shown inFIG.2H.

If the photograph104is accepted at operation418, the method400proceeds to operation420shown inFIG.4B. At operation420, the requester device106sends payment to the provider116in accordance with the offer126. From operation420, the method400proceeds to operation422. At operation422, the requester device106obtains the photograph104. From operation422, the method400proceeds to operation424. At operation424, the requester device106saves the photograph104. From operation424, the method400proceeds to operation426. The method400can end at operation426.

Returning toFIG.4A, and particularly operation418, if the photograph104is rejected, the method400proceeds to operation428inFIG.4B. At operation428, the requester device106creates a request for the provider116to retake the photograph104. The request can be generated automatically in response to the requester102selecting the “decline photograph” soft button258(shown inFIG.2H). From operation428, the method400proceeds to operation430. At operation430, the requester device106sends the request for retake to the provider device114. From operation430, the method400returns to operation416and the method400proceeds as described above until the photograph104is accepted by the requester102. It is contemplated that at any time the requester102and/or the provider116may be permitted to cancel the transaction. Whether or not either party may cancel the transaction can be incorporated into a smart contract stored on the distributed ledger136.

Turning now toFIG.5, a flow diagram illustrating aspects of a method500for utilizing a photography composition service from the perspective of the provider device114will be described, according to an illustrative embodiment of the concepts and technologies disclosed herein. The method500begins and proceeds to operation502. At operation502, the provider device114launches the provider application112. From operation502, the method500proceeds to operation504. At operation504, the provider device114receives input that defines a service area and a minimum offer. From operation504, the method500proceeds to operation506. At operation506, the provider device114triggers provider status based on location using a geo-fence defined by the service area input at operation504. From operation506, the method500proceeds to operation508. At operation508, the provider device114presents one or more offers126to the provider116. The offers126can be received from the requester device106and/or via the marketplace132.

From operation508, the method500proceeds to operation510. At operation510, the provider device114receives input of an offer acceptance and the provider device114notifies the requester device106that the offer126was accepted. From operation510, the method500proceeds to operation512. At operation512, the provider device114presents a photography user interface (see example inFIG.3G) and receives input to take the photograph104. From operation512, the method500proceeds to operation514. At operation514, the provider device114sends the photograph preview254to the requester device106.

From operation514, the method500proceeds to operation516. At operation516, the provider device114determines if the photograph104was accepted (e.g., by receiving an indication of acceptance or rejection from the requester device106). If the photograph104was accepted, the method500proceeds to operation518. At operation518, the provider device114receives payment from the requester102. From operation518, the method500proceeds to operation520. At operation520, the provider device114sends the photograph104to the requester device106. From operation520, the method500proceeds to operation522. At operation522, the method500can end.

Returning to operation516, if the photograph104was rejected, the method500proceeds to operation524. At operation524, the provider device114receives a request for retake. The method500then returns to operation512and the method500proceeds as described above.

Turning now toFIG.6, a block diagram illustrating a computer system600configured to provide the functionality described herein in accordance with various embodiments. In some embodiments, the requester device106is configured the same as or similar to the computer system600. In some embodiments, the provider device(s)114is/are configured the same as or similar to the computer system600. In some embodiments, the photography composition system108is configured the same as or similar to the computer system600. The computer system600includes a processing unit602, a memory604, one or more user interface devices606, one or more input/output (“I/O”) devices608, and one or more network devices610, each of which is operatively connected to a system bus612. The bus612enables bi-directional communication between the processing unit602, the memory604, the user interface devices606, the I/O devices608, and the network devices610.

The processing unit602may be a standard central processor that performs arithmetic and logical operations, a more specific purpose programmable logic controller (“PLC”), a programmable gate array, or other type of processor known to those skilled in the art and suitable for controlling the operation of the server computer. The processing unit602can be a single processing unit or a multiple processing unit that includes more than one processing component. Processing units are generally known, and therefore are not described in further detail herein.

The memory604communicates with the processing unit602via the system bus612. The memory604can include a single memory component or multiple memory components. In some embodiments, the memory604is operatively connected to a memory controller (not shown) that enables communication with the processing unit602via the system bus612. The memory604includes an operating system614and one or more program modules616. The operating system614can include, but is not limited to, members of the WINDOWS, WINDOWS CE, and/or WINDOWS MOBILE families of operating systems from MICROSOFT CORPORATION, the LINUX family of operating systems, the SYMBIAN family of operating systems from SYMBIAN LIMITED, the BREW family of operating systems from QUALCOMM CORPORATION, the MAC OSX, iOS, and/or families of operating systems from APPLE CORPORATION, the FREEBSD family of operating systems, the SOLARIS family of operating systems from ORACLE CORPORATION, other operating systems, and the like.

The program modules616may include various software and/or program modules described herein. The program modules616can include the requester application110, the provider application112, the marketplace132, and/or other program modules. In some embodiments, multiple implementations of the computer system600can be used, wherein each implementation is configured to execute one or more of the program modules616. The program modules616and/or other programs can be embodied in computer-readable media containing instructions that, when executed by the processing unit602, perform the methods400,500described herein. According to embodiments, the program modules616may be embodied in hardware, software, firmware, or any combination thereof. The memory604also can be configured to store the photographs104, the photograph requests122, the parameters124, the offers126, the composition template repository130, the templates128, the photograph repository134, and/or other data disclosed herein.

The user interface devices606may include one or more devices with which a user accesses the computer system600. The user interface devices606may include, but are not limited to, computers, servers, personal digital assistants, cellular phones, or any suitable computing devices. The I/O devices608enable a user to interface with the program modules616. In one embodiment, the I/O devices608are operatively connected to an I/O controller (not shown) that enables communication with the processing unit602via the system bus612. The I/O devices608may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices608may include one or more output devices, such as, but not limited to, a display screen or a printer.

The network devices610enable the computer system600to communicate with other networks or remote systems via the network(s)118. Examples of the network devices610include, but are not limited to, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge, a router, or a network card. The network118may include a wireless network such as, but not limited to, a Wireless Local Area Network (“WLAN”) such as a WI-FI network, a Wireless Wide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”) such as BLUETOOTH, a Wireless Metropolitan Area Network (“WMAN”) such a WiMAX network, or a cellular network. Alternatively, the network118may be a wired network such as, but not limited to, a Wide Area Network (“WAN”) such as the Internet, a Local Area Network (“LAN”) such as the Ethernet, a wired Personal Area Network (“PAN”), or a wired Metropolitan Area Network (“MAN”).

Turning now toFIG.7, an illustrative mobile device700and components thereof will be described. In some embodiments, the requester device106and/or the provider device(s)114is/are configured similar to or the same as the mobile device700. While connections are not shown between the various components illustrated inFIG.7, it should be understood that some, none, or all of the components illustrated inFIG.7can be configured to interact with one another to carry out various device functions. In some embodiments, the components are arranged so as to communicate via one or more busses (not shown). Thus, it should be understood thatFIG.7and the following description are intended to provide a general understanding of a suitable environment in which various aspects of embodiments can be implemented, and should not be construed as being limiting in any way.

As illustrated inFIG.7, the mobile device700can include a display702for displaying data. According to various embodiments, the display702can be configured to display various GUI elements such as shown inFIGS.2A-2I and3A-3I, text, images, video, virtual keypads and/or keyboards, messaging data, notification messages, metadata, Internet content, device status, time, date, calendar data, device preferences, map and location data, combinations thereof, and/or the like. The mobile device700also can include a processor704and a memory or other data storage device (“memory”)706. The processor704can be configured to process data and/or can execute computer-executable instructions stored in the memory706. The computer-executable instructions executed by the processor704can include, for example, an operating system708, one or more applications710, other computer-executable instructions stored in the memory706, or the like. In some embodiments, the applications710also can include the requester application110and/or the provider application112. In some embodiments, the applications710also can include a UI application.

The UI application can be executed by the processor704to aid a user in entering/deleting data, entering and setting user IDs and passwords for device access, configuring settings, manipulating content and/or settings, multimode interaction, interacting with other applications710, and otherwise facilitating user interaction with the operating system708, the applications710, and/or other types or instances of data712that can be stored at the mobile device700.

The applications710, the data712, and/or portions thereof can be stored in the memory706and/or in a firmware714, and can be executed by the processor704. The firmware714also can store code for execution during device power up and power down operations. It can be appreciated that the firmware714can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory706and/or a portion thereof.

The mobile device700also can include an input/output (“I/O”) interface716. The I/O interface716can be configured to support the input/output of data such as location information, presence status information, user IDs, passwords, and application initiation (start-up) requests. In some embodiments, the I/O interface716can include a hardwire connection such as a universal serial bus (“USB”) port, a mini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ47) port, an RJ11 port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device700can be configured to synchronize with another device to transfer content to and/or from the mobile device700. In some embodiments, the mobile device700can be configured to receive updates to one or more of the applications710via the I/O interface716, though this is not necessarily the case. In some embodiments, the I/O interface716accepts I/O devices such as keyboards, keypads, mice, interface tethers, printers, plotters, external storage, touch/multi-touch screens, touch pads, trackballs, joysticks, microphones, remote control devices, displays, projectors, medical equipment (e.g., stethoscopes, heart monitors, and other health metric monitors), modems, routers, external power sources, docking stations, combinations thereof, and the like. It should be appreciated that the I/O interface716may be used for communications between the mobile device700and a network device or local device.

The mobile device700also can include a communications component718. The communications component718can be configured to interface with the processor704to facilitate wired and/or wireless communications with one or more networks, such as the network118, the Internet, or some combination thereof. In some embodiments, the communications component718includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.

The communications component718, in some embodiments, includes one or more transceivers. The one or more transceivers, if included, can be configured to communicate over the same and/or different wireless technology standards with respect to one another. For example, in some embodiments, one or more of the transceivers of the communications component718may be configured to communicate using Global System for Mobile communications (“GSM”), Code-Division Multiple Access (“CDMA”) CDMAONE, CDMA2000, Long-Term Evolution (“LTE”) LTE, and various other 2G, 2.5G, 3G, 4G, 4.5G, 5G, and greater generation technology standards. Moreover, the communications component718may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, Time-Division Multiple Access (“TDMA”), Frequency-Division Multiple Access (“FDMA”), Wideband CDMA (“W-CDMA”), Orthogonal Frequency-Division Multiple Access (“OFDMA”), Space-Division Multiple Access (“SDMA”), and the like.

In addition, the communications component718may facilitate data communications using General Packet Radio Service (“GPRS”), Enhanced Data services for Global Evolution (“EDGE”), the High-Speed Packet Access (“HSPA”) protocol family including High-Speed Downlink Packet Access (“HSDPA”), Enhanced Uplink (“EUL”) (also referred to as High-Speed Uplink Packet Access (“HSUPA”), HSPA+, and various other current and future wireless data access standards. In the illustrated embodiment, the communications component718can include a first transceiver (“TxRx”)720A that can operate in a first communications mode (e.g., GSM). The communications component718also can include an Nthtransceiver (“TxRx”)720N that can operate in a second communications mode relative to the first transceiver720A (e.g., UMTS). While two transceivers720A-720N (hereinafter collectively and/or generically referred to as “transceivers720”) are shown inFIG.7, it should be appreciated that less than two, two, and/or more than two transceivers720can be included in the communications component718.

The communications component718also can include an alternative transceiver (“Alt TxRx”)722for supporting other types and/or standards of communications. According to various contemplated embodiments, the alternative transceiver722can communicate using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), near field communications (“NFC”), other RF technologies, combinations thereof, and the like. In some embodiments, the communications component718also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component718can process data from a network such as the Internet, an intranet, a broadband network, a WI-FI hotspot, an Internet service provider (“ISP”), a digital subscriber line (“DSL”) provider, a broadband provider, combinations thereof, or the like.

The mobile device700also can include one or more sensors724. The sensors724can include temperature sensors, light sensors, air quality sensors, movement sensors, accelerometers, magnetometers, gyroscopes, infrared sensors, orientation sensors, noise sensors, microphones proximity sensors, combinations thereof, and/or the like. Additionally, audio capabilities for the mobile device700may be provided by an audio I/O component726. The audio I/O component726of the mobile device700can include one or more speakers for the output of audio signals, one or more microphones for the collection and/or input of audio signals, and/or other audio input and/or output devices.

The illustrated mobile device700also can include a subscriber identity module (“SIM”) system728. The SIM system728can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system728can include and/or can be connected to or inserted into an interface such as a slot interface730. In some embodiments, the slot interface730can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface730can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device700are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.

The mobile device700also can include an image capture and processing system732(“image system”). The image system732can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system732can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device700may also include a video system734. The video system734can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system732and the video system734, respectively, may be added as message content to an MMS message, email message, and sent to another device. The video and/or photo content also can be shared with other devices via various types of data transfers via wired and/or wireless communication devices as described herein.

The mobile device700also can include one or more location components736. The location components736can be configured to send and/or receive signals to determine a geographic location of the mobile device700. According to various embodiments, the location components736can send and/or receive signals from global positioning system (“GPS”) devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellular network triangulation data, combinations thereof, and the like. The location component736also can be configured to communicate with the communications component718to retrieve triangulation data for determining a location of the mobile device700. In some embodiments, the location component736can interface with cellular network nodes, telephone lines, satellites, location transmitters and/or beacons, wireless network transmitters and receivers, combinations thereof, and the like. In some embodiments, the location component736can include and/or can communicate with one or more of the sensors724such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device700. Using the location component736, the mobile device700can generate and/or receive data to identify its geographic location, or to transmit data used by other devices to determine the location of the mobile device700. The location component736may include multiple components for determining the location and/or orientation of the mobile device700.

The illustrated mobile device700also can include a power source738. The power source738can include one or more batteries, power supplies, power cells, and/or other power subsystems including alternating current (“AC”) and/or direct current (“DC”) power devices. The power source738also can interface with an external power system or charging equipment via a power I/O component740. Because the mobile device700can include additional and/or alternative components, the above embodiment should be understood as being illustrative of one possible operating environment for various embodiments of the concepts and technologies described herein. The described embodiment of the mobile device700is illustrative, and should not be construed as being limiting in any way.

By way of example, and not limitation, computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-executable instructions, data structures, program modules, or other data. For example, computer media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the mobile device700or other devices or computers described herein, such as the computer system600described above with reference toFIG.6. In the claims, the phrase “computer storage medium,” “computer-readable storage medium,” and variations thereof does not include waves or signals per se and/or communication media, and therefore should be construed as being directed to “non-transitory” media only.

In light of the above, it should be appreciated that many types of physical transformations may take place in the mobile device700in order to store and execute the software components presented herein. It is also contemplated that the mobile device700may not include all of the components shown inFIG.7, may include other components that are not explicitly shown inFIG.7, or may utilize an architecture completely different than that shown inFIG.7.

Turning now toFIG.8, a block diagram illustrating an example virtualized cloud architecture800and components thereof will be described, according to an exemplary embodiment. In some embodiments, the virtualized cloud architecture800can be utilized to implement, at least in part, the photography composition system108, the network(s)118, or some portion thereof. The virtualized cloud architecture800is a shared infrastructure that can support multiple services and network applications. The illustrated virtualized cloud architecture800includes a hardware resource layer802, a control layer804, a virtual resource layer806, and an application layer808that work together to perform operations as will be described in detail herein.

The hardware resource layer802provides hardware resources, which, in the illustrated embodiment, include one or more compute resources810, one or more memory resources812, and one or more other resources814. The compute resource(s)810can include one or more hardware components that perform computations to process data, and/or to execute computer-executable instructions of one or more application programs, operating systems, and/or other software. The compute resources810can include one or more central processing units (“CPUs”) configured with one or more processing cores. The compute resources810can include one or more graphics processing unit (“GPU”) configured to accelerate operations performed by one or more CPUs, and/or to perform computations to process data, and/or to execute computer-executable instructions of one or more application programs, operating systems, and/or other software that may or may not include instructions particular to graphics computations. In some embodiments, the compute resources810can include one or more discrete GPUs. In some other embodiments, the compute resources810can include CPU and GPU components that are configured in accordance with a co-processing CPU/GPU computing model, wherein the sequential part of an application executes on the CPU and the computationally-intensive part is accelerated by the GPU. The compute resources810can include one or more system-on-chip (“SoC”) components along with one or more other components, including, for example, one or more of the memory resources812, and/or one or more of the other resources814. In some embodiments, the compute resources810can be or can include one or more SNAPDRAGON SoCs, available from QUALCOMM; one or more TEGRA SoCs, available from NVIDIA; one or more HUMMINGBIRD SoCs, available from SAMSUNG; one or more Open Multimedia Application Platform (“OMAP”) SoCs, available from TEXAS INSTRUMENTS; one or more customized versions of any of the above SoCs; and/or one or more proprietary SoCs. The compute resources810can be or can include one or more hardware components architected in accordance with an advanced reduced instruction set computing (“RISC”) machine (“ARM”) architecture, available for license from ARM HOLDINGS. Alternatively, the compute resources810can be or can include one or more hardware components architected in accordance with an x86 architecture, such an architecture available from INTEL CORPORATION of Mountain View, Cali., and others. Those skilled in the art will appreciate the implementation of the compute resources810can utilize various computation architectures, and as such, the compute resources810should not be construed as being limited to any particular computation architecture or combination of computation architectures, including those explicitly disclosed herein.

The memory resource(s)812can include one or more hardware components that perform storage operations, including temporary or permanent storage operations. In some embodiments, the memory resource(s)812include volatile and/or non-volatile memory implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data disclosed herein. Computer storage media includes, but is not limited to, random access memory (“RAM”), read-only memory (“ROM”), Erasable Programmable ROM (“EPROM”), Electrically Erasable Programmable ROM (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store data and which can be accessed by the compute resources810.

The other resource(s)814can include any other hardware resources that can be utilized by the compute resources(s)810and/or the memory resource(s)812to perform operations described herein. The other resource(s)814can include one or more input and/or output processors (e.g., network interface controller or wireless radio), one or more modems, one or more codec chipset, one or more pipeline processors, one or more fast Fourier transform (“FFT”) processors, one or more digital signal processors (“DSPs”), one or more speech synthesizers, and/or the like.

The hardware resources operating within the hardware resource layer802can be virtualized by one or more virtual machine monitors (“VMMs”)816A-816N (also known as “hypervisors”; hereinafter “VMMs816”) operating within the control layer804to manage one or more virtual resources that reside in the virtual resource layer806. The VMMs816can be or can include software, firmware, and/or hardware that alone or in combination with other software, firmware, and/or hardware, manages one or more virtual resources operating within the virtual resource layer806.

The virtual resources operating within the virtual resource layer806can include abstractions of at least a portion of the compute resources810, the memory resources812, the other resources814, or any combination thereof. These abstractions are referred to herein as virtual machines (“VMs”). In the illustrated embodiment, the virtual resource layer806includes VMs818A-818N (hereinafter “VMs818”). Each of the VMs818can execute one or more applications820A-820N in the application layer808.

Turning now toFIG.9, details of the network118are illustrated, according to an illustrative embodiment. The network118includes a cellular network902, a packet data network904, and a circuit switched network906(e.g., a public switched telephone network). The cellular network902includes various components such as, but not limited to, base transceiver stations (“BTSs”), Node-Bs or e-Node-Bs, base station controllers (“BSCs”), radio network controllers (“RNCs”), mobile switching centers (“MSCs”), mobility management entities (“MMEs”), short message service centers (“SMSCs”), multimedia messaging service centers (“MMSCs”), home location registers (“HLRs”), home subscriber servers (“HSSs”), visitor location registers (“VLRs”), charging platforms, billing platforms, voicemail platforms, GPRS core network components, location service nodes, and the like. The cellular network902also includes radios and nodes for receiving and transmitting voice, data, and combinations thereof to and from radio transceivers, networks, the packet data network904, and the circuit switched network906.

A mobile communications device908, such as, for example, the requester device106, the provider device114, a cellular telephone, a user equipment, a mobile terminal, a PDA, a laptop computer, a handheld computer, and combinations thereof, can be operatively connected to the cellular network902. The mobile communications device908can be configured similar to or the same as the mobile device700described above with reference toFIG.7.

The cellular network902can be configured as a GSM network and can provide data communications via GPRS and/or EDGE. Additionally, or alternatively, the cellular network902can be configured as a 3G Universal Mobile Telecommunications System (“UMTS”) network and can provide data communications via the HSPA protocol family, for example, HSDPA, EUL, and HSPA+. The cellular network902also is compatible with mobile communications standards such as LTE, or the like, as well as evolved and future mobile standards.

The packet data network904includes various systems, devices, servers, computers, databases, and other devices in communication with one another, as is generally known. In some embodiments, the packet data network904is or includes one or more WI-FI networks, each of which can include one or more WI-FI access points, routers, switches, and other WI-FI network components. The packet data network904devices are accessible via one or more network links. The servers often store various files that are provided to a requesting device such as, for example, a computer, a terminal, a smartphone, or the like. Typically, the requesting device includes software for executing a web page in a format readable by the browser or other software. Other files and/or data may be accessible via “links” in the retrieved files, as is generally known. In some embodiments, the packet data network904includes or is in communication with the Internet. The circuit switched network906includes various hardware and software for providing circuit switched communications. The circuit switched network906may include, or may be, what is often referred to as a plain old telephone system (“POTS”). The functionality of a circuit switched network906or other circuit-switched network are generally known and will not be described herein in detail.

The illustrated cellular network902is shown in communication with the packet data network904and a circuit switched network906, though it should be appreciated that this is not necessarily the case. One or more Internet-capable systems/devices910such as the photography composition system108, a laptop, a portable device, or another suitable device, can communicate with one or more cellular networks902, and devices connected thereto, through the packet data network904. It also should be appreciated that the Internet-capable device910can communicate with the packet data network904through the circuit switched network906, the cellular network902, and/or via other networks (not illustrated).

As illustrated, a communications device912, for example, a telephone, facsimile machine, modem, computer, or the like, can be in communication with the circuit switched network906, and therethrough to the packet data network904and/or the cellular network902. It should be appreciated that the communications device912can be an Internet-capable device, and can be substantially similar to the Internet-capable device910.

Turning now toFIG.10, a machine learning system1000capable of implementing aspects of the embodiments disclosed herein will be described. In some embodiments, aspects of the requester application110, the provider application112, the marketplace132, and/or other elements disclosed herein can be improved via machine learning. Accordingly, the requester device106, the provider device(s)114, and/or the photography composition system108can include the machine learning system1000or can be in communication with the machine learning system1000.

The illustrated machine learning system1000includes one or more machine learning models1002. The machine learning models1002can include, unsupervised, supervised, and/or semi-supervised learning models. The machine learning model(s)1002can be created by the machine learning system1000based upon one or more machine learning algorithms1004. The machine learning algorithm(s)1004can be any existing, well-known algorithm, any proprietary algorithms, or any future machine learning algorithm. Some example machine learning algorithms1004include, but are not limited to, neural networks, gradient descent, linear regression, logistic regression, linear discriminant analysis, classification tree, regression tree, Naive Bayes, K-nearest neighbor, learning vector quantization, support vector machines, any of the algorithms described herein, and the like. Classification and regression algorithms might find particular applicability to the concepts and technologies disclosed herein. Those skilled in the art will appreciate the applicability of various machine learning algorithms1004based upon the problem(s) to be solved by machine learning via the machine learning system1000.

The machine learning system1000can control the creation of the machine learning models1002via one or more training parameters. In some embodiments, the training parameters are selected modelers at the direction of an enterprise, for example. Alternatively, in some embodiments, the training parameters are automatically selected based upon data provided in one or more training data sets1006. The training parameters can include, for example, a learning rate, a model size, a number of training passes, data shuffling, regularization, and/or other training parameters known to those skilled in the art.

The learning rate is a training parameter defined by a constant value. The learning rate affects the speed at which the machine learning algorithm1004converges to the optimal weights. The machine learning algorithm1004can update the weights for every data example included in the training data set1006. The size of an update is controlled by the learning rate. A learning rate that is too high might prevent the machine learning algorithm1004from converging to the optimal weights. A learning rate that is too low might result in the machine learning algorithm1004requiring multiple training passes to converge to the optimal weights.

The model size is regulated by the number of input features (“features”)1008in the training data set1006. A greater the number of features1008yields a greater number of possible patterns that can be determined from the training data set1006. The model size should be selected to balance the resources (e.g., compute, memory, storage, etc.) needed for training and the predictive power of the resultant machine learning model1002.

The number of training passes indicates the number of training passes that the machine learning algorithm1004makes over the training data set1006during the training process. The number of training passes can be adjusted based, for example, on the size of the training data set1006, with larger training data sets being exposed to fewer training passes in consideration of time and/or resource utilization. The effectiveness of the resultant machine learning model1002can be increased by multiple training passes.

Data shuffling is a training parameter designed to prevent the machine learning algorithm1004from reaching false optimal weights due to the order in which data contained in the training data set1006is processed. For example, data provided in rows and columns might be analyzed first row, second row, third row, etc., and thus an optimal weight might be obtained well before a full range of data has been considered. By data shuffling, the data contained in the training data set1006can be analyzed more thoroughly and mitigate bias in the resultant machine learning model1002.

Regularization is a training parameter that helps to prevent the machine learning model1002from memorizing training data from the training data set1006. In other words, the machine learning model1002fits the training data set1006, but the predictive performance of the machine learning model1002is not acceptable. Regularization helps the machine learning system1000avoid this overfitting/memorization problem by adjusting extreme weight values of the features1008. For example, a feature that has a small weight value relative to the weight values of the other features in the training data set1006can be adjusted to zero.

The machine learning system1000can determine model accuracy after training by using one or more evaluation data sets1010containing the same features1008′ as the features1008in the training data set1006. This also prevents the machine learning model1002from simply memorizing the data contained in the training data set1006. The number of evaluation passes made by the machine learning system1000can be regulated by a target model accuracy that, when reached, ends the evaluation process and the machine learning model1002is considered ready for deployment.

After deployment, the machine learning model1002can perform a prediction operation (“prediction”)1014with an input data set1012having the same features1008″ as the features1008in the training data set1006and the features1008′ of the evaluation data set1010. The results of the prediction1014are included in an output data set1016consisting of predicted data. The machine learning model1002can perform other operations, such as regression, classification, and others. As such, the example illustrated inFIG.10should not be construed as being limiting in any way.