CN106060155A - P2P (Peer to Peer) resource sharing method and device - Google Patents
P2P (Peer to Peer) resource sharing method and device Download PDFInfo
- Publication number
- CN106060155A CN106060155A CN201610514920.4A CN201610514920A CN106060155A CN 106060155 A CN106060155 A CN 106060155A CN 201610514920 A CN201610514920 A CN 201610514920A CN 106060155 A CN106060155 A CN 106060155A
- Authority
- CN
- China
- Prior art keywords
- message
- resource
- information
- suspicious object
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a P2P (Peer to Peer) resource sharing method and device. The method comprises the steps of sending P2P protocol acknowledgement messages to corresponding client and server according to source node information and destination node information of a message when a protocol type of the message is not identified according to a message feature; determining that the message is a P2P resource request message if a P2P protocol response message is received; obtaining suspicious target P2P resources corresponding to the message according to access records of the client to the server, and caching the suspicious target P2P resources; sending a file list of the suspicious target P2P resources to the client; and sending the corresponding P2P resources to the client after the suspicious target P2P resource obtaining request is received. Through application of the method, the encrypted P2P traffic can be identified in a CDN (Content Delivery Network) system; the P2P resources can be locally stored according to the encrypted P2P traffic; and the cached P2P resources are distributed to a user according to the demand of the user.
Description
Technical field
The application relates to network communication technology field, particularly relates to P2P (Peer to Peer is called for short P2P) resource-sharing
Method and device.
Background technology
CDN (Content Delivery Network, content distributing network) system is by existing Internet
Increase by one layer of new network architecture, it is possible to achieve P2P resource is carried out local cache, make the user in CDN system can be nearby
Get required P2P resource, thus improve efficiency when user obtains P2P resource, further improve Internet simultaneously
The situation that network is crowded.
In prior art, owing to P2P flow occupies a large amount of network bandwidth, therefore P2P flow is adopted by Internet provider
Take restriction.In order to not affect normal use, its P2P flow transmitted is encrypted by a lot of P2P application softwaries,
So that Internet provider is difficult to the P2P flow of encryption is identified and is limited.
But, owing to P2P flow is the most encrypted, then CDN system also would become hard to encryption P2P flow be identified and
Process, thus be difficult to again P2P resource be carried out local cache, and ask to divide to user according to the P2P resource acquisition of user
Send out the P2P resource cached.
Summary of the invention
In view of this, the application provides the method and device of a kind of P2P resource-sharing, to realize in CDN system, permissible
Identify the P2P flow of encryption, and realize P2P resource is carried out local cache according to the P2P flow of encryption, and realize according to user
Demand, distribute, to user, the P2P resource that cached.
Specifically, the application is achieved by the following technical solution:
First aspect according to the embodiment of the present application, it is provided that a kind of method of P2P resource-sharing, described method includes:
When not can recognize that, according to the message characteristic of received message, the protocol type that described message is applied, root
According to source node identification and the destination node information of described message, send P2P agreement to corresponding client and service end respectively true
Recognize message；
If receiving the P2P protocol responses report that described client and service end send according to described P2P protocol validation message
Literary composition, it is determined that described message is P2P resource request message；
According to the described client access record to service end, obtain the suspicious object P2P resource corresponding to described message,
And cache described suspicious object P2P resource；
The listed files of described suspicious object P2P resource is sent, so that described client is according to described to described client
Listed files determines that the P2P resource of institute's acquisition request is whether in described suspicious object P2P resource；
After receiving P2P resource acquisition request, sending corresponding P2P resource to described client, described P2P resource obtains
Sent when the P2P resource that the request that takes is described client acquisition request determining is in described suspicious object P2P resource.
Alternatively, described method also includes:
After determining that described message is P2P resource request message, by source node identification and the destination node letter of described message
Breath adds in the P2P nodal information of preservation, and adds P2P labelling, institute in the session information of session corresponding to described message
State P2P nodal information and include source node identification and the corresponding relation of destination node information；
When receiving message, it is judged that whether described message is the literary composition of reporting for the first time of session, the most then according to the source of described message
P2P nodal information described in nodal information or destination node information searching, if finding described source node identification or destination node letter
Breath, it is determined that described message is P2P resource request message；
If described message is not the literary composition of reporting for the first time of session, then judge whether the session information of session corresponding to described message has
P2P labelling, if there being P2P labelling, it is determined that described message is P2P resource request message in described session information.
Alternatively, described method also includes:
If finding the source node identification of described message in described P2P nodal information, then the purpose of described message is saved
Dot information adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message；
If finding the destination node information of described message in described P2P nodal information, then the source of described message is saved
Dot information adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message.
Alternatively, the described access record according to described client to service end, obtain corresponding to described message is suspicious
Target P2P resource, including:
Source node identification according to described message searches described P2P nodal information, if finding described source node identification, then
Obtain all destination node information that described source node identification is corresponding；
The request for checking shared listed files is sent to the service end corresponding to destination node information each described
Message；
Receive the shared listed files that described service end is sent according to described request message；
The suspicious object P2P resource corresponding to described message is obtained according to described shared listed files.
Alternatively, described according to the suspicious object P2P resource corresponding to the described shared listed files described message of acquisition, bag
Include:
Obtain the information being the same from sharing file in each described shared listed files, according to described shared file
Suspicious object P2P resource corresponding to message described in acquisition of information.
Alternatively, described caching described suspicious object P2P resource, including:
Cryptographic Hash according to described suspicious object P2P resource determines that this locality has cached described suspicious object P2P resource the most；
If there is uncached suspicious object P2P resource, then according to the Hash of described uncached suspicious object P2P resource
Value and resource size, construct, by P2P agreement, the URL address that described uncached suspicious object P2P resource is corresponding；
According to described URL address, send the download request carrying described URL address to corresponding service end；
Receive the P2P resource that described service end is sent according to the described request of downloading, and cache described P2P resource, until
Cache all described suspicious object P2P resources.
Second aspect according to the embodiment of the present application, it is provided that the device of a kind of P2P resource-sharing, described device includes:
According to the message characteristic of received message, first transmitting element, for not can recognize that described message is answered
Protocol type time, according to source node identification and the destination node information of described message, respectively to corresponding client kimonos
Business end sends P2P protocol validation message；
Determine unit, if for receiving what described client and service end sent according to described P2P protocol validation message
P2P protocol responses message, it is determined that described message is P2P resource request message；
Buffer unit, for according to the described client access record to service end, obtain corresponding to described message can
Doubt target P2P resource, and cache described suspicious object P2P resource；
Second transmitting element, for sending the listed files of described suspicious object P2P resource to described client, so that institute
State client and determine that the P2P resource of institute's acquisition request is whether in described suspicious object P2P resource according to described listed files；
Dispatching Unit, for, after receiving P2P resource acquisition request, sending corresponding P2P resource to described client,
The P2P resource that described P2P resource acquisition request is described client acquisition request determining is in described suspicious object P2P resource
Sent time middle.
Alternatively, described device also includes:
First adding device, for after determining that described message is P2P resource request message, by the source node of described message
Information and destination node information are added in the P2P nodal information of preservation, and at the session information of session corresponding to described message
Middle interpolation P2P labelling, described P2P nodal information includes source node identification and the corresponding relation of destination node information；
First judging unit, for when receiving message, it is judged that whether described message is the literary composition of reporting for the first time of session；
Search unit, for described message be session report for the first time literary composition time, according to source node identification or the mesh of described message
Nodal information search described P2P nodal information；
Processing unit, if for finding described source node identification or destination node information, it is determined that described message is P2P
Resource request message；
Second judging unit, if being used for the literary composition of reporting for the first time that described message is not session, then judges session corresponding to described message
Session information in whether have P2P labelling；
Described processing unit, is additionally operable to: if there being P2P labelling in described session information, it is determined that described message is P2P resource
Request message.
Alternatively, described device also includes:
Second adding device, if for the source node identification finding described message in described P2P nodal information, then will
The destination node information of described message is added in described P2P nodal information, and at the session letter of session corresponding to described message
Breath adds P2P labelling；
If finding the destination node information of described message in described P2P nodal information, then the source of described message is saved
Dot information adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message.
Alternatively, described buffer unit, including:
Search subelement, search described P2P nodal information for the source node identification according to described message；
First obtains subelement, if for finding described source node identification, then obtaining described source node identification corresponding
All destination node information；
Send subelement, for send to the service end corresponding to destination node information each described be used for checking shared
The request message of listed files；
Receive subelement, for receiving the shared listed files that described service end is sent according to described request message；
Second obtains subelement, for obtaining the suspicious object corresponding to described message according to described shared listed files
P2P resource.
Alternatively, described second obtains subelement, specifically for:
Obtain the information being the same from sharing file in each described shared listed files, according to described shared file
Suspicious object P2P resource corresponding to message described in acquisition of information.
Alternatively, described buffer unit, including:
Determine subelement, described for determining that this locality has cached the most according to the cryptographic Hash of described suspicious object P2P resource
Suspicious object P2P resource；
, if for there is uncached suspicious object P2P resource, then according to described uncached suspicious mesh in constructor unit
The cryptographic Hash of mark P2P resource and resource size, construct described uncached suspicious object P2P resource by P2P agreement corresponding
URL address；
Lower subelements, for according to described URL address, sends to corresponding service end and carries under described URL address
Carry request；
Caching subelement, for receiving the P2P resource that described service end is sent according to the described request of downloading, and caches institute
State P2P resource, until caching all described suspicious object P2P resources.
As seen from the above-described embodiment, by sending P2P agreement to the client corresponding to the message received and service end
Confirmation message, follow-up is receiving the P2P protocol responses message that client and service end send according to this P2P protocol validation message
Time, determine that this message is P2P resource request message, it is achieved thereby that the P2P resource request message of encryption is identified；Pass through
The client access record to service end, can obtain and cache the suspicious object P2P resource that this message is corresponding, and this is suspicious
The listed files of target P2P resource is supplied to client, client whether the P2P resource needed for judging is in suspicious object P2P
In resource, receive client determine asked P2P resource in suspicious object P2P resource, the P2P sent afterwards
After resource acquisition request, corresponding P2P resource can be sent to client, thus realize P2P resource is carried out local cache, and
The P2P resource cached is distributed to client.
Accompanying drawing explanation
Fig. 1 illustrates the application scenarios schematic diagram that the embodiment of the present application realizes the method for P2P resource-sharing；
Fig. 2 illustrates an embodiment flow chart of the method for the application P2P resource-sharing；
Fig. 3 illustrates an embodiment flow chart of the method for the P2P message of the application identification encryption；
Fig. 4 illustrates another embodiment flow chart of the method for the application P2P resource-sharing；
Fig. 5 is a kind of hardware structure diagram of the device place network equipment of the application P2P resource-sharing；
Fig. 6 illustrates an embodiment block diagram of the device of the application P2P resource-sharing；
Fig. 7 illustrates another embodiment block diagram of the device of the application P2P resource-sharing；
Fig. 8 illustrates another embodiment block diagram of the device of the application P2P resource-sharing.
Detailed description of the invention
Here will illustrate exemplary embodiment in detail, its example represents in the accompanying drawings.Explained below relates to
During accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represents same or analogous key element.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistent with the application.On the contrary, they are only with the most appended
The example of the apparatus and method that some aspects that described in detail in claims, the application are consistent.
It is only merely for describing the purpose of specific embodiment at term used in this application, and is not intended to be limiting the application.
" a kind of ", " described " and " being somebody's turn to do " of singulative used in the application and appended claims is also intended to include majority
Form, unless context clearly shows that other implications.It is also understood that term "and/or" used herein refers to and wraps
Any or all containing one or more projects of listing being associated may combination.
Although should be appreciated that in the application possible employing term first, second, third, etc. to describe various information, but this
A little information should not necessarily be limited by these terms.These terms are only used for same type of information is distinguished from each other out.Such as, without departing from
In the case of the application scope, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as
One information.Depend on linguistic context, word as used in this " if " can be construed to " ... time " or " when ...
Time " or " in response to determining ".
Refer to Fig. 1, illustrate the application scenarios schematic diagram that the embodiment of the present application realizes the method for P2P resource-sharing.Fig. 1
Include: P2P application end 11 and P2P application end 12, CND service end 13.Wherein, in applying at P2P, client and service
End is relative, i.e. computer in network both can serve as the requestor of network service, can ask other computer again
Asking and respond, it is provided that resource and service, the most in this application, client is also relative with the role of service end.At this
In application scenarios, it is assumed that P2P application end 11 is to P2P application end 12 acquisition request P2P resource, then, P2P application end 11 is then visitor
Family end, P2P application end 12 is then service end.For convenience, in this application scene, P2P application end 11 is referred to as client
End 11, is referred to as service end 12 by P2P application end 12；It is to be appreciated that, in actual applications, multiple client kimonos can be included
Business end, this is not restricted by the application.CDN service end 13 can include server, server cluster or cloud platform.
In application scenarios shown in Fig. 1, by, in existing P2P network, adding the CDN system network architecture, then may be used
P2P resource is carried out local cache by CDN service end 13 so that client 11 can get required P2P money nearby
Source.Such as, client 11 sends P2P resource request message to service end 12, to obtain P2P resource, and this P2P resource request report
Literary composition can first transmit to CDN service end 13.CDN service end 13 can be according to this P2P resource request message, it is judged that client 11 institute
The P2P resource needed caches in this locality the most, the most then directly this P2P resource can be sent extremely by CDN service end 13
Client 11；If this P2P resource uncached, then CDN service end 13 to this P2P resource of service end 12 acquisition request, and can be incited somebody to action
This P2P caching resource in this locality, when follow-up have this P2P resource of client acquisition request time, CDN service end 13 can directly incite somebody to action should
P2P resource sends to client.Processed by this kind, client 11 can be improved and obtain the efficiency of P2P resource, and due to P2P
Resource request message can no longer be transferred to remote service end 12, thus reduces the load of network, simultaneously because service end
12 can process each P2P resource request message, thus reduce the load of service end 12.
But conventionally, as P2P flow occupies a large amount of network bandwidth, therefore P2P is flowed by Internet provider
Amount takes restriction.In that case, the P2P flow that it sends can be encrypted by client 11, so that P2P
Flow is the most identified, to avoid being restricted.But, just because of being encrypted P2P flow, CND service end 13 uses
Prior art, also will be incapable of recognizing that it is P2P flow, then, CDN service end 13 will be unable to cache P2P resource, with
And send P2P resource to client.In order to solve this problem, the method that this application provides P2P resource-sharing, CDN service end
13 can apply the method, are identified the P2P flow of encryption, and realize the local cache of P2P resource and to client
Distribution P2P resource.
For the method making those skilled in the art can understand P2P resource-sharing provided herein in more detail,
To be described from below embodiment.
Refer to Fig. 2, illustrate an embodiment flow chart of the method for the application P2P resource-sharing, shown in this Fig. 2
Flow process, on the basis of application scenarios shown in above-mentioned Fig. 1, performs to illustrate as a example by the method by CDN service end 13, can wrap
Include following steps:
Step S201: not can recognize that the agreement that described message is applied according to the message characteristic of received message
During type, according to source node identification and the destination node information of described message, send to corresponding client and service end respectively
P2P protocol validation message.
As it is shown in figure 1, client 11 is when service end 12 sends message, this message can first be transferred to CDN service end
13, then CDN service end 13 can receive this message, and do recognition processing this message, to identify that whether this message is as P2P
Resource request message.
CDN service end 13 can be first according to the message characteristic of this message, such as, and the source port of message, destination interface, agreement
Eigenvalue, etc., this message is identified, to identify the agreement that this message is applied.The most how according to message characteristic
Carrying out protocol identification, may refer to associated description of the prior art, this is not described in detail by the application.
When CDN service end 13 is according to the message characteristic of message, when not can recognize that the protocol type that this message is applied, this
In application, the technology of a kind of active probe can be used, this message is carried out protocol identification.Specifically, CDN service end 13 is permissible
Source node identification (such as source IP address and source port number) according to this message, and destination node information (such as purpose IP address
With destination slogan), the client corresponding to this message and service end, such as client 11 and service end 12, send P2P agreement
Confirmation message.
Step S202: if receiving the P2P association that described client and service end send according to described P2P protocol validation message
View response message, it is determined that described message is P2P resource request message.
If CDN service end 13 receives the P2P that client 11 and service end 12 are returned according to this P2P protocol validation message
Protocol responses message, then it is believed that this message is P2P resource request message, thus through performing step S201 and step
S202, it is possible to achieve the message encrypted is carried out the identification of P2P agreement.
Additionally, in this application, when execution of step S202, determine that received message is P2P resource request message
After, it is also possible to the source node identification of this message and destination node information are added in the P2P nodal information of preservation, and at this report
The session information of session belonging to literary composition adds P2P labelling, all applies P2P agreement identifying all messages corresponding to this session.
Such as table 1 below, for a kind of example of P2P nodal information:
Table 1
From above-mentioned table 1, in P2P nodal information, source node identification and destination node information can be one-to-many
Relation, " relation of one-to-many " should refer to, same client can be to multiple service end acquisition request P2P resources.
Follow-up, CDN service end 13 can P2P nodal information accordingly, quickly judge received by message whether be P2P money
The most how source request message, judge, may refer to the associated description in following embodiment, is not first described further at this.
Step S203: according to the described client access record to service end, obtain the suspicious mesh corresponding to described message
Mark P2P resource, and cache described suspicious object P2P resource.
Seen from the above description, same client can be optional at one to multiple service end acquisition request P2P resources
In implementation, the client access record to service end, can be embodied by the P2P nodal information of above-mentioned record, specifically,
In P2P nodal information, each source node identification and the corresponding relation of destination node information, all can embody client to service
The access record of end, the client that i.e. source node identification is corresponding crosses P2P to the service end acquisition request that destination node information is corresponding
Resource.
In this application, owing to the P2P resource request message of transmission is encrypted by client 11, then CND service
End 13 cannot directly obtain the P2P resource of 11 acquisition request of client from the P2P resource request message that this has been encrypted.That
, in this application, then can pass through the client 11 access record to service end, obtain client 11 and may wish to acquisition
P2P resource, for convenience, the P2P resource that may wish to client 11 obtain is referred to as suspicious object P2P resource.
These suspicious object P2P resources can also be cached by CDN service end 13, in order to follow-up directly sends out to client
Send P2P resource, the most how to cache, may refer to the associated description in following embodiment, be not first described further at this.
Step S204: send the listed files of described suspicious object P2P resource to described client, so that described client
Determine that the P2P resource of institute's acquisition request is whether in described suspicious object P2P resource according to described listed files.
The listed files of the suspicious object P2P resource got can be sent to client 11 by CDN service end 13, so that
Obtain client 11 and check this document list, to confirm self to need the P2P resource obtained whether in suspicious object P2P resource.
Step S205: after receiving P2P resource acquisition request, sends corresponding P2P resource to described client, described
The P2P resource that P2P resource acquisition request is described client acquisition request determining is in described suspicious object P2P resource
Time sent.
When client 11 is according to listed files, after determining that the required P2P resource obtained is in suspicious object P2P resource,
Can to CDN service end 13 send P2P resource acquisition request, thus, CDN service end 13 receive this P2P resource acquisition please
After asking, its required P2P resource can be sent to client 11.
As seen from the above-described embodiment, by sending P2P agreement to the client corresponding to the message received and service end
Confirmation message, follow-up is receiving the P2P protocol responses message that client and service end send according to this P2P protocol validation message
Time, determine that this message is P2P resource request message, it is achieved thereby that the P2P resource request message of encryption is identified；Pass through
The client access record to service end, can obtain and cache the suspicious object P2P resource that this message is corresponding, and this is suspicious
The listed files of target P2P resource is supplied to client, client whether the P2P resource needed for judging is in suspicious object P2P
In resource, receive client determine asked P2P resource in suspicious object P2P resource, the P2P sent afterwards
After resource acquisition request, corresponding P2P resource can be sent to client, thus realize P2P resource is carried out local cache, and
The P2P resource cached is distributed to client.
Refer to Fig. 3, illustrate an embodiment flow chart of the method for the P2P message of the application identification encryption, this Fig. 3
Shown flow process, on the basis of flow process shown in application scenarios shown in above-mentioned Fig. 1 and Fig. 2, performs the party with CDN service end 13
As a example by method, the P2P message that be how to identify encryption is described in detail in the application, may comprise steps of:
Step S301: when receiving message, it is judged that whether described message is the literary composition of reporting for the first time of session, the most then perform step
Rapid S302, otherwise performs step S306.
As shown in fig. 1, client 11 is when service end 12 sends message, and this message can first be transferred to CDN service
End 13, after CND service end 13 receives this message, it can be determined that whether this message is the literary composition of reporting for the first time of session, if this message is meeting
The literary composition of reporting for the first time of words, then continue executing with step S302, otherwise, continue executing with step S306.The most how to judge, may refer to
Associated description of the prior art, this is not described further by the application.
Step S302: according to P2P nodal information described in the source node identification of described message or destination node information searching, if
Find described source node identification or destination node information, then perform step S303, otherwise perform step S304.
How P2P nodal information in this step is set up, and may refer to the related introduction in above-described embodiment, at this
Do not remake and be described in detail.
Step S303: determine that described message is P2P resource request message, and, if searching in described P2P nodal information
To the source node identification of described message, then the destination node information of described message is added in described P2P nodal information, and
The session information of session corresponding to described message adds P2P labelling；If finding described message in described P2P nodal information
Destination node information, then the source node identification of described message is added in described P2P nodal information, and in described message institute
The session information of respective session adds P2P labelling；Terminate flow process.
From the related introduction in above-described embodiment, when message is P2P resource request message, can be by the source of message
Nodal information and destination node information are added in P2P nodal information, thus, in the present embodiment, when in P2P nodal information
When finding source node identification or the destination node information of message, it is believed that this message is P2P resource request message.
In the present embodiment, it is also possible to continue to safeguard P2P nodal information, specifically, when believing at P2P node according to this message
When breath finds source node identification, the destination node information in message can be added in P2P nodal information；When at P2P
When nodal information finds destination node information, the source node identification in message can be added in P2P nodal information.
Further, after confirming that this literary composition of reporting for the first time is P2P resource request message, can believe in the session of this session belonging to literary composition of reporting for the first time
In breath, add P2P labelling.
Step S304: according to source node identification and the destination node information of described message, respectively to corresponding client and
Service end sends P2P protocol validation message.
Step S305: judge whether that receiving described client and service end sends according to described P2P protocol validation message
P2P protocol responses message, the most then perform step S307；Otherwise, step S308 is performed.
What the detailed description of step S304 and step S305 may refer in above-mentioned steps S201 and step S202 relevant retouches
State, do not remake at this and be described in detail.
Step S306: judge whether to have in the session information of session belonging to described message P2P labelling, the most then perform step
Rapid S307, otherwise performs step S308.
From step S303, when the literary composition of reporting for the first time confirming session is P2P resource request message, can be in this session
In session information add P2P labelling, then, in the present embodiment, when confirmation message be not session report for the first time literary composition time, the most permissible
Judge whether the session information of session belonging to this message has P2P labelling, judge whether this message is P2P resource request report accordingly
Literary composition.
Step S307: determine that described message is P2P resource request message, terminates flow process.
Step S308: determine that described message is not P2P resource request message.
As seen from the above-described embodiment, at the literary composition of reporting for the first time that message is session that confirmation receives, and message is P2P resource request
During message, safeguard P2P nodal information by this message, and in the session information of respective session, add P2P labelling, receipt of subsequent
During to message, can be according to P2P nodal information and P2P labelling, it is achieved identify P2P message rapidly, thus improve identification effect
Rate.
Refer to Fig. 4, illustrate another embodiment flow chart of the method for the application P2P resource-sharing, shown in this Fig. 4
Flow process on the basis of application scenarios, and flow process shown in Fig. 2 shown in above-mentioned Fig. 1, describe the application in detail and cache suspicious
The detailed process of target P2P resource, may comprise steps of:
Step S401: not can recognize that the agreement that described message is applied according to the message characteristic of received message
During type, according to source node identification and the destination node information of described message, send to corresponding client and service end respectively
P2P protocol validation message.
Step S402: if receiving the P2P association that described client and service end send according to described P2P protocol validation message
View response message, it is determined that described message is P2P resource request message.
Step S401 and the detailed description of step S402, may refer to above-mentioned steps S201 and the relevant of step S202 is retouched
State, do not remake at this and be described in detail.
Step S403: according to the described client access record to service end, obtain the suspicious mesh corresponding to described message
Mark P2P resource.
From the description in above-described embodiment, client can be embodied in P2P node letter to the access record of service end
In breath, the most in the present embodiment, CDN service end 13 can search P2P nodal information according to the source node identification of message, finds
During this source node identification, obtain all destination node information corresponding to this source node identification.
In an optional implementation, CDN service end 13 can be to the clothes corresponding to each destination node information
Business end sends the request message for checking shared listed files, to obtain the shared listed files of service end.Service end receives
After this request message, can send the shared listed files of self to CDN service end 13, CDN service end 13 then can be by every
All P2P resources in the shared listed files that one service end is sent are as described suspicious object P2P resource.
In another optional implementation, CDN service end 13 receives the shared file that each service end sends
After list, these shared listed files can be taken common factor, to obtain the shared literary composition existed in each shared listed files
The information of part, will be somebody's turn to do the P2P resource in " common factor " as described suspicious object P2P resource.By the way of " taking common factor ", permissible
Reduce the scope of suspicious object P2P resource, thus improve subsequent client and obtain the efficiency of P2P resource.
Step S404: determine that this locality has cached described suspicious mesh the most according to the cryptographic Hash of described suspicious object P2P resource
Mark P2P resource.
In the present embodiment, can be according to determining that this locality has cached this P2P money the most with the cryptographic Hash of target P2P resource
Source.Specifically, can search cache resources list according to the cryptographic Hash of target P2P resource, this can in cache resources list
To include the cryptographic Hash of the P2P resource cached.
Step S405: if there is uncached suspicious object P2P resource, then according to described uncached suspicious object P2P
The cryptographic Hash of resource and resource size, construct, by P2P agreement, the URL ground that described uncached suspicious object P2P resource is corresponding
Location；
If finding to there is uncached suspicious object P2P resource, then can be according to this uncached suspicious object P2P resource
Cryptographic Hash and resource size, by P2P agreement construct URL address, the most how to construct, may refer in prior art
Associated description, this is not described in detail by the application.
Step S406: according to described URL address, send the download request carrying described URL address to corresponding service end.
Step S407: receive the P2P resource that described service end is sent according to the described request of downloading, and cache described P2P
Resource, until caching all described suspicious object P2P resources.
In step S406 and step S407, CDN service end 13 can send the URL ground constructed to corresponding service end
Location, with acquisition request P2P resource.Follow-up, CDN service end 13, after receiving the P2P resource that service end sends, can cache this
P2P resource, to realize the follow-up hit distribution to this P2P resource.
Step S408: send the listed files of described suspicious object P2P resource to described client, so that described client
Determine that according to described listed files the P2P resource of institute's acquisition request has been buffered in this locality the most.
Step S409: after receiving P2P resource acquisition request, sends corresponding P2P resource to described client, described
The P2P resource that P2P resource acquisition request is described client acquisition request determining has been sent after being buffered in this locality.
Step S408 and the detailed description of step S409, may refer in above-mentioned steps S204 and step S205 relevant retouches
State, do not remake at this and be described in detail.
As seen from the above-described embodiment, by sending P2P agreement to the client corresponding to the message received and service end
Confirmation message, follow-up is receiving the P2P protocol responses message that client and service end send according to this P2P protocol validation message
Time, determine that this message is P2P resource request message, it is achieved thereby that the P2P resource request message of encryption is identified；Pass through
The client access record to service end, can obtain the suspicious object P2P resource that this message is corresponding, and by structure URL ground
Location, sends, to service end, the request of download, to obtain uncached suspicious object P2P resource, it is achieved that according to the P2P resource of encryption
Request message caching P2P resource；Follow-up, by the listed files of this suspicious object P2P resource is supplied to client, by client
P2P resource needed for end judgement, whether in suspicious object P2P resource, is determining asked P2P money receiving client
Source, in suspicious object P2P resource, after the P2P resource acquisition request sent afterwards, can send corresponding P2P to client
Resource, it is achieved thereby that distribute the P2P resource cached to client.
Corresponding with the embodiment of the method for aforementioned P2P resource-sharing, present invention also provides the device of P2P resource-sharing
Embodiment.
The embodiment of the device of the application P2P resource-sharing can be applied at the network equipment, such as on CDN service end.Dress
Put embodiment to be realized by software, it is also possible to realize by the way of hardware or software and hardware combining.Implemented in software it is
Example, as the device on a logical meaning, is that the processor by its place network equipment is by right in nonvolatile memory
The computer program instructions answered reads and runs formation in internal memory.For hardware view, as it is shown in figure 5, be the application P2P
A kind of hardware structure diagram of the device place network equipment of resource-sharing, except the processor 51 shown in Fig. 5, internal memory 52, network
Outside interface 53 and nonvolatile memory 54, in embodiment, the network equipment at device place is generally according to this network equipment
Actual functional capability, it is also possible to include other hardware, this repeated no more.
Refer to Fig. 6, illustrate an embodiment block diagram of the device of the application P2P resource-sharing, the dress shown in this Fig. 6
Put and may include that the first transmitting element 61, determine unit 62, buffer unit the 63, second transmitting element 64, Dispatching Unit 65.
Wherein, this first transmitting element 61, may be used for failing to identify according to the message characteristic of received message
When going out the protocol type that described message is applied, according to source node identification and the destination node information of described message, respectively to right
The client answered and service end send P2P protocol validation message；
This determines unit 62, if may be used for receiving described client and service end according to described P2P protocol validation report
The P2P protocol responses message that literary composition sends, it is determined that described message is P2P resource request message；
This buffer unit 63, may be used for, according to the described client access record to service end, obtaining described message institute
Corresponding suspicious object P2P resource, and cache described suspicious object P2P resource；
This second transmitting element 64, may be used for sending the file row of described suspicious object P2P resource to described client
Table, so that according to described listed files, described client determines that whether the P2P resource of institute's acquisition request is in described suspicious object P2P
In resource；
This Dispatching Unit 65, may be used for, after receiving P2P resource acquisition request, sending correspondence to described client
P2P resource, the P2P resource that described P2P resource acquisition request is described client acquisition request determining is at described suspicious mesh
Sent time in mark P2P resource.
Refer to Fig. 7, illustrate another embodiment block diagram of the device of the application P2P resource-sharing, shown in this Fig. 7
Device is on the basis of above-mentioned Fig. 6 shown device, it is also possible to including: first adding device the 66, first judging unit 67, lookup list
Unit 68, processing unit the 69, second judging unit the 610, second adding device 611.
Wherein, this first adding device 66, may be used for after determining that described message is P2P resource request message, by institute
State the source node identification of message and destination node information is added in the P2P nodal information of preservation, and corresponding to described message
Adding P2P labelling in the session information of session, described P2P nodal information includes the right of source node identification and destination node information
Should be related to；
This first judging unit 67, may be used for when receiving message, it is judged that whether described message is reporting for the first time of session
Literary composition；
This lookup unit 68, may be used for described message be session report for the first time literary composition time, according to the source node of described message
P2P nodal information described in information or destination node information searching；
This processing unit 69, if may be used for finding described source node identification or destination node information, it is determined that described
Message is P2P resource request message；
This second judging unit 610, if may be used for the literary composition of reporting for the first time that described message is not session, then judges described message institute
Whether the session information of respective session has P2P labelling；
This second adding device 611, if may be used for finding the source node of described message in described P2P nodal information
Information, then add to the destination node information of described message in described P2P nodal information, and in session corresponding to described message
Session information in add P2P labelling；
If finding the destination node information of described message in described P2P nodal information, then the source of described message is saved
Dot information adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message.
In one embodiment, this processing unit 69, it is also possible to be used for: if there being P2P labelling in described session information, it is determined that
Described message is P2P resource request message.
Refer to Fig. 8, illustrate another embodiment block diagram of the device of the application P2P resource-sharing, shown in this Fig. 8
Device is on the basis of above-mentioned Fig. 6 shown device, wherein, buffer unit 63, may include that lookup subelement 631, first obtains
Subelement 632, transmission subelement 633, reception subelement 634, second obtain subelement 635, determine subelement 636, constructor
Unit 637, lower subelements 638, caching subelement 639.
Wherein, this lookup subelement 631, may be used for the source node identification according to described message and search described P2P node
Information；
This first acquisition subelement 632, if may be used for finding described source node identification, then obtains described source node letter
All destination node information that breath is corresponding；
This transmission subelement 633, may be used for sending to the service end corresponding to destination node information each described using
In the request message checking shared listed files；
This reception subelement 634, may be used for receiving the shared literary composition that described service end is sent according to described request message
Part list；
This second acquisition subelement 635, may be used for obtaining corresponding to described message according to described shared listed files
Suspicious object P2P resource.
In one embodiment, this second obtains subelement 635, can be specifically for: obtain each described shared file
List is the same from sharing the information of file, according to the suspicious mesh corresponding to message described in the acquisition of information of described shared file
Mark P2P resource.
This determines subelement 636, may be used for the cryptographic Hash according to described suspicious object P2P resource and determines that this locality is the most
Cache described suspicious object P2P resource；
This constructor unit 637, if may be used for there is uncached suspicious object P2P resource, does not then delay according to described
The cryptographic Hash of the suspicious object P2P resource deposited and resource size, construct described uncached suspicious object P2P by P2P agreement
The URL address that resource is corresponding；
This lower subelements 638, may be used for, according to described URL address, sending to corresponding service end and carrying described URL
The download request of address；
This caching subelement 639, may be used for receiving the P2P money that described service end is sent according to the described request of downloading
Source, and cache described P2P resource, until caching all described suspicious object P2P resources.
In said apparatus, the function of unit and the process that realizes of effect specifically refer to corresponding step in said method
Realize process, do not repeat them here.
For device embodiment, owing to it corresponds essentially to embodiment of the method, so relevant part sees method in fact
The part executing example illustrates.Device embodiment described above is only schematically, wherein said as separating component
The unit illustrated can be or may not be physically separate, and the parts shown as unit can be or can also
It not physical location, i.e. may be located at a place, or can also be distributed on multiple NE.Can be according to reality
Need to select some or all of module therein to realize the purpose of the application scheme.Those of ordinary skill in the art are not paying
In the case of going out creative work, i.e. it is appreciated that and implements.
The foregoing is only the preferred embodiment of the application, not in order to limit the application, all essences in the application
Within god and principle, any modification, equivalent substitution and improvement etc. done, should be included within the scope of the application protection.
Claims (12)
1. the method for an end-to-end P2P resource-sharing, it is characterised in that described method includes:
When not can recognize that, according to the message characteristic of received message, the protocol type that described message is applied, according to institute
State source node identification and the destination node information of message, send P2P protocol validation report to corresponding client and service end respectively
Literary composition；
If receiving the P2P protocol responses message that described client and service end send according to described P2P protocol validation message, then
Determine that described message is P2P resource request message；
According to the described client access record to service end, obtain the suspicious object P2P resource corresponding to described message, and delay
Deposit described suspicious object P2P resource；
The listed files of described suspicious object P2P resource is sent, so that described client is according to described file to described client
List determines that the P2P resource of institute's acquisition request is whether in described suspicious object P2P resource；
After receiving P2P resource acquisition request, sending corresponding P2P resource to described client, described P2P resource acquisition please
Sent when asking the P2P resource for described client acquisition request determining in described suspicious object P2P resource.
Method the most according to claim 1, it is characterised in that described method also includes:
After determining that described message is P2P resource request message, source node identification and the destination node information of described message are added
It is added in the P2P nodal information preserved, and in the session information of session corresponding to described message, adds P2P labelling, described P2P
Nodal information includes source node identification and the corresponding relation of destination node information；
When receiving message, it is judged that whether described message is the literary composition of reporting for the first time of session, the most then according to the source node of described message
P2P nodal information described in information or destination node information searching, if finding described source node identification or destination node information, then
Determine that described message is P2P resource request message；
If described message is not the literary composition of reporting for the first time of session, then judge whether the session information of session corresponding to described message has P2P
Labelling, if there being P2P labelling, it is determined that described message is P2P resource request message in described session information.
Method the most according to claim 2, it is characterised in that described method also includes:
If finding the source node identification of described message in described P2P nodal information, then the destination node of described message is believed
Breath adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message；
If finding the destination node information of described message in described P2P nodal information, then the source node of described message is believed
Breath adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message.
Method the most according to claim 2, it is characterised in that the described access note according to described client to service end
Record, obtains the suspicious object P2P resource corresponding to described message, including:
Source node identification according to described message searches described P2P nodal information, if finding described source node identification, then obtains
All destination node information that described source node identification is corresponding；
The request message for checking shared listed files is sent to the service end corresponding to destination node information each described；
Receive the shared listed files that described service end is sent according to described request message；
The suspicious object P2P resource corresponding to described message is obtained according to described shared listed files.
Method the most according to claim 4, it is characterised in that described according to the described shared listed files described message of acquisition
Corresponding suspicious object P2P resource, including:
Obtain the information being the same from sharing file in each described shared listed files, according to the information of described shared file
Obtain the suspicious object P2P resource corresponding to described message.
Method the most according to claim 1, it is characterised in that described caching described suspicious object P2P resource, including:
Cryptographic Hash according to described suspicious object P2P resource determines that this locality has cached described suspicious object P2P resource the most；
If there is uncached suspicious object P2P resource, then according to the cryptographic Hash of described uncached suspicious object P2P resource and
Resource size, constructs, by P2P agreement, the URL address that described uncached suspicious object P2P resource is corresponding；
According to described URL address, send the download request carrying described URL address to corresponding service end；
Receive the P2P resource that described service end is sent according to the described request of downloading, and cache described P2P resource, until caching
All described suspicious object P2P resources.
7. the device of a P2P resource-sharing, it is characterised in that described device includes:
First transmitting element, for not can recognize that what described message was applied according to the message characteristic of received message
During protocol type, according to source node identification and the destination node information of described message, respectively to corresponding client and service end
Send P2P protocol validation message；
Determine unit, if for receiving the P2P association that described client and service end send according to described P2P protocol validation message
View response message, it is determined that described message is P2P resource request message；
Buffer unit, for according to the described client access record to service end, obtaining the suspicious mesh corresponding to described message
Mark P2P resource, and cache described suspicious object P2P resource；
Second transmitting element, for sending the listed files of described suspicious object P2P resource to described client, so that described visitor
According to described listed files, family end determines that the P2P resource of institute's acquisition request is whether in described suspicious object P2P resource；
Dispatching Unit, for after receiving P2P resource acquisition request, sends corresponding P2P resource to described client, described
When the P2P resource that P2P resource acquisition request is described client acquisition request determining is in described suspicious object P2P resource
Sent.
Device the most according to claim 7, it is characterised in that described device also includes:
First adding device, for after determining that described message is P2P resource request message, by the source node identification of described message
Add to destination node information in the P2P nodal information of preservation, and add in the session information of session corresponding to described message
Adding P2P labelling, described P2P nodal information includes source node identification and the corresponding relation of destination node information；
First judging unit, for when receiving message, it is judged that whether described message is the literary composition of reporting for the first time of session；
Search unit, for described message be session report for the first time literary composition time, according to the source node identification of described message or purpose joint
Dot information searches described P2P nodal information；
Processing unit, if for finding described source node identification or destination node information, it is determined that described message is P2P resource
Request message；
Second judging unit, if being used for the literary composition of reporting for the first time that described message is not session, then judges the meeting of session corresponding to described message
Whether words information has P2P labelling；
Described processing unit, is additionally operable to: if there being P2P labelling in described session information, it is determined that described message is P2P resource request
Message.
Device the most according to claim 8, it is characterised in that described device also includes:
Second adding device, if for the source node identification finding described message in described P2P nodal information, then by described
The destination node information of message is added in described P2P nodal information, and in the session information of session corresponding to described message
Add P2P labelling；
If finding the destination node information of described message in described P2P nodal information, then the source node of described message is believed
Breath adds in described P2P nodal information, and adds P2P labelling in the session information of session corresponding to described message.
Device the most according to claim 8, it is characterised in that described buffer unit, including:
Search subelement, search described P2P nodal information for the source node identification according to described message；
First obtains subelement, if for finding described source node identification, then obtains corresponding the owning of described source node identification
Destination node information；
Send subelement, be used for checking shared file for sending to the service end corresponding to destination node information each described
The request message of list；
Receive subelement, for receiving the shared listed files that described service end is sent according to described request message；
Second obtains subelement, for obtaining the suspicious object P2P money corresponding to described message according to described shared listed files
Source.
11. devices according to claim 10, it is characterised in that described second obtains subelement, specifically for:
Obtain the information being the same from sharing file in each described shared listed files, according to the information of described shared file
Obtain the suspicious object P2P resource corresponding to described message.
12. devices according to claim 7, it is characterised in that described buffer unit, including:
Determine subelement, described suspicious for determining that this locality has cached the most according to the cryptographic Hash of described suspicious object P2P resource
Target P2P resource；
, if for there is uncached suspicious object P2P resource, then according to described uncached suspicious object in constructor unit
The cryptographic Hash of P2P resource and resource size, construct, by P2P agreement, the URL that described uncached suspicious object P2P resource is corresponding
Address；
Lower subelements, for according to described URL address, the download carrying described URL address to corresponding service end transmission please
Ask；
Caching subelement, for receiving the P2P resource that described service end is sent according to the described request of downloading, and caches described
P2P resource, until caching all described suspicious object P2P resources.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610514920.4A CN106060155B (en) | 2016-06-28 | 2016-06-28 | The method and device of P2P resource-sharing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610514920.4A CN106060155B (en) | 2016-06-28 | 2016-06-28 | The method and device of P2P resource-sharing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106060155A true CN106060155A (en) | 2016-10-26 |
| CN106060155B CN106060155B (en) | 2019-04-05 |
Family
ID=57201663
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610514920.4A Active CN106060155B (en) | 2016-06-28 | 2016-06-28 | The method and device of P2P resource-sharing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106060155B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109376001A (en) * | 2017-08-10 | 2019-02-22 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus of resource allocation |
| WO2021150244A1 (en) * | 2020-01-24 | 2021-07-29 | Hewlett-Packard Development Company, L.P. | Resource download in peer-to-peer networks |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7539664B2 (en) * | 2001-03-26 | 2009-05-26 | International Business Machines Corporation | Method and system for operating a rating server based on usage and download patterns within a peer-to-peer network |
| CN102082699A (en) * | 2009-11-27 | 2011-06-01 | 上海博达数据通信有限公司 | P2P (peer-to-peer) protocol identification method on basis of active detection mode |
| CN102130838A (en) * | 2011-04-02 | 2011-07-20 | 南京邮电大学 | Method for realizing peer-to-peer network caching system based on Ares protocol |
| US8131760B2 (en) * | 2000-07-20 | 2012-03-06 | Digimarc Corporation | Using object identifiers with content distribution |
| CN102404396A (en) * | 2011-11-14 | 2012-04-04 | 北京星网锐捷网络技术有限公司 | Method, device and system for identifying peer-to-peer (P2P) flow and equipment |
| US8244884B2 (en) * | 2007-04-11 | 2012-08-14 | The Directv Group, Inc. | Method and apparatus for file sharing between a group of user devices with crucial portions sent via satellite and non-crucial portions sent using a peer-to-peer network |
| CN102739712A (en) * | 2011-04-08 | 2012-10-17 | 中国移动通信集团贵州有限公司 | Method and system for network cache data distribution |
-
2016
- 2016-06-28 CN CN201610514920.4A patent/CN106060155B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8131760B2 (en) * | 2000-07-20 | 2012-03-06 | Digimarc Corporation | Using object identifiers with content distribution |
| US7539664B2 (en) * | 2001-03-26 | 2009-05-26 | International Business Machines Corporation | Method and system for operating a rating server based on usage and download patterns within a peer-to-peer network |
| US8244884B2 (en) * | 2007-04-11 | 2012-08-14 | The Directv Group, Inc. | Method and apparatus for file sharing between a group of user devices with crucial portions sent via satellite and non-crucial portions sent using a peer-to-peer network |
| CN102082699A (en) * | 2009-11-27 | 2011-06-01 | 上海博达数据通信有限公司 | P2P (peer-to-peer) protocol identification method on basis of active detection mode |
| CN102130838A (en) * | 2011-04-02 | 2011-07-20 | 南京邮电大学 | Method for realizing peer-to-peer network caching system based on Ares protocol |
| CN102739712A (en) * | 2011-04-08 | 2012-10-17 | 中国移动通信集团贵州有限公司 | Method and system for network cache data distribution |
| CN102404396A (en) * | 2011-11-14 | 2012-04-04 | 北京星网锐捷网络技术有限公司 | Method, device and system for identifying peer-to-peer (P2P) flow and equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109376001A (en) * | 2017-08-10 | 2019-02-22 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus of resource allocation |
| WO2021150244A1 (en) * | 2020-01-24 | 2021-07-29 | Hewlett-Packard Development Company, L.P. | Resource download in peer-to-peer networks |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106060155B (en) | 2019-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10951395B2 (en) | Data fetching in data exchange networks | |
| US10554748B2 (en) | Content management | |
| KR101850351B1 (en) | Method for Inquiring IoC Information by Use of P2P Protocol | |
| US8514749B2 (en) | Routing requests for duplex applications | |
| CN103597471A (en) | Methods and systems for caching data communications over computer networks | |
| US20150088995A1 (en) | Method and apparatus for sharing contents using information of group change in content oriented network environment | |
| CN102333127A (en) | Resource downloading method, device and system | |
| CN111917900A (en) | Request processing method and device for domain name proxy | |
| CN109873855A (en) | A kind of resource acquiring method and system based on block chain network | |
| CN107580021A (en) | A kind of method and apparatus of file transmission | |
| CN112272164A (en) | Message processing method and device | |
| US20200137173A1 (en) | USER BASED mDNS SERVICE DISCOVERY | |
| US8650313B2 (en) | Endpoint discriminator in network transport protocol startup packets | |
| US10594584B2 (en) | Network analysis and monitoring tool | |
| CN115297098A (en) | Edge service acquisition method and device, edge computing system, medium and equipment | |
| US8959243B2 (en) | System and method to guide active participation in peer-to-peer systems with passive monitoring environment | |
| CN105357260B (en) | Realize system, VDI data cache method and the VDI buffer memory device of virtual desktop | |
| CN106060155A (en) | P2P (Peer to Peer) resource sharing method and device | |
| CN105933298B (en) | Apparatus and method for performing transmission control protocol handshaking | |
| CN108011801A (en) | Method, unit and the system of data transfer | |
| US9912757B2 (en) | Correlation identity generation method for cloud environment | |
| CN110995890B (en) | Domain name request scheduling method and device | |
| CN110086702B (en) | Message forwarding method and device, electronic equipment and machine-readable storage medium | |
| US10849179B1 (en) | Mobile network tool | |
| CN106230924A (en) | The compression method of message and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Binjiang District and Hangzhou city in Zhejiang Province Road 310051 No. 68 in the 6 storey building Applicant after: Hangzhou Dipu Polytron Technologies Inc Address before: Binjiang District and Hangzhou city in Zhejiang Province Road 310051 No. 68 in the 6 storey building Applicant before: Hangzhou Dipu Technology Co., Ltd. |
|
| COR | Change of bibliographic data | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |