WO2016050143A1

WO2016050143A1 - Method for sharing resources between devices and electronic device

Info

Publication number: WO2016050143A1
Application number: PCT/CN2015/089957
Authority: WO
Inventors: 魏鹏飞
Original assignee: 阿里巴巴集团控股有限公司; 魏鹏飞
Priority date: 2014-09-29
Filing date: 2015-09-18
Publication date: 2016-04-07
Also published as: CN105530590A

Abstract

Embodiments of the present application provide a method for sharing resources between devices and an electronic device. The method comprises: during the process of starting a resource browsing application to browse a resource, detecting a trigger condition of activating a near field communication (NFC) communication link to realize resource information sharing; encapsulating a resource identifier of the resource browsed by the resource browsing application as load information into an NFC data packet; and sending the NFC data packet to a receiver device so that the receiver device parses out the resource identifier according to the NFC data packet and acquires the resource by using the resource identifier. According to the embodiments of the present application, a resource identifier can be transferred through an NFC communication link between a sender device and a receiver device, and a resource can be acquired by using the resource identifier; because the resource identifier is transferred through the NFC communication link, a wireless local area network is not required, and because the resource is acquired by using the resource identifier, the sender device and the receiver device no longer need to join the same wireless local area network.

Description

Method and electronic device for sharing resources between devices

Technical field

The present application belongs to the field of wireless communication technologies, and in particular, to a method and an electronic device for sharing resources between devices.

Background technique

In the prior art, the multimedia file sharing such as video between the electronic devices such as the wireless smart device mainly shares the URI (Uniform Resource Identifier) of the multimedia, and then the electronic device acquires the multimedia file according to the received URI. Play. The URI of the multimedia file belongs to the resource information of the multimedia file. Currently, the URI sharing technology of the multimedia file mainly includes the DLNA (Digital Living Network Alliance) based on the UPNP (Universal Plug and Play) protocol. Alliance technology, Apple's Air Play technology, etc., these technologies undoubtedly need to share the same LAN environment based on WIFI connection, that is, the resource information sharing before acquiring multimedia files for playback needs to be in the same LAN.

Today, with the popularization of smart devices such as smart phones, people increasingly need to share files between electronic devices anytime and anywhere. Obviously, it is very inconvenient to restrict people from going to the same WIFI-based LAN.

Summary of the invention

The purpose of the embodiments of the present application is to provide a method and an electronic device for sharing resources between devices, which can implement point-to-point sharing between devices without adding to the same WLAN.

To solve the above technical problem, the embodiment of the present application provides a method for sharing resources between devices and an electronic device is implemented as follows:

In one aspect, the embodiment of the present application provides a method for sharing resources between devices, including:

In the process of browsing the resource by the resource browsing application, detecting a trigger condition for starting the NFC communication link of the incoming communication to realize resource information sharing;

The resource identifier of the resource browsed by the resource browsing application is encapsulated into the NFC data packet as load information;

And sending the NFC data packet to the receiver device, so that the receiver device parses the resource identifier according to the NFC data packet, and acquires the resource by using the resource identifier.

In a preferred embodiment, the method further includes:

The progress information browsed by the resource browsing application is encapsulated into the NFC data package as load information.

In a preferred embodiment, the resource identifier of the resource browsed by the resource browsing application and the progress information browsed are encapsulated into the load information of the same NFC data packet.

In a preferred embodiment, the triggering condition for starting the NFC communication link to implement resource information sharing includes: an event that is touched by the receiver device occurs.

In a preferred embodiment, the method further includes: after detecting a trigger condition for starting the NFC communication link to implement resource information sharing, continuing to determine whether the current resource browsing application provides the resource identifier of the browsed resource.

In a preferred embodiment, the resource identifier is a uniform resource identifier URI.

Another aspect of the embodiment of the present application further provides a method for sharing resources between devices, including:

After receiving the NFC data packet, extracting the resource identifier from the load information of the NFC data packet;

Finding a resource browsing application capable of processing the extracted resource identifier;

Obtaining, according to the resource identifier, the resource identified by the resource identifier;

The resource browsing application is used to browse the resource identified by the resource identifier.

In a preferred embodiment, the method further includes:

Progress information is also extracted from the NFC data packet;

When browsing the resource identified by the resource identifier by using the resource browsing application, browsing starts from the location identified by the progress information.

In a preferred embodiment, the resource browsing application capable of processing the extracted resource identifier includes:

The search is performed by the protocol header of the resource identifier, and a resource browsing application capable of processing the resource identifier is obtained.

A further aspect of the embodiments of the present application further provides an electronic device, including:

The detecting unit is configured to detect, when the resource browsing application is enabled to browse the resource, whether a trigger condition for starting the NFC communication link to implement resource information sharing is detected;

a resource identifier encapsulating unit, configured to encapsulate the resource identifier of the resource browsed by the resource browsing application as load information into an NFC data packet after the detecting unit detects the triggering condition;

And an NFC communication unit, configured to send the NFC data packet to the receiver device, so that the receiver device parses the resource identifier according to the NFC data packet, and acquires the resource by using the resource identifier.

In a preferred embodiment, the method further includes:

The progress information encapsulating unit is configured to encapsulate the progress information browsed by the resource browsing application as load information into the NFC data package.

In a preferred embodiment, the resource representation encapsulation unit and the progress information encapsulation unit specifically encapsulate the resource identifier and the progress information of the resource browsed by the resource browsing application into the load information of the same NFC data packet.

In a preferred embodiment, the triggering condition for enabling the NFC communication link to implement resource information sharing includes: an event that is touched by the receiver device occurs.

In a preferred embodiment, the method further includes:

The resource identifier existence identifying unit is configured to determine, after the detecting unit detects the trigger condition, whether the current resource browsing application provides the resource identifier of the browsed resource.

In a preferred embodiment, the resource identifier is a URI.

Another aspect of the embodiment of the present application further provides an electronic device, including:

a resource identifier extracting unit, configured to extract a resource identifier from load information of the NFC data packet after receiving the NFC data packet;

An application matching unit, configured to search for a resource browsing application capable of processing the extracted resource identifier;

a resource obtaining unit, configured to acquire, according to the resource identifier, a resource identified by the resource identifier;

The initiating unit is configured to start the resource browsing application to browse the resource identified by the resource identifier.

In a preferred embodiment, the application matching unit includes:

The protocol matching unit is configured to perform a search by using a protocol header of the resource identifier, and obtain a resource browsing application capable of processing the resource identifier.

In a preferred embodiment, the method further includes:

a progress information extracting unit, configured to extract progress information from the received NFC data packet;

The initiating unit is specifically configured to start the resource browsing application, browse the resource identified by the resource identifier, and start browsing from the location identified by the progress information.

It can be seen that the technical solution provided by the foregoing embodiment of the present application can implement that the resource identifier is transmitted between the sender device and the receiver device through the NFC communication link, and the resource identifier is used to obtain the resource, because the resource identifier is adopted by the NFC. The communication link does not need to be implemented by means of the WLAN, and the resource identification by the resource identifier eliminates the need for the sender device and the receiver device to join the same WLAN, thereby reducing the resource sharing requirements for the network environment.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a few embodiments described in the present application, and other drawings can be obtained from those skilled in the art without any inventive labor.

FIG. 1 is a flowchart of a method for sharing resources between devices according to an embodiment of the present application;

2 is a flowchart of a method for sharing resources between devices according to another embodiment of the present application;

3 is a flowchart of an embodiment of a method for sharing resources between devices provided by the present application;

4 is a flow chart of another embodiment of a method for sharing resources between devices provided by the present application;

FIG. 5 is a schematic diagram of an electronic device according to an embodiment of the present application; FIG.

FIG. 6 is a schematic diagram of an electronic device according to another embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following, in which the technical solutions in the embodiments of the present application are clearly and completely described. The embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope shall fall within the scope of the application.

An embodiment of the present application provides a method for sharing resources between devices, which is described from the sender device side. As shown in FIG. 1 , the method includes the following steps:

Step S101: In the process of browsing the resource by the resource browsing application, detecting a trigger condition for starting the NFC communication link to implement resource information sharing;

Step S102: The resource identifier of the resource browsed by the resource browsing application is encapsulated into the NFC data packet as load information.

Step S103: Send the NFC data packet in step S102 to the receiver device, so that the receiver device parses the resource identifier according to the NFC data packet, and acquires the resource by using the resource identifier.

The recipient device herein can be any electronic device with certain computing power, especially for smart mobile devices with an operating system, such as a smart phone, a tablet, a personal digital assistant (PDA), and the like.

Through the solution, the resource identifier can be transmitted through the NFC communication link with the receiver device, and the resource information can be shared between the devices, and the resource information sharing based on the point-to-point communication can be realized without adding the same wireless local area network.

After the receiver device obtains the resource identifier, it is often necessary to use the network identifier to obtain the resource, such as a local area network, the Internet, etc., of course, if the resource itself is in the storage device of the receiver device, the network environment is no longer needed. You can open the resource to browse.

In fact, the data transmission through the NFC communication link is particularly suitable for small data volume data transmission. In the embodiment of the present application, the resource identifier of the resource is often small, so it is more suitable for transmission using an NFC communication link. .

Another embodiment of the present application further provides a method for sharing resources between devices, which is described from a receiver device, as shown in FIG. 2, the method includes the following steps:

Step S201: After receiving the NFC data packet, extracting the capital contribution from the received load information of the NFC data packet. Source identifier

Step S202: Search for a resource browsing application capable of processing the resource identifier extracted in step S201;

Step S203: Acquire, according to the resource identifier, the resource identified by the resource identifier.

Step S204: Browse, by using the resource browsing application, the resource identified by the resource identifier.

With the solution, the resource identifier can be transmitted through the NFC communication link with the sender device, and the resource identifier is used to obtain the resource. Since the resource identifier is transmitted through the NFC communication link, it does not need to be implemented by using a wireless local area network. Obtaining resources through the resource identifier eliminates the need for the sender device and the receiver device to join the same WLAN. This reduces the resource sharing requirements for the network environment.

In practice, the resource identifiers shared by the devices may have various types of resources, such as sound files, video files, picture files, etc. The specific implementation of the present application is described in detail below with a few examples.

Embodiment 1

3 is a flow chart showing one embodiment of a method of sharing resources between devices provided by the present application. In this example, the electronic device A serves as the initiator of the shared resource information, and the electronic device B serves as the receiver of the shared resource information. Both the electronic device A and the electronic device B have an NFC communication module to complete NFC communication between the electronic devices. The electronic device A and the electronic device B in this example may be any electronic device that can communicate through the NFC communication module, including but not limited to smart mobile phones, tablets, desktop computers, portable computers, PDAs (personal digital assistants), and the like. . As a specific example, in the embodiment, the electronic device A and the electronic device B are both smart mobile phones as an example.

As shown in FIG. 3, the method for sharing resources between devices provided by this embodiment includes the following steps:

Step S301: The electronic device A starts a certain video application and plays the selected video resource.

The video application launched by the user may be a local video player capable of playing a specific format, such as a video player provided by the operating system installed in the electronic device A or a video player downloaded from the application store by the user; or some The client application corresponding to the video website or local server.

The video resource played by the user may be a video resource from a video website server in the Internet, or may be a video resource from a streaming media server in the local area network.

The resource type of the resource information that is shared in the actual is not limited to the video resource. In an alternative embodiment, the resource to which the shared resource information belongs may also be a multimedia resource such as a picture or a sound, or may be supported by Microsoft Office by default. Text files, spreadsheet files, slide files, small database files, etc., as well as plain text files supported by the Notepad program by default. Accordingly, the electronic device A launches an application that can open the resources that need to be shared for browsing. When opening a resource (such as video, Flash animation, sound, etc.) with the playback time as the browsing progress, playing the resource belongs to a kind of browsing of the resource; opening the resource with the current reading page number as the browsing progress (such as a slide file) Text Piece, PDF file, etc.), page by page to view the resource belongs to a kind of browsing of the resource; open the resource with the current reading line number as the browsing progress (such as plain text file, spreadsheet file, etc.), view line by line The resource belongs to a kind of browsing of the resource; when opening a resource with a special embedded object as a browsing progress (such as a small database file carried by a single file), viewing or editing the content in the embedded object belongs to the resource. Browse.

Step S302: After the electronic device A and the electronic device B are touched, the electronic device A detects the occurrence of a touch event, thereby achieving a trigger condition for starting resource information sharing by means of the NFC communication link.

When the user using the electronic device A wants to share the resource information of the video resource that he has opened and is playing to the user who uses the electronic device B, the electronic device A and the electronic device B can be touched to generate communication by means of NFC. The link triggers the resource information sharing. In actuality, when the electronic device A and the electronic device B touch, the operating system bottom layer of the electronic device A generates a corresponding touch event, and the application currently opened by the electronic device A can The event is captured, and then electronic device A begins to enter the preparation phase of sharing resources through the NFC communication link.

The electronic device A can utilize the mechanism of the NFC module itself to complete the detection of the touch.

Those skilled in the art should be able to understand that the trigger condition for sharing resource information through the NFC communication link in this example is defined as the fact that the electronic device A is touched by other devices is only an example, and in practice, it can also be defined as the electronic device A receives The sharing request sent by other electronic devices through a short-range communication connection such as Bluetooth or infrared, or may be defined as the electronic device A transmitting a sharing request to other electronic devices through a short-range communication connection such as Bluetooth or infrared, and receiving feedback information indicating permission. .

Step S303: The electronic device A determines whether its own NFC function is enabled.

Based on the consideration of improving energy efficiency and extending standby time, usually the electronic device does not turn on the NFC function for a long time, but only when it is needed. For this reason, it is necessary to verify whether the NFC function of the electronic device A is turned on before the electronic device A shares the resource information through the NFC communication link. If you find that the NFC function is enabled, you can enter the shared resource information. If you find that the NFC function is not enabled, you can directly end the process. You can also go to the step of setting the NFC function to be enabled. In practice, when the NFC function is not enabled, the setting interface for setting the NFC function can be presented. When the user selects to enable the NFC function and successfully starts the NFC function, the subsequent steps are continued.

In an alternative embodiment in some specific scenarios, step S303 may also be omitted, for example, in a scenario where the electronic device does not need to consider an energy efficiency problem, or when the electronic device starts an application for browsing resources, the NFC function is automatically turned on, and the like. The electronic device A can determine whether the error code that is fed back when the resource information is shared by the NFC communication link is an error that the NFC function is not turned on.

Step S304: When the result of the determination in step S303 is YES, it is continued to determine whether the current video application of the electronic device A provides the URI for the resource transmitted through the NFC communication link.

In practice, based on copyright, privacy, etc., not every resource resource of an open resource supports sharing. In the shared resource information, resource information of resources that meet specific requirements can also be limited to support transmission through the NFC communication link. Therefore, before sharing the resource information through the NFC communication link, it may first be determined whether the current video application provides a URI for transmission over the NFC communication link. When the result of the determination in step S304 is NO, the subsequent steps may be stopped.

Step S305: When the result of the determination in step S304 is YES, the electronic device A encapsulates the URI of the video resource being played by the current video application as load information into the NFC data packet, and sends the data to the electronic device B through the NFC communication module.

For example, the Android platform supports the transmission of data in the NDEF (NFC Data Exchange Format) format, and the NDEF data is the data format in the NFC Tag (tag) information agreed by the NFC organization. In the Android platform, the data in the NDEF format will be encapsulated into NFC packets (in practice, it can be NdefMessage, but this application is not limited to this).

One or more NdefRecords can be included in an NdefMessage, and an NdefRecord contains the following fields:

Type Name Format (TNF), which is used to specify how to escape the variable length type field to be described later. The length is usually defined as 3 bits.

Variable Length Type, used to describe the type of the NdefRecord, which can be filled in according to the type name format field;

Variable Length ID, which is used to uniquely identify the NdefRecord. This field is not required to be filled in.

Variable Length Payload is used to contain data that needs to be transmitted. In this embodiment, resource information (such as the URI of the video resource) that needs to be shared may be wrapped into the field.

In practice, wrapping the URI of the video resource into NdefMessage can be done by the NFC module of the Android system.

Step S306: The electronic device B monitors whether the NFC data packet is received on the premise that the NFC function is enabled.

In practice, monitoring whether an NFC packet is received depends on whether the received NFC packet is valid or not, and sometimes the receiving data is incorrect due to the instability of the communication link, thereby causing the NFC packet to be unrecognizable.

Step S307: After the electronic device B detects that the NFC data packet is received in step S306, the load information in the received NFC data packet is extracted.

In this embodiment, after analyzing the load information of the NFC data packet sent from the electronic device A, the electronic device B can extract the URI of the video resource.

Step S308: The electronic device B determines whether there is an application in the electronic device B that can process the URI of the extracted video resource.

In practice, the operation that the application will carry to the electronic device B during the installation of the new application to the electronic device B The system declares the data and events that it can handle. For example, you can declare that you can open the image in png format, or you can process the URI of a protocol (for example, you can handle the URI in the http protocol: http://play.google.com). Or it can handle events of a certain system (such as low battery, WIFI disconnected, NFC communication connection, etc.).

After extracting the URI of the video resource, the electronic device B can query whether there is an application in the operating system that can process such events and data. If there is, the application is called. In practice, when more than one application is queried to process the URI, the plurality of queried applications may be displayed in a graph or other manner for the user to select, after receiving the application selection information, according to the application. The selection information invokes the selected application.

The actual URI consists of a protocol header (such as "http://", "Ftp://", etc.), a host name (Host), a port (Port), and a path (Path). The electronic device B can perform a query according to the above information to check whether there is a matching application. For example, the protocol header can be matched first to check whether there is an application in the system that can process the protocol header. If the query can continue to match the next level, for example, matching the host name, check whether there is an application in the system that can process the URI of the host. .

In a preferred embodiment, the protocol header portion of the URI of the video resource is specifically defined, for example, as "taobao.com://", and when an application capable of processing the URI is installed in the electronic device B, The application can declare to the operating system that it can handle the URI with the protocol header "taobao.com://". In this way, when the device B performs the matching, the application that can process the URI can be quickly matched, and in practice, if only one application capable of processing the protocol header is used, the user needs to avoid multiple matching applications. Trouble in selecting (ie, from multiple candidates).

Step S309: The electronic device B starts an application capable of processing the URI of the extracted video resource, and plays the video resource pointed to by the URI.

It can be seen that in the embodiment, when the URI of the video resource is shared by the NFC communication between the two electronic devices, the point-to-point sharing between the devices can be realized, and the wireless local area network is not required. Even if the resources pointed to by the URI are played, LAN support may still be needed, but the two electronic devices that do not need to be shared are in the same LAN.

Embodiment 2

FIG. 4 is a flowchart of an embodiment of a method for sharing resources between devices according to Embodiment 2 of the present application. In this example, the electronic device A is still the initiator of the shared resource information, and the electronic device B is used as the initiator. The recipient of the shared resource information. Both the electronic device A and the electronic device B have an NFC communication module to complete NFC communication between the electronic devices.

Electronic device A and electronic device B in this example may be any electronic device that can communicate through an NFC communication link, including but not limited to smart mobile phones, tablets, desktop computers, portable computers, PDAs (personal digital assistants). Wait. As a specific example, in the embodiment, the electronic device A and the electronic device B are both smart mobile phones as an example.

The difference from the first embodiment is mainly that the viewing progress information of the resources is shared together in this embodiment. Here The resource viewing progress may be, for example, the progress of playing a video or music file, the progress of viewing a document file (such as viewing the number of lines, or viewing the number of pages).

In this example, the resource may be used as a video resource, and the progress of the resource is described as an example of the progress of the video resource, the resource information being the URI of the video resource, and the playback progress of the video resource. In a specific example, the playing progress of the video resource herein may be information such as the time point of playing or the chapter played.

Referring to FIG. 4, the method for sharing resources between devices provided by this embodiment includes the following steps:

Step S401: The electronic device A starts a certain video application and plays the selected video resource.

The resource type of the resource information that is shared in the actual is not limited to the video resource. In an alternative embodiment, the resource to which the shared resource information belongs may also be a multimedia resource such as a picture or a sound, or may be supported by Microsoft Office by default. Text files, spreadsheet files, slide files, small database files, etc., as well as plain text files supported by the Notepad program by default. Accordingly, the electronic device A launches an application that can open the resources that need to be shared for browsing. When opening a resource (such as video, Flash animation, sound, etc.) with the playback time as the browsing progress, playing the resource belongs to a kind of browsing of the resource; opening the resource with the current reading page number as the browsing progress (such as a slide file) , text file, PDF file, etc.), page by page to view the resource belongs to a kind of browsing of the resource; open the resource with the current reading line number as the browsing progress (such as plain text file, spreadsheet file, etc.) Viewing the resource belongs to a kind of browsing of the resource; opening a resource with a special embedded object as the browsing progress (such as a small database file carried by a single file), viewing or editing the content in the embedded object belongs to the resource A kind of browsing.

Step S402: After the electronic device A and the electronic device B touch, the electronic device A detects the occurrence of the touch time, and further triggers the triggering of resource information sharing by using the NFC communication module.

When the user using the electronic device A wants to share the resource information of the video resource that he has opened and is playing to the user who uses the electronic device B, the electronic device A and the electronic device B can be touched to generate communication by means of NFC. The trigger condition for the link to implement resource information sharing. In practice, when the electronic device A and the electronic device B make a touch, the operating system bottom layer of the electronic device A generates a corresponding touch event, and the application currently opened by the electronic device A can capture the event, and then the electronic device A starts. Enter the preparation phase of sharing resource information through the NFC communication link.

Those skilled in the art should be able to understand that the trigger condition for sharing resource information through the NFC communication link in this example is defined as the fact that the electronic device A is touched by other devices is only an example, and in practice, it can also be defined as the electronic device A receives Its The sharing request sent by the electronic device through a short-range communication connection such as Bluetooth or infrared, or may be defined as the electronic device A transmitting a sharing request to other electronic devices through a short-range communication connection such as Bluetooth or infrared, and receiving feedback information indicating permission. .

