CN104620552B - Use the information sharing of the label received by short-range communication - Google Patents

Abstract

The source data being stored on source device can be shared with other equipment.The processing of shared source data may include：Promote to carry out communication associated with source data based on the first communication protocol between the first equipment and another equipment.Promote to receive the first label associated with source data.First label can be encoded, so as to be communicated using short-range communication (NPC) agreement.It, can be by the first marker passing to the second equipment less than 5 feet at a distance from the first equipment, so that the second equipment can access source data using the second communication protocol by using NPC agreements.The NPC agreements are wireless communication protocols, and support to execute automatic connection between at least two equipment of the distance less than 5 feet.First and second equipment is the equipment for enabling NPC.

Description

Information sharing using tags received via short-range communication

technical field

The technical subject matter relates generally to information sharing, and more particularly to information sharing using short-range communications.

Background technique

With the advancement of network technology and the rapid development of many social networks (such as Facebook, LinkedIn, MySpace, Twitter, Google+, ...), people can use various methods to share information. For example, with e-mail, we can attach files to be shared, including numerous documents and media files (such as image files, audio files, video files, etc.) Uniform Resource Locators (URLs) for online resources to provide links to online information resources. Information sharing through social networking is also very common and can be effectively used for multiple purposes, for example, people can easily share various media files and even inform their peers about their whereabouts and the type of activities they are enjoying.

Money can be transferred from one account to another by using a mobile phone. A mobile phone can be used as a credit card reader to transfer money from one credit card holder's account to an account associated with another. In addition, credit card holders can set up mobile phones to store credit card information, and can use the mobile phone instead of the credit card to conduct transactions with machines such as automated teller machines (ATMs).

Contents of the invention

In one aspect of the present disclosure, a non-transitory machine-readable medium may include stored thereon instructions executable/executable by one or more processors to perform a method that causes sharing of source data. method. The method may include supporting communication between the first device and the remote device based on a first communication protocol. The communication can be associated with the source data and can be based on detecting the presence of the second device within 5 feet of the first device. The method may cause receiving a first marker associated with source data. By causing encoding of the first indicium, the communication may be performed using a near field communication (NPC) protocol. Using the NPC protocol, communication of the first token to a second device within 5 feet of the first device may be facilitated. If the first token is not used, the second device may not be able to access the source data. The NPC protocol is different from the first and second communication protocols, and the first communication protocol and the second communication protocol may be the same or different. The data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol or the data transmission rate supported by the second communication protocol. And the NPC protocol may be a wireless communication protocol that supports automatic connection between at least two devices within a distance of 5 feet. The first device may be an NPC-enabled device adapted to detect the presence of a second device within 5 feet of the first device, which may be a communication endpoint device.

In another aspect of the present disclosure, a non-transitory machine-readable medium may include stored thereon instructions executable by one or more processors to facilitate performing a method that causes sharing of source data. method. The method may include causing receipt of a marker associated with the source data. Here it is possible to cause the tag to be encoded to enable communication using the Near Field Communication (NPC) protocol. Using a near field communication (NPC) protocol, there may be provided a process of communicating the marker to a second device within a distance of 5 feet from the first device to enable the second device to access the source data using the communication protocol. If the tag is not used, the second device may not be able to access the source data.

The NPC protocol may be a wireless communication protocol that supports automatic connection between at least two devices within a distance of 5 feet. The first device may be an NPC-enabled device adapted to detect the presence of the second device within a range of 5 feet from the first device, and the marker may be a non-public marker.

In another aspect of the present disclosure, an apparatus for facilitating sharing of source data may include a processor operable to cause receipt of indicia associated with source data stored in the apparatus or otherwise. The processor is operable to cause the indicia to be encoded to enable communication using a near field communication (NPC) protocol. The NPC interface is operable to provide the process of communicating the marker to a first device within 5 feet of the apparatus using the NPC protocol to enable the first device to access source data using a communication protocol. If the tag is not used, the first device may not be able to access the source data. The data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the communication protocol.

The NPC protocol may be a wireless communication protocol that supports automatic connection between two or more devices within 5 feet of each other. The apparatus may include an NPC-enabled device adapted to detect the presence of the first device within 5 feet of the apparatus, and the source data may be non-public data.

In another aspect of the present disclosure, a method of facilitating sharing of source data may include supporting communication between a first device and a remote device based on a first communication protocol. The communication can be associated with the source data and can be based on detecting the presence of the second device within 5 feet of the first device. Receiving a first marker associated with source data is caused. Encoding the first token is caused to enable communication using a Near Field Communication (NPC) protocol. Using the NPC protocol, the communication of the first token to the second device within 5 feet of the first device is caused to enable the second device to access the source data using the second communication protocol. If the first token is not used, the second device may not be able to access the source data. The NPC protocol may be different from the first and second communication protocols, and the first communication protocol and the second communication protocol may be the same or different. The data transmission rate supported by the NPC protocol is neither greater than the data transmission rate supported by the first communication protocol, nor greater than the data transmission rate supported by the second communication protocol. The NPC protocol may be a wireless communication protocol that supports automatic connection between at least two devices within a distance of 5 feet. The first device may be an NPC-enabled device adapted to detect the presence of the second device within a range of 5 feet from the first device, and the first device may be a communication endpoint device.

In another aspect of the present disclosure, a method of facilitating sharing of source data may include facilitating receipt of indicia associated with the source data. The tag is caused to be encoded to enable communication using a Near Field Communication (NPC) protocol. By using a near field communication (NPC) protocol, the marker can be facilitated to be communicated to a second device within 5 feet of the first device to enable the second device to access the source data using a certain communication protocol. If the tag is not used, the second device may not be able to access the source data. The NPC protocol may be a wireless communication protocol that supports automatic connection between at least two devices within a distance of 5 feet. The first device may be an NPC-enabled device adapted to detect the presence of the second device within a range of 5 feet from the first device, the marker being a non-public marker.

In another aspect of the present disclosure, a non-transitory machine-readable medium includes stored therein instructions executable by one or more processors to perform a method of causing sharing of source data, Including causing receiving, on the first device, the indicia associated with the source data from the second device within a distance of no more than 5 feet from the first device by using a near field communication (NPC) protocol. The method may support generating the first indicia based on detecting the presence of the first device within 5 feet of the second device. The first marker may be an encoded first marker for short-range communication. The first marker may be a non-public marker and may be based on source data to be shared. The process of receiving the first indicia may be based on said detection process. Decoding of the first token can be caused here. Furthermore, communication based on the first communication protocol and directed to the third device can be provided in order to download the source data using the decoded first signature. The first device may be an NPC enabled device having an NPC interface to allow the second device to detect the presence of the first device when the first device is within 5 feet of the second device. The second device may be an NPC-enabled device, and the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol. The two or more NPC devices are within 5 feet of each other.

In another aspect of the present disclosure, an apparatus for facilitating the sharing of source data may include being operable to cause receiving a message associated with the source data from a first device within 5 feet of the apparatus using the NPC protocol. The first marked processor. The first indicium may be based on detecting the presence of the first device within 5 feet of the apparatus, and the first indicia may be a first indicia encoded for short-range communication. The first indicia may be a non-public number plate and may be based on source data to be shared. The processor is operable to cause decoding of the first indicia. The processor is operable to provide communication based on the first communication protocol to the second device for downloading source data using the decoded first indicia. The apparatus may be an NPC-enabled device having an NPC interface to allow the first device to detect the presence of the apparatus when the apparatus is within 5 feet of the first device. The first device may be an NPC-enabled device. In addition, the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol. The NPC protocol may be a wireless communication protocol that supports automatic connection between at least two devices within a distance of 5 feet.

In another aspect of the present disclosure, a method of facilitating the sharing of source data may include: on a first device, facilitating, by using a near field communication (NPC) The second device receives a tag associated with the source data. The NPC protocol may support the process of generating the first indicia based on detecting the presence of the first device within 5 feet of the second device. The first marker may be a coded first marker for short-range communication, and may be a non-disclosure marker. The first signature may be based on the source data to be shared, wherein the process of receiving the first signature may be based on the detection process. Decoding of the first token can be caused here. Furthermore, communication based on the first communication protocol and directed to the third device can be provided in order to download the source data using the decoded first signature. The first device may be an NPC enabled device having an NPC interface to allow the second device to detect the presence of the first device when the first device is within 5 feet of the second device. The second device is an NPC-enabled device, and the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol. The NPC protocol may be a wireless communication protocol that supports automatic connection between two or more devices within 5 feet of each other.

It should be understood that in the present disclosure, various configurations of the present technical subject matter are shown and described as examples, from which those skilled in the art can easily understand the various configurations of the present technical subject matter. In addition, it should be realized that the subject technology is capable of other different configurations and its several details are capable of modifications in other different respects, all without departing from the scope of the subject technology. Accordingly, the Summary, Drawings, and Detailed Description are to be regarded as illustrative in nature and not restrictive.

Description of drawings

1A-1D are conceptual block diagrams pertaining to examples of systems for sharing information using near field communication (NPC) protocols.

2A-2C are conceptual block diagrams pertaining to examples of systems for sharing information using the NPC protocol.

3A-3B are example diagrams of tags that include metadata associated with source data shared using the NPC protocol.

Figure 4 is an example block diagram of source data that can be shared using the NPC protocol.

5 is a conceptual block diagram of an example of devices that share information using the NPC protocol.

6 is a conceptual block diagram of an example of a device that receives shared information using the NPC protocol.

7A-7C are flowcharts illustrating example methods of sharing information using the NPC protocol.

8A-8B are flowcharts illustrating example methods of sharing information using the NPC protocol.

9A-9B are flowcharts illustrating example methods of downloading source files using information shared based on the NPC protocol.

10 is a conceptual block diagram of an example of a device or server.

11 is an example block diagram illustrating an apparatus for sharing information using the NPC protocol.

12 is an example block diagram illustrating an apparatus for sharing information using the NPC protocol.

13 is an example block diagram illustrating an apparatus for sharing information using the NPC protocol.

Detailed ways

The detailed description set forth below is intended to describe various configurations of the subject technology, not the only configurations in which the subject technology may be practiced. The drawings incorporated herein constitute a part of the Detailed Description. The detailed description includes specific details for a thorough understanding of the technical subject matter. It will be apparent, however, to one skilled in the art that the subject technology may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the technical subject matter. Also, for ease of understanding, the same components are labeled with the same part numbers.

Typically, email or one or more social networks are used to share information between devices. Near Field Communication (NFC) may be used to communicate certain information between multiple devices. For example, for credit card transactions, a handheld device such as a mobile phone can be used as a credit card substitute, and credit card information can be exchanged between the mobile phone and an automated teller machine (ATM). In another example using NFC, two handheld devices containing the necessary NFC hardware and applications can exchange business card information between them. The information shared in such NFC exchanges is usually limited to information held on the first device (such as credit card or business card information held on a mobile phone), and this information is transferred directly to the second device. The size of the data file transferred is limited by the limited data rate of the available NFC technology (e.g. 106 kbit/s-424 kbit/s currently) and the fact that the two devices remain in contact or are in close proximity to each other (e.g. less than 20 cm or less). to 5 cm) for the actual duration.

In one aspect of the subject technology, the source data for sharing between the first and second devices can be stored on the remote device and have a desired size not limited by aspects of the subject technology. The source data types are likewise not limited with respect to the subject technology. For example, the source data may include: a data file containing media data, connection setting information, device management information, device configuration information, etc., wherein the second device may use a token to download these source data from the remote device, so The token is communicated from the first device to the second device using a Near Field Communication (NPC) protocol. The NPC protocol facilitates communication between two devices that are physically within approximately 5 feet of each other, and the two devices can connect automatically without user intervention or input, and the time to establish a connection is fast (e.g., less than 1 second). In one example, the NPC does not work beyond 5 feet, so if devices are separated from each other by more than 5 feet, the devices will not be able to detect each other and will not be able to communicate with each other using the NPC protocol. Data transmission rates in the NPC protocol may vary with technology, are not limited by aspects of the present technical subject matter, and may include, but are not limited to, data rates applicable to the NPC protocol.

1A-1D are conceptual block diagrams of examples of systems that share information using the NPC protocol. Systems 100A-100B include a first device 110 (hereinafter referred to as "device 110"), one or more second devices 120 (hereinafter referred to as "device 120"), and one or more remote devices 130 and 140 . Device 110 and device 120 may include handheld devices (eg, mobile phones, personal digital assistants (PDAs), tablet computers, laptop computers, etc.). Remote devices 130 and 140 may include servers, including cloud servers, desktops or portable devices such as laptops, tablets, personal digital assistants (PDAs), mobile phones, and the like. In one aspect, a "remote" device or a device located "remote" from a system or other device may be a device that is not directly connected to the system or other device. For example, remote devices 130 and 140 are located remotely from devices 110 and 120 because remote devices 130 and 140 are not directly connected to devices 110 and 120, but may be indirectly connected via a network, which may include, for example, other server or the Internet. In particular, device 120 may not be authorized to access remote devices 130 and 140 .

A user of device 110 may decide to share source data 135 stored in the source device with device 120 or other devices. In one aspect, the source device may be a remote device, such as one or more remote devices 130 and 140 or one or more other remote devices. In another aspect, the source device may be a local device such as device 110 or another local device. In the case where the source device is a remote device, once the user of the device 110 decides to share the source data 135 stored in the source device with the device 120, the device 110 can request and obtain a process ( Tag 150) associated information (eg metadata). Device 110 may encode token 150 to be able to communicate token 150 using the NPC protocol, and device 110 may communicate token 150 to device 120 using the NPC protocol. For example, a user of a first device 110 may place device 110 in close proximity to device 120 (eg, a distance of a few inches or less than 5 feet) in order to be able to transfer marker 150 from device 110 to device 120 . Device 120 may then use token 150 to gain authorized access to remote device 130 and may download source data 135 (see FIG. 1B ).

In one aspect, once marker 150 is delivered to device 120, device 110 no longer needs to be in close proximity to device 120, devices 110 and 120 can be separated from each other, for example, by more than 5 feet, and device 120 can still use a method as described herein. One or more different communication protocols to obtain/download source data.

In the case where device 110 is the source device (for simplicity, no relevant arrows are shown in FIG. , the token 150 can be easily accessed and encoded so that it can be communicated to the device 120 using the NPC protocol. Device 120 may then use marker 150 to download source data 135 from device 110 (for simplicity, the associated arrow is not shown in FIG. 1B ). In both cases, device 120 may download source data 135 using one or more communication protocols, such as Point-to-Point (P2P) protocol, Interactive Connection Establishment (ICE) protocol, Session Initiation Protocol, Bluetooth protocol (BT ), Wireless Fidelity (WiFi) protocol, Extensible Messaging and Presence Protocol (XMPP), push protocol or non-industry standard communication protocol. If the source data is small enough, the NPC protocol is also available. When downloading source data 135, device 120 need not be in close proximity to device 110 unless the source data 135 is downloaded using the NPC protocol.

In one aspect, device 120 may comprise a mobile device provided to new employees in a business entity (e.g., company, business, organization, business, etc.), device 110 may be for use by information technology (IT) personnel in the business entity Mobile devices. As long as the IT staff puts the device 110 near each new employee's device 120, it can transmit the necessary information for setting and configuring the new employee's device 120, and even execute the setting and configuration process of the device 120 by passing commands, Device 110 may thus be used to set up or configure device 120 for numerous new employees. IT personnel can also use the same technique to update information on employee devices 120 when necessary. Configuration of device 120 may include providing authentication and connection information for connecting to a business unit's private network, servers, and other computers. In addition, IT personnel may also use device 110 to deliver files to device 120 using the NPC protocol, the files including metadata associated with source files located at device 110 or remote device 130 . As will be described herein, the new employee may use the metadata and access device 110 by using Bluetooth or WiFi, or may also access device 130 by using WiFi or a proxy server.

In another aspect, remote devices 130 and 140 may represent multiple computing devices or servers in a business entity. IT personnel may want to enable one or more users of device 120 (e.g., new hires such as IT technicians) to be able to log in to one or more remote devices 130 and 140 and perform a number of operations, such as This may be to access files and perform device settings, configure the device, or perform other activities on either remote device 130 or 140 . The IT personnel may place the device 110 in proximity to the IT technician's device 120 and may transmit the token 150 to the device 120 using the NPC protocol. The token 150 may authorize the user of the device 120 to access the remote devices 130 and/or 140 .

In one aspect, token 150 may be requested and obtained from a remote device, such as remote device 130 . Device 120 may use token 150 to access device 130 and may download source data 135 . 1A-1D show source data 135 stored in remote device 130 for simplicity, source data 135 may generally be stored in one or more other remote devices 140, and tags 140 may be provided for Access information connected to the device 140 holding the source data 135 , and download permission for downloading the source data 135 . For simplicity, only one device 120 is shown in FIG. 1B . If there are multiple devices 120, for each device 120, the device 110 requests and receives from the remote device 130 a corresponding token 150, which may include details of the device 120, and is expiry.

In systems 100C and 100D, devices 110 and 120 are coupled to remote devices 130 and 140 (which may be behind a firewall) via a proxy server 160 (hereinafter referred to as "proxy 160"). The proxy 160 can establish various modes of communication (eg, P2P communication through the ICE protocol) via a network (eg, the Internet) between devices that cannot otherwise be directly contacted with each other. Correspondingly, as shown in FIG. 1C , device 110 may request and acquire information (such as tag 150 ) related to device 120 accessing source data 135 from remote device 130 through proxy 160, and may use the NPC protocol as described above. To pass the token 150 to the device 120. Device 120 may then access remote device 130 and/or 140 via proxy 160 by using token 150 (only one device 120 coupled to remote device 140 via proxy server 160 is shown in FIG. 1D for simplicity). If source data 135 is stored in device 110 (relative arrow not shown in FIG. 1D for simplicity), device 120 may access source data 135 via proxy 160 or using other communication protocols such as BitTorrent. Device 120 may not need to be in close proximity to device 110 while source data 135 is being downloaded.

2A-2C are conceptual block diagrams of examples of systems 200A, 200B, and 200C that share information using the NPC protocol. System 200A includes device 110 , one or more devices 120 , network 150 , remote device 130 , server 230 , and cloud server 240 . In one aspect, device 110 may instruct remote device 130 to transmit source data 135 in FIG. 1 to another remote device, such as server 230 or cloud server 240 . Device 110 may then request and obtain a real-time created token (eg, token 150 ) for each device 120 from remote device 130 . Device 110 may communicate token 150 to each device 120 using the NPC protocol. The device 120 can be coupled to the remote device 130 , the server 230 and the cloud server 240 via the network 250 . Indicia 150 may include metadata that may include information enabling device 120 to connect to any server 230 or cloud server 240 that received source data 135 transmitted by remote device 130 , and to download source data 135 .

To access the source data, each device 120 (only one device 120 is shown in FIG. 2B for simplicity) can use the metadata contained in the tag 150 and connect to either server 230 or cloud server 240 via the network 250, and Download source data 135 . As an example, the network 250 may include any one or more of the following networks: personal area network (PAN), local area network (LAN), campus network (CAN), metropolitan area network (MAN), wide area network (WAN), broadband network (BBN), the Internet, and more. Furthermore, the network 250 may include, but is not limited to, any one or more topological structures, including a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree or hierarchical network, etc. .

In one example, the system 200C includes a device 210 coupled via a network 250, one or more devices 220, a web server 260 (eg, associated with pocketcloud.com), a remote server (eg, a local access translation (NAT) traversal server) and source device 280 (optional). Device 210 may receive marker 150 in FIGS. 1A-1D from remote server 270 (or origin device 280 ) via network 250 . In one aspect, source data 135 may be stored in device 210 , and device 110 may generate markup 150 . As noted above, device 210 may encode indicia 150 so that indicia 150 can be communicated to one or more devices 220 via the NPC protocol. Device 220 may use token 150 to access source device 280 or remote device 270 via network 250 to obtain source data 135 . If the source data 135 is saved in the device 210, the tag 150 includes access information associated with the device 210, and the device 220 can access the device 210 using a communication protocol such as BT protocol, P2P protocol, and the network 250 or other communication modes.

In some aspects, indicia 150 may be encoded in the form of a Uniform Resource Locator (URL) (e.g., HTTPURL) to allow device 220 to access source data 135 via the website represented by the URL in indicium 150 (e.g., pocketcloud.com) . The HTTP URL can be launched by any web browser without any special application. The HTTP URL may point to a web application that contains the necessary JavaScript code to detect whether an appropriate application (eg, a remote access application or a PocketCloud application) is installed locally on the device 220 . If a native application is installed on device 220, the web browser can launch the native application. The local application may initiate a download of source data 135 from, for example, source device 280, remote device 270, or device 210 in accordance with information encoded in indicia 150, wherein the information encoded in indicia 150 includes identification information of the device that stored source data 135 . If the application is not installed locally on device 220, the web browser can communicate back to the web server (e.g., web server 260) and request the web server to send data from the device (e.g., source device 280, remote device 270, or One of the devices 210) obtains the source data 135. Doing so may allow the web browser to download files from the web server 260 immediately without requiring a web application (eg, a native application).

3A-3B are illustrations of examples of tags 150 that include metadata associated with source data 135 in FIG. 1A shared using the NPC protocol. As noted above, source data 135 to be shared by a user of device 110 in FIG. 1A with a user of device 120 in FIG. 1A may be stored in remote device 130 or 140 of FIGS. 1A-1D . For this case, markup 150 may include a plurality of metadata. For example, indicia 150 may include information associated with source devices, as well as other information, such as with respect to any source device that holds source data 135 (e.g., device 130 or 140, device 110, or devices 270, 280, and 220 in FIG. 2C ). Linked identifier 310 and authentication information 320. Additionally, marker 150 may also include information related to source data 135 , such as identifier 330 and path 340 . Identifier 330 may identify a file containing source data 135 among the plurality of files, and path 340 may display a path in the file system of the source device to the file containing source data 135 . Indicia 150 can be encoded in the form of a URL 342 (eg, an HTTP URL) that can be launched by any web browser without requiring any special application.

In another scenario discussed above in connection with FIGS. 2A-2B , source data is transferred from device 130 of FIGS. 2A-2B to one or more remote servers (eg, server 230 or cloud server 240 of FIGS. 2A-2B ). In this case, indicia 150 may include information related to the remote server as well as other information, such as identifier 350 and authentication information 360 associated with any server 230 or cloud server 240 holding source data 135 . Additionally, marker 150 may also include information related to source data 135 , such as identifier 370 and path 380 . Identifier 370 can identify a file containing source data among files stored on a remote server (e.g., server 230 or cloud server 240), while path 380 can indicate a path to a file containing source data 135 in the remote server's file system . The token 150 may be issued by the remote device 130 with an expiration time after which the remote device 130 will no longer recognize the token 150 as valid. Additionally, token 150 may also uniquely represent or be uniquely associated with one or more of: source data 135 , device 120 , user of device 120 , time associated with creation or use of token 150 . In one aspect, token 150 is generated based on or as a function (e.g., a hash function) of one or more of: source data 135, identification of device 120, identity of user of device 120, and token 150 associated with the time of creation or use. Indicia 150 may be a non-disclosed unique/unique indicia. And token 150 may be a secure (or encrypted) token. In one aspect, marker 150 is temporary rather than permanent, and exists only when the presence of device 120 is detected and the source data is identified. In one aspect, the marker 150 is generated only after the device 110 identifies or selects the source data 135 for sharing.

FIG. 4 is an example block diagram of source data 135 that may be shared using the NPC protocol. While the metadata associated with source data 135 (i.e., tags 150 in FIGS. 3A-3B ) may be limited in size such that tags 150 can be communicated using the NPC protocol, the subject technology employs shared source data 135 in which The size and type of information is unlimited. For example, source data 135 may include media files 410, source path information 420, remote desktop connection information 430, security information 440, device management information 450, device configuration information 460, and other information. As examples, media files may include audio files 412 (such as music, recorded speech, recorded sound effects, etc.), video files 414 (such as files containing image frames such as video clips), audio-video files 416 (such as movies, video clips with sound), images 418 (such as personal photographs, graphic art, images of various objects, advertising images, etc.), or other files, such as text files including PDF files. As an example, source path information 420 may include directory name 422 , folder name 424 , subfolder name 426 , and file name 428 . The source path information 426 may allow a user of the device 120 of FIGS. 1A-1D to access remote devices and update files. For example, IT personnel may use path information 426 to update or change certain files on an employee's computer.

As an example, remote desktop connection information 430 may include: an Internet Protocol (IP) address 432 , a username 434 , and a filename 436 . Remote desktop connection information 430 may cause a mobile device user (eg, user of device 120 ) to remotely connect to the desktop of a remote computer (eg, personal computer) and access the file identified by filename 436 . As an example, the security information 440 may include network security information 422 (such as security marks such as shared secrets) and security encoding information 444 (such as password encryption information such as public keys). The security information enables a user of device 120 to access a protected remote computer or server.

As examples, device management information 450 may include color depth 452 , resolution 454 , and desktop settings 456 . Device management information 450 is very useful to users of mobile devices (eg, device 120 ) and enables users to remotely modify various features of their desktop computers (eg, resolution, color, or other settings) from the mobile device. As an example, device configuration information 460 may include network configuration information 462 , peripheral device configuration information 464 , and client-server configuration information 466 . A user of a mobile device (e.g., device 120) can use network configuration information 462 to configure the device (e.g., a mobile device, or a remote device such as a desktop computer) to connect to a network (e.g., PAN, LAN, CAN, MAN, WAN, etc. Wait). As an example, a user of device 120 may configure the device (e.g., device 120 or a remote device such as a remote computer) to connect to a printer (e.g., a dedicated printer or a network printer) or to connect a television to a computer by using peripheral device configuration information 464. The machine is configured to connect to other equipment, such as a digital video recorder (DVR). Client server configuration information 466 may be used by a user of device 120 to configure a number of remote computers as clients or servers.

5 is a conceptual block diagram of an example of device 110 in FIGS. 1A-1D or device 210 in FIG. 2C using the NPC protocol to share information. For simplicity, reference will be made to devices 110 and 120 below. Such references are also valid for devices 210 and 220 in Figure 2C. The device 110 may include an NPC interface 510 , a storage 520 , a processor 530 , a first network interface 512 , a second network interface 514 , a display 540 , and a memory 550 coupled to each other via a bus 555 . It should be understood that other communication means besides buses could equally be used with the disclosed arrangements. The memory may store various software modules such as authentication module 552 , remote desktop module 554 , security module 556 , encoder 558 , identification module 560 , decoder module 562 and interface module 570 . NPC interface module 510 may facilitate communication between device 110 of FIGS. 1A-1D and one or more devices 120 using the NPC protocol, wherein marker 150 of FIGS. to device 120. In one aspect, device 110 may communicate with a source device such as device 110, device 220, or with a remote device using first network interface 512 and by using a first communication protocol (e.g., HTTP protocol or otherwise). (eg, remote device 130 or 140 in FIGS. 1A-1D , or device 270 or 280 in FIG. 2C ) to communicate to connect to a source device via a network (eg, network 250 in FIGS. 2A-2B ). In another aspect, the device 110 can use the second network interface 514 and communicate via a second communication protocol (such as P2P protocol, ICE protocol, session initiation protocol, BT protocol, Wi-Fi protocol, XMPP, push protocol, or non-industry standard communication protocol) to communicate with the remote device 130. When using the second network interface 514, the device 110 may connect to the source device through the proxy server 160 of FIGS. 1C-1D.

When a first user (eg, a user of device 110 or 210 ) decides to share source data 135 in FIG. 4 with a second user (eg, a user of device 120 ), the first user may launch an application in device 110 . The application can include a remote desktop module 554 and an identification module 560 . The remote desktop module 554 may be configured to cause display on the display 540 of the device 110 of a desktop representation of the remote device. The remote desktop module 554 can then cause the display of various files that can be selected for sharing on the source device. Identification module 560 (eg, in conjunction with remote desktop module 554 ) may be configured to facilitate searching or selecting source data 135 , determining source data 135 , and providing identification information for source data 135 . As an example, the identifying information may include: one or more identifiers of the source device (e.g., device name, IP address, etc.), the file system path of the source device, or a file identifying the file containing the source data 135 name. The first or second network interface 512 or 514 may facilitate connection to the source device and communicate identification information to the source device. The source device may create the token 150 in real-time and may provide the token 150 to the device 110 , which may be received by one of the first or second network interfaces 512 or 514 . In one aspect, the provided indicia 150 is sent via a proxy server (eg, proxy server 160) using a communication protocol (eg, XMPP or ICE), and the indicia is encoded based on the communication protocol. On device 110, decoder 562 may decode encoded indicia 150, after which encoder 558 encodes indicia 150 so that indicia 150 can be communicated via the NPC protocol. When a user of device 110 (or device 120 ) brings devices 110 and 120 close to each other, NPC interface 510 may communicate encoded indicia 150 to device 120 .

As an example, device 120, described in more detail with reference to FIG. 6, connects to a source device (such as remote device 130 or 140 of FIGS. When receiving data 135, source device may obtain an identifier of device 120 or a user of device 120 and may notify device 110 of the attempt. On device 110, security module 556 may facilitate implementation of one or more security measures. For example, security module 556 may cause first or second network interface 512 or 514 to receive an identifier of device 120 or a user of device 120 from a source device. Verification module 552 may verify the identifier by displaying the identifier using display 540 and receiving permission from a user of device 110 . The security module 556 may then cause the first or second network interface 512 or 514 to communicate this permission to the source device in order to be able to authenticate the device 120 or the user of the device 120 . In one aspect, when device 120 downloads source data 135 by attempting to access the source device, security module 445 may instruct first or second network interface 512 or 514 to communicate to the source device information that may identify device 120 or the user of device 120 , so that the source device can authenticate the device 120 or the user of the device 120.

The interface module 570 may provide a user interface for communicating various information to a user of the device 110 . For example, the user interface provided by interface module 570 and displayed on display 540 may be configured to receive input from a user of device 110, such as permissions discussed above in connection with security measures. The display 540 may include a liquid crystal display (LCD) or a touch-sensitive display. The processor 530 may be a general-purpose processor (such as a central processing unit (CPU)), a graphics processing unit (GPU), a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array ( FPGA), programmable logic device (PLD), controller, state machine, gate logic, discrete hardware element, or any other suitable entity capable of performing computational or other information operations. The processor 530 can run/execute various applications and software modules stored in the memory 550, such as an authentication module 552, a remote desktop module 554, a security module 556, an encoder 558 and so on. In one aspect, some applications or modules may be implemented as firmware.

In some aspects, various applications and software modules, such as authentication module 552, remote desktop module 554, security module 556, encoder 558, etc., may be stored on storage 520, which may include one or more machine-readable media. Storage 520 may include random access memory (RAM), flash memory, read only memory (ROM), programmable read only memory (PROM), erasable PROM (EPROM), registers, hard disk, removable disc, CD - ROM, DVD, or any other suitable storage device. The machine-readable medium can be a single medium or multiple media (eg, a centralized or distributed database, and/or associated caches and servers) on which one or more sets of instructions are stored. The term "machine-readable medium" shall be taken to include any non-transitory medium capable of storing, encoding or carrying a set of instructions executable by a machine and causing the machine to perform one or more methods of the embodiments discussed herein. Accordingly, the term "machine-readable medium" shall be considered to include, but not be limited to, storage media such as solid-state memory, optical media, and magnetic media. Non-transitory media includes both volatile and nonvolatile memory.

Still referring to FIG. 5 , as an example, in one aspect, by using an NPC interface (eg, 510 ), device 110 may automatically detect the presence of device 120 without user intervention. For example, the operating system of device 110 may include an NPC communication module 581 capable of monitoring and detecting the presence of NPC-enabled devices. As an example, upon detecting the presence of device 120, NPC communication module 581 may automatically launch an application for sharing information (such as the applications described with reference to FIGS. 5, 7A and 8A) without user intervention. As an example, the identification module 560 of the application may display a graphical user interface to allow the user to select source data among a plurality of source data, or to allow the user to enter information for identifying the source data (such as typing the name of the file), A user of device 110 is enabled to identify or select source data for sharing (eg, identify or select one or more source devices or one or more files within them). Identification module 560 may also determine an identifier for device 120 based on detection of the presence of device 120 . In one example, if multiple devices 120 are detected, identification module 560 may display the detected devices to allow a user of device 110 to select one or more detected devices to share source data.

In one aspect, device 110 is a hardware device (including software) and is a communication endpoint device. For example, device 110 may be an end-user handheld device. Typically, the device 110 has user interface modules/devices (eg, items 570, 540) for providing/receiving information to/from a user. In one aspect, device 110 is not a router or access point that merely routes data transmissions initiated by other hardware devices. As a communications endpoint device, device 110 may initiate data communications. For example, device 110 (eg, using items 560, 570) may initiate a source data sharing process based on user actions on device 110 (eg, based on selections made to source data and/or selections made to device 120). In one aspect, device 110 (eg, using items 560, 570) may determine the final destination of the data communication. As an example, item 560 for device 110 may determine that the final destination of the data communication is devices 110 and 130 that requested and received the token. Once the token is received and processed, device 110 may decide that the final destination of the data communication is devices 110 and 120 that sent and received the processed token, and device 110 may initiate the transaction with device 120 .

Device 110 may also initiate a remote desktop session between device 110 (as a first endpoint) and device 130 (as a second endpoint) to provide a display on device 110 with a representation of the entire desktop of device 130 (or device 130). 130), thereby allowing access to any file on device 130 (or a file that is permitted to be accessed by the user of device 110), and exchanging requests and receipts for said tokens.

In one aspect, device 120 is a hardware device (including software) and is a communications endpoint device. For example, upon receipt of the token, device 120 (eg, item 652 in FIG. 6 ) can determine that the final destination of the data communication is devices 120 and 130 that requested and downloaded the source data, and can initiate a download transaction.

In one aspect, device 130 is a hardware device (including software) and is a communication endpoint device. For example, device 130 may be the final destination point for generating indicia with respect to the identified source data by receiving a request originating from device 110 . The device 130 may be the final destination point for providing source data to the device 120 by receiving a request originating from the device 120 .

In one aspect, source data 135 may be non-public information (eg, information stored on source devices that are not generally accessible to the public without special permission). The non-public source device may be a server, and said server is not an HTTP server.

In one aspect, each item 510, 520, 530, 555, 512, 514, and 540 includes hardware and each item in memory 550 includes software. In one aspect, each of items 510, 520, 530, 555, 512, 514, and 540 may include hardware and software. Item 510 may include software, such as items 558 , 562 and/or 581 . Additionally, each of items 512 and 514 may include software, such as items 558 , 562 and/or 582 .

6 is a conceptual block diagram of an example of device 120 in FIGS. 1A-1D or device 220 in FIG. 2C using the NPC protocol to receive shared information. For simplicity, reference will be made to devices 110 and 120 below. These references are also valid for devices 210 and 220 of Figure 2C. The device 120 may include an NPC interface 610 , a storage 620 , a processor 630 , a first network interface 612 , a second network interface 614 , a display 640 and a memory 650 coupled to each other via a bus 655 . It should be understood that other communication means besides buses may be used with the disclosed arrangements. Memory 650 can store various applications and software modules, such as download module 652, remote desktop module 654, decoder module 656, interface module 658, encoder 672, NPC communication module 681 and network communication module 682, wherein the network communication module 682 includes web browsers and applications (eg remote access applications, PocketCloud applications). When the device 120 is close to the device 110 (eg, within 5 feet), the NPC interface 610 can cause the device 120 of FIGS. 1A-1D to communicate with the device 110 using the NPC protocol, wherein the codes in FIGS. Based on the NPC protocol) token 150 will be transferred from device 110 to device 120 . The decoder 656 may decode the encoded indicia 150 . Device 120 may then use decoded token 150 (before the expiration date of token 150) to access a source device (eg, remote device 130 or 140 of FIGS. 1A-1D , devices 270 and 280 of FIG. 2C , device 110 , or the source data 135 in FIG. 4 stored on the device 220).

During the period prior to the expiration date of token 150 , download manager 562 may cause access to source device using decoded token 150 and download of source data 135 . Download manager 562 may cause first network interface 512 to access the source device via a network (eg, network 250 of FIGS. 2A-2B ) and by using a communication protocol such as HTTP. In one aspect, download manager 562 may cause first network interface 614 to access the source device via a proxy server (eg, proxy server 160 in FIGS. 1C-1D ) using a communication protocol such as XMPP or ICE. Remote desktop module 654 may be configured to cause display on display 640 of device 120 of a desktop representation of the source device. The interface module 658 may provide a user interface for communicating various information to a user of the device 120 . For example, the user interface provided by interface module 658 and displayed on display 640 may be configured to receive input from a user of device 120 , such as a location in device 120 where the user wishes to save downloaded source data 135 .

In some aspects, indicia 150 may include an HTTP URL to allow device 220 to access source data 135 via the website represented by the URL in indicia 150 (eg, pocketcloud.com). The HTTP URL can be launched by a web browser without any special application. And the HTTP URL can point to a web application, wherein the application contains the necessary JavaScript code for detecting whether the appropriate application (eg remote access application, PocketCloud application) is installed on the device 220 . If the application is installed locally on the device 220, the web browser can launch the local application. The native application can begin downloading source data 135 from the source device. If the necessary application is not installed locally on the device 220, the web browser may communicate back to the web server (eg, web server 260 of FIG. 2C ) and request the web server to retrieve the source data 135 from the device storing the source data. Doing so may allow the web browser to download files from the web server 260 immediately without requiring a web application (eg, a native application).

The display 640 may include a liquid crystal display (LCD) or a touch-sensitive display. The processor 630 may be a general-purpose processor (such as a central processing unit (CPU)), a graphics processing unit (GPU), a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array ( FPGA), programmable logic device (PLD), controller, state machine, gate logic, discrete hardware element, or any other suitable entity capable of performing computational or other information operations. The processor 630 can run/execute various applications and software modules stored in the memory 650 , such as a download manager 652 , a remote desktop module 654 , a decoder 656 , and an interface module 658 . In one aspect, some applications or modules may be implemented as firmware. In some aspects, various applications and software modules, such as download manager 652, remote desktop module 654, decoder 656, and interface module 658, may be stored on storage 620, which may include one or more machine-readable media. Storage 620 may include random access memory (RAM), flash memory, read only memory (ROM), programmable read only memory (PROM), erasable PROM (EPROM), registers, hard disk, removable disc, CD - ROM, DVD, or any other suitable storage device. The machine-readable medium can be a single medium or multiple media (eg, a centralized or distributed database, and/or associated caches and servers) on which one or more sets of instructions are stored.

In one aspect, each item 610, 620, 630, 655, 612, 614, and 640 includes hardware and each item in memory 650 includes software. In one aspect, each of items 610, 620, 630, 655, 612, 614, and 640 may include hardware and software. Item 610 may include software, such as items 672, 656, and/or 681. Additionally, each of items 612 and 614 may include software, such as items 672 , 656 and/or 682 .

7A-7B are flowcharts illustrating example methods 700A and 700B of sharing information by using the NPC protocol. Method 700A is implemented on device 110 of Figures 1A-1D or device 210 of Figure 2C. For simplicity, reference will now be made to devices 110 and 120 in FIGS. 1A-1D . These references are also valid for devices 210 and 220 of Figure 2C. Method 700A begins at operation 710, wherein device 110 supports a based Communication of a first protocol (eg HTTP or XMPP). As an example, the identification module 560 may determine or provide identification information of the source data, and the interface 512 or 514 may communicate via a network communication module 582 (which provides software support for the items 512 and/or 514) and/or the encoder 558. One or more other items of , directly or indirectly, to receive identifying information. Interface 512 or 514 may then cause identification information to be communicated from device 110 to the source device using the first protocol. As such, at least one of items 560 , 512 , 514 and/or other items (eg, 582 ) can support communication between devices 110 and 130 based on the first protocol. By using items such as 558 and/or 582, information can be encoded into the first protocol.

At operation 720 , the device 110 causes receipt of the markup 150 of FIGS. 3A-3B associated with the source data 135 of FIG. 4 . For example, interface 512 or 514 may receive token 150, which is then received by one or more items, such as items 582, 562, 558, for processing. As such, at least one of items 512 , 514 , 582 , 562 , 558 , and/or other items may cause receipt of indicia 150 .

Device 110 (eg, encoder 558 and/or other items such as item 581) may cause encoding of indicia 150 so that indicia 150 can be communicated using the NPC protocol (operation 730). At operation 740 , device 110 may communicate marker 150 to one or more devices 120 that are within 5 feet of device 110 . Indicia 150 may be communicated using the NPC protocol. As an example, encoder 558 and/or NPC communication module 581 may allow indicia 150 to be provided to NPC interface 510 , which may then initiate (directly or indirectly) sending indicia 150 to device 120 . Thus, at least one of items 558 , 581 , 510 and/or other items may communicate encoded indicia 150 to device 120 . In one aspect, once source data is identified or selected by device 110, all of the operations shown in FIG. 7A can be performed automatically without user intervention.

Method 700B is implemented on device 120 and begins with operation 750 in which device 120 causes receipt of token 150 from device 110 using the NPC protocol when device 120 is within 5 feet of device 110 . In one example, at least one of items 610 , 656 , 681 , and/or other items may perform or cause operation 750 to be performed. Subsequently, the device 120 may decode the token 150 encoded to perform NPC protocol-based communication (operation 760). In one example, at least one of items 656, 681, and/or other items may perform or cause operation 760 to be performed. In operation 770, the device 120 may perform an action based on a certain communication protocol (such as P2P protocol, ICE protocol, session initiation protocol, BT protocol, Wi-Fi protocol, XMPP, push protocol, non-industry standard communication protocol, or HTTP). Communication of the source device to download the source file 135 using the decoded token 150. In one example, at least one of items 612 , 614 , 672 , 682 and/or other items may perform or cause operation 770 to be performed.

In an advantageous embodiment, some or all of the operations shown in Figure 7B are performed automatically without user intervention.

8A-8B are flowcharts illustrating example methods 800A and 800B of sharing information using the NPC protocol. Method 800A may be implemented on device 110 of FIGS. 1A-1D . For simplicity, reference will now be made to devices 110 and 120 of FIGS. 1A-1D . These references are also valid for devices 210 and 220 of Figure 2C. Method 800A begins at operation 810, where a user of device 110 launches an application on device 110 to share source data with a user of device 120 in FIGS. 1A-1D. At operation 815, the user of device 110 searches and locates (or selects from a list) a source device (eg, remote device 130 or 140 of FIGS. 1A-1D , devices 270 and 280 of FIG. Or the source data 135 of FIG. 4 stored on the device 220). Device 110 may receive metadata (eg, tags 150 of FIGS. 3A-3B ) associated with source data 135 and may save the metadata on device 110 (operation 820). In operation 825, the device 110 may encode metadata using an expiration date in order to perform NPC transmission. The encoded metadata may then be shared with device 120 using the NPC protocol (operation 830).

Method 800B may be implemented on device 120 and begins at operation 840 , where a user of device 120 launches an application for receiving encoded metadata from device 110 that is within 5 feet of device 120 . At operation 845, the device 120 may listen for the NPC record received from the device 110 and containing metadata. Device 120 may decode the metadata (operation 850), and at operation 855, device 120 may push the metadata to the application's download queue. The application may include the download manager 652 of FIG. 6, a web browser, or a web application. At operation 860, the download manager 652 may cause the source data 135 to be downloaded using the metadata. In some aspects, source data 135 may be downloaded through a web browser using a URL contained in marker 150, or downloaded through a web application.

9A-9B are flowcharts illustrating an example method 900 of downloading source files by using information shared based on the NPC protocol. Method 900A includes portions 940 , 950 and 970 . Portion 940 may be implemented on device 110 of FIGS. 1A-1D or device 210 of FIG. 2C. For simplicity, reference is made below to devices 210 and 220 of FIG. 2C. These references are equally valid for devices 110 and 120 of FIGS. 1A-1D . Portion 950 may be implemented on device 120 or 220, and portion 970 may be implemented by device 260 of FIG. 2C or either device 130 or 140 of FIGS. 1A-1D. Section 940 begins with operation 942 , where, on device 210 , a user of device 210 selects a file to share with device 210 . At operation 944, NPC communication is initiated between devices 210 and 220, as described in more detail above. Using NPC communication, metadata encoded in a URL may be delivered to device 220, which may include, for example, source device identification (SID), source file details (FD), and tags 150 (operation 946).

Portion 950 of method 900A begins at operation 952, where device 220 receives NPC information (eg, metadata). Device 220 may use a web browser to access web server 260 (operation 954). At operation 974, the server 260 points to the URL to a web application that includes the necessary JavaScript for detecting the native web application. At operation 956, the web application detects whether a native web application (eg, the PocketCloud application) is installed on the device 220 . At control operation 958, if the PocketCloud application is installed on the device 220, control is passed to operation 960, where the PocketCloud application will be launched on the device 220 and the SID, FD, and token 150 will be passed to the PocketCloud application. Subsequently, at operation 962, the PocketCloud application downloads the source data 135 of FIGS. 1A-1D from a source device (such as, for example, the remote device 130 or 140 of FIGS. .

Otherwise, if the PocketCloud application is not installed on the device 220, control is passed to operation 964, where a request to download the source file 135 is initiated to the web server 260 (eg, PocketCloud server). Subsequently, at operation 972, the server 260 may access the source file 135 from the source device. Finally, the web browser will download source file 135 from web server 260 to device 220 (operation 966).

In method 900B, after starting the operation, the download manager 652 of FIG. 6 queries, in control operation 910, one of the first network interface 612 or the second network interface 614 in FIG. For example, whether a connection is established between the remote device 130 or 140 in FIGS. 1A-1D , the devices 270 and 280 in FIG. 2C , the device 110, or the device 220). If a connection is established, control is transferred to control operation 920, otherwise, the download manager 652 will continue to query. At control operation 920, the device 120 may determine whether there is a file to be downloaded. If there are no files to download, then control is passed back to control operation 910 . Otherwise, at operation 930, the download manager 652 downloads the source file 135 using the shared metadata (eg, marker 150 of FIGS. 3A-3B ).

10 is a conceptual block diagram of an example of a device or server. System 1000 may include remote device 130 or 140 of FIGS. 1A-1D , server 230 or cloud server 240 of FIGS. 2A-2B , or any of devices 260 , 270 , 280 . System 1000 may be device 110 , 120 , 210 or 220 . System 1000 includes a processing system 1002, which may include one or more processors or one or more processing systems. Processor 530 or 630 may be processing system 1002, and the processor may be one or more processors. Processing system 1002 is capable of communicating with receiver 1006 and transmitter 1009 via bus 1004 or other interface or device. It should be understood that other communication means besides buses could equally be used with the disclosed arrangements. Processing system 1002 may generate marker 150 of FIGS. 3A-3B . In some aspects, processing system 1002 may generate audio, video, multimedia, and/or other types of data that is provided to transmitter 1009 for transmission. Additionally, audio, video, multimedia, and/or other types of data may be received at receiver 1006 and may be processed by processing system 1002 .

Processing system 1002 may include a general-purpose processor or a special-purpose processor for running/executing instructions, and may also include a machine-readable medium 1019, such as volatile or non-volatile, for storing data and/or instructions for software programs sexual memory. These instructions may be stored in machine-readable storage media 1010 and/or 1019 and may be executed/executed by processing system 1002 to control and manage access to various networks, and to provide other communication and processing functions. Additionally, these instructions may also include instructions executed/run by processing system 1002 for various user interface devices such as display 1012 and numeric keypad 1014 . Processing system 1002 may include input ports 1022 and output ports 1024 . Each input port 1022 and output port 1024 may include one or more ports. The input port 1022 and the output port 1024 can be the same port (eg, a bidirectional port), or different ports.

The processing system 1002 may be implemented in software, hardware, or a combination of software and hardware. For example, processing system 1002 may be implemented with one or more processors. The processor can be a general purpose microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), programmable logic device (PLD), controller, state computers, gate logic, discrete hardware components, and/or any other suitable device capable of performing computational or other information operations.

A machine-readable medium may be one or more machine-readable media. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software shall be construed broadly to mean instructions, data, or any combination thereof. Instructions may comprise code (eg, in source code format, binary code format, executable code format, or any other suitable code format).

A machine-readable medium (eg, 1019) may include memory integrated in the processing system, as is the case with an ASIC. The machine-readable medium (eg, 1010) can also include memory located external to the processing system, such as random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), rewritable PROM (EPROM), registers, hard disk, removable disk, CD-ROM, DVD or any other suitable storage device. Additionally, a machine-readable medium may include a transmission line or carrier wave that encodes a data signal. Those skilled in the art will recognize how best to implement the described functionality of the processing system 1002 . According to one aspect of the present disclosure, a machine-readable medium is a computer-readable medium that encodes or stores instructions, and is a computer-readable medium that defines the structural and functional interrelationships between the instructions and the rest of the system capable of implementing the functions of the instructions. computing components. As an example, the instructions can be executed/executed by either the client terminal or the server, or by the processing system of the client terminal or the server. The instructions may be, for example, a computer program comprising code.

Network interface 1016 may be any type of interface to a network (eg, any type of Internet network interface) or to a proxy server using XMPP, and may be located between any of the components shown in FIG. 10 . Taking remote device 130 in FIGS. 1A-1D as an example, network interface 1016 may be used to communicate with device 110 or 120 to receive identification information and permissions from device 110 over network 250 or via proxy server 160 of FIGS. 1C-1D , receiving from device 120 an identification of device 120 or a user of device 120 , and passing token 150 to device 110 , or passing source data 135 to device 120 .

Device interface 1018 may be any type of interface that interfaces to a device and may be located between any of the components shown in FIG. 10 . As an example, the device interface 1018 may be an interface that interfaces with an external device (eg, a USB device) plugged into a port (eg, a USB port) of the system 1000 .

The transceiver component 1007 may represent one or more transceivers, and each transceiver may include a receiver 1006 and a transmitter 1009 . Functionality implemented in processing system 1002 may be implemented in a portion of receiver 1006, a portion of transmitter 1009, a portion of machine-readable medium 1010, a portion of display 1012, a portion of numeric keypad 1014, or a portion of interface 1016, and vice versa. Of course.

The subject technology may provide a mechanism for transferring information between two or more separate devices through an NPC protocol mechanism for file sharing, remote desktop connection settings, and device management settings. The above information transmission is originally performed locally through device-to-device communication such as WiFi or Bluetooth connection. In addition, the subject technology also facilitates final transmission through an intermediary cloud-based server infrastructure. And the subject technology can be seen as a simple mechanism for transferring complex information from one device to another. As an example, this complex information transfer may include file sharing, which may involve sharing source path information (eg, remote path information), remote desktop connection details, security information, device management setting information, and the like.

In one aspect, the subject technology can provide various advantages, including but not limited to the following: fast exchange of connection information or file information between two different devices by using hardware device-based NPC method Initial information transfer (e.g. setup time less than 0.1 second), transfer of Remote Desktop connection information without user interaction (especially text input); and when no user interaction (especially text input or manual setup) is required Next, send device management information.

Advantageously, the two devices can use the built-in NPC hardware to perform information sharing. For example, a mobile application may provide mechanisms for selecting files or connection settings to be shared. The application can perform communication from one device to another through the NPC. And the application can handle the process of finally retrieving and applying NFC payload information (such as file transfer information, remote connection details, and device management details). The cloud-based server infrastructure may contain software that allows downloading of file data being shared, connection information for one or more remote desktops, or device management information. A WiFi connection can provide the necessary transfer processing for downloading files, connection information, or device management information. In addition, the Bluetooth connection can also provide the necessary transport processing for downloading files, connection information or device management information.

In one aspect, the various components of the subject technology may include: two devices (e.g., smartphones) with built-in NPC support hardware; a mobile application using the subject technology framework; (optionally) a cloud-based server infrastructure; (optional) WiFi connectivity; (optional) Bluetooth connectivity; and (optional) P2P connectivity. In one aspect, the subject technology may use a plurality of steps, as an example, the steps for sharing a source file between two devices may be as follows: use an application in the first device to discover the file shared with the second device; Optionally, if the file is remotely shared, the file is uploaded to a cloud-based remote server; the file containing the meta information related to information sharing is transmitted to the second device through the NPC; the second device runs the software to read data encoded with NPC; the second device uses the meta-information and performs the download directly via Bluetooth, WiFi, P2P, or from a cloud-based server hosting shared files.

In one aspect, a method for transmitting remote desktop connection information may include the steps of: using an application to discover the remote desktop connection or connection group to be shared; file of meta-information; the second device runs a software to receive meta-information via NPC; said second device directly uses meta-information to read coded information in order to reproduce remote desktop connection settings, or directly via Bluetooth, WiFi, downloads via P2P, or from a cloud-based server infrastructure that houses files containing extended remote desktop connection information.

In one advantageous example, for example, in addition to requiring a user to identify/select source data for sharing, select one or more devices 120, and/or grant/authenticate a device 120 or its user to enable a device 120 to Aside from the processing of accessing source data, the various operations described here can be performed automatically without user intervention.

In one aspect, a communication protocol may include one or more communication protocols. In one aspect, the first communication protocol can be the same as the second communication protocol used by the same or a different device. In one aspect, the first communication protocol may be different from the second communication protocol used by the same or a different device. Also, in one aspect, an annotation such as a first device/item and a second device/item can be the same. And in one aspect, an annotation such as a first device/item may be different than a second device/item.

Method/machine-readable storage medium/apparatus for facilitating sharing of information among multiple devices using NPC protocol Examples of placement (described as clauses)

For convenience, examples pertaining to different aspects of the disclosure are described as numbered clauses (1, 2, 3, . . . ). These terms are provided as examples, not limitations of the technical subject matter. The reference signs and reference numbers provided below are only examples and for illustration purposes, and these terms are not limited by these signs.

Examples of coded clauses

1. A non-transitory machine-readable medium (such as 520, 550 of FIG. 5 ), including instructions stored therein, which can be run/executed by one or more processors (such as 530 of FIG. 5 ) , so as to implement a method (for example, 700A of FIG. 7A ) for facilitating the sharing of source data, the method comprising:

Communication between a first device and a remote device based on a first communication protocol is supported, wherein the communication is associated with the source data and the communication is based on detection of the second device within less than 5 feet of the first device. exists (eg, 710 of FIG. 7A );

causing receipt of a first marker (eg, 720 of FIG. 7A ) associated with the source data;

causing encoding of the first indicium to enable communication using a near field communication (NPC) protocol (eg, 730 of FIG. 7A ); and

Using the NPC protocol to provide communication that communicates the first marker to a second device that is within 5 feet of the first device to enable the second device to access the source data using the second communication protocol, where the second device cannot accessing the source data (e.g., 740 of FIG. 7A ) without using the first tag,

wherein the NPC protocol is different from the first and second communication protocols, and wherein the first communication protocol is the same or different from the second communication protocol,

Wherein the data transmission rate supported by the NPC protocol is neither greater than the data transmission rate supported by the first communication protocol nor greater than the data transmission rate supported by the second communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the first device is an NPC-enabled device configured to detect the presence of the second device within 5 feet of the first device,

Wherein the first device is a communication endpoint device.

2. The non-transitory machine-readable medium of clause 1, wherein the method comprises determining the source data based on a user action on the first device to begin sharing the source data.

3. The non-transitory machine-readable medium of clause 1, wherein the method comprises: determining, on the first device, source data for sharing, wherein the communicating-enabling process comprises: providing for using the first communication protocol to Communication of source data identification information based on source data identification processing from the first device to the remote device through the proxy server, wherein the NPC protocol includes a near field communication (NFC) protocol.

4. The non-transitory machine-readable medium of clause 1, wherein the method comprises: determining source data for sharing,

Wherein the supporting communication includes: providing communication for transferring identification information of the source data to the remote device, wherein the identification information includes at least one of a remote device identifier, a remote device file system path, or a file name,

wherein said supporting communication comprises: providing communication to the remote device to communicate a request for the first marker,

Wherein causing the receiving includes: causing the first token to be received in response to the request.

5. The non-transitory machine-readable medium of clause 1, wherein the method comprises: determining source data for sharing,

wherein said processing to enable communication comprises: causing identification information of the source data to be provided to the remote device, so that the first marker can be generated in real time in response to the processing causing provision of the source data identification information,

wherein causing receipt of the first indicia comprises causing receipt of the first indicia from the remote device via a proxy server using a first communication protocol on the first device in response to causing source data identification information to be provided,

Wherein the method comprises: prior to encoding, decoding a first token received using a first communication protocol,

wherein providing to the second device a communication communicating the first indicia comprises: providing a communication communicating the first indicia from the first device to the second device,

Wherein the method includes: providing for communicating from the first device to the second device other information for accessing the source data, wherein the other information includes the source data location, the first flag for passing to the second device, and the size of the other information is smaller than the size of the source data, and where the source data consists of more than one megabyte,

Wherein said encoding process includes encoding the first mark on the first device.

6. The non-transitory machine-readable medium of clause 1, wherein the method includes at least one of a first security measure and a second security measure,

The first security measures include:

causing receiving, from the remote device, information identifying at least one of the second device or a user of the second device in response to the second device attempting to access the source data; and

providing an approved communication to the remote device after the first device user verifies the received information,

The second security measures include:

providing to the remote device a communication of information determining at least one of the second device or a user of the second device to enable the remote device to authenticate the second device or the user of the second device when the second device attempts to access the source data .

7. The non-transitory machine-readable medium of clause 1, wherein the method comprises one or more of the first method, the second method, the third method, or the fourth method,

The first method includes:

providing a request to a remote device to transmit source data to a first server comprising a cloud server to enable a second device to access the source data via the first server;

The second method includes:

providing a request to the remote device to transmit the source data to a second server comprising a cloud server and sending a second token to the first device;

using the NPC protocol to provide a second device within 5 feet of the first device with a communication communicating the second indicia to enable the second device to access the source data communicated to the second server;

Wherein the third method includes: causing the source data to be transmitted to a third server including a cloud server, so that the second device can access the source data via the third server;

The fourth method includes:

prompts generation of a third token;

causing transfer of source data from the first device to the fourth server;

Communication passing the third indicia is provided to a second device less than 5 feet from the first device using the NPC protocol to enable the second device to access the source data via the fourth server.

8. The non-transitory machine-readable medium of clause 1, wherein the first indicia includes metadata comprising at least some of: an origin device identifier, authentication information associated with the origin device , a source data identifier, or a source data path, wherein the source device is a device that stores the source data, and wherein the source device is a first device or a remote device.

9. The non-transitory machine-readable medium of clause 1, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information.

10. The non-transitory machine-readable medium of clause 9, wherein:

The media file includes at least one of an audio file, a video file, an audio-video file, or an image,

The remote path information includes at least one of directory name, folder name, subfolder name or file name,

The remote desktop connection information includes at least one of an Internet Protocol (IP) address, username, or password,

The security information includes at least one of network security information or security coding information,

the device management information includes at least one of color depth, resolution, or desktop settings, and

The device configuration includes at least one of network configuration, peripheral device configuration, or client-server configuration.

11. The non-transitory machine-readable medium of clause 1, wherein the first indicia is expiring and is a unique representation of one or more of: the source data, the second device, the first a user of the device, and a time associated with the creation or use of the first token, wherein the method includes at least one of the first method and the second method,

The first method includes:

causing receipt of a second marker associated with the second source data;

encoding the second token to enable communication using the NPC protocol; and

providing communication conveying the second indicia to a third device located less than 5 feet from the first device using the NPC protocol to enable the third device to access the second source data using the third communication protocol,

Wherein the first communication protocol and the third communication protocol are the same or different,

where the Second Token is a unique representation of one or more of: the Second Data, the Third Device, and the time associated with the creation or use of the Second Token,

The second method includes:

causing receipt on the first device of a third marker associated with the source data,

encoding a third token on the first device to enable communication using the NPC protocol; and

providing communication conveying the third indicia to a fourth device located less than 5 feet from the first device using the NPC protocol to enable the fourth device to access the source data using the fourth communication protocol,

Wherein the first communication protocol and the fourth communication protocol are the same or different,

Wherein the third token is a unique representation of one or more of the following: source data, third device, third device user, and time associated with the creation or use of the third token.

12. The non-transitory machine-readable medium of clause 1, wherein the first device is a device comprising one or more displays, one or more processors, one or more network interfaces, and the non-transitory machine-readable medium A mobile device, wherein a first network interface of the one or more network interfaces is configured to support communication based on the first communication protocol, and a second network interface of the one or more network interfaces is configured to support communication based on the NPC protocol communications, wherein the second device is a mobile device, wherein the remote device is a computing device behind a firewall, wherein the first token does not exist until the source data to be shared is determined, and wherein the first token is created in real time and Indefinite, wherein each of the first and second communication protocols includes one or more communication protocols.

13. A non-transitory machine-readable medium (such as 520, 550 of FIG. 5 ), including instructions stored therein, which can be run/executed by one or more processors (such as 530 of FIG. 5 ) , so as to implement a method (for example, 700C of FIG. 7C ) to facilitate sharing of source data, the method comprising:

causing receipt of a marker (e.g., 780 of FIG. 7C ) associated with the source data;

causing the indicia to be encoded to enable communication using a near field communication (NPC) protocol (eg, 782 of FIG. 7C ); and

Use the NPC protocol to provide a second device within 5 feet of the first device with a communication delivering the token to enable the second device to access the source data using the communication protocol, wherein the second device cannot access the source data without using the token In the case of accessing source data (for example, 784 of FIG. 7C ),

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the first device is an NPC-enabled device adapted to detect the presence of the second device within 5 feet of the first device,

where the markup is non-public.

14. The non-transitory machine-readable medium of clause 13, wherein the method comprises: determining the source data based on a user action on the first device to begin sharing the source data,

wherein the NPC protocol is different from the communication protocol,

The data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the communication protocol.

15. The non-transitory machine-readable medium of clause 13, wherein the source data is stored on the first device, wherein the method comprises: causing generation of a marker associated with the source data stored on the first device, wherein the The process causing encoding causes receiving the indicia prior to encoding.

16. The non-transitory machine-readable medium of clause 13, wherein the communication protocol comprises a point-to-point protocol, an interactive connection establishment protocol, a session initiation protocol, an NPC protocol, a Bluetooth protocol, a Wireless Fidelity (WiFi) protocol, At least one of Extensible Messaging and Presence Protocol (XMPP), a push protocol, or a non-industry standard communication protocol.

17. The non-transitory machine-readable medium of clause 13, wherein causing the encoding of the markup comprises: causing encoding of the markup in the form of a Uniform Resource Locator (URL) to allow the second device to be accessed via the URL in the markup. Indicates the website to access the source data.

18. The non-transitory machine-readable medium of clause 13, wherein the method includes a security measure comprising:

causing receiving, from the remote device, information identifying at least one of the second device or a user of the second device in response to the second device attempting to access the source data;

verifying the received information by a user of the first device; and

The second device or a user of the second device is authenticated prior to allowing the second device to access the source data.

19. The non-transitory machine-readable medium of clause 13, wherein the process of providing communication allows the second device to access the source data via the third device,

wherein the first device supports communication between the first device and the third device to facilitate receipt of an indicia from the third device, or to facilitate access of source data by the second device,

Wherein the marking includes metadata comprising at least some of the following: an identifier of the first device, authentication information associated with the first device, an identifier of the source data, a path to the source data, wherein The indicia allows downloading of source data, and wherein the source data is used at least to set up, configure or manage the second device or one or more computers.

20. An apparatus (such as 110 of FIG. 5 ) for facilitating the sharing of source data, the apparatus comprising:

The first network interface (for example, 512 in FIG. 5 ) is configured to support communication based on the first communication protocol between the first device and the remote device;

an encoder (eg, 558 of FIG. 5 ) configured to cause receipt of a first marker associated with the source data;

The encoder is configured to cause encoding of the first indicium to enable communication using a Near Field Communication (NPC) protocol; and

An NPC interface (eg, 510 of FIG. 5 ), configured to provide communication using the NPC protocol to communicate the first marker to a first device (eg, 120 of FIG. 6 ) that is less than 5 feet away from the apparatus, such that the first device (eg, 120 of FIG. 6 ) a device is able to access source data using a second communication protocol, wherein the source data cannot be accessed by the first device without using the first token,

wherein the NPC protocol is different from the first and second communication protocols, and wherein the first communication protocol is the same or different from the second communication protocol,

Wherein the data transmission rate supported by the NPC protocol is neither greater than the data transmission rate supported by the first communication protocol nor greater than the data transmission rate supported by the second communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet.

21. The device of clause 20, further comprising:

an identification module configured to determine source data based on a user action on the device, and to provide identification information about the source data to facilitate sharing of the source data; and

A second network interface configured to support the transfer of identification information from the apparatus to the remote device through the proxy server based on a first communication protocol, wherein the first communication protocol includes Extensible Messaging and Presence Protocol (XMPP), wherein The NPC protocol includes a Near Field Communication (NFC) protocol, wherein the identification information includes at least one of a remote device identifier, a remote device file system path, or a file name.

22. The apparatus of clause 20, further comprising: an identification module configured to determine source data based on user actions on the apparatus, and to provide identification information of the source data to facilitate sharing of the source data, wherein the first A network interface is further configured to support the process of communicating identification information from the apparatus to the remote device based on the first communication protocol, wherein the identification information includes at least one of a remote device identifier, a remote device file system path, or a file name. One.

23. The apparatus of clause 20, further comprising an identification module configured to determine source data based on a user action on the apparatus, and to cause identification information of the source data to be provided to support source data sharing,

wherein the first network interface is configured to support communication for providing identification information of the source data to the remote device such that the first indicia can be generated in real time in response to the communication providing the identification information of the source data,

wherein the first network interface is further configured to cause, in response to the communication providing the source data identification information, to cause, on the apparatus, a first indicia originating from the remote device to be received using a first communication protocol and via a proxy server,

wherein the apparatus comprises: a decoder for decoding, prior to encoding, the first indicia received using the first communication protocol,

wherein the first network interface is further configured to provide communication communicating the first token from the apparatus to the first device,

Wherein the first network interface is further configured to provide communication for passing other information from the apparatus to the first device for accessing the source data, wherein the other information includes the location of the source data, wherein the first device passed to the first device the size of the tags and other information is smaller than the size of the source data, and wherein the source data consists of more than one megabyte,

Wherein the encoder is further configured to encode the first indicia on the device.

24. The apparatus of clause 20, further comprising: a security module configured to cause implementation of at least one of the first security measure and the second security measure,

The first security measures include:

causing, in response to the first device attempting to access the source data, from the remote device via the first network interface, information identifying at least one of the first device or a user of the first device; and

providing an approved communication to the remote device via the first network interface after the user of the apparatus has verified the received information,

The second security measures include:

providing, via the first network interface, to the remote device a communication conveying information for determining at least one of the first device or a user of the first device to enable the remote device to authenticate the first device when the first device attempts to access the source data or the user of the first device.

25. The apparatus of clause 20, wherein the first network interface is further configured to cause a request to the remote device to transmit the source data to the server comprising the cloud server, and to send the second token to the apparatus , wherein the NPC interface is further configured to provide, using the NPC protocol, to a first device located less than 5 feet from the apparatus to communicate the second indicia to enable the first device to access source data communicated to the server.

26. The apparatus of clause 25, wherein the first or second token includes metadata including at least some of the following: an identifier of the remote device, an identifier of the server, an identifier associated with the source remote device authentication information of the connection, an identifier of the source data stored in the remote device, a path of the source data stored in the remote device, an identifier of the source data transmitted to the server, or a path of the source data transmitted to the server.

27. The apparatus of clause 25, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information, and wherein:

The media file includes at least one of an audio file, a video file, an audio-video file, or an image,

The remote path information includes at least one of directory name, folder name, subfolder name or file name,

The remote desktop connection information includes at least one of an Internet Protocol (IP) address, username, or password,

The security information includes at least one of network security information or security coding information,

the device management information includes at least one of color depth, resolution, or desktop settings, and

The device configuration includes at least one of network configuration, peripheral device configuration, or client-server configuration.

28. The means of clause 20, the first token is expiring and is a unique representation of one or more of: the source data, the first device, the user of the first device, and A time associated with creation or use of a first token, wherein the apparatus is configured to communicate each of the plurality of first tokens to the plurality of first devices by providing for receiving the plurality of tokens from the remote device and providing for using the NPC protocol communication of one of the devices to support a plurality of first devices, wherein each of the plurality of first tags is a unique representation of one or more of the following: source data, between the plurality of first devices One, a user of one of the plurality of first devices, and a time associated with creation or use of a token of the plurality of first tokens.

29. The apparatus of clause 20, wherein the apparatus is a mobile device comprising one or more displays, one or more processors, one or more network interfaces, and a non-transitory machine-readable medium, wherein the first the device is another mobile device, wherein the remote device is a computing device behind a firewall, wherein the first token does not exist until the source data to be shared is determined, and wherein the first token is created in real time and expires, Each of the first and second communication protocols includes one or more communication protocols.

30. An apparatus (such as 110 of FIG. 5 ) for facilitating sharing of source data, the apparatus comprising:

a processor (eg, 530 of FIG. 5 ) operable to cause receipt of indicia associated with source data stored in the apparatus or otherwise;

a processor (e.g., 530 of FIG. 5 ) operable to cause an encoded tag to enable communication using a Near Field Communication (NPC) protocol; and

An NPC interface (e.g., 510 of FIG. 5 ) operable to provide communication conveying the indicia to a first device (e.g., 120 of FIG. 6 ) within 5 feet of the device using the NPC protocol, such that the first device is capable of accessing the source data using a communication protocol, wherein the first device cannot access the source data without using a token,

The data transmission rate supported by the NPC is not greater than the data transmission rate supported by the communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the apparatus includes an NPC-enabled device adapted to detect the presence of the first device within 5 feet of the apparatus,

The source data is non-public.

31. The apparatus of clause 30, further comprising an identification module operable to determine source data based on user actions on the apparatus to initiate sharing of source data,

Wherein the NPC protocol is different from the communication protocol.

32. The device of clause 30, wherein the source data is stored on the device, and wherein the processor is operable to cause generation of the marker associated with the source data before causing encoding of the marker.

33. The apparatus of clause 30, wherein the communication protocols include Point-to-Point Protocol, Interactive Connection Establishment Protocol, Session Initiation Protocol, NPC Protocol, Bluetooth Protocol, Wireless Fidelity (WiFi) Protocol, Extensible Messaging and Presence Protocol (XMPP), push protocol or at least one of non-industry standard communication protocols.

34. The apparatus of clause 30, wherein the processor is operable to cause the markup to be encoded in the form of a Uniform Resource Locator (URL) so as to allow the first device to access the source data via a website represented by the URL in the markup.

35. The apparatus as recited in clause 30, wherein the NPC interface is operable to provide a process of communicating a token to the first device to allow the first device to access the source data via the second device,

wherein the means supports communication between said means and a second device to cause receipt of a token from the second device, or to cause access to source data by the first device,

Wherein the marking includes metadata comprising at least some of the following: an identifier of the device, authentication information associated with the device, an identifier of the source data, a path to the source data, wherein the Said marking allows downloading of source data, and wherein said source data is used to set up, configure or manage at least the first device or one or more computers.

36. A method (eg, 700A of FIG. 7A ) of facilitating sharing of source data, the method comprising:

Supports communication between a first device and a remote device based on a first communication protocol, wherein the communication is associated with source data and the communication is based on detection of the second device within less than 5 feet of the first device the presence of (eg, 710 of FIG. 7A );

causing receipt of a first marker (eg, 720 of FIG. 7A ) associated with the source data;

causing encoding of the first indicia to enable communication using a near field communication (NPC) protocol (e.g., 730 of FIG. 7A ); and

Using the NPC protocol to provide communication that communicates the first marker to a second device that is within 5 feet of the first device to enable the second device to access the source data using the second communication protocol, where the second device cannot accessing the source data (e.g., 740 of FIG. 7A ) without using the first tag,

wherein the NPC protocol is different from the first and second communication protocols, and wherein the first communication protocol is the same or different from the second communication protocol,

Wherein the data transmission rate supported by the NPC protocol is neither greater than the data transmission rate supported by the first communication protocol nor greater than the data transmission rate supported by the second communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the first device is an NPC-enabled device configured to detect the presence of the second device within 5 feet of the first device,

Wherein the first device is a communication endpoint device.

37. The method of clause 36, wherein the method comprises determining the source data based on a user action on the first device to begin sharing the source data.

