English:
[0003] FIG. 1 is a block diagram of an example computing device to authorize printing of print content received via direct wireless communication;
[0004] FIG. 2is a block diagram of an exampleprinting environmentto authorize printing of print content received via direct wireless communication at a printing device;
[0005] FIG.3is a flowchart of an example method for providing a mobile device identifier to a printing device to authorize direct wireless printing by the mobile device; and
[0006] FIG. 4 is a flowchart of an example method for providing a mobile device identifier, included in a remote printing request, to a printing device to authorize direct wireless printing by the mobile device.
[0007] As noted above, a printing device may receive content to be printed via a computer network. For example, the printing device may be a web-connected printing device capable of printing content received via the internet from a remote printing service. !n such examples, a mobile device (e.g., smart phone, tablet, etc.) may provide a remote printing request to a remote printing service via the internet, and the remote printing service may provide the content to the printing device if the sender of the request is authorized to print on the printing device via the remote printing service. In some examples, the remote printing request may be provided to the remote printing service as an email including the content, or as an application programming interface (API) function call, for example.
[0008] In some examples, the printing device may also be capable of receiving content to print from a mobile device via direct wireless communication, such as near-field communication (NFC), or the like. As such, a printing device may be able to receive content to print from a mobile device via multiple different communication channels. However, in some examples, a sender of content may be authorized by separate processes for each channel. For example, an email address of a user of a mobile device may be added to a whitelist for the printing device to authorize the user to print on the printing device via the remote printing service in connection with the email address. This email address may be added to the whitelist via a first authorization process (e.g., via a web interface for the remote printing service).
[0009] However, this process may not authorize the user to provide content to the printing device via direct wireless communication with the mobile device. In such examples, although the user has been authorized to print on the. printing device via the remote printing service, the user may be prevented from printing on the printing device via direct wireless communication until another authorization process for the direct wireless communication channel is performed. Utilizing separate authorization processes to authorize printing on the same printing device via different channels may be inconvenient for a user of the printing device.
[0010] To address these issues, examples described hereinmayenable a mobile device to be automatically authorized for direct wireless printing on a printing device when a user of the mobile device, authorized to print to the printing device via the remote printing service, prints to the printing device via the remote printing service.
[0011] In examples described herein, a remote printing server of a remote printing service may acquire a remote printing request from a mobile device, the remote printing request comprising first print content and identifying a print request sender, a destination printing device, and a mobile device identifier associated with the mobile device. Examples described herein may furtherdetermine that the identified print request sender is authorized to print on at least the destination printing device via the remote printing service and, in response to the determination that the print request sender is authorized, provide a print-ready version of the first print content to the destination printing device for printing. Examples described herein may furtherprovide authorization information to the destination printing device to authorize printing of at least second print content received by the destination printing device from the mobile device via direct wireless communication, when at least the mobile device identifier is provided by the mobile device to the destination printing device via the direct wireless communication in association with the second print content.
[0012] In this manner, examples described herein may automatically authorize a mobile device to print from a printing device via direct wireless communication when a sender associated with the mobile device is already authorized to print on the printing device via the remote printing service.
[0013] Referring now to the drawings, FIG. 1 is a block diagram of an example computing device 100 to authorize printing of print content received via direct wireless communication. As used herein, a "computing device" may be a desktop computer, notebook computer, workstation, tablet computer, mobile phone, smart device, server, blade enclosure, printing device, or any other processing device or equipment. In the example of FIG. 1 , computing device 100 maybe a remote printing server 100 to at least partially implement a remote printing service.
[0014] In examples described herein, a "remote printing service" may be a service implemented by one or more networked computing devices to receive a print request from a sending computing deviceand provide content associated with the request to a destination printing device, wherein the sending computing device and the printing device are eachremote from the networked computing device(s) implementing the remote printing service. In examples described herein, first computing device "remote" from a second computing device may be a first computing device that is separate from, and not directly connected to, the second computing device, wherein the first and second computing devices may access one another over a computer network. As used herein, a computer network may include, for example, a local area network (LAN), a wireless local area network (WLAN), a virtual private network (VPN), the Internet, or the like, or a combination thereof. In some examples, a computer network may include a telephone network (e.g., a cellular telephone network).
[0015] In the example of FIG. 1 , remote printing server 100 includes a processing resource 110 and a machine-readable storage medium 120 encoded with instructions 122, 124, 126, and 128. In some examples, storage medium 120 may include additional instructions. In some examples, instructions 122, 124, 126, and 128, and any other instructions described herein in relation to storage medium 120, may be stored on a machine-readable storage medium remote from but accessible to computing device 100 and processing resource 1 10 (e.g., via a computer network).
[0016] In examples described herein, a processing resource may include, for example, one processor or multiple processors included in a single computing device or distributed across multiple computing devices. As used herein, a "processor" may be at least one of a central processing unit (CPU), a semiconductor-based microprocessor, a graphics processing unit (GPU), a field-programmable gate array (FPGA) configured to retrieve and execute instructions, other electronic circuitry suitable for the retrieval and execution instructions stored on a machine-readable storage medium, or a combination thereof. Processing resource 110 may fetch, decode, and execute instructions stored on storage medium 120 to perform the functionalities described below. In other examples, the functionalities of any of the instructions of storage medium 120 may be implemented in the form of electronic circuitry, in the form of executable instructions encoded on a machine- readable storage medium, or a combination thereof.
[0017] As used herein, a "machine-readable storage medium" may be any electronic, magnetic, optical, or other physical storage apparatus to contain or store information such as executable instructions, data, and the like. For example, any machine-readable storage medium described herein may be any of Random Access Memory (RAM), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disc (e.g., a compact disc, a DVD, etc.), and the like, or a combination thereof. Further, any machine-readable storage medium described herein may be non-transitory.
[0018] In the example of FIG. 1, instructions 122 may actively acquire (e.g., retrieve, etc.) or passively acquire (e.g., receive, etc.) a remote printing request 180 from a mobile device via any suitable computer network. Remote printing server 100 and the mobile device may communicate via any suitable computer network. As used herein, a "mobile device" may be a mobile phone, smart device (e.g., smartphone), tablet computer, laptop, or any other computing device including a portable energy source (e.g., battery, etc.) capable of powering the device when not connected to an externa! power source.Remote printing request 180 may comprise first print content 162 to be printedand identify a mobile device identifier 160 associated with the mobile device. Remote printing request 180 may further identify a print request sender and a destination printing device to print the first print content 162. In some examples, remote printing request 180 may include first print content 162 and'mobile device identifier 160.
[0019] In examples described herein, a mobile device identifier may be any information identifying the mobile device. Example mobile device identifiers may include, for example, a mobile device's International Mobile Station Equipment Identity (IMEI) number, serial number or other product-specific number, unique device ID (UDID), an operating system (OS) identifier, a machine address (MAC), or the like, or a combination thereof.ln some examples, the mobile device identifier may be information associated with the mobile device that is at least one of unique across mobile devices and not alterable or replaceable by a user of the mobile device.
[0020] In some examples, remote printing request 180 may comprise an email (i.e., at least one electronic mail message) sent by the mobile device. In such examples, the email may include the mobile device identifier 160 and the first print content 162, and may identify the print request sender and the destination printing device. For example, first print content 162 may be included as an attachment to the email, and mobile device identifier 160 may be included in a header of the email (e.g., in custom metadata of the header).ln some examples, the email may include an email address of the sender (e.g., the address in the "From" field of the email header), which may identify the print request sender. The email may also include an email address associated with (e.g., assigned to) the destination printing device (e.g., the address in the "To" field of the email header, or the like), which may identify the destination printing device.
[0021] In other examples, remote printing request 180 may comprise an API function call, such as a call to a print request function of an API of the remote printing service. In such examples, the API function call may comprise first print content 162 and the destination printing device, and may identify the print request sender andmobi!e device identifier 160 in any suitable manner. For example, the API function call may include first print content 162, an identifier for the destination printing device, and a security token (or any other suitable information) associated with the print request sender andmobile device identifier 160. In such examples, the remote printing server may determine the print request sender andmobile device identifier 160 based on the security token. In some examples, the API function call may be provided to remote printing server 100 via hypertext transfer protocol (HTTP), or any other suitable protocol. In such examples, instructions 122 may acquire the API function call 280 (as the remote printing request 280) from a printing application of the mobile device.
[0022] Instructions 24 may determine that the identified print request sender is authorized to print on at least the identified destination printing device via the remote printing service. For example, the remote printing service may maintain" a list (e.g., a whitelist) of authorized senders for the identified destination printing device. In such examples, server 100 may provide print content received in a remote printing request to the identified destination printing device when the sender identified in the request is included in the list. In such examples, in response to receiving a remote printing request, instructions 124 may access a whitelist for the identified destination printing device and determine whether the sender identified in the print request is authorized to print on the destination printing device via the remote printing service. In other examples, instructions 124 may determine that the identified print request sender is authorized to print on a plurality of printing devices associated with the remote printing service, including the destination printing device. For example, in response to a determination or indication that a security token included in the print request is a valid security token (e.g., from a security service), and in response, instructions 124 may determine that the identified print request sender is authorized to print on a plurality of printing devices associated with the remote printing service, including the destination printing device.
[0023] In the example of FIG. 1 , instructions 124 may determine that the identified print request sender of request 180 is authorized to print on the identified destination printing device via the remote printing service. For example, in an example in which the remote printing request 180 is an email, instructions 24 may access a whitelist for the identified destination printing device (e.g., associated with the destination email address), determine that the email address of the sender is included the whitelist and thereby determine that the print request sender is authorized to print on the destination printing device via the remote printing service.
[0024] Based on the determination that the print request sender is authorized, instructions 126 may make a print-ready version 182 of the first print content 162available to the destination printing device for printing in any suitable manner. In some examples, instructions 126 may make the print-ready version 182 available by storing the print-ready version 182 in storage accessible to the destination printing device via a computer network, and providing, to the printing device, information the printing device may use to retrieve the print-ready version 182, such as a uniform resource identifier (URI), uniform resource locator (URL), or other any other suitable type of address or reference. In other examples, instructions 126 may make the print- ready version 182 available by providing the print-ready version 182 to the destination printing device.
[0025] in examples described herein, a "printing device" may be a hardware device, such as a printer, multifunction printer (MFP), or any other device including at least functionalities to physically produce graphical representation(s) (e.g., text, images, etc.) on paper, or the like. In some examples, an MFP may be capable of performing a combination of multiple different functionalities such as, for example, printing, photocopying, scanning, faxing, etc.ln examples described herein, a printing device may be capable of communicating over a computer network, such as the internet, or the like.Such a printing device may be referred to herein as a "web-connected" printing device.
[0026] In examples described herein, a "print-ready" version of print content for a given printing device may be a version of the print content in a form that may be printed by the given printing device. For example, a given printing device may be able to print documents in one or more of portable document format (PDF), at least one version of printer command language (PCL) format, or the like. A document in any such format that may be printed by a given printing device may be considered a "print-ready" version of the document for that printing device. A document in a format that may not be printed by a given printing device (e.g., a word processing document format, or the like), may not be considered a print-ready version of the document. In such examples, the document may be rendered (converted, or the like) into a print-ready format for the destination printing device before being made available to the printing device. In such examples, the remote printing service (e.g., instructions 126, or a computing device separate from but accessible to server 100) may render the document to produce the print-ready version to provide to the printing device.
[0027] In some examples, first print content 162 included in request 180 may be in a print-ready format for the destination printing device. In such examples, print-ready version 182 is equivalent to first print content 162. In other examples, first print content 162 included in request 180 may not be in a print-ready format for the destination printing device, and first print content 162 may be rendered to produce a print-ready version 182 of first print content 162 to provide to the destination printing device.
[0028] In the example of FIG. 1 , instructions 128 may provide authorization information 184 to the destination printing device to authorize printing of at least second print content received by the destination printing device from the mobile device via direct wireless communication, when at least the mobile device identifier 160 is provided by the mobile device to the destination printing device via the direct wireless communication in association with the second print content. Remote printing server 100 and the destination printing device may communicate via any suitable computer network. In such examples, instructions 128 may provide authorization information 184 to the destination printing device via any suitable computer network.
[0029] In examples described herein, "direct wireless communication" may be any form of wireless communicationthat may be performed directly between a wireless interface of a mobile device and a wireless interface of a printing device (e.g., without any intervening computing device, component, or the like). Examples of direct wireless communication may include, for example, near field communication (NFC), Bluetooth, Bluetooth low energy (BLE), ad hoc WI-FI, WI-FI DIRECT, or the like. In some examples, the direct wireless communication may be close-proximity direct wireless communication, which may be any type of short-range wireless communication having a range of about ten centimeters (10 cm) or less, such as NFC. In some examples, close-proximity direct wireless communication, may be a type of wireless communication having a range of about four centimeters (4 cm) or less.
[0030] In the example of FIG. 1 , authorization information 184, provided by instructions 128, may comprise any suitable information to causethe destination printing device to authorize printing of at least second print content received, with mobile device identifier 160, via direct wireless communicationfrom a mobile device.
[0031] In some examples, the destination printing device may maintain an authorization list indicating mobile device identifiers associated with mobile devices authorized to print on the destination printing device via direct wireless communication. In such examples, when the destination printing device receives print content with a mobile device identifier via direct wireless communication, the destination printing device may check the authorization list of for the provided mobile device identifier, and may print the print content if the provided mobile device identifier is in the authorization list. In such examples, authorization information 184 may include mobile device identifier 60.
[0032] In such examples, instructions 128 may provide mobile device identifier 160 to the destination printing device such that the destination printing device stores mobile device identifier 160 in the authorization list stored in local memory of the destination printing device, to authorize the mobile device associated with mobile device identifier 160 is authorized to print on the destination printing device via direct wireless communication. In some examples, instructions 128 may provide mobile device identifier 160 to the destination printing device in an API function call of an API of the destination printing device to cause the destination printing device to store mobile device identifier 160 in the authorization- list, in seme examples, instructions 128 ma provide mobile device identifier 160 to the destination printing device to authorize the associated mobile device to print via direct wireless communication in response to a determination by instructions 124 that the identified sender of request 180 is authorized to print on the identified destination printing device via the remote printing service.
[0033] In other examples, when the destination printing device receives print content with a mobile device identifier via direct wireless communication, the destination printing device may contact the remote printing service to determine whether a mobile device associated with the provided mobile device identifier is authorized to print via direct wireless communication. In such examples, the destination may provide the received mobile device identifier to remote printing server 100 with a request for authorization information. In such examples, instructions 128 may determine whether the mobile device is authorized and, based on the determination, instructions 128 may provide authorization information 184 indicating whether or not the mobile device (associated with the received mobile device identifier) is authorized to print on the destination printing device via direct wireless communication. In such examples, if instructions 128 provide authorization information 184 indicating thai the mobile device is authorized, then destination printing device may print the print content provided with the mobile device identifier via direct wireless communication. If instructions 128 provide authorization information 184 indicating that the mobile device is not authorized, then destination printing device may not print the print content.
[0034] In some examples, instructions 122, 124, 126, and 128, may be part of an installation package that, when installed, may be executed by processing resource 110 to implement the functionalities described herein in relation to instructions 122, 124, 126, and 128. In such examples, storage medium 20 may be a portable medium, such as a CD, DVD, or flash drive, or a memory maintained by a server from which the installation package can be downloaded and installed. In other examples, instructions 122, 124, 126, and 128may be part of an application, applications, or component already installed on remote printing server 100 including processing resource 110. In such examples, the storage medium 120 may include memory such as a hard drive, solid state drive, or the like. In some examples, functionalities described herein in relation to FIG. 1 may be provided in combination with functionalities described herein in relation to any of FIGS. 2- 4.
[0035] FIG. 2 is a block diagram of an example printing environment 200 to authorize printing of print content received via direct wireless communication at a printing device. In the example of FIG. 2, printing environment 200 comprises a remote printing service 205, a printing device 230, and a mobile device 250.
[0037] In the example of FIG. 2, printing device 230 includes engines 232-236. Each of engines 232-236 of printing device 230 may be any combination of hardware and programming to implement the functionalities of the respective engine. In examples described herein, such combinations of hardware and programming may be implemented in a number of different ways. For example, the programming for the engines may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the engines may include a processing resource to execute those instructions. In such examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement engines 232-236. In such examples, printing device 230 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to printing device 230 and the processing resource. In other examples, the functionalities of any of the engines may be implemented in the form of electronic circuitry.
[0038] In some examples, the instructions can be part of an installation package that, when installed, can be executed by the processing resource to implement engines 232- 236. In such examples, the machine-readable storage medium may be a portable medium, such as a CD, DVD, or flash drive, or a memory maintained by a server from which the installation package can be downloaded and installed. In other examples, the instructions may be part of an application, applications, or component already installed on printing device 230 including the processing resource. In such examples, the machine- readable storage medium may include memory such as a hard drive, solid state drive, or the like.
[0039] ! the example of FIG. 2, printing device 230· further includes^ print engine 241. Print engine 241 may comprise any combination of hardware and programming to implement the functionalities described herein in relation to engine 241 , including at least hardware to physically produce graphical representation(s) (e.g., text, images, etc.) on paper, or the like. In some examples, printing device 230 may include additional engines. Printing device 230 also includes a direct wireless interface 240. In examples described herein, a direct wireless interface may comprise any combination of hardware and programming to perform at least the functionalities of communicating with other direct wireless interface(s) via direct wireless communication, as described above.
[0040] In the example of FIG. 2, mobile device 250 may comprise an application 252, a mobile device identifier 160 associated with mobile device 250, and a direct wireless interface 245, as described above. Mobile device identifier 160 may be any suitable identifier associated with mobile device 250, as described above in relation to FIG. 1. In some examples, application 252 may be any type of software (implemented in the form of instructions encoded on a machine-readable storage medium and executable by a processing resource of mobile device 230) to determine mobile device identifier 160 of mobile device 250 and provide a remote printing request 280, including or otherwise identifying mobile device identifier 160, to remote printing service 205. In the example of FIG. 2, remote printing request 280 may comprise mobile device identifier 160, first print content 162, identification 164 of the sender of the request, and identification 166 of the destination printing device. In the example of FIG. 2, identification 166 may identify (e.g., may be associated with) printing device 230.
[0041] As described above in relation to request 180, in some examples, remote printing request 280 may comprise an email message provided by the mobile device. In such examples, application 252 may be an application to send an email messages (e.g., via Simple Mail Transfer Protocol (SMTP)), such as an email client, or the like. In such examples, application 252 may send an email (directly or indirectly) to remote printing service 205 as remote printing request 280. In such examples, in response to user inputs, application 252 may create the email request 280 including first print content 162 as an attachment to the email, and including mobile device identifier 160 (e.g., in the email header), as described above. In such examples, application 252 may determine mobile device identifier 160 of mobile device 250, and include the identifier 160 in the email request 280. In some examples, the email request 280 may, as described above, include an email address of the sender as the sender identification 164, and may include an email address associated with destination printing device 230 as the printing device identification 66·.
[0042] In other examples, as described above, remote printing request 280 may comprise an API function call to a print request function of an API of the remote printing service. In such examples, application 252 may be a printing application of mobile device 250 to provide remote printing requests to remote printing service 205. The API function call may be provided to remote printing service 205 via HTTP, or any other suitable protocol.ln such examples, remote printing request 280 may include.as function call parameters of the API function call, first print content 162, and destination printing device identification 166 and other information (such as a security token, as described above) identifying mobile device identifier 160 and sender identification 164. In some examples, the other information included in the API function call and identifying mobile device identifier 160 and sender identification 164 may be a security token, or the like, as described above in relation to FIG. 1. In such examples, the security token may be associated with mobile device identifier 160 and sender identification 164, such that remote printing server 100, for example, may retrieve mobile device identifier 160 and sender identification 164 based on the security token (e.g., from a security service). In some examples, the security token may also be used for authentication. In such examples, instructions 122 may acquire the API function call 280 provided by application 252 of mobile device 250.
[0043] In the example of FIG. 2, remote printing server 100 and mobile device 250 may communicate via any suitable computer network, and instructions 122 may (actively or passively) acquire remote printing request 280 from mobile device 250 via any suitable computer network. In such examples, instructions 124 may determine whether the identified printing request sender (i.e., associated with identification 164) is authorized to print on at least the identified destination printing device 230(i.e., associated with identification 166) via remote printing service 205. For example, the remote printing service may maintain a list 102 (e.g., a whitelist 102) of authorized senders for the identified destination printing device 230, as described above in relation to FIG. 1. In some examples, in response to receiving remote printing request 280, instructions 124 may access whitelist 102 to determine whether the sender identified (e.g., by identification 164) in the print request 280 is authorized to print on destination printing device 280 via the remote printing service 250. In some examples, sender identification 164 may not be included in whitelist 102 for printing device 230. In such examples, instructions 124 may determine that the identified sender of request 280 is not authorized to print on destination printing device 230 via the remote printing service 2Q5, and may not provide print content 162 to printing device 230. In other examples, instructions 124 may determine that the identified print request sender is authorized to print on a plurality of printing devices associated with the remote printing service, including the destination printing device, as described above in relation to FIG. 1.
[0044] In the example of FIG. 2, sender identification 164 (e.g., an email address of the sender) is included in whitelist 102 for printing device 230. In such examples, instructions 124 may determine that the identified sender of request 280 is authorized to print on destination printing device 230 via the remote printing service 205. In some examples, in response to the determination that the identified sender (associated with identification 164) is authorized, instructions 124 may store mobile device identifier 160 of request 280 in device credential storage 112, which is associated with (e.g., accessible to) remote printing server 100, as described above. In some examples, mobile device identifier 160 may be stored in credential storage 12 in association with printing device 230 (e.g., in association with an identifier for printing device 230) to indicate that mobile device 250 is authorized to print on printing device 230 via direct wireless communication.
[0045] Further, based on the determination that the sender of print request 280 is authorized to print on at least printing device 230 via remote printing service 205, instructions 126 may make a print-ready version 182 of the first print content 162 available to the destination printing device for printing in any suitable manner, as described above in relation to FIG. 1. As described above, remote printing service 205 may render first print content 162 to generate print-ready version 182, when first print content 162 is not in a print-ready format for printing device 230.
[0046] In the example of FIG. 2, remote acquisition engine 232 of printing device 230 may acquire.from remote printing service 205, the print-ready version 182 of first print content 162of remote printing request 280 received by remote printing service 205 (e.g., server 100) from mobile device 250 and determined, by remote printing service 205, to be from a print request sender authorized to print on at least printing device 230 via remote printing service 205. For example, engine 232 may receive the print-ready version 82 provided to printing device 230 by instructions 126 of remote printing server 100 via a suitable computer network. In other examples, engine 232 may acquire the print-ready version 182 from storage accessible to printing device 230 via a computer network at an address or other reference acquired from server 100, for example. After engine 232 acquires print-ready version 182, a print engine 241 may print the print-ready version 182 of first print content 162 on a physical medium, such as paper, cr the like.
[0047] As described above in relation to FIG. 1 , instructions 128 may provide authorization information 184 to destination printing device 230 to authorize printing of at least second print content 292 received by printing device 230 from mobile device 205 via direct wireless communication 290, when at least mobile device identifier 160 is provided by mobile device 250 to printing device 230 via direct wireless communication in association with second print content 292. Remote printing server 100 and destination printing device 230 may communicate via any suitable computer network, and instructions 128 may provide authorization information 184 to destination printing device 230 via any suitable computer network. In the example of FIG. 1 , authorization information 184, provided by instructions 128, may comprise any suitable information to cause the destination printing device to authorize printing of at least second print content received, with mobile device identifier 160, via direct wireless communication from a mobile device.
[0048] For example, based on a determination by instructions 124 that the identified printing request sender (i.e., associated with identification 164) of request 280 is authorized to print on identified printing device 230 via remote printing service 205, instructions 128 may provide authorization information 184 comprising mobile device identifier 160 to destination printing device 230 (as shown in FIG. 2). In such examples, instructions 128 may provide mobile device identifier 160 to printing device 230 in a manner to authorize printing of at least second print content 292 received, with at least mobile device identifier 160, by printing device 230 from mobile device 250 via direct wireless communication.
[0049] For example, printing device 230 may maintain an authorization list 239 including mobile device identifiers associated with respective mobile devices authorized to print on printing device 230 via direct wireless communication. In such examples, when the destination printing device receives print content with a mobile device identifier via direct wireless communication, the destination printing device may check authorization list 239 of for the provided mobile device identifier, and may print the print content if the provided mobile device identifier is in authorization list 239. In some examples, authorization list 239 may be implemented by at least one machine-readable storage medium included on printing device 230 (i.e., local to printing device 230).
[0050] In some examples, based on a determination by instructions 124 that the sender (i.e., associated with identification 164) of request 280 is authorized to print on device 230 via service 205, instructions 128 may provide mobile device identifier 160 to printing d©vice 230 such that printing device 2-30 stcF@& mobile device identifier 160 in authorization list 239 to authorize mobile device 250 associated with mobile device identifier 160 to print on the destination printing device via direct wireless communication. For example, instructions 128 may provide mobile device identifier 160 to printing device 230 in an API function call of an API of printing device 230 to cause printing device 230 to store mobile device identifier 160 in authorization list 239. In some examples, instructions 128 may provide mobile device identifier 160 to printing device 230 based on the determination by instructions 124 that the sender of request 280 is authorized to print on device 230 via service 205, by providing mobile device identifier 160 to printing device 230 with the print-ready version 182 of first print content 162.
[0051] In other examples, instructions 128 may provide mobile device identifier 160 to printing device 230, based on the determination by instructions 124 that the sender of request 280 is authorized to print on device 230 via service 205, by providing mobile device identifier 160 to printing device 230 after receiving an indication from printing device 230 that first print content 162 (previously provided to printing device 230 based on the determination) was successfully printed by printing device 230. In such examples, instructions 128 may provide mobile device identifier 160 to printing device 230, based on the determination by instructions 124 that the sender of request 280 is authorized to print on device 230 via service 205, and based on the indication that first print content 162 was successfully printed.
[0052] Referring to printing device 230 of FIG. 2, in examples in which instructions 128 provide mobile device identifier 160 to printing device 230, remote acquisition engine 232 of printing device 230 may acquire (e.g., receive),from remote printing server 100, the mobile device identifier 160 associated with mobile device 250and identified via (e.g:, included in) remote print request 280. In such examples, storage engine 234 may store the acquired mobile device identifier 160 in authorization Iist239 in local memory (e.g., in a machine-readable storage medium) of printing device 230. In such examples, by storing mobile device identifier 160 in authorization list 239, printing device 230 may authorize mobile device 250 (associated with identifier 160) to print on printing device 230 via direct wireless communication.
[0053] In the example of FIG. 2, a communication engine 236 may actively acquire (e.g., retrieve, etc.) or passively acquire (e.g., receive, etc.) second print content 292 and mobile device identifier 160 from mobile device 250 via direct wireless communication 290 between mobile device 250 and printing device 230. In some examples, second print content 292 and ma e provided with mobile device identifier 160, from mobile device 250 to printing device 230 via direct wireless communication. In some examples, second print content 292 and mobile device identifier 160 may be provided from mobile device 250 to printing device 230 via one or more messages communicated via the direct wireless communication. In such examples, mobile device identifier 160 may be provided to printing device 230 in association with second print content 292 via the direct wireless communication. For example, mobile device identifier 160 and second print content 292 may be provided to printing device 230 in the same communication, communication session, connection, or the like, or in any other manner linking or associating second print content 292 with mobile device identifier 160.
[0054] In response to receiving at least mobile device identifier 160, authorization engine 235 may determine whether at least mobile device identifier 160, acquired with (or in association with) second print content 292 via direct wireless communication, is stored in authorization list 239. In the example of FIG. 2, mobile device identifier 160 is stored in authorization list 239. In such examples, in response to receiving at least mobile device identifier 160, authorization engine 235 may determine that at least mobile device identifier 160, acquired with (or in association with) second print content 292 via direct wireless communication, is stored in authorization list 239. In response to this determination, authorization engine 235 may cause the print engine 241 to print second print content 292.
[0055] In some examples described herein, authorization engine 235 may determine that the mobile device 250 providing mobile device identifier 160 is authorized to print on printing device 230 via direct wireless communication based on the presence of mobile device identifier 160 in authorization list 239, independent of (i.e., without) any further input to the printing device after the direct wireless communication of mobile device identifier 160. In this manner, examples described herein may simplify the process of becoming authorized to print via direct wireless communication utilizing a remote printing service.
[0056] In some examples, printing device 230 may receive second print content 292 from mobile device 250 in a print-ready format for printing device 232. In other examples, printing device 230 may receive second print content 292 from mobile device 205 in a format that is not a print-ready format for printing device 232. In such examples, render engine 233 of printing device 230 may render the acquired second print content 292 into a print-ready format for printing device 230. In such examples, print engine 241 ma print the print-ready version 182 of second print content 292 in response to the determination that mobile device identifier 160 is included in authorization list 239.
[0057] In some examples, authorization engine 235 may prevent printing device 230 from printing third print content received via direct wireless communication with (or in association with) another mobile device identifier not stored in authorization list 239. In such examples, in response to acquiring the other mobile device identifier, engine 235 may determine that the other mobile device identifier is not present in authorization list 239 and, in response to the determination, prevent printing device 230 from printing third print content received, via direct wireless communication, with (or in association with) the other mobile device identifier.
[0058] In other examples, when printing device 230 receives print content in association with a mobile device identifier via direct wireless communication, printing device 230 may contact remote printing service 205 to determine whether the mobile device providing the mobile device identifier is authorized to print on printing device 230 via direct wireless communication. In such examples, in response to communication engine 236 acquiring mobile device identifier 160 in association with second print content 292 from mobile device 250 via direct wireless communication 290, authorization engine 235 may provide, to remote printing service 205, a request to determine whether printing of second print content 292 received in association with mobile device identifier 160 via direct wireless communication is authorized.
[0059] In such examples, referring to remote printing server 100, instructions 128 may acquire (e.g., receive), from printing device 230, the request to determine whether printing of second print content 292 received by printing device 230 in association with mobile device identifier 160 via direct wireless communication is authorized.
[0060] In response to the request, instructions 124 may determine whether mobile device identifier 160 is associated with printing device 230 in device credential storage 1 12 associated with remote printing server 100. In the example of FIG. 2, mobile device identifier 160 is associated with printing device 230 in device credential storage 1 12 as a result of being stored in storage 1 12 by instructions 124 based on the prior determination that sender identification 164 was included in whitelist 102 in response to remote printing request 102. In such examples, in response to the determination that mobile device identifier 160 is associated with printing device 230 in device credential storage 112, instructions 128 may provide an indication (i.e., authorization information 184 indicating) to printing device 230 that the printing of second print content 292 received,via direct wireless communication is authorized, In response to this indication, authorization engine 235 of printing device 230 may cause print engine 241 to print second print content 292. In examples in which mobile device identifier 160 is not associated with printing device 230 in device credential storage 112, instructions 128 may provide authorization information 184 to printing device 230 indicating that the printing of second print content 292 is not authorized and, in response, authorization engine 235 of printing device 230 may prevent printing device 230 (i.e., print engine 241) from printing second print content 292.
[0061] In other examples, the authorization of a mobile device to print via direct wireless communication may be based on both a mobile device identifier and a mobile device user identifier. In this manner, particular user(s) of a mobile device may be authorized to print on a printing device via direct wireless communication, rather than any user of a given mobile device. For example, remote printing request 280 may additionally include a mobile device user identifier associated with mobile device 250, which may be any suitable information identifying a user of mobile device 250 that initiated the request 280. In such examples, based on the determination that the sender of print request 280 is authorized to print on printing device 230 via remote printing service 205,'instructions 124 may store both themobile device user identifier and the mobile device identifier 160 in association with a printing device in credential storage- 112.
[0062] Also, in some examples, based on the determination that the sender is authorized, instructions 128 may provide mobile device identifier 160 and the mobile device user identifier to destination printing device 230 to authorize printing of print content received by printing device 230, in association with mobile device identifier 160 and the mobile device user identifier, from mobile device 250 via direct wireless communication. In such examples, remote acquisition engine 232 may acquire, from remote printing server 100, a mobile device user identifier associated with mobile device 250 and included in remote print request 280. Storage engine 234 may store the acquired mobile device user identifier in authorization list 239 in association with mobile device identifier 160.
[0063] In such examples, communication engine 236 may acquire the mobile device user identifier with mobile device identifier 160, both in association with the second print content 292, from mobile device 250 via direct wireless communication between mobile device 250 and printing device 230. In such examples, authorization engine 235 may cause print engine 241 to print second print content 292 in response to a determination that the mobile device user identifier is stored m- authorization -fist 239 in association with mobile device identifier 160.The mobile device user identifier may be equivalent to or different from sender identification 164. In some examples, sender identification 164 may be used as the mobile device user identifier.
[0064] Referring to remote printing server of FIG. 2, in some examples, instructions 122 may (actively or passively) acquire a request 290 to remove the authorization of the print request sender (associated with identification 164) to print on printing device 230 via remote printing service 205. In such examples, in response to request 290, instructions 128 may instruct printing device 230 to remove mobile device identifier 160 (or mobile device identifier 160 and an associated mobile device user identifier) from authorization list 239. In response, engine 234 of printing device 230 may remove mobile device identifier 160 (or mobile device identifier 160 and the associated mobile device user identifier) from authorization list 239. In such examples, remote printing service 205 may store an association between sender identification 164 and mobile device identifier 160 (and mobile device user identifier, in some examples) such that mobile device identifier 160 (and mobile device user identifier, in some examples) may be removed from authorization list 239 in response to the request to remove the authorization of the print request sender associated with identification 64 for printing on printing device 230, as described above. In some examples, functionalities described herein in relation to FIG. 2may be provided in combination with functionalities described herein in relation to any of FIGS. 1 and 3-4.
[0065] FIG. 3 is a flowchart of an example method 300 for providing a mobile device identifier to a printing device to authorize direct wireless printing by the mobile device. Although execution of method 300 is described below with reference to server 100 of FIG. 1 described above, other suitable systems for the execution of method 300 can be utilized. Additionally, implementation of method 300 is not limited to such examples.
[0066] At 305 of method 300, instructions 122 of remote printing server, at least partially implementing a remote printing service, may acquire a remote printing request 180 from a mobile device, the remote printing request 180 comprising first print content 162 and identifying a print request sender, a destination printing device, and a mobile device identifier 160 associated with the mobile device. At 310, instructions 124 may determine that the identified print request sender is authorized to print on at least the destination printing device via the remote printing service.
[0067] At 315, in response to the determination, instructions 126 may provide a print- ready Version 182 of first print content 162 to the destination printing device for printing. At 32Q, instructions 6 may receive an -indication that first print content 160 was successfully printed by the destination printing device. At 325, in response to the indication, instructions 128 may provide mobile device identifier 160 to the destination printing device to authorize printing of at least second print content received, with the mobile device identifier, by the destination printing device from the mobile device via close-proximity, direct wireless communication.
[0068] Although the flowchart of FIG. 3shows a specific order of performance of certain functionalities, method 300 is not limited to that order. For example, the functionalities shown in succession in the flowchart may be performed in a different order, may be executed concurrently or with partial concurrence, or a combination thereof. In some examples, functionalities described herein in relation to FIG. 3 may be provided in combination with functionalities described herein in relation to any of FIGS. 1-2 and 4.
[0069] FIG. 4 is a flowchart of an example method 400 for providing a mobile device identifier, included in a remote printing request, to a printing device to authorize direct wireless printing by the mobile device. Although execution of method 400 is described below with reference to server 100 of FIG. 2 described above, other suitable systems for the execution of method 400 can be utilized. Additionally, implementation of method 400 is not limited to such examples.
[0070] At 405 of method 400, instructions 122 of remote printing server, at least partially implementing a remote printing service, may acquire a remote printing request 180 from a mobile device, the remote printing request 180 comprising first print content 162 and identifying a print request sender, a destination printing device, and a mobile device identifier 160 associated with the mobile device.
[0071] At 410, instructions 124 may determine whether the identified print request sender is authorized to print on at least the destination printing device via the remote printing service. In the example of FIG. 4, the remote printing request may comprise an email including an email address of the print request sender, which may identify the sender of the request 180, and may comprise the mobile device identifier. At 410, instructions 124 may determine whether the identified print request sender is authorized to print on the destination printing device via the remote printing service based on whether the email address of the print request sender is included in a whitelist 102 for the destination printing device.
[0072] If the sender's email address is not included in the whitelist 102, then the sender is not authorized and method 400 may proceed to 415, where instructions 124 may reject remote printing request 180 such thai first print content 162 is- not printed at the destination printing device. If it is determined at 410 that the sender's email address is included in the whitelist 102, and thus authorized, then method 400 may proceed to 420. At 420, in response to the determination, instructions 126 may provide a print- ready version 182 of first print content 162 to the destination printing device for printing.
[0073] At 425, in response to the determination, instructions 124 may store mobile device identifier 160 in device credential storage 122 and in association with the remote printing server. At 430, instructions 126 may receive an indication that first print content 160 was successfully printed by the destination printing device. At 435, in response to the indication, instructions 128 may provide mobile device identifier 160 to the destination printing device to authorize printing of at least second print content received, with the mobile device identifier, by the destination printing device from the mobile device via close-proximity, direct wireless communication, such as NFC.
[0074] Although the flowchart of FIG. 4 shows a specific order of performance of certain functionalities, method 400 is not limited to that order. For example, the functionalities shown in succession in the flowchart may be performed in a different order, may be executed concurrently or with partial concurrence, or a combination thereof. In some examples, functionalities described herein in relation to FIG. 4 may be provided in combination with functionalities described herein in relation to any of FIGS. 1- 3.

中文:
[0003]图1是授权经由直接无线通信接收的打印内容的打印的示例计算设备的框图;
[0004]图2是授权在打印设备处经由直接无线通信接收的打印内容的打印的示例打印环境的框图;
[0005]图3是用于向打印设备提供移动设备标识符以授权通过移动设备的直接无线打印的示例方法的流程图;以及
[0006]图4是用于向打印设备提供包括在远程打印请求中的移动设备标识符以授权通过移动设备的直接无线打印的示例方法的流程图。
[0007]如以上所指示的,打印设备可以经由计算机网络接收要打印的内容。例如,打印设备可以是web连接的打印设备,其能够打印经由互联网从远程打印服务接收的内容。在这样的示例中,移动设备(例如智能电话、平板计算机等)可以经由互联网向远程打印服务提供远程打印请求,并且远程打印服务可以向打印设备提供内容,如果请求的发送方被授权经由远程打印服务在打印设备上打印的话。在一些示例中,远程打印请求可以被提供给远程打印服务作为包括内容的电子邮件,或者作为例如应用编程接口(API)功能调用。
[0008]在一些示例中,打印设备还可以能够经由诸如近场通信(NFC)等之类的直接无线通信从移动设备接收要打印的内容。照此,打印设备可以能够经由多个不同的通信信道从移动设备接收要打印的内容。然而,在一些示例中,内容的发送方可能被分离的过程授权以用于每一个信道。例如,可以将移动设备的用户的电子邮件地址添加到使打印设备授权用户经由与电子邮件地址连接的远程打印服务在打印设备上打印的白名单。该电子邮件地址可以经由第一授权过程(例如经由用于远程打印服务的web接口)添加到白名单。
[0009]然而,该过程可能不授权用户经由与移动设备的直接无线通信向打印设备提供内容。在这样的示例中,尽管已经授权用户经由远程打印服务在打印设备上打印,但是可能防止用户经由直接无线通信在打印设备上打印,直到施行针对直接无线通信信道的另一授权过程。利用分离的授权过程来经由不同信道授权在相同打印设备上的打印对于打印设备的用户而言可能是不方便的。
[0010]为了解决这些问题,本文所描述的示例可以使得移动设备在被授权经由远程打印服务对打印设备打印的移动设备用户经由远程打印服务对打印设备打印时,能够被自动地授权用于打印设备上的直接无线打印。
[0011]在本文所描述的示例中,远程打印服务的远程打印服务器可以从移动设备获取远程打印请求,远程打印请求包括第一打印内容,并且标识打印请求发送方、目的地打印设备和与移动设备相关联的移动设备标识符。本文所描述的示例还可以确定所标识的打印请求发送方被授权经由远程打印服务在至少目的地打印设备上打印,并且响应于打印请求发送方被授权的确定,向目的地打印设备提供第一打印内容的打印就绪版本以用于打印。本文所描述的示例还可以在至少移动设备标识符被移动设备经由与第二打印内容相关联的直接无线通信提供到目的地打印设备时,向目的地打印设备提供授权信息以授权由目的地打印设备经由直接无线通信从移动设备接收的至少第二打印内容的打印。
[0012]以此方式,本文所描述的示例可以自动授权移动设备在与移动设备相关联的发送方已经被授权经由远程打印服务在打印设备上打印时经由直接无线通信从打印设备打印。
[0013]现在参照附图,图1是授权经由直接无线通信接收的打印内容的打印的示例计算设备100的框图。如本文所使用的,“计算设备”可以是台式计算机、笔记本计算机、工作站、平板计算机、移动电话、智能设备、服务器、刀片机箱、打印设备或任何其它处理设备或装备。在图1的示例中,计算设备100可能是远程打印服务器100以至少部分地实现远程打印服务。
[0014]在本文所描述的示例中,“远程打印服务”可以是由一个或多个联网计算设备实现以从发送计算设备接收打印请求并且向目的地打印设备提供与请求相关联的内容的服务,其中发送计算设备和打印设备每一个远离实现远程打印服务的(一个或多个)联网计算设备。在本文所描述的示例中,“远离”第二计算设备的第一计算设备可以是与第二计算设备分离并且不直接连接到第二计算设备的第一计算设备,其中第一和第二计算设备可以通过计算机网络访问彼此。如本文所使用的,计算机网络可以包括例如局域网(LAN)、无线局域网(WLAN)、虚拟私人网络(VPN)、互联网等或其组合。在一些示例中,计算机网络可以包括电话网络(例如蜂窝电话网络)。
[0015]在图1的示例中,远程打印服务器100包括处理资源110和编码有指令122,124,126和128的机器可读存储介质120。在一些示例中,存储介质120可以包括附加指令。在一些示例中,指令122,124,126和128以及本文结合存储介质120描述的任何其它指令可以存储在远离计算设备100和处理资源110但是可被它们访问(例如经由计算机网络)的机器可读存储介质上。
[0016]在本文所描述的示例中,处理资源可以包括例如一个处理器或包括在单个计算设备中或者跨多个计算设备分布的多个处理器。如本文所使用的,“处理器”可以是中央处理单元(CPU)、基于半导体的微处理器、图形处理单元(GPU)、配置成检索和执行指令的现场可编程门阵列(FPGA)、适合用于存储在机器可读存储介质上的指令的检索和执行的其它电子电路或其组合中的至少一个。处理资源110可以提取、解码和执行存储在存储介质120上的指令以施行以下描述的功能。在其它示例中,存储介质120的任何指令的功能可以以电子电路的形式、编码在机器可读存储介质上的可执行指令的形式或其组合来实现。
[0017]如本文所使用的,“机器可读存储介质”可以是包含或存储诸如可执行指令、数据等之类的信息的任何电子、磁性、光学或其它物理存储装置。例如,本文所描述的任何机器可读存储介质可以是随机存取存储器(RAM)、易失性存储器、非易失性存储器、闪速存储器、存储驱动器(例如硬盘驱动器)、固态驱动器、任何类型的存储盘(例如致密盘、DVD等)等或其组合中的任一个。另外,本文所描述的任何机器可读存储介质可以是非暂时性的。
[0018]在图1的示例中,指令122可以从移动设备经由任何合适的计算机网络主动获取(例如检索等)或被动地获取(例如接收等)远程打印请求180。远程打印服务器100和移动设备可以经由任何合适的计算机网络通信。如本文所使用的,“移动设备”可以是移动电话、智能设备(例如智能电话)、平板计算机、膝上型计算机或包括能够在不连接到外部电源时为设备供电的便携式能量源(例如电池等)的任何其它计算设备。远程打印请求180可以包括要打印的第一打印内容162并且标识与移动设备相关联的移动设备标识符160。远程打印请求180还可以标识打印请求发送方和目的地打印设备以打印第一打印内容162。在一些示例中,远程打印请求180可以包括第一打印内容162和移动设备标识符160。
[0019]在本文所描述的示例中,移动设备标识符可以是标识移动设备的任何信息。示例移动设备标识符可以包括例如移动设备的国际移动站装备身份(IMEI)号码、序列号或其它产品特定号码、唯一设备ID(UDID)、操作系统(OS)标识符、机器地址(MAC)等或其组合。在一些示例中,移动设备标识符可以是与移动设备相关联的信息,该信息是以下情况中的至少一种:跨移动设备唯一和不可由移动设备的用户更改或更换。
[0020]在一些示例中,远程打印请求180可以包括由移动设备发送的电子邮件(即至少一个电子邮件消息)。在这样的示例中,电子邮件可以包括移动设备标识符160和第一打印内容162,并且可以标识打印请求发送方和目的地打印设备。例如,第一打印内容162可以作为电子邮件的附件而被包括,并且移动设备标识符160可以被包括在电子邮件的标题中(例如在标题的定制元数据中)。在一些示例中,电子邮件可以包括发送方的电子邮件地址(例如电子邮件标题的“来自”字段中的地址),电子邮件地址可以标识打印请求发送方。电子邮件还可以包括与目的地打印设备相关联(例如向其分配)的电子邮件地址(例如电子邮件标题的“去往”字段中的地址等),电子邮件地址可以标识目的地打印设备。
[0021]在其它示例中,远程打印请求180可以包括API功能调用,诸如对远程打印服务的API的打印请求功能的调用。在这样的示例中,API功能调用可以包括第一打印内容162和目的地打印设备,并且可以以任何合适的方式标识打印请求发送方和移动设备标识符160。例如,API功能调用可以包括第一打印内容162、用于目的地打印设备的标识符,以及与打印请求发送方和移动设备标识符160相关联的安全令牌(或任何其它合适的信息)。在这样的示例中,远程打印服务器可以基于安全令牌确定打印请求发送方和移动设备标识符160。在一些示例中,API功能调用可以经由超文本传输协议(HTTP)或任何其它合适的协议被提供给远程打印服务器100。在这样的示例中,指令122可以从移动设备的打印应用获取API功能调用280(作为远程打印请求280)。
[0022]指令124可以确定所标识的打印请求发送方被授权经由远程打印服务在至少所标识的目的地打印设备上打印。例如,远程打印服务可以维护针对所标识的目的地打印设备的经授权发送方的列表(例如白名单)。在这样的示例中,服务器100可以在请求中所标识的发送方包括在列表中时向所标识的目的地打印设备提供在远程打印请求中所接收到的打印内容。在这样的示例中,响应于接收到远程打印请求,指令124可以访问针对所标识的目的地打印设备的白名单并且确定在打印请求中所标识的发送方是否被授权经由远程打印服务在目的地打印设备上打印。在其它示例中,指令124可以确定所标识的打印请求发送方被授权在与远程打印服务相关联的多个打印设备(包括目的地打印设备)上打印。例如,响应于包括在打印请求中的安全令牌是(例如来自安全服务的)有效安全令牌的确定或指示,并且作为响应,指令124可以确定所标识的打印请求发送方被授权在与远程打印服务相关联的多个打印设备(包括目的地打印设备)上打印。
[0023]在图1的示例中,指令124可以确定请求180的所标识的打印请求发送方被授权经由远程打印服务在所标识的目的地打印设备上打印。例如,在其中远程打印请求180是电子邮件的示例中,指令124可以访问针对所标识的目的地打印设备(例如与目的地电子邮件地址相关联)的白名单,确定发送方的电子邮件地址包括在白名单中并且从而确定打印请求发送方被授权经由远程打印服务在目的地打印设备上打印。
[0024]基于打印请求发送方被授权的确定,指令126可以以任何合适的方式使第一打印内容162的打印就绪版本182可用于目的地打印设备以用于打印。在一些示例中,指令126可以通过将打印就绪版本182存储在经由计算机网络可由目的地打印设备访问的储存中,并且向打印设备提供打印设备可以用于检索打印就绪版本182的信息(诸如唯一资源标识符(URI)、唯一资源定位符(URL)或其它任何其它合适类型的地址或引用)来使打印就绪版本182可用。在其它示例中,指令126可以通过向目的地打印设备提供打印就绪版本182来使打印就绪版本182可用。
[0025]在本文所描述的示例中,“打印设备”可以是硬件设备,诸如打印机、多功能打印机(MFP)或至少包括在纸张等上物理地产生(一个或多个)图形表示(例如文本、图像等)的功能的任何其它设备。在一些示例中,MFP可以能够施行多个不同功能的组合,诸如例如打印、影印、扫描、传真等。在本文所描述的示例中,打印设备可以能够通过诸如互联网等之类的计算机网络进行通信。这样的打印设备可以在本文中称为“web连接的”打印设备。
[0026]在本文所描述的示例中,用于给定打印设备的打印内容的“打印就绪”版本可以是以可以由给定打印设备打印的形式的打印内容版本。例如,给定打印设备可以能够打印采用可移植文档格式(PDF)、打印机命令语言(PCL)格式的至少一个版本等中的一个或多个的文档。采用可以由给定打印设备打印的任何这样的格式的文档可以被视为用于该打印设备的文档的“打印就绪”版本。采用不可以由给定打印设备打印的格式(例如文字处理文档格式等)的文档不可以被视为文档的打印就绪版本。在这样的示例中,文档可以在使其可用于打印设备之前被再现(转换等)成针对目的地打印设备的打印就绪格式。在这样的示例中,远程打印服务(例如指令126或与服务器100分离但可被服务器100访问的计算设备)可以再现文档以产生提供给打印设备的打印就绪版本。
[0027]在一些示例中,包括在请求180中的第一打印内容162可能采用针对目的地打印设备的打印就绪格式。在这样的示例中,打印就绪版本182等同于第一打印内容162。在其它示例中,包括在请求180中的第一打印内容162可能不采用针对目的地打印设备的打印就绪格式,并且第一打印内容162可以被再现以产生提供给目的地打印设备的第一打印内容162的打印就绪版本182。
[0028]在图1的示例中,当至少移动设备标识符160由移动设备经由与第二打印内容相关联的直接无线通信提供给目的地打印设备时,指令128可以向目的地打印设备提供授权信息184以授权由目的地打印设备从移动设备经由直接无线通信接收的至少第二打印内容的打印。远程打印服务器100和目的地打印设备可以经由任何合适的计算机网络进行通信。在这样的示例中,指令128可以经由任何合适的计算机网络向目的地打印设备提供授权信息184。
[0029]在本文所描述的示例中,“直接无线通信”可以是可以在移动设备的无线接口与打印设备的无线接口之间直接施行的任何形式的无线通信(例如没有任何居间计算设备、组件等)。直接无线通信的示例可以包括例如近场通信(NFC)、蓝牙、蓝牙低能量(BLE)、自组织WI-FI、WI-FIDIRECT(直接)等。在一些示例中,直接无线通信可以是紧邻(close-proximity)直接无线通信,其可以是任何类型的短程无线通信,具有大约十厘米(10cm)或更小的范围,诸如NFC。在一些示例中,紧邻直接无线通信可以是具有大约四厘米(4cm)或更小的范围的无线通信类型。
[0030]在图1的示例中,由指令128提供的授权信息184可以包括使目的地打印设备授权经由直接无线通信从移动设备与移动设备标识符160一起接收的至少第二打印内容的打印。
[0031]在一些示例中,目的地打印设备可以维护指示与被授权经由直接无线通信在目的地打印设备上打印的移动设备相关联的移动设备标识符的授权列表。在这样的示例中,当目的地打印设备经由直接无线通信与移动设备标识符一起接收打印内容时,目的地打印设备可以针对所提供的移动设备标识符检查授权列表,并且如果所提供的移动设备标识符在授权列表中可以打印打印内容。在这样的示例中,授权信息184可以包括移动设备标识符160。
[0032]在这样的示例中,指令128可以向目的地打印设备提供移动设备标识符160使得目的地打印设备在存储于目的地打印设备的本地存储器中的授权列表中存储移动设备标识符160,以授权与移动设备标识符160相关联的移动设备被授权经由直接无线通信在目的地打印设备上打印。在一些示例中,指令128可以在目的地打印设备的API的API功能调用中向目的地打印设备提供移动设备标识符160以使目的地打印设备在授权列表中存储移动设备标识符160。在一些示例中,响应于指令124确定请求180的所标识的发送方被授权经由远程打印服务在所标识的目的地打印设备上打印,指令128可以向目的地打印设备提供移动设备标识符160以授权相关联的移动设备经由直接无线通信进行打印。
[0033]在其它示例中,当目的地打印设备经由直接无线通信与移动设备标识符一起接收到打印内容时,目的地打印设备可以联系远程打印服务以确定与所提供的移动设备标识符相关联的移动设备是否被授权经由直接无线通信打印。在这样的示例中,目的地可以利用针对授权信息的请求向远程打印服务器100提供所接收到的移动设备标识符。在这样的示例中,指令128可以确定移动设备是否被授权,并且基于确定,指令128可以提供指示(与所接收到的移动设备标识符相关联的)移动设备是否被授权经由直接无线通信在目的地打印设备上打印的授权信息184。在这样的示例中,如果指令128提供指示移动设备被授权的授权信息184,则目的地打印设备可以打印经由直接无线通信与移动设备标识符一起提供的打印内容。如果指令128提供指示移动设备未被授权的授权信息184,则目的地打印设备可以不打印该打印内容。
[0034]在一些示例中,指令122,124,126和128可以是安装包的部分,其在被安装时,可以由处理资源110执行以实现本文结合指令122,124,126和128所描述的功能。在这样的示例中,存储介质120可以是便携式介质,诸如CD、DVD或闪速驱动器,或者由安装包可以从其下载和安装的服务器维护的存储器。在其它示例中,指令122,124,126和128可以是已经安装在包括处理资源110的远程打印服务器100上的一个应用、多个应用或组件的部分。在这样的示例中,存储介质120可以包括存储器,诸如硬盘驱动器、固态驱动器等。在一些示例中,本文结合图1所描述的功能可以与本文结合图2-4中任一个描述的功能组合提供。
[0035]图2是授权在打印设备处打印经由直接无线通信接收的打印内容的示例打印环境200的框图。在图2的示例中,打印环境200包括远程打印服务205、打印设备230和移动设备250。
[0037]在图2的示例中,打印设备230包括引擎232-236。打印设备230的引擎232-236中的每一个可以是硬件和程序的任何组合以实现相应引擎的功能。在本文所描述的示例中,这样的硬件和程序的组合可以以数个不同方式实现。例如,用于引擎的程序可以是存储在非暂时性机器可读存储介质上的处理器可执行指令,并且用于引擎的硬件可以包括执行那些指令的处理资源。在这样的示例中,机器可读存储介质可以存储指令,所述指令在由处理资源执行时,实现引擎232-236。在这样的示例中,打印设备230可以包括存储指令的机器可读存储介质和执行指令的处理资源,或者机器可读存储介质可以是分离的但是可被打印设备230和处理资源可访问。在其它示例中,任何引擎的功能可以以电子电路的形式实现。
[0038]在一些示例中,指令可以是安装包的部分,其在被安装时,可以由处理资源执行以实现引擎232-236。在这样的示例中,机器可读存储介质可以是便携式介质,诸如CD、DVD或闪速驱动器或由安装包可以从其下载和安装的服务器维护的存储器。在其它示例中,指令可以是已经安装在包括处理资源的打印设备230上的一个应用、多个应用或组件的部分。在这样的示例中,机器可读存储介质可以包括诸如硬盘驱动器、固态驱动器等之类的存储器。
[0039]在图2的示例中,打印设备230还包括打印引擎241。打印引擎241可以包括硬件和程序的任何组合以实现本文结合引擎241描述的功能,至少包括在纸张等上物理地产生(一个或多个)图形表示(例如文本、图像等)的硬件。在一些示例中,打印设备230可以包括附加引擎。打印设备230还包括直接无线接口240。在本文所描述的示例中,直接无线接口可以包括硬件和程序的任何组合以至少施行经由直接无线通信与(一个或多个)其它直接无线接口通信的功能,如以上所描述的。
[0040]在图2的示例中,移动设备250可以包括应用252、与移动设备250相关联的移动设备标识符160以及直接无线接口245,如以上所描述的。移动设备标识符160可以是与移动设备250相关联的任何合适的标识符,如以上结合图1所描述的。在一些示例中,应用252可以是任何类型的软件(以编码在机器可读存储介质上并且可由移动设备230的处理资源执行的指令的形式实现)以确定移动设备250的移动设备标识符160并且向远程打印服务205提供远程打印请求280,其包括或以其它方式标识移动设备标识符160。在图2的示例中,远程打印请求280可以包括移动设备标识符160、第一打印内容162、请求发送方的标识164和目的地打印设备的标识166。在图2的示例中,标识166可以标识打印设备230(例如可以与其相关联)。
[0041]如以上结合请求180所描述的,在一些示例中,远程打印请求280可以包括由移动设备提供的电子邮件消息。在这样的示例中,应用252可以是发送电子邮件消息(例如经由简单邮件传输协议(SMTP))的应用,诸如电子邮件客户端等。在这样的示例中,应用252可以(直接或间接地)向远程打印服务205发送电子邮件作为远程打印请求280。在这样的示例中,响应于用户输入,应用252可以创建包括作为对电子邮件的附件的第一打印内容162并且包括移动设备标识符160(例如在电子邮件标题中)的电子邮件请求280,如以上所描述的。在这样的示例中,应用252可以确定移动设备250的移动设备标识符160,并且包括电子邮件请求280中的标识符160。在一些示例中,电子邮件请求280可以,如以上所描述的,包括作为发送方标识164的发送方的电子邮件地址,并且可以包括与目的地打印设备230相关联的电子邮件地址作为打印设备标识166。
[0042]在其它示例中,如以上所描述的,远程打印请求280可以包括对远程打印服务的API的打印请求功能的API功能调用。在这样的示例中,应用252可以是移动设备250的打印应用以向远程打印服务205提供远程打印请求。API功能调用可以经由HTTP或任何其它合适的协议提供给远程打印服务205。在这样的示例中,远程打印请求280可以包括,作为API功能调用的功能调用参数,第一打印内容162,以及目的地打印设备标识166和标识移动设备标识符160和发送方标识164的其它信息(诸如安全令牌,如以上所描述的)。在一些示例中,包括在API功能调用中并且标识移动设备标识符160和发送方标识164的其它信息可以是安全令牌等,如以上结合图1所描述的。在这样的示例中,安全令牌可以与移动设备标识符160和发送方标识164相关联,使得远程打印服务器100例如可以基于(例如来自安全服务的)安全令牌而检索移动设备标识符160和发送方标识164。在一些示例中,安全令牌还可以用于验证。在这样的示例中,指令122可以获取由移动设备250的应用252提供的API功能调用280。
[0043]在图2的示例中,远程打印服务器100和移动设备250可以经由任何合适计算机网络进行通信,并且指令122可以(主动或被动地)经由任何合适的计算机网络从移动设备250获取远程打印请求280。在这样的示例中,指令124可以确定所标识的打印请求发送方(即与标识164相关联)是否被授权经由远程打印服务205在至少所标识的目的地打印设备230(即与标识166相关联)上打印。例如,远程打印服务可以维护针对所标识的目的地打印设备230的经授权发送方的列表102(例如白名单102),如以上结合图1所描述的。在一些示例中,响应于接收到远程打印请求280,指令124可以访问白名单102以确定在打印请求280中(例如通过标识164)标识的发送方是否被授权经由远程打印服务250在目的地打印设备280上打印。在一些示例中,发送方标识164可以不包括在针对打印设备230的白名单120中。在这样的示例中,指令124可以确定所标识的请求280的发送方不被授权经由远程打印服务205在目的地打印设备230上打印,并且可以不向打印设备230提供打印内容162。在其它示例中,指令124可以确定所标识的打印请求发送方被授权在与远程打印服务相关联的多个打印设备(包括目的地打印设备)上打印,如以上结合图1所描述的。
[0044]在图2的示例中,发送方标识164(例如发送方的电子邮件地址)包括在针对打印设备230的白名单102中。在这样的示例中,指令124可以确定所标识的请求280的发送方被授权经由远程打印服务205在目的地打印设备230上打印。在一些示例中,响应于所标识的发送方(与标识164相关联)被授权的确定,指令124可以在设备凭证储存112中存储请求280的移动设备标识符160,设备凭证储存112与远程打印服务器100相关联(例如可被其访问),如以上所描述的。在一些示例中,移动设备标识符160可以存储在与打印设备230相关联的凭证储存112中(例如与针对打印设备230的标识符相关联)以指示移动设备250被授权经由直接无线通信在打印设备230上打印。
[0045]另外,基于打印请求280的发送方被授权经由远程打印服务205在至少打印设备230上打印的确定,指令126可以以任何合适的方式使第一打印内容162的打印就绪版本182可用于目的地打印设备以用于打印,如以上结合图1所描述的。如以上所描述的,当第一打印内容162不是采用用于打印设备230的打印就绪格式时,远程打印服务205可以再现第一打印内容162以生成打印就绪版本182。
[0046]在图2的示例中,打印设备230的远程获取引擎232可以从远程打印服务205获取由远程打印服务205(例如服务器100)从移动设备250接收并且由远程打印服务205确定为来自被授权经由远程打印服务205在至少打印设备230上打印的打印请求发送方的远程打印请求280的第一打印内容162的打印就绪版本182。例如,引擎232可以接收由远程打印服务器100的指令126经由合适的计算机网络提供给打印设备230的打印就绪版本182。在其它示例中,引擎232可以在从例如服务器100获取的地址或其它引用处经由计算机网络从可由打印设备230访问的储存获取打印就绪版本182。在引擎232获取打印就绪版本182之后,打印引擎241可以在诸如纸张等之类的物理介质上打印第一打印内容162的打印就绪版本182。
[0047]如以上结合图1描述的,当至少移动设备标识符160由移动设备250经由与第二打印内容292相关联的直接无线通信提供给打印设备230时,指令128可以向目的地打印设备230提供授权信息184以授权由打印设备230经由直接无线通信290从移动设备205接收的至少第二打印内容292的打印。远程打印服务器100和目的地打印设备230可以经由任何合适的计算机网络进行通信,并且指令128可以经由任何合适的计算机网络向目的地打印设备230提供授权信息184。在图1的示例中,由指令128提供的授权信息184可以包括任何合适的信息以使目的地打印设备授权经由直接无线通信从移动设备与移动设备标识符160一起接收的至少第二打印内容的打印。
[0048]例如,基于指令124确定所标识的请求280的打印请求发送方(即与标识164相关联)被授权经由远程打印服务205在所标识的打印设备230上打印,指令128可以向目的地打印设备230(如图2中所示)提供包括移动设备标识符160的授权信息184。在这样的示例中,指令128可以以授权通过打印设备230经由直接无线通信从移动设备250与至少移动设备标识符160一起接收的至少第二打印内容292的打印的方式向打印设备230提供移动设备标识符160。
[0049]例如,打印设备230可以维护包括与被授权经由直接无线通信在打印设备230上打印的相应移动设备相关联的移动设备标识符的授权列表239。在这样的示例中,当目的地打印设备经由直接无线通信与移动设备标识符一起接收打印内容时,目的地打印设备可以针对所提供的移动设备标识符检查授权列表239,并且如果所提供的移动设备标识符在授权列表239中可以打印打印内容。在一些示例中,授权列表239可以通过包括在打印设备230上(即在打印设备230本地)的至少一个机器可读存储介质来实现。
[0050]在一些示例中,基于指令124确定请求280的发送方(即与标识164相关联)被授权经由服务205在设备230上打印,指令128可以向打印设备230提供移动设备标识符160,使得打印设备230在授权列表239中存储移动设备标识符160以授权与移动设备标识符160相关联的移动设备250经由直接无线通信在目的地打印设备上打印。例如,指令128可以在打印设备230的API的API功能调用中向打印设备230提供移动设备标识符160以使打印设备230在授权列表239中存储移动设备标识符160。在一些示例中,指令128可以基于指令124确定请求280的发送方被授权经由服务205在设备230上打印,通过向打印设备230提供移动设备标识符160与第一打印内容162的打印就绪版本182来向打印设备230提供移动设备标识符160。
[0051]在其它示例中,指令128可以基于指令124确定请求280的发送方被授权经由服务205在设备230上打印,通过在从打印设备230接收到第一打印内容162(之前基于确定而被提供给打印设备230)由打印设备230成功打印的指示之后向打印设备230提供移动设备标识符160来向打印设备230提供移动设备标识符160。在这样的示例中,指令128可以基于指令124确定请求280的发送方被授权经由服务205在设备230上打印,并且基于第一打印内容162被成功打印的指示而向打印设备230提供移动设备标识符160。
[0052]参照图2的打印设备230,在其中指令128向打印设备230提供移动设备标识符160的示例中,打印设备230的远程获取引擎232可以从远程打印服务器100获取(例如接收)与移动设备250相关联并且经由远程打印请求280标识(例如包括在其中)的移动设备标识符160。在这样的示例中,存储引擎234可以在打印设备230的本地存储器中(例如机器可读存储介质中)的授权列表239中存储所获取的移动设备标识符160。在这样的示例中,通过在授权列表239中存储移动设备标识符160,打印设备230可以授权移动设备250(与标识符160相关联)经由直接无线通信在打印设备230上打印。
[0053]在图2的示例中,通信引擎236可以经由移动设备250与打印设备230之间的直接无线通信290从移动设备250主动获取(例如检索等)或被动获取(例如接收等)第二打印内容292和移动设备标识符160。在一些示例中,第二打印内容292可以与移动设备标识符160一起从移动设备250经由直接无线通信提供给打印设备230。在一些示例中,第二打印内容292和移动设备标识符160可以从移动设备250经由一个或多个消息提供给打印设备230,一个或多个消息经由直接无线通信传送。在这样的示例中,移动设备标识符160可以经由直接无线通信提供给与第二打印内容292相关联的打印设备230。例如,移动设备标识符160和第二打印内容292可以在相同通信、通信会话、连接等中或者以将第二打印内容292与移动设备标识符160链接或关联的任何其它方式提供给打印设备230。
[0054]响应于接收到至少移动设备标识符160,授权引擎235可以确定经由直接无线通信与第二打印内容292一起(或与其相关联地)获取的至少移动设备标识符160是否存储在授权列表239中。在图2的示例中,移动设备标识符160存储在授权列表239中。在这样的示例中,响应于接收到至少移动设备标识符160,授权引擎235可以确定经由直接无线通信与第二打印内容292一起(或与其相关联地)获取的至少移动设备标识符160存储在授权列表239中。响应于该确定,授权引擎235可以使打印引擎241打印第二打印内容292。
[0055]在本文所描述的一些示例中,独立于(即没有)在移动设备标识符160的直接无线通信之后对打印设备的任何另外的输入,授权引擎235可以基于授权列表239中移动设备标识符160的存在而确定提供移动设备标识符160的移动设备250被授权经由直接无线通信在打印设备230上打印。以此方式,本文所描述的示例可以简化变成被授权利用远程打印服务经由直接无线通信进行打印的过程。
[0056]在一些示例中,打印设备230可能以针对打印设备232的打印就绪格式从移动设备250接收第二打印内容292。在其它示例中,打印设备230可能以不是针对打印设备232的打印就绪格式的格式从移动设备205接收第二打印内容292。在这样的示例中,打印设备230的再现引擎233可以将所获取的第二打印内容292再现成针对打印设备230的打印就绪格式。在这样的示例中,打印引擎241可以响应于移动设备标识符160包括在授权列表239中的确定而打印第二打印内容292的打印就绪版本182。
[0057]在一些示例中,授权引擎235可以防止打印设备230打印经由直接无线通信与不存储在授权列表239中的另一移动设备标识符一起(或与其相关联地)接收的第三打印内容。在这样的示例中,响应于获取到其它移动设备标识符,引擎235可以确定其它移动设备标识符不存在于授权列表239中,并且响应于该确定,防止打印设备230打印经由直接无线通信与其它移动设备标识符一起(或与其相关联地)接收的第三打印内容。
[0058]在其它示例中,当打印设备230经由直接无线通信与移动设备标识符相关联地接收到打印内容时,打印设备230可以联系远程打印服务205以确定提供移动设备标识符的移动设备是否被授权经由直接无线通信在打印设备230上打印。在这样的示例中,响应于通信引擎236经由直接无线通信290从移动设备250获取到与第二打印内容292相关联的移动设备标识符160,授权引擎235可以向远程打印服务205提供请求以确定经由直接无线通信与移动设备标识符160相关联地接收的第二打印内容292的打印是否被授权。
[0059]在这样的示例中,参照远程打印服务器100,指令128可以从打印设备230获取(例如接收)请求以确定经由直接无线通信与移动设备标识符160相关联地由打印设备230接收的第二打印内容292的打印是否被授权。
[0060]响应于该请求,指令124可以确定移动设备标识符160是否在与远程打印服务器100相关联的设备凭证储存112中与打印设备230相关联。在图2的示例中,作为响应于远程打印请求102通过指令124基于发送方标识164包括在白名单102中的之前确定而存储在储存112中的结果,移动设备标识符160在设备凭证储存112中与打印设备230相关联。在这样的示例中,响应于移动设备标识符160在设备凭证储存112中与打印设备230相关联的确定,指令128可以向打印设备230提供指示(即授权信息184指示)经由直接无线通信接收的第二打印内容292的打印被授权。响应于该指示,打印设备230的授权引擎235可以使打印引擎241打印第二打印内容292。在其中移动设备标识符160在设备凭证储存112中不与打印设备230相关联的示例中,指令128可以向打印设备230提供指示第二打印内容292的打印未被授权的授权信息184,并且作为响应,打印设备230的授权引擎235可以防止打印设备230(即打印引擎241)打印第二打印内容292。
[0061]在其它示例中,移动设备经由直接无线通信打印的授权可以基于移动设备标识符和移动设备用户标识符二者。以此方式,移动设备的(一个或多个)特定用户可以被授权经由直接无线通信在打印设备上打印,而不是给定移动设备的任何用户。例如,远程打印请求280可以此外包括与移动设备250相关联的移动设备用户标识符,其可以是标识发起请求280的移动设备250的用户的任何合适信息。在这样的示例中,基于打印请求280的发送方被授权经由远程打印服务205在打印设备230上打印的确定,指令124可以存储移动设备用户标识符和在凭证储存112中与打印设备相关联的移动设备标识符160二者。
[0062]而且,在一些示例中,基于发送方被授权的确定,指令128可以向目的地打印设备230提供移动设备标识符160和移动设备用户标识符以授权由打印设备230经由直接无线通信从移动设备250接收的与移动设备标识符160和移动设备用户标识符相关联的打印内容的打印。在这样的示例中,远程获取引擎232可以从远程打印服务器100获取与移动设备250相关联并且包括在远程打印请求280中的移动设备用户标识符。存储引擎234可以在授权列表239中与移动设备标识符160相关联地存储所获取的移动设备用户标识符。
[0063]在这样的示例中,通信引擎236可以经由移动设备250与打印设备230之间的直接无线通信从移动设备250获取与第二打印内容292相关联的移动设备用户标识符与移动设备标识符160二者。在这样的示例中,授权引擎235可以响应于移动设备用户标识符与移动设备标识符160相关联地存储在授权列表239中的确定而使打印引擎241打印第二打印内容292。移动设备用户标识符可以等同于或不同于发送方标识164。在一些示例中,发送方标识164可以用作移动设备用户标识符。
[0064]参照图2的远程打印服务器,在一些示例中,指令122可以(主动或被动地)获取请求290以移除打印请求发送方(与标识164相关联)经由远程打印服务205在打印设备230上打印的授权。在这样的示例中,响应于请求290,指令128可以指示打印设备230从授权列表239移除移动设备标识符160(或移动设备标识符160和相关联的移动设备用户标识符)。作为响应,打印设备230的引擎234可以从授权列表239移除移动设备标识符160(或移动设备标识符160和相关联的移动设备用户标识符)。在这样的示例中,远程打印服务205可以存储发送方标识164与移动设备标识符160(在一些示例中,以及移动设备用户标识符)之间的关联,使得移动设备标识符160(在一些示例中,以及移动设备用户标识符)可以响应于移除与标识164相关联的打印请求发送方用于在打印设备230上打印的授权的请求而从授权列表239被移除,如以上描述的。在一些示例中,本文结合图2描述的功能可以与本文结合图1和3-4中任一个描述的功能组合提供。
[0065]图3是用于向打印设备提供移动设备标识符以授权通过移动设备的直接无线打印的示例方法300的流程图。尽管以下参照以上描述的图1的服务器100来描述方法300的执行,但是可以利用用于方法300的执行的其它合适系统。此外,方法300的实现不限于这样的示例。
[0066]在方法300的305处,至少部分地实现远程打印服务的远程打印服务器的指令122可以从移动设备获取远程打印请求180,远程打印请求180包括第一打印内容162并且标识打印请求发送方、目的地打印设备和与移动设备相关联的移动设备标识符160。在310处,指令124可以确定所标识的打印请求发送方被授权经由远程打印服务在至少目的地打印设备上打印。
[0067]在315处,响应于确定,指令126可以向目的地打印设备提供第一打印内容162的打印就绪版本182以用于打印。在320处,指令126可以接收第一打印内容160由目的地打印设备成功打印的指示。在325处,响应于指示,指令128可以向目的地打印设备提供移动设备标识符160以授权由目的地打印设备经由紧邻直接无线通信从移动设备与移动设备标识符一起接收的至少第二打印内容的打印。
[0068]尽管图3的流程图示出一定功能的具体施行次序,方法300不限于该次序。例如,在流程图中接连示出的功能可以以不同次序施行,可以同时或者部分同时地或者其组合地执行。在一些示例中,本文结合图3描述的功能可以与本文结合图1-2和4中任一个所描述的功能组合提供。
[0069]图4是用于向打印设备提供包括在远程打印请求中的移动设备标识符以授权移动设备的直接无线打印的示例方法400的流程图。尽管以下参照以上描述的图2的服务器100描述方法400的执行,但是可以利用用于方法400的执行的其它合适系统。此外,方法400的实现不限于这样的示例。
[0070]在方法400的405处,至少部分地实现远程打印服务的远程打印服务器的指令122可以从移动设备获取远程打印请求180,远程打印请求180包括第一打印内容162并且标识打印请求发送方、目的地打印设备和与移动设备相关联的移动设备标识符160。
[0071]在410处,指令124可以确定所标识的打印请求发送方是否被授权经由远程打印服务在至少目的地打印设备上打印。在图4的示例中,远程打印请求可以包括电子邮件并且可以包括移动设备标识符,电子邮件包括打印请求发送方的电子邮件地址,电子邮件地址可以标识请求180的发送方。在410处,指令124可以基于打印请求发送方的电子邮件地址是否包括针对目的地打印设备的白名单102中来确定所标识的打印请求发送方是否被授权经由远程打印服务在目的地打印设备上打印。
[0072]如果发送方的电子邮件地址不包括在白名单102中,则发送方未被授权并且方法400可以进行到415,其中指令124可以拒绝远程打印请求180使得第一打印内容162不在目的地打印设备处打印。如果在410处确定发送方的电子邮件地址包括在白名单102中,并且因而被授权,则方法400可以进行到420。在420处,响应于确定,指令126可以向目的地打印设备提供第一打印内容162的打印就绪版本182以用于打印。
[0073]在425处,响应于确定,指令124可以在设备凭证储存122中并且与远程打印服务器相关联地存储移动设备标识符160。在430处,指令126可以接收第一打印内容160由目的地打印设备成功打印的指示。在435处,响应于指示,指令128可以向目的地打印设备提供移动设备标识符160以授权由目的地打印设备进行经由紧邻直接无线通信(诸如NFC)从移动设备与移动设备标识符一起接收的至少第二打印内容的打印。
[0074]尽管图4的流程图示出一定功能的具体施行次序,但是方法400不限于该次序。例如,在流程图中接连示出的功能可以以不同次序施行,可以同时或部分同时地或者其组合地执行。在一些示例中,本文结合图4描述的功能可以与本文结合图1-3中任一个描述的功能组合提供。