Step S403: The electronic device A determines whether its own NFC function is enabled.

Step S404: When the result of the determination in step S403 is YES, it is continued to determine whether the current video application of the electronic device A provides a URI for the resource transmitted through the NFC communication link.

Step S405: When the result of the determination in step S404 is YES, the electronic device A encapsulates the URI and the play progress of the video resource being played by the current video application into the NFC data packet as the load information, and sends the data to the electronic device B through the NFC communication module.

When the electronic device A encapsulates the URI and the playback progress as load information into the NFC data packet, the electronic device A and the electronic device B can follow a unified protocol, for example, the first N bits in the load information are the locations where the URI information is placed. The next part is where the playback progress is placed.

Step S406: The electronic device B monitors whether the NFC data packet is received on the premise that the NFC function is enabled.

In step S407, after the electronic device B detects that the NFC data packet is received, the electronic device B extracts the load information in the received NFC data packet, thereby obtaining the URI and the playback progress of the video resource. A common protocol is adhered between the electronic device A and the electronic device B, based on which the electronic device B can normally separate the URI and the playback progress information from the load information.

It should be noted that, as a special case, in this embodiment, the resource identifier and the progress information are encapsulated into the load information of the same NFC data packet. In another alternative embodiment, the electronic device A may also identify the resource and Progress information It is not encapsulated into the load information of two NFC data packets, and is transmitted and received through the implementation of the agreed protocol, so that the resource identification and progress information can be correctly extracted from the two NFC data packets.

Step S408: The electronic device B determines whether there is an application in the electronic device B that can process the URI of the extracted video resource.

In practice, in the process of installing a new application to the electronic device B, the application declares the data and events that the electronic device B is capable of processing, for example, can declare that it can open the image in the png format, or Can handle the URI of a protocol (for example, can handle the URI in the http protocol: http://play.google.com), or can handle events of a system (such as low battery, WIFI disconnected, NFC communication connection) Wait).

Step S409: The electronic device B starts an application capable of processing the URI of the extracted video resource, and continues to play the video resource pointed to by the URI from the obtained playback progress.

It can be seen that in the embodiment, when the URI of the video resource and the playback progress are shared by the NFC communication between the two electronic devices, the wireless local area network is not required. Even if the resources pointed to by the URI are played, LAN support may still be needed, but the two electronic devices that do not need to be shared are in the same LAN.

Another aspect of the embodiment of the present application further provides an electronic device, which is a sender of a shared resource. As shown in FIG. 5, the electronic device includes a detecting unit 501, a resource identifier encapsulating unit 502, and an NFC communication unit 503.

The detecting unit 501 is configured to detect, in the process of browsing the resource by the resource browsing application, whether there is a trigger condition for starting the NFC communication link to implement resource information sharing. Here, the triggering condition for starting the NFC communication link to implement resource information sharing may specifically be an event that occurs by the receiving device.

The resource identifier encapsulating unit 502 is configured to encapsulate the resource identifier of the resource browsed by the resource browsing application as load information into the NFC data packet after the detecting unit 501 detects the trigger condition.

The NFC communication unit 503 is configured to send the encapsulated NFC data packet to the receiver device, so that the receiver device parses the resource identifier according to the NFC data packet, and acquires the resource by using the resource identifier. The resource identifier here can be the URI of the resource.

The resource type of the resource information that is shared in the actual is not limited to the video resource. In an alternative embodiment, the resource of the shared resource information may also be a multimedia resource such as a picture or a sound, or may be a text supported by Microsoft Office by default. Files, spreadsheet files, slide files, small database files, etc., as well as plain text files supported by the Notepad program by default. Accordingly, the electronic device A launches an application that can open the resources that need to be shared for browsing. When opening a resource (such as video, Flash animation, sound, etc.) with the playback time as the browsing progress, playing the resource belongs to a kind of browsing of the resource; opening the resource with the current reading page number as the browsing progress (such as a slide file) , text file, PDF file, etc.), page by page to view the resource belongs to a kind of browsing of the resource; open the resource with the current reading line number as the browsing progress (such as plain text file, spreadsheet file, etc.) Viewing the resource belongs to a kind of browsing of the resource; opening a resource with a special embedded object as the browsing progress (such as a small database file carried by a single file), viewing or editing the content in the embedded object belongs to the resource A kind of browsing.