38. The method of clause 36, wherein the method includes determining, on the first device, source data for sharing, wherein the communicating-enabling processing includes providing for using a first communication protocol to identify the processing based on the source data The source data identifying information is communicated from the first device to the remote device via the proxy server, wherein the first communication protocol includes Extensible Messaging and Presence Protocol (XMPP), and wherein the NPC protocol includes a Near Field Communication (NFC) protocol.

39. The method of clause 36, wherein the method comprises: determining source data for sharing,

Wherein, the processing of supporting communication includes: providing communication for transferring identification information of the source data to the remote device, wherein the identification information includes at least one of a remote device identifier, a remote device file system path, or a file name,

wherein the processing to support the communication comprises: providing communication to the remote device communicating a request for the first marker,

Wherein the processing of causing receipt includes: in response to the request, causing receipt of the first marker.

40. The method of clause 36, wherein the method comprises: determining source data for sharing,

wherein said processing to enable communication comprises: causing identification information of the source data to be provided to the remote device, so that the first marker can be generated in real time in response to the processing causing provision of the source data identification information,

wherein causing receipt of the first indicia comprises causing receipt of the first indicia from the remote device via a proxy server using a first communication protocol on the first device in response to causing source data identification information to be provided,

wherein the method comprises: decoding a first indicia received using a first communication protocol prior to encoding,

wherein preparing to communicate the first indicia to the second device comprises: providing communication to communicate the first indicia from the first device to the second device,

Wherein the method comprises: providing communication of other information for accessing the source data from the first device to the second device, wherein the other information includes the location of the source data, wherein the first flag for passing to the second device and other information whose size is smaller than the size of the source data, and where the source data consists of more than one megabyte,

wherein the first communication protocol comprises Extensible Messaging and Presence Protocol (XMPP),

Wherein said encoding process includes encoding the first mark on the first device.

41. The method of clause 36, wherein the method includes at least one of a first security measure and a second security measure,

The first security measures include:

causing receiving, from the remote device, information identifying at least one of the second device or a user of the second device in response to the second device attempting to access the source data; and

providing communication to transfer permission to the remote device after the first device user verifies the received information,

The second security measures include:

When the second device attempts to access the source data, providing a communication to the remote device conveying information identifying at least one of the second device or a user of the second device, such that the remote device can authenticate the second device or the second device's user.

42. The method of clause 36, wherein the method comprises:

providing a request to the remote device to transmit the source data to a second server comprising a cloud server and sending a second token to the first device;

A second device within 5 feet of the first device is provided using the NPC protocol to communicate the second indicia to enable the second device to access the source data communicated to the server.

43. The method of clause 42, wherein the first or second token includes metadata including at least some of the following: an identifier of the remote device, an identifier of a server, an identifier associated with the remote device authentication information associated with the server, the identifier of the source data, the path of the source data, the identifier of the source data transmitted to the server, or the path of the source data transmitted to the server, and the first and second Two tags allow downloading of source data for at least setting up, configuring or managing one or more computers.

44. The method of clause 36, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information.

45. The method of clause 44, wherein:

The media file includes at least one of an audio file, a video file, an audio-video file, or an image,

The remote path information includes at least one of directory name, folder name, subfolder name or file name,

The remote desktop connection information includes at least one of an Internet Protocol (IP) address, username, or password,

The security information includes at least one of network security information or security coding information,

the device management information includes at least one of color depth, resolution, or desktop settings, and

The device configuration includes at least one of network configuration, peripheral device configuration, or client-server configuration.

46. The method of clause 36, wherein the first token is expiring and is a unique representation of one or more of: the source data, the second device, the user of the second device, and a time associated with the creation or use of the first marker, wherein the method comprises at least one of the first method and the second method,

The first method includes:

causing receipt of a second marker associated with the second source data;

encoding the second token to enable communication using the NPC protocol; and

providing communication conveying the second indicia to a third device located less than 5 feet from the first device using the NPC protocol to enable the third device to access the second source data using the third communication protocol,

Wherein the first communication protocol and the third communication protocol are the same or different,

where the Second Token is a unique representation of one or more of: the Second Data, the Third Device, and the time associated with the creation or use of the Second Token,

The second method includes:

causing receipt on the first device of a third marker associated with the source data,

encoding a third token on the first device to enable communication using the NPC protocol; and

providing communication conveying the third indicia to a fourth device located less than 5 feet from the first device using the NPC protocol to enable the fourth device to access the source data using the fourth communication protocol,

Wherein the first communication protocol and the fourth communication protocol are the same or different,

Wherein the third token is a unique representation of one or more of the following: source data, third device, third device user, and time associated with the creation or use of the third token.

47. The method of clause 36, wherein the first device is a mobile device that includes one or more displays, one or more processors, one or more network interfaces, and a non-transitory machine-readable medium, one of or the first network interface of the plurality of network interfaces is configured to support communication based on the first communication protocol, wherein the second network interface of the one or more network interfaces is configured to support communication based on the NPC protocol, wherein the second device is a mobile device, wherein the remote device is a computing device behind a firewall, wherein the first token does not exist until the source data to be shared is determined, and wherein the first token is real-time createable and expired, wherein the first token Each of the first and second communication protocols includes one or more communication protocols.

48. A method of facilitating sharing of source data (eg, 700C of FIG. 7C ), comprising:

causing receipt of a marker (e.g., 780 of FIG. 7C ) associated with the source data;

causing the indicia to be encoded to enable communication using a near field communication (NPC) protocol (eg, 782 of FIG. 7C ); and

Use the NPC protocol to provide a second device within 5 feet of the first device with a communication delivering the token to enable the second device to access the source data using the communication protocol, wherein the second device cannot access the source data without using the token In the case of accessing source data (for example, 784 of FIG. 7C ),

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the first device is an NPC-enabled device adapted to detect the presence of the second device within 5 feet of the first device,

where the markup is non-public.

49. The method of clause 48, wherein the method comprises: determining the source data based on a user action on the first device to initiate sharing of the source data,

wherein the NPC protocol is different from the communication protocol,

The data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the communication protocol.

50. The method of clause 48, wherein the source data is stored on the first device, wherein the method comprises: causing generation of a marker associated with the source data stored on the first device, wherein said process of causing the encoding The token is caused to be received prior to encoding.

51. The method of clause 48, causing the encoding of the markup comprises: causing the markup to be encoded in the form of a Uniform Resource Locator (URL) to allow the second device to access the source data via a website represented by the URL in the markup .

52. The method of clause 48, providing that the process of communicating allows the second device to access the source data via a third device, the third device being a remote device,

Wherein the first device supports communication between the first device and the third device to facilitate receipt of a token from the third device, or to facilitate access of source data by the second device.

53. The method of clause 48, wherein the method for facilitating sharing allows for a distance between the first device and the second device of greater than 5 feet after providing communication of an operation of providing the indicia to the second device, and the method allows access to source data regardless of distance.

54. An apparatus (such as 1100 of FIG. 11 ) for facilitating sharing of source data, the apparatus comprising:

means for enabling communication between a first device and a remote device based on a first communication protocol, wherein the communication is associated with source data and the communication is based on detecting a device within less than 5 feet of the first device to the presence of a second device (eg, 1110 of FIG. 11 );

means for causing receipt of a first marker associated with the source data (eg, 1120 of FIG. 11 );

means for causing encoding of the first indicium to enable communication using a near field communication (NPC) protocol (eg, 1130 of FIG. 11 ); and

means for providing communication using an NPC protocol to communicate a first marker to a second device within 5 feet of the first device to enable the second device to access the source data using the second communication protocol, wherein the first The second device cannot access the source data (such as 1140 of FIG. 11 ) without using the first tag,

wherein the NPC protocol is different from the first and second communication protocols, and wherein the first communication protocol is the same or different from the second communication protocol,

Wherein the data transmission rate supported by the NPC protocol is neither greater than the data transmission rate supported by the first communication protocol nor greater than the data transmission rate supported by the second communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the first device is an NPC-enabled device configured to detect the presence of the second device within 5 feet of the first device,

Wherein the first device is a communication endpoint device.

55. An apparatus (such as 1300 of FIG. 13 ) for facilitating sharing of source data, the apparatus comprising:

means for causing receipt of a marker associated with the source data (e.g., 1310 of FIG. 13);

means for causing encoding of the indicia to enable communication using a Near Field Communication (NPC) protocol (eg, 1320 of FIG. 13 ); and

means for providing, using the NPC protocol, to a second device located within 5 feet of the first device, communicating communicating the indicia to enable the second device to access source data using a communication protocol, wherein the second The device cannot access the source data without using the tag (eg 1330 of Figure 13),

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet,

wherein the first device is an NPC-enabled device adapted to detect the presence of the second device within 5 feet of the first device,

where the markup is non-public.

56. A hardware device comprising means adapted to perform a method associated with any preceding clause.

57. An apparatus comprising means for performing a method associated with any preceding clause.

58. An apparatus comprising one or more processors configured to perform a method associated with any preceding clause.

59. An apparatus comprising one or more processors and a machine-readable medium comprising instructions executable by the one or more processors to perform a method associated with any preceding clause.

Example on decoding clauses

1. A non-transitory machine-readable medium (such as 620, 650 of FIG. 6 ), including instructions stored therein, which can be run/executed by one or more processors (such as 630 of FIG. 6 ) , so as to implement a method for prompting sharing of source data, the method (such as 700B in FIG. 7B ) comprising:

Causes the use of a near field communication (NPC) protocol to receive, at the first device, the first marker associated with the source data from the second device within 5 feet of the first device, the protocol supporting detects the presence of the first device within a range of feet to generate a first token, wherein the first token is an encoded first token for short-range communication, wherein the first token is a non-public token, and wherein the first token Based on the source data for sharing, and wherein the receipt of the first marker is based on the detection (e.g., 750 of FIG. 7B ),

causing the first token to be decoded (eg, 760 of FIG. 7B ),

providing communication based on the first communication protocol to the third device to download the source data using the decoded first token (e.g., 770 of FIG. 7B ),

wherein the first device is an NPC-enabled device having an NPC interface to allow the second device to detect the presence of the first device when the first device is within 5 feet of the second device,

where the second device is an NPC-enabled device,

Wherein the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet.

2. The non-transitory machine-readable medium of clause 1, further comprising: causing the first device to access the source data after a period of time in order to allow the third device to receive from the second device the user-given data of the second device. Source data access permissions for .

3. The non-transitory machine-readable medium described in clause 1, further comprising:

causing the use of the NPC protocol to receive a second token associated with the source data from a second device within 5 feet of the first device, wherein the second token is an encoded second token for near-field communication;

causing decoding of the second token; and

After transmitting the source data to the server, in response to a request from the second device, communication based on the second communication protocol is provided to the server including the cloud server to download the source data using the decoded second token.

4. The non-transitory machine-readable medium of clause 1, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information.

5. The non-transitory machine-readable medium of clause 3, wherein the first indicium or the second indicium contains metadata including at least some of: an identifier of the third device, an identifier of the server An identifier, authentication information associated with a third device, authentication information associated with a server, an identifier of source data, a path of source data, an identifier of source data transmitted to a server, or source data transmitted to a server A path in which the first and second tokens are definite and are unique representations of one or more of the following: the source data, the first device, the user of the first device, and the or the time associated with the creation or use of the second token.

6. The non-transitory machine-readable medium recited in clause 3, further comprising:

providing communication based on the first communication protocol to the third device for downloading the source data for a period prior to expiration of the first token; and

Communication based on the second communication protocol is provided to the server for downloading the source data in a period prior to expiration of the second token.

7. The non-transitory machine-readable medium of clause 3, wherein the first device is a device comprising one or more displays, one or more processors, one or more network interfaces, and the non-transitory machine-readable medium The mobile device of , wherein a first network interface of the one or more network interfaces is configured to support communication based on a first communication protocol or a second communication protocol, and wherein a second of the one or more network interfaces The network interface is configured to support communication based on the NPC protocol, wherein the second device is a mobile device, wherein the third device is a computing device behind a firewall, wherein the first tag and the second tag are preceded by identifying source data to be shared does not exist, and wherein the first token and the second token are real-time createable and time-limited, and wherein each of the first and second communication protocols includes one or more communication protocols.

8. The non-transitory machine-readable medium of clause 1, wherein the third device is a remote device, wherein the source data is stored in the remote device, and wherein the NPC protocol is different from the first communication protocol.

9. The non-transitory machine-readable medium of clause 1, wherein the source data is stored in the second device.

10. The non-transitory machine-readable medium of clause 1, wherein the decoded first token comprises a Uniform Resource Locator (URL), wherein providing the communication comprises: causing opening of the URL on a web browser, In order to allow a determination of whether the first device is able to cause the source data to be downloaded using the decoded first token.

11. A non-transitory machine-readable medium as described in clause 10,

wherein if the first device is enabled to facilitate said downloading, the method comprises causing the source data to be downloaded based on the decoded first token,

Wherein if the first device is not enabled to facilitate said downloading, the method includes providing a communication to the third device with a request to download the source data, and causing receipt of the source data based on the request.

12. The non-transitory machine-readable medium of clause 1, wherein the decoded first token comprises a Uniform Resource Locator (URL), wherein the URL comprises an identifier of the device storing the source data, stored in the device The path to the source data in , along with authentication information.

13. The non-transitory machine-readable medium of clause 1, wherein the first communication protocol comprises a point-to-point protocol, an interactive connection establishment protocol, a session initiation protocol, an NPC protocol, a Bluetooth protocol, a wireless fidelity (WiFi) protocol , Extensible Messaging and Presence Protocol (XMPP), push protocol or at least one of non-industry-standard communication protocols.

14. An apparatus (such as 120 of FIG. 6 ) for facilitating the sharing of source data, the apparatus comprising:

A processor (e.g., 630 of FIG. 6 ) operable to cause receiving of data associated with the source from a first device (e.g., 110 of FIG. 5 ) within 5 feet of the apparatus using a near field communication (NPC) protocol. A first indicia associated with the first device, wherein the first indicium is based on detecting the presence of the device within 5 feet of the first device, wherein the first indicia is an encoded first indicia for short-range communication, wherein the first indicia a marker is a non-public marker, and wherein the first marker is based on source data for sharing,

a processor (eg, 630 of FIG. 6 ) operable to cause decoding of the first token;

a processor (eg, 630 of FIG. 6 ) operable to provide communication based on the first communication protocol to the second device to download the source data using the decoded first token,

wherein the device is an NPC-enabled device having an NPC interface to allow the first device to detect the presence of the device when the device is within 5 feet of the first device,

where the first device is the NPC-enabled device,

Wherein the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet.