Through the foregoing electronic device, the resource identifier can be transmitted to the receiver device through the NFC communication link, so that the receiver device acquires the resource by using the resource identifier. Since the resource identifier is transmitted through the NFC communication link, the wireless local area network is not needed. The resource is not required to be added to the same WLAN through the resource identifier. Therefore, the resource sharing requirement for the network environment is reduced.

In addition, in order to further share the browsing progress of the resource by the sender device, in a preferred embodiment, the electronic device further includes a progress information encapsulating unit 504, configured to encapsulate the progress information browsed by the resource browsing application as load information. In the NFC packet.

In a preferred embodiment, the resource representation encapsulation unit 502 and the progress information encapsulating unit 504 specifically encapsulate the resource identification and progress information of the resource browsed by the resource browsing application into the load information of the same NFC data packet.

In addition, not all the resource browsing applications support the resource identification sharing. Therefore, in an alternative embodiment, the resource identifier existence identifying unit is further configured to determine the current resource browsing application after the detecting unit 501 detects the triggering condition. Whether the resource identifier of the browsed resource is provided, and only after the current resource browsing application provides the resource identifier of the browsed resource, the resource identifier encapsulating unit 502 starts to perform the encapsulation process.

Another aspect of the embodiment of the present application further provides an electronic device as a receiver device for resource sharing. As shown in FIG. 6, the electronic device includes a resource identifier extraction unit 601, an application matching unit 602, and a startup unit 603.

The resource identifier extraction unit 601 is configured to extract the resource identifier from the received load information of the NFC data packet after receiving the NFC data packet.

The application matching unit 602 is configured to search for a resource browsing application that can process the resource identifier extracted by the resource identifier extraction unit 601.

The resource obtaining unit 604 is configured to obtain, according to the resource identifier, the resource identified by the resource identifier.

The initiating unit 603 is configured to start the resource browsing application found by the application matching unit 602 to browse the resources identified by the extracted resource identifier.

The matching logic of the application matching unit 602 in the search process may have many specific implementation manners. For example, a special case URI as a resource identifier is composed of a protocol header, a host name, a port, and a path, and the application matching unit 602 may start from a protocol header. Matches step by step to find matching resource browsing applications. In a preferred embodiment, the application matching unit 602 includes: a protocol matching unit, configured to perform a lookup by using a protocol header of the resource identifier, to obtain a resource browsing application capable of processing the resource identifier.

In addition, in order to enable the electronic device in this embodiment to share the browsing progress information of the resource from the sender device, in a preferred embodiment, the sender device also encapsulates the progress information in the NFC data packet. The electronic device in this embodiment further includes: a progress information extracting unit, configured to extract progress information from the received NFC data packet. After the startup unit starts the resource browsing application, the resource browsing application starts browsing the resource identified by the resource identifier from the location identified by the progress information.

Obtaining, by using the foregoing electronic device, the resource identifier transmitted by the sender device through the NFC communication link, and acquiring the resource by using the resource identifier, because the resource identifier is transmitted through the NFC communication link, and does not need to be implemented by using a wireless local area network, and Obtaining resources through the resource identifier eliminates the need to join the same WLAN device with the sender device. This reduces the resource sharing requirements for the network environment.