15. The apparatus of clause 14, wherein the processor is operable to cause the apparatus to access the source data after a period of time in order to allow the second device to receive from the first device a user-given Source Data Access Permission.

16. The apparatus of clause 14, wherein the processor is operable to cause receiving a second marker associated with the source data from a first device within 5 feet of the apparatus using an NPC protocol, wherein the The second token is an encoded second token for short-range communication; wherein the processor is operable to cause decoding of said second token; and wherein, after transmitting the source data to the server, in response to a request from the first device The processor is operable to provide communication based on the second communication protocol to the server, including the cloud server, for downloading the source data using the decoded second token.

17. The apparatus of clause 14, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information.

18. The apparatus of clause 16, wherein the first marker or the second marker contains metadata including at least some of the following: an identifier of the second device, an identifier of the server, and the second The authentication information associated with the device, the authentication information associated with the server, the identifier of the source data, the path of the source data, the identifier of the source data transmitted to the server, or the path of the source data transmitted to the server, wherein the first and the second token are limited in time and are unique representations of one or more of the following: source data, the device, the user of the device, and the creation of the first token or the second token Or use the relevant time.

19. The device of clause 16, wherein:

the processor is operable to provide communication based on the first communication protocol to the second device for downloading the source data in a period prior to expiration of the first token; and

The processor is operable to provide communication based on the second communication protocol to the server for downloading the source data in a period prior to expiration of the second token.

20. The apparatus of clause 16, wherein the apparatus is a mobile device comprising one or more displays, one or more processors, one or more network interfaces, and a non-transitory machine-readable medium, wherein the second The device is a computing device behind a firewall, wherein the first token and the second token do not exist until the source data to be shared is determined, and wherein the first token and the second token are created in real-time and have an expiration date, and wherein The first and second indicia allow downloading of source data for at least setting up, configuring or managing one or more computers, and wherein each of the first and second communication protocols includes one or more communication protocol.

21. The device of clause 14, wherein the second device is a remote device, wherein the source data is stored in the remote device, and wherein the NPC protocol is different from the first communication protocol.

22. The device of clause 14, wherein the source data is stored in the first device.

23. The device of clause 14, wherein the decoded first token comprises a Uniform Resource Locator (URL), wherein the processor is operable to cause opening of said URL on a web browser to allow determination of said URL. Whether the device can cause the source data to be downloaded using the decoded first token.

24. A device as described in clause 23,

wherein if said means is enabled to cause said downloading, the processor is operable to cause downloading of source data based on the decoded first token,

Wherein if the means is not enabled to facilitate the downloading, the processor is operable to prepare a communication to the second device for a request to download the source data, and to cause receipt of the source data based on the request.

25. A method (eg, 700B of FIG. 7B ) of facilitating sharing of source data, comprising:

Causes the use of a near field communication (NPC) protocol to receive, at the first device, the first marker associated with the source data from the second device within 5 feet of the first device, the protocol supporting detects the presence of the first device within feet to generate a first token, wherein the first token is an encoded first token for short-range communication, wherein the first token is a non-public token, and wherein the first token is based on based on shared source data, and wherein the receipt of the first marker is based on the detection (eg, 750 of FIG. 7B );

causing the first token to be decoded (e.g., 760 of Figure 7B);

providing communication based on the first communication protocol to the third device to download the source data using the decoded first token (e.g., 770 of FIG. 7B ),

wherein the first device is an NPC-enabled device having an NPC interface to allow the second device to detect the presence of the first device when the first device is within 5 feet of the second device,

where the second device is an NPC-enabled device,

Wherein the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet.

26. The method of clause 25, further comprising causing the first device to access the source data after a period of time in order to allow the third device to receive source data access permission from the second device from a user of the second device.

27. The method of clause 25, further comprising:

causing the use of the NPC protocol to receive a second token associated with the source data from a second device within 5 feet of the first device, wherein the second token is an encoded second token for near-field communication ;

causing decoding of the second token; and

After transmitting the source data to the server, in response to a request from the second device, communication based on the second communication protocol is provided to the server including the cloud server to download the source data using the decoded second token.

28. The method of clause 25, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information.

29. The method of clause 27, wherein the first marker or the second marker contains metadata including at least some of the following: an identifier of the third device, an identifier of the server, and a third The authentication information associated with the device, the authentication information associated with the server, the identifier of the source data, the path of the source data, the identifier of the source data transmitted to the server, or the path of the source data transmitted to the server, wherein the first and Secondary Tokens are limited in duration and are unique representations of one or more of the following: source data, the Second Device, the user of the Second Device, and the creation of either the First Token or the Second Token Or use the relevant time.

30. The method of clause 27, further comprising:

providing communication based on the first communication protocol to the third device for downloading the source data for a period prior to expiration of the first token; and

Communication based on the second communication protocol is provided to the server for downloading the source data for a period prior to expiration of the second token.

31. The method of clause 25, wherein the third device is a remote device, wherein the source data is stored in the remote device, and wherein the NPC protocol is different from the first communication protocol.

32. The method of clause 25, wherein the source data is stored in the second device.

33. The method of clause 25, wherein the decoded first token comprises a Uniform Resource Locator (URL), wherein providing the communication comprises: causing the URL to be opened on a web browser to allow a determination of whether the first device Downloading of source data using the decoded first token can be caused.

34. A method as described in clause 33,

wherein if the first device is enabled to facilitate said downloading, the method comprises causing the source data to be downloaded based on the decoded first token,

Wherein if the first device is not enabled to facilitate said downloading, the method includes providing a communication to the third device requesting download of the source data, and causing receipt of the source data based on the request.

35. An apparatus (such as 1200 of FIG. 12 ) for facilitating sharing of source data, comprising:

Means for causing, on a first device, to receive a first marker associated with source data from a second device within 5 feet of the first device using a near field communication (NPC) protocol that supports The second device detects the presence of the first device within 5 feet to generate a first token, wherein the first token is an encoded first token for short-range communication, wherein the first token is a non-public token, and wherein the first token is a non-public token, and wherein a flag is based on the source data for sharing, and wherein the receipt of the first flag is based on the detection (e.g. 1210 of FIG. 12 ),

means (eg, 1220 of FIG. 12 ) for causing the first token to be decoded,

means for providing communication based on the first communication protocol to the third device so as to download the source data using the decoded first token (for example, 1230 of FIG. 12 ),

wherein the first device is an NPC-enabled device having an NPC interface to allow the second device to detect the presence of the first device when the first device is within 5 feet of the second device,

where the second device is an NPC-enabled device,

Wherein the data transmission rate supported by the NPC protocol is not greater than the data transmission rate supported by the first communication protocol,

Wherein the NPC protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet.

36. A hardware device comprising means adapted to perform a method associated with any preceding clause.

37. An apparatus comprising means for performing a method associated with any preceding clause.

38. An apparatus comprising one or more processors configured to perform a method associated with any preceding clause.

39. An apparatus comprising one or more processors and a machine-readable medium comprising instructions executable by the one or more processors to perform a method associated with any preceding clause.

In one aspect, any clause herein may be subordinated to any independent clause or any dependent clause. And in one aspect, any clause (eg, dependent or independent clause) can be combined with any other clause (eg, dependent or independent clause). In one aspect, a claim may contain some or all of the words (eg, steps, operations, means or components) mentioned in a clause, sentence, phrase or paragraph. And in an aspect, a claim may include some or all of the words recited in one or more clauses, sentences, phrases or paragraphs. In one aspect, some words in each clause, statement, phrase or paragraph are removable. Additionally, in one aspect, additional words or elements may be added to the clause, statement, phrase or paragraph. In one aspect, the subject technology can be practiced without some of the components, elements, functions or operations described herein. Furthermore, in one aspect, the subject technology may also be implemented with additional components, elements, functions or operations.

In one aspect, any method, instruction, code, device, logic, component, component, module, etc. (eg, software or hardware) described or claimed herein may be represented graphically (eg, flowchart, block diagram), Such figures, whether explicitly shown or not, are expressly incorporated herein by reference, and such figures, if not explicitly shown, may be added to this disclosure without constituting a new matter. For clarity, some (but not necessarily all) clauses/descriptions/claims are graphically explicit, but any clause/description/claim may be represented in a drawing similar to the figure in which it is explicitly shown way to express. For example, a flow diagram may be drawn here for the clauses, sentences or claims of a method whereby each operation or step is connected to the next operation or step by an arrow. In another example, a clause, sentence, or claim having an element of "means for" (eg, means for performing a certain act) could be block diagrammed whereby each could be used in a... An element of a device is represented as a module for the element (eg, a module for performing an operation).

Those skilled in the art will appreciate that the different items described herein, such as the various illustrative components, modules, elements, components, methods, operations, steps, and algorithms (e.g., components or operations on the client 102 or server 104/304) Both may be implemented as hardware, computer software, or a combination of both.

To illustrate this interchangeability of hardware and software, items such as the various illustrative components, modules, elements, components, methods, operations, steps and algorithms are described herein primarily in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application.

In one aspect, a "means", part, module, element, component or processor may be an item for performing one or more functions or operations (such as one or more of a part, module, element, component or processor) indivual). In one aspect, such items may be equipment, hardware, or parts thereof. As an example, in one example, a project may have a structure in the form of one or more instructions for performing one or more functions or one or more operations, wherein the one or more instructions are encoded or stored in One or more instructions may be software, one or more applications, one or more subroutines, or a part thereof. In one example, an item may be implemented as one or more circuits configured to perform one or more functions or one or more operations. A circuit may include one or more circuits and/or logic. The circuitry may be analog and/or digital. Furthermore, the circuits may also be electronic and/or optical. In addition, the circuit may also include transistors. In one example, one or more items may be implemented as a processing system (eg, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), etc.). Those skilled in the art will recognize how to implement these instructions, circuits and processing systems.

Reference to an element in the singular does not mean "there is and only one" unless otherwise specified, but means "one or more". For example, a client device can refer to one or more client devices, a connection can refer to one or more connections, and a message, request, reply, or stream can refer to one or more messages, requests, replies, or streams .

Unless specifically stated otherwise, the term "some" means one or more. Masculine pronouns (such as his) encompass the feminine and neuter gender (such as her and its) and vice versa. Headings and subheadings appearing herein are used for convenience only and do not limit the invention.

The word "exemplify" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as superior or preferred over other aspects or designs. In one aspect, the various alternative configurations and operations described herein may be considered at least equivalent.

Phrases such as "aspects" neither imply that such aspects are essential to the subject technology nor that such aspects apply to all configurations of the subject technology. A disclosure associated with an aspect may apply to all configurations, or to one or more configurations. An aspect may provide one or more examples. Phrases such as aspects may refer to one or more aspects and vice versa. Phrases such as "an embodiment" neither imply that the embodiment is required by the subject technology nor that the embodiment applies to all configurations of the subject technology. A disclosure associated with one embodiment may apply to all embodiments, or to one or more embodiments. An embodiment may provide one or more examples. A phrase such an embodiment may refer to one or more embodiments and vice versa. A phrase such as "a configuration" neither implies that the configuration is required by the subject technology nor does it imply that the configuration applies to all configurations of the subject technology. A disclosure associated with a configuration may apply to all configurations, or to one or more configurations. A configuration can provide one or more instances. The phrase "such configurations" may refer to one or more configurations and vice versa.

It should be understood that in one aspect of this disclosure, if an operation or function is described as being performed by an item (e.g. modify, intercept, redirect, determine, obtain, create, operate, delete, remove, receive, provides, produces, converts, displays, informs, receives, selects, controls, transmits, reports, sends or any other operation or function), then such operation or function may be performed directly or indirectly by the item. In one aspect, when a module is described as performing an operation, the module may be understood as directly performing the operation. In the same aspect, when a module is described as performing an operation, the module may be understood as performing that operation indirectly, for example by causing, enabling, or causing such operation to be performed.

In one aspect, unless otherwise stated, all measurements, values, levels, positions, magnitudes, sizes and other specifications set forth in this specification, including the claims below, are approximate and not exact. In one aspect, this is done with a reasonable scope consistent with the associated functionality and conventions in the field involved.

In one aspect, "coupled" and like terms may refer to direct coupling. In another aspect, "coupled" and like terms may refer to an indirect connection.

Different items may be arranged in different ways (eg, arranged in a different order or divided in a different way) without departing from the scope of the present technical subject matter. In an aspect of the present disclosure, elements recited in the appended claims may be implemented by one or more modules or sub-modules.

It is understood that the specific order or hierarchy of disclosed steps, operations, or processes is illustrative of illustrative methods. In addition, it is understood that the specific order or hierarchy of steps, operations or processes may be rearranged based on design preferences. Some steps, operations or processes may be performed concurrently. Furthermore, some or all of the steps, operations or processes may be performed automatically without user intervention. If accompanied by method claims, such claims present the various steps, operations, or processing elements in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

This disclosure is provided to enable those skilled in the art to practice the various aspects described herein. The present disclosure provides various examples regarding the technical subject matter, and the technical subject matter is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein will apply to other aspects as well.

All structural and functional equivalents to the elements of the various aspects described in this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and the claims are intended to encompass such equivalents. Furthermore, these disclosures should be dedicated to the public at no charge regardless of whether they are explicitly recited in the claims. Unless the phrase "means for" is expressly used to describe a component, or the phrase "step for" is used to describe an element in a method claim, it cannot be claimed under paragraph 6 of 35 U.S.C. & 112 Explain the elements in the claims. In addition, in the sense of using terms such as "comprising", "having", etc., similar to the interpretation made when the term "comprising" is used as a transitional word in the claims, such terms should also be inclusive.

The Title, Background, Summary, Drawings, and Abstract are incorporated into this disclosure and are presented as illustrative examples of the disclosure rather than as a restrictive description. These should be submitted with the understanding that they will not limit the scope or meaning of the claims. In addition, it can be seen in the Detailed Description that the Detailed Description provides illustrative examples and various features are grouped in different embodiments in order to simplify the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed arrangement or operation. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

These claims are not limited to the aspects described herein, but are to be accorded full scope to the text claims and encompassing all statutory equivalents. However, none of the claims contain subject matter that does not satisfy the requirements of 35 U.S.C. § 101, 102, or 103, and the claims should not be construed in this manner. Accordingly, such topics are discarded if they are inadvertently included.

Claims (37)