In the 1990s, improvements to a technology could clearly distinguish between hardware improvements (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (for process flow improvements). However, as technology advances, many of today's method flow improvements can be seen as direct improvements in hardware circuit architecture. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented by hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by the user programming the device. The designer is self-programming to "integrate" a digital system onto a single PLD without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip 2 . Moreover, today, instead of manually making integrated circuit chips, this type of programming is mostly implemented using "logic compiler" software, which is compatible with the software compiler used in programming development. Similarly, the original code to be compiled must also be written in a specific programming language. This is called the Hardware Description Language (HDL), and HDL is not the only one, but there are many kinds, such as ABEL. (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language) Etc. Currently, the most commonly used VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog2. It should also be apparent to those skilled in the art that the hardware flow for implementing the logic method flow can be easily obtained by simply programming the method flow into the integrated circuit with a few hardware description languages.

The controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. In the form of logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.

Those skilled in the art will also appreciate that in addition to implementing the controller in purely computer readable program code, the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding. The form of a microcontroller or the like to achieve the same function. Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component. Or even a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit may be implemented in the same software or software and/or hardware when implementing the present application.

It will be apparent to those skilled in the art from the above description of the embodiments that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, portions of the technical solution of the present application that contribute substantially or to the prior art may be embodied in the form of a software product. In a typical configuration, the computing device includes one or more processors (CPU ), input / output interface, network interface and memory. The computer software product can include instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments. The computer software product can be stored in the memory The memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium. Computer readable media includes both permanent and non-persistent, removable and non-removable media. Information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media, such as modulated data signals and carrier waves.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

This application can be used in a variety of general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor based systems, set-top boxes, programmable consumer electronics devices, network PCs, small computers, mainframe computers, including A distributed computing environment of any of the above systems or devices, and the like.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including storage devices.

While the present invention has been described by the embodiments of the present invention, it will be understood by those skilled in the art

Claims

A method for sharing resources between devices, comprising:

In the process of browsing the resource by the resource browsing application, detecting a trigger condition for starting the NFC communication link of the incoming communication to realize resource information sharing;

The resource identifier of the resource browsed by the resource browsing application is encapsulated into the NFC data packet as load information;

And sending the NFC data packet to the receiver device, so that the receiver device parses the resource identifier according to the NFC data packet, and acquires the resource by using the resource identifier.
The method of claim 1 further comprising:

The progress information browsed by the resource browsing application is encapsulated into the NFC data package as load information.
The method according to claim 2, wherein the resource identifier of the resource browsed by the resource browsing application and the browsed progress information are encapsulated into load information of the same NFC data packet.
The method according to claim 1, wherein the triggering condition for starting the NFC communication link to implement resource information sharing comprises: generating an event touched by the receiving device.
The method according to claim 1, wherein the method further comprises: after detecting that the triggering condition for starting the NFC communication link to implement resource information sharing, continuing to determine whether the current resource browsing application provides the browsed resource. Resource ID.
The method according to claim 1, wherein the resource identifier is a uniform resource identifier URI.
A method for sharing resources between devices, comprising:

After receiving the NFC data packet, extracting the resource identifier from the load information of the NFC data packet;

Finding a resource browsing application capable of processing the extracted resource identifier;

Obtaining, according to the resource identifier, the resource identified by the resource identifier;

The resource browsing application is used to browse the resource identified by the resource identifier.
The method of claim 7, wherein the method further comprises:

Progress information is also extracted from the NFC data packet;

When browsing the resource identified by the resource identifier by using the resource browsing application, browsing starts from the location identified by the progress information.
The method according to claim 7, wherein the searching for the resource browsing application capable of processing the extracted resource identifier comprises:

The search is performed by the protocol header of the resource identifier, and a resource browsing application capable of processing the resource identifier is obtained.
An electronic device, comprising:

The detecting unit is configured to detect whether the NFC is started during the browsing of the resource by the resource browsing application. The triggering condition for the communication link to realize resource information sharing;

a resource identifier encapsulating unit, configured to encapsulate the resource identifier of the resource browsed by the resource browsing application as load information into an NFC data packet after the detecting unit detects the triggering condition;

And an NFC communication unit, configured to send the NFC data packet to the receiver device, so that the receiver device parses the resource identifier according to the NFC data packet, and acquires the resource by using the resource identifier.
The electronic device according to claim 10, further comprising:

The progress information encapsulating unit is configured to encapsulate the progress information browsed by the resource browsing application as load information into the NFC data package.
The electronic device according to claim 11, wherein the resource representation encapsulation unit and the progress information encapsulating unit specifically encapsulate the resource identifier and the progress information of the resource browsed by the resource browsing application into the same NFC data packet. Load information.
The electronic device according to claim 10, wherein the triggering condition for starting the NFC communication link to implement resource information sharing comprises: generating an event that is touched by the receiving device.
The electronic device according to claim 10, further comprising:

The resource identifier existence identifying unit is configured to determine, after the detecting unit detects the trigger condition, whether the current resource browsing application provides the resource identifier of the browsed resource.
The electronic device of claim 10, wherein the resource identifier is a URI.
An electronic device, comprising:

a resource identifier extracting unit, configured to extract a resource identifier from load information of the NFC data packet after receiving the NFC data packet;

An application matching unit, configured to search for a resource browsing application capable of processing the extracted resource identifier;

a resource obtaining unit, configured to acquire, according to the resource identifier, a resource identified by the resource identifier;

The initiating unit is configured to start the resource browsing application to browse the resource identified by the resource identifier.
The electronic device according to claim 16, wherein the application matching unit comprises:

The protocol matching unit is configured to perform a search by using a protocol header of the resource identifier, and obtain a resource browsing application capable of processing the resource identifier.
The electronic device according to claim 16, further comprising:

a progress information extracting unit, configured to extract progress information from the received NFC data packet;

The initiating unit is specifically configured to start the resource browsing application, browse the resource identified by the resource identifier, and start browsing from the location identified by the progress information.