1. An apparatus for sharing source data located on a remote device, the apparatus comprising: a first network interface configured to communicate with the remote device based on a first communication protocol; an encoder configured to receive a first indicia associated with the source data, and encode the first indicia for communication using a short-range communication protocol; and a short-range communication interface configured to communicate the first indicia to a first device within 5 feet of the apparatus using the short-range communication protocol to enable the first device to use a second communication protocol to access the source data on the remote device, wherein the first device cannot access the source data on the remote device without using the first token, wherein the short-range communication protocol is different from both the first communication protocol and the second communication protocol, wherein said short-range communication protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet; wherein said first flag is non-public, is based on said source data for sharing, and is generated after the presence of said first device is detected within a range of less than 5 feet from the apparatus. 2. The apparatus according to claim 1, wherein the data transmission rate supported by the short-range communication protocol is neither greater than the data transmission rate supported by the first communication protocol, nor greater than the data transmission rate supported by the second communication protocol. Transmission rate. 3. The apparatus of claim 1, further comprising: an identification module configured to determine the source data based on a user operation on the device, and to provide identification information of the source data for sharing the source data; and a second network interface configured to transmit the identification information from the apparatus to the remote device via a proxy server based on the first communication protocol, wherein said first communication protocol comprises an Extensible Messaging and Presence Protocol, Wherein the short-range communication protocol includes a near-field communication protocol, The identification information includes at least one of an identifier of the remote device, a path in a file system of the remote device, or a file name. 4. The apparatus of claim 1, further comprising: an identification module configured to determine the source data based on a user operation on the device, and to provide identification information of the source data for sharing the source data, wherein the first network interface is further configured to support communication of the identification information from the apparatus to the remote device based on the first communication protocol, The identification information includes at least one of an identifier of the remote device, a path in a file system of the remote device, or a file name. 5. The apparatus of claim 1, further comprising: an identification module configured to determine the source data based on a user operation on the device, and to provide identification information of the source data for sharing the source data, wherein the first network interface is configured to transmit identification information of the source data to the remote device such that the first indicia can be generated in real time in response to a communication providing identification information of the source data, wherein said first network interface is further configured to receive said first communication from said remote device at the apparatus using said first communication protocol and via a proxy server in response to a communication providing identification information of said source data a mark, wherein the means comprises a decoder for decoding said first indicia received using said first communication protocol prior to encoding, wherein the first network interface is further configured to transmit the first indicia from the apparatus to the first device, wherein the first network interface is further configured to communicate the location of the source data for accessing the source data from the apparatus to the first device, wherein the size of the location of the first marker and the source data passed to the first device is smaller than the size of the source data, Wherein said source data includes more than one megabyte of bytes. 6. The apparatus of claim 1, further comprising: a security module configured to implement at least one of a first security measure and a second security measure, The first security measures include: receiving from the remote device via the first network interface information identifying at least one of the first device or a user of the first device in response to the first device attempting to access the source data ;as well as transmitting a permission to said remote device via said first network interface after a user of said apparatus has verified the received information, Wherein said second security measures include: transmitting to the remote device via the first network interface information identifying at least one of the first device or a user of the first device when the first device attempts to access the source data, to enable the remote device to authenticate the first device or a user of the first device. 7. The apparatus of claim 1, wherein the first network interface is further configured to provide a request to the remote device to transmit the source data to a server comprising a cloud server, and to transmit the second flags are sent to the device, and wherein the short-range communication interface is further configured to transmit the second indicia to a first device located within 5 feet of the apparatus using the short-range communication protocol, such that the first device can access the transmitted Source data to this server. 8. The apparatus of claim 7, wherein the first indicia or the second indicia comprise metadata comprising at least some of: an identifier of the remote device, the An identifier of a server, authentication information associated with said remote device, authentication information associated with said server, an identifier of source data stored in said remote device, source data stored in said remote device the path of the source data transmitted to the server, or the path of the source data transmitted to the server. 9. The apparatus of claim 7, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information, and wherein: The media file includes at least one of an audio file, a video file, an audio-video file, or an image, The remote path information includes at least one of directory name, folder name, subfolder name or file name, The remote desktop connection information includes at least one of an Internet Protocol address, a user name or a password, The security information includes at least one of network security information or security coding information, the device management information includes at least one of color depth, resolution, or desktop settings, and The device configuration information includes at least one of network configuration, peripheral device configuration, or client-server configuration. 10. The apparatus of claim 1, wherein the first token is expiring and is a unique representation of one or more of: the source data, the first device, a user of the first device, and a time associated with the creation or use of the first token, wherein the apparatus is configured to send Each of the plurality of first indicia is transmitted to one of the plurality of first devices to support the plurality of first devices, wherein each of the plurality of first indicia is one or more of the following independent Some represent: the source data, one of the plurality of first devices, a user of the one of the plurality of first devices, and a time associated with the creation or use of the plurality of first tokens. 11. The apparatus of claim 1, wherein the apparatus is a mobile device comprising one or more displays, one or more processors, one or more non-transitory machine-readable media, wherein the first the device is another mobile device, wherein the remote device is a computing device located behind a firewall, wherein the first token does not exist prior to determining the source data to be shared, wherein the first token can be created in real-time, and Indefinite, wherein each of said first communication protocol and said second communication protocol includes one or more communication protocols. 12. An apparatus for sharing source data located on a remote device, the apparatus comprising: a processor operable to receive, via a communication protocol, an indicia associated with source data stored in said remote device; a processor operable to encode said indicia to enable communication using a short-range communication protocol; and a short-range communication interface operable to communicate the indicia to a first device within 5 feet of the apparatus using the short-range communication protocol to enable the first device to access the indicia using the communication protocol source data on said remote device, wherein said first device cannot access source data on said remote device without using said token, wherein said short-range communication protocol is different from said communication protocol, wherein said short-range communication protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet, wherein the apparatus comprises a short-range communication enabled device adapted to detect the presence of said first device within 5 feet of the apparatus, wherein said source data is non-public, wherein the flag is non-public, is based on source data for sharing, and is generated after the presence of the first device is detected within a range of less than 5 feet from the device. 13. The apparatus of claim 12, wherein the data transmission rate supported by the short-range communication protocol is not greater than the data transmission rate supported by the communication protocol. 14. The device of claim 12, further comprising an identification module operable to determine the source data based on user actions on the device to initiate sharing of the source data. 15. The apparatus of claim 12, wherein the source data is stored on the apparatus, wherein the processor is operable to generate a marker associated with the source data prior to encoding the marker. 16. The apparatus of claim 12, wherein the communication protocols include Point-to-Point Protocol, Interactive Connection Establishment Protocol, Session Initiation Protocol, Bluetooth Protocol, Wireless Fidelity Protocol, Extensible Messaging and Presence Protocol, Push Protocol Or at least one of non-industry-standard communication protocols. 17. The apparatus of claim 12, wherein the processor is operable to encode the marker in the form of a Uniform Resource Locator so as to allow the first device to access Access said source data. 18. The apparatus of claim 12, wherein the short-range communication interface is operable to communicate a marker to the first device so as to allow the first device to access the source data via a second device, wherein the means supports communication between said means and said second device to receive said indicia from said second device or to cause said first device to access said source data, wherein the indicia includes metadata comprising at least some of the following: an identifier of the device, authentication information associated with the device, an identifier of the source data, the source A path of data, wherein said marking allows downloading of said source data, wherein said source data is used at least to set up, configure or manage said first device or one or more computers. 19. A method for sharing source data located on a remote device, the method comprising: receiving a first marker associated with the source data via a first communication protocol between the first device and the remote device; encoding the first token to enable communication using a short-range communication protocol; and Using the short-range communication protocol to communicate the first tag to a second device within 5 feet of the first device, such that the second device can use the second communication protocol to access the source data on a remote device, wherein the second device cannot access the source data on the remote device without using the first token, wherein the short-range communication protocol is different from both the first communication protocol and the second communication protocol, wherein said short-range communication protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet, wherein the first device is a proximity communication enabled device configured to detect the presence of the second device within 5 feet of the first device, Wherein the first device is a communication endpoint device, Wherein the first flag is non-public, is based on the source data for sharing, and is generated after the presence of the second device is detected within a range of less than 5 feet from the first device. 20. The method of claim 19, wherein the data transmission rate supported by the short-range communication protocol is neither greater than the data transmission rate supported by the first communication protocol, nor greater than the data transmission rate supported by the second communication protocol. Transmission rate. 21. The method of claim 19, wherein the method comprises determining the source data based on a user action on the first device to initiate sharing of the source data. 22. The method of claim 19, wherein the method comprises: Determining source data for sharing on the first device, wherein receiving the first marker includes: using the first communication protocol, transferring the source data identification information based on the determining the source data from the The first device is provided to the remote device through a proxy server, wherein the first communication protocol includes an Extensible Messaging and Presence Protocol. 23. The method of claim 19, wherein the method comprises: determining source data for sharing, Wherein receiving the first mark includes: providing identification information of the source data to the remote device, wherein the identification information includes at least one of a remote device identifier, a remote device file system path, or a file name, wherein receiving the first indicia comprises: providing a request for the first indicia to the remote device, Wherein receiving includes: receiving the first mark in response to the request. 24. The method of claim 19, wherein the method comprises: determining source data for sharing, wherein receiving the first marker comprises: providing identification information of the source data to the remote device, so that the first marker can be generated in real time in response to providing the source data identification information, wherein receiving the first indicia comprises, in response to providing the source data identification information, receiving the first indicia from the remote device via a proxy server using the first communication protocol at the first device, wherein the method comprises: decoding said first indicia received using said first communication protocol prior to encoding, wherein transmitting the first indicia to the second device comprises: transmitting the first indicia from the first device to the second device, Wherein the method includes: transferring from the first device to the second device other information for accessing the source data, wherein the other information includes the location of the source data for transferring to the The size of the first tag and other information of the second device is smaller than the size of the source data, wherein the source data comprises more than one megabyte, wherein said first communication protocol comprises an Extensible Messaging and Presence Protocol, Wherein the encoding process includes encoding the first indicia on the first device. 25. The method of claim 19, wherein the method includes at least one of a first security measure and a second security measure, The first security measures include: receiving from the remote device information identifying at least one of the second device or a user of the second device in response to the second device attempting to access the source data; and transmitting permission to the remote device after the user of the first device verifies the received information, Wherein said second security measures include: When the second device attempts to access the source data, transmitting to the remote device information identifying at least one of the second device or a user of the second device to enable the remote device Authenticating the second device or a user of the second device. 26. The method of claim 19, wherein the method comprises: providing a request to the remote device to transmit the source data to a server comprising a cloud server, and sending a second token to the first device; communicating the second token to the second device within 5 feet of the first device using the short-range communication protocol to enable the second device to access source data communicated to the server . 27. The method of claim 26, wherein the first indicia or the second indicia include metadata including at least some of the following: an identifier of the remote device, the The identifier of the server, the authentication information associated with the remote device, the authentication information associated with the server, the identifier of the source data, the path of the source data, the source data transmitted to the server an identifier, or a path to source data transmitted to said server, and wherein said first and said second flags allow downloading of said source data, wherein said source data is used at least to set up, configure or manage one or Multiple computers. 28. The method of claim 19, wherein the source data includes at least one of media files, documents, remote path information, remote desktop connection information, security information, device management information, or device configuration information. 29. The method of claim 28, wherein: The media file includes at least one of an audio file, a video file, an audio-video file, or an image, The remote path information includes at least one of directory name, folder name, subfolder name or file name, The remote desktop connection information includes at least one of an Internet Protocol address, a user name or a password, The security information includes at least one of network security information or security coding information, the device management information includes at least one of color depth, resolution, or desktop settings, and The device configuration information includes at least one of network configuration, peripheral device configuration, or client-server configuration. 30. The method of claim 19, wherein the first token is expiring and is a unique representation of one or more of: the source data, the second device, a user of said second device, and a time associated with the creation or use of said first token, wherein the method comprises at least one of a first method and a second method, Wherein said first method comprises: receiving a second marker associated with the second source data; encoding the second tag to enable communication using the short-range communication protocol; and Using the short-range communication protocol to transmit the second indicia to a third device within 5 feet of the first device, such that the third device can access the second device using a third communication protocol. source data, wherein said second token is a unique representation of one or more of: said second source data, said third device, and a time associated with the creation or use of said second token, Wherein said second method comprises: receiving a third marker associated with the source data at the first device, encoding the third indicia on the first device to enable communication using the short-range communication protocol; and transmitting the third indicia to a fourth device located within 5 feet of the first device using the short-range communication protocol to enable the fourth device to access the source data using a fourth communication protocol, wherein the third token is a unique representation of one or more of: the source data, the third device, the user of the third device, and the creation of the third token Or use the relevant time. 31. The method of claim 19, wherein the first device is a mobile device comprising one or more displays, one or more processors, one or more network interfaces, wherein the one or more A first network interface of the network interfaces is configured to communicate based on the first communication protocol, wherein a second network interface of the one or more network interfaces is configured to communicate based on the short-range communication protocol, wherein The second device is a mobile device, wherein the remote device is a computing device located behind a firewall, wherein the first indicia does not exist prior to determining the source data to be shared, wherein the first indicia is real-time createable and time-limited, wherein each of the first communication protocol and the second communication protocol includes one or more communication protocols. 32. A method for sharing source data located on a remote device, comprising: receiving an indicia associated with the source data at a first device via a first communication protocol; encoding the indicia to enable communication using a short-range communication protocol; and transmitting the indicia to a second device located within 5 feet of the first device using the short-range communication protocol to enable the second device to access all information on the remote device using the second communication protocol said source data, wherein said second device cannot access said source data on said remote device without using said token, wherein said short-range communication protocol is a wireless communication protocol that supports automatic connection between at least two devices within a distance of less than 5 feet, wherein the short-range communication protocol is different from both the first communication protocol and the second communication protocol, wherein the first device is a proximity communication enabled device adapted to detect the presence of the second device within 5 feet of the first device, wherein the flag is non-public, is based on source data for sharing, and is generated after detecting the presence of the second device within a range of less than 5 feet from the first device. 33. The method of claim 32, wherein the method comprises: determining the source data based on a user action on the first device to begin sharing the source data, wherein said short-range communication protocol is different from said first communication protocol and said second communication protocol, Wherein the data transmission rate supported by the short-distance communication protocol is neither greater than the data transmission rate supported by the first communication protocol, nor greater than the data transmission rate supported by the second communication protocol. 34. The method of claim 32, wherein the source data is stored on the first device, wherein the method comprises: generating the source data associated with the source data stored on the first device The indicia, wherein the encoding includes receiving the indicia prior to encoding. 35. The method of claim 32, encoding the indicia comprises: encoding the indicia in the form of a Uniform Resource Locator to allow the second device to access the website to access the source data. 36. The method of claim 32, the communicating allowing the second device to access the source data via a third device, the third device being a remote device, Wherein the first device communicates with the third device to receive the mark from the third device, or to cause the second device to access the source data. 37. The method of claim 32 , wherein the method for sharing allows the distance between the first device and the second device to be greater than 5 feet, and the method allows access to said source data regardless of distance.