CN101867601B - File-level P2P network flow identification method - Google Patents
File-level P2P network flow identification method Download PDFInfo
- Publication number
- CN101867601B CN101867601B CN2010101754826A CN201010175482A CN101867601B CN 101867601 B CN101867601 B CN 101867601B CN 2010101754826 A CN2010101754826 A CN 2010101754826A CN 201010175482 A CN201010175482 A CN 201010175482A CN 101867601 B CN101867601 B CN 101867601B
- Authority
- CN
- China
- Prior art keywords
- packet
- payload
- protocol type
- file
- source
- 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.)
- Expired - Fee Related
Links
Abstract
The invention relates to a file-level P2P network flow identification method, belonging to the technical field of networks. Based on the existing deep-level data packet detection technology, hash information of a file is extracted from the effective load of a data packet according to the P2P protocol type labeled by the data packet. Since the specific file information transmitted by a P2P stream is extracted through the method, the grain size of identification is finer. By adopting the method of the invention, a network administrator can take more effective measures to manage P2P flow; and moreover, the file information identified by the method of the invention can be used for judging the validity of the file and analyzing the concern degree of resources and the downloading behaviors of users and the like.
Description
Technical field
The present invention relates to a kind of file-level P 2 P (Peer-to-Peer) network flow identification method, belong to networking technology area.
Background technology
In recent years, along with the continuous progress of P2P network technology, the popularity degree that various P2P use is increasingly high.The ratio of P2P flow just surpassed the flow that HTTP uses on the Internet from 2004, became the main body of internet traffic.The Germany one tame authoritative Ipoque of mechanism claims that in a the Internet of 2008-2009 investigation report the P2P flow has reached whole more than 60% of flow in the Internet.
P2P has brought great challenge when bringing fundamental change to the Internet use pattern, also for network management and safety.Its harm shows: 1. P2P uses and adopts many concurrent connections to carry out transfer of data usually, has aggravated the congested of core net and Access Network, makes that other important service can not get ensureing, directly has influence on the quality of services for users rank.2. the reciprocity transmission means of P2P network has been brought the change of network traffics patterns; The uplink traffic of Access Network significantly increases; Making with ADSL is that traditional asymmetrical network access way of representative does not more and more receive user's approval, has brought more overhead to Virtual network operator.3. the P2P network provides and has shared easily and the mechanism of routing fast, and for some internet worm, wooden horse provide better invasion chance, it is big to involve scope, broad covered area, and the loss meeting that causes is very big.4. the prosperity of P2P application has been aggravated the distribution of pirate medium, makes that impinge issues such as mp3, video display are serious day by day, has increased the difficulty of intellectual property protection.
Virtual network operator and enterprise network management department want the P2P network traffics are effectively managed, and just must capture its bottleneck technology---the identification of P2P flow.Existing P 2P flow recognition technology mainly contains the three major types method:
(1) based on the recognition methods of port numbers
Recognition methods based on port numbers is specially: the default port that the port numbers of the network data flow that obtains and P2P are used number matees, if mate successfully, thinks that then this network data flow is the P2P flow.Its shortcoming is: the accuracy of identification is lower.Main cause has: along with the P2P application and development, most of P2P use the port numbers that allows the user manually to select to be provided with acquiescence; In addition, many emerging P2P use and adopt port numbers at random, and this just makes that its port numbers is unpredictable; Also have other a kind of phenomenon at present, P2P uses the default port number bring into use some other regular services, such as the function port that pretends oneself with 80 ports.
(2) deep layer packet detection technique (Deep Packet Inspection, DPI)
Deep layer packet detection technique is through finding that to the detection of packet application layer protocol P2P uses.This technology is used a feature database storage payload characteristic information, and the packet that meets the payload characteristic promptly is regarded as the P2P packet.The accuracy of this method identification is higher, easy to understand, upgrading are convenient, it is simple to safeguard, is the most general method of utilization at present.But present deep layer packet detection technique only can be accomplished other identification of stream (flow) level, does not also accomplish the identification of file-level, promptly identifies the concrete fileinfo of P2P flow transmission.
(3) based on the recognition methods of traffic characteristic
P2P uses as a kind of new application that makes full use of client resource, and it is used with respect to other at the traffic characteristic that transport layer shows, and like HTTP, FTP, DNS etc. many different places is arranged.Recognition methods based on traffic characteristic is: the traffic characteristic through detection makes new advances finds that P2P uses.Its shortcoming has: 1. because the transport layer stream measure feature generally can not clearly be indicated the application layer protocol type, so this method to the ability of P2P application class a little less than, and application class is extremely important for the enforcement of QoS (Quality of Servic, service quality).2. since the existence of asymmetric route and packet loss, re-transmission phenomenon cause accurately confirming traffic characteristic, thereby might the accuracy of P2P flow detection be impacted.
Summary of the invention
The objective of the invention is on the basis of existing deep layer packet detection technique, to propose a kind of file-level P 2 P network flow identification method in order to overcome the deficiency that prior art exists.The present invention is deep into file-level, and then identifies the concrete fileinfo of P2P flow transmission on the basis that accurately identification P2P flows.
The objective of the invention is to realize through following technical proposals.
A kind of file-level P 2 P network flow identification method, its concrete operations step is following:
Step 1: set up a network flow table, the structure of this table includes, but are not limited to following field: the source IP of packet, source port, purpose IP, destination interface and file hash information;
Step 2: this step can with step 1 simultaneous operation: set up a P2P feature database, it only comprises the P2P payload characteristic information relevant with file; The structure of this P2P feature database comprises following field: P2P protocol type, payload characteristic.
Step 3: resolve in the packet header to the packet that receives, obtains upper strata transport protocol type, source IP, source port, purpose IP, the destination interface of this packet;
Step 4: whether the upper strata transport protocol type of judging this packet is TCP, if execution in step 5 then; Otherwise turn to step 3;
Step 5: whether inquiry exists a record in the network flow table that step 1 is set up; Source IP, source port, purpose IP, the destination interface of the packet that its source IP, source port, purpose IP, destination interface receive with step 3 respectively are identical, and perhaps purpose IP, destination interface, source IP, the source port of the packet that receives with step 3 respectively of its source IP, source port, purpose IP, destination interface are identical; If there is a such record, be that P2P uses then with the package identification that receives in the step 3, turn to step 3 then; Otherwise execution in step 6;
Step 6: the payload of the packet that payload feature field in the P2P feature database of successively step 2 being set up and step 3 receive is mated; If mate successfully; Be the successful pairing P2P protocol type of payload characteristic of coupling in the P2P feature database with this package identification then, execution in step 7 then; Otherwise turn to step 3;
Step 7: according to the step 6 pair P2P protocol type that this packet identified; Extraction document hash information from the payload of this packet; And with source IP, source port, purpose IP, destination interface and the file hash information of this packet as a new record; Add the network flow table to, forward step 3 then to.
Said P2P feature database includes but not limited to the following P2P payload characteristic information relevant with file, and its P2P protocol type field is respectively with corresponding payload feature field:
1. P2P protocol type field: BitTorrent agreement; Corresponding payload feature field: the payload of packet starts with " 0x13BitTorrent protocol ";
2. P2P protocol type field: eDonkey/eMule agreement; Corresponding payload feature field: the payload of packet is " 0x47 " with " 0xe3 " beginning and the 6th byte, is " 0x81 " with " 0xc5 " beginning and the 6th byte perhaps;
3. P2P protocol type field: Gnutella agreement; Corresponding payload feature field: the payload of packet with " GET/uri-res/N2R? urn:sha1: " beginning;
4. P2P protocol type field: Fast Track agreement; Corresponding payload feature field: the payload of packet starts with " GET/.hash=";
5. P2P protocol type field: Direct Connect agreement; Corresponding payload feature field: the payload of packet is with “ $ADCGET file TTH/ " beginning;
6. P2P protocol type field: Ares agreement; Corresponding payload feature field: the payload of packet starts with " GET sha1: ";
Preferably, described in the step 7 from the payload of packet the method for extraction document hash information be:
If the P2P protocol type of this package identification is BitTorrent, then, extract 20 character strings as the file hash information from the 29th beginning of the payload of this packet; If the P2P protocol type of this package identification is eDonkey/eMule, then, extract 16 character strings as the file hash information from the 7th beginning of the payload of this packet; If the P2P protocol type of this package identification is Gnutella, then, extract 32 character strings as the file hash information from the 27th beginning of the payload of this packet; If the P2P protocol type of this package identification is Fast Track, then, extract 40 character strings as the file hash information from the 12nd beginning of the payload of this packet; If the P2P protocol type of this package identification is Direct Connect, then, extract 39 character strings as the file hash information from the 18th beginning of the payload of this packet; If the P2P protocol type of this package identification is Ares, then, extract 28 character strings as the file hash information from the 10th beginning of the payload of this packet.
Beneficial effect
Compare with existing recognition methods, a kind of file-level P 2 P network flow identification method of the present invention is owing to extracted the concrete fileinfo of P2P flow transmission, and grain size of identification is thinner.Use method provided by the invention, network manager can take more effective measures to manage the P2P flow; In addition, the fileinfo that the inventive method identifies can also be used to judge this document legitimacy, analyzes the degree of concern of resource and user's trend such as download behavior.
Embodiment
Below in conjunction with specific embodiment the present invention is elaborated.
Among the embodiment, 5 packets that successively receive are respectively:
1. source IP:60.25.8.92; Source port: 1409, purpose IP:119.6.8.234, destination interface: 7678; Upper strata transport protocol type: UDP, payload (hexadecimal): 01 1e, 60 21 d3 1e, 6,122 91 3b 7a 2f 9b, 00 00 e1 16 05
2. source IP:58.247.204.241; Source port: 2399; Purpose IP:114.223.152.51; Destination interface: 80; Upper strata transport protocol type: TCP, payload (hexadecimal): 13 42 69 7454 6f, 72 72 65 6e, 74 20 70 72 6f, 74 6f, 63 6f 6c, 00 00 00 00 00 10 00 052c 1a ad, 34 85 6e, 44 a3 de fb df 7c fc e6,45 c1 1e, 46 f3,66 4d, 36 2d 332d, 30 2d 2d 4d, 42 6e b0,08 30 02 3a, 05 1f
3. source IP:89.134.31.170; Source port: 1563; Purpose IP:86.106.112.163; Destination interface: 22417, upper strata transport protocol type: TCP, payload (hexadecimal): e3 29 00 0,000 58 07 8d da 14 0b f6 c8 6e 6a d3 45 b5 a5 e7 23 b2 00 20 1e 08 00 f020 08 00 c0 23 08 00 f0 20 08 00 c0 23 08 00 90 26 08
4. source IP:114.223.152.51, source port: 80, purpose IP:58.247.204.241, destination interface: 2399, upper strata transport protocol type: TCP, payload: 00 00 00 01 02
5. source IP:210.51.188.91; Source port: 3680, purpose IP:61.147.114.9, destination interface: 4163; Upper strata transport protocol type: TCP, payload: 15 00 00 00 03 ae b3 ad 4b0c, 00 00 00 00 80 01 00 00 20 00 00 36 d4 ac 4b
The concrete steps of the inventive method are:
Step 1: set up a network flow table, its structure comprises: the source IP of packet, source port, purpose IP, destination interface and file hash information; This table initial condition is empty table.
Step 2: this step can with step 1 simultaneous operation: set up a P2P feature database, comprise the P2P payload characteristic information relevant with file, its P2P protocol type is respectively with corresponding payload characteristic:
1. BitTorrent agreement, the payload of packet starts with " 0x13BitTorrent protocol ";
2. eDonkey/eMule agreement, the payload of packet is " 0x47 " with " 0xe3 " beginning and the 6th byte, is " 0x81 " with " 0xc5 " beginning and the 6th byte perhaps;
3. Gnutella agreement, the payload of packet with " GET/uri-res/N2R? urn:sha1: " beginning;
4. Fast Track agreement, the payload of packet starts with " GET/.hash=";
5. Direct Connect agreement, the payload of packet is with “ $ADCGET file TTH/ " beginning;
6. Ares agreement, the payload of packet starts with " GET sha1: ".
Step 3: receive 1. number packet, the packet header of this packet is resolved, the upper strata transport protocol type that obtains this packet is that UDP, source IP are that 60.25.8.92, source port are 1409, purpose IP is that 119.6.8.234, destination interface are 7678.
Step 4: the upper strata transport protocol type of judging this packet is not TCP, turns to step 3.
Step 3: receive 2. number packet, the upper strata transport protocol type that obtains this packet is that TCP, source IP are that 58.247.204.241, source port are 2399, purpose IP is that 114.223.152.51, destination interface are 80;
Step 4: the upper strata transport protocol type of judging this packet is TCP, turns to step 5;
Step 5: whether inquiry exists a record in the network flow table that step 1 is set up; Source IP, source port, purpose IP and the destination interface of the packet that its source IP, source port, purpose IP and destination interface and step 3 receive are identical, and perhaps purpose IP, destination interface, the source IP of the packet that receives of its source IP, source port, purpose IP and destination interface and step 3 are identical with source port; Because this moment, the network flow table was empty, so there is not such record, turned to step 6;
Step 6: the payload condition code in the P2P feature database of successively step 2 being set up is mated with the 2. payload of number packet; 2. the payload of number packet starts with hexadecimal string 13 42 69 74 546f 72 72 65 6e 74 20 70 72 6f 74 6f 63 6f 6c; The characteristic that meets the BitTorrent agreement; Demarcating this packet is that BitTorrent uses, and turns to step 7;
Step 7: according to the step 6 P2P protocol type that pair 2. number packet identified is BitTorrent; From 2. the 29th beginning of number data packet payload; Extract 20 character string 2c 1a ad, 34 85 6e 44a3 de fb df 7c fc e6,45 c1 1e, 46 f3 66 as the file hash information; And with source IP, source port, purpose IP, destination interface and the file hash information of this packet as a new record, add the network flow table to, turn to step 3 then.
Step 3: resolve in the 3. packet header of number packet to receiving, and the upper strata transport protocol type that obtains this packet is that TCP, source IP are that 89.134.31.170, source port are 1563, purpose IP is that 86.106.112.163, destination interface are 22417;
Step 4: the upper strata transport protocol type of judging this packet is TCP, turns to step 5;
Step 5: whether inquiry exists a record in the network flow table that step 1 is set up; Source IP, source port, purpose IP and the destination interface of the packet that its source IP, source port, purpose IP and destination interface and step 3 receive are identical, and perhaps purpose IP, destination interface, the source IP of the packet that receives of its source IP, source port, purpose IP and destination interface and step 3 are identical with source port; Do not exist such record this moment, turns to step 6;
Step 6: the payload condition code in the P2P feature database of successively step 2 being set up is mated with the 2. payload of number packet; 3. to start the 6th byte with hexadecimal character e3 be hexadecimal character 47 to the payload of number packet; The characteristic that meets the eDonkey/eMule agreement; Demarcating this packet is that eDonkey/eMule uses, and turns to step 7;
Step 7: according to the step 6 P2P protocol type that pair 3. number packet identified is eDonkey/eMule; From 3. the 7th beginning of number data packet payload; Extract 16 character strings, 07 8d da, 14 0b f6 c86e 6a d3,45 b5 a5 e7,23 b2 as the file hash information; And with source IP, source port, purpose IP, destination interface and the file hash information of this packet as a new record, add the network flow table to, turn to step 3.
Step 3: resolve in the 4. packet header of number packet to receiving, and the upper strata transport protocol type that obtains this packet is that TCP, source IP are that 114.223.152.51, source port are 80, purpose IP is that 58.247.204.241, destination interface are 2399;
Step 4: the upper strata transport protocol type of judging this packet is TCP, turns to step 5;
Step 5: whether inquiry exists a record in the network flow table that step 1 is set up; Source IP, source port, purpose IP and the destination interface of the packet that its source IP, source port, purpose IP and destination interface and step 3 receive are identical, and perhaps purpose IP, destination interface, the source IP of the packet that receives of its source IP, source port, purpose IP and destination interface and step 3 are identical with source port; Have a such record this moment, demarcation 4. number packet is that P2P uses, and turns to step 3;
Step 3: resolve in the 5. packet header of number packet to receiving, and the upper strata transport protocol type that obtains this packet is that TCP, source IP are 210.51.188.91, and source port is 3680, and purpose IP is 61.147.114.9, and destination interface is 4163;
Step 4: the upper strata transport protocol type of judging this packet is TCP, turns to step 5;
Step 5: whether inquiry exists a record in the network flow table that step 1 is set up; Source IP, source port, purpose IP and the destination interface of the packet that its source IP, source port, purpose IP and destination interface and step 3 receive are identical, and perhaps purpose IP, destination interface, the source IP of the packet that receives of its source IP, source port, purpose IP and destination interface and step 3 are identical with source port; Do not exist such record this moment, turns to step 6;
Step 6: the payload condition code in the P2P feature database of successively step 2 being set up is mated with the 5. payload of number packet; 5. the payload 15 00 00 00 03 ae b3 ad 4b 0,c00 00 00 00 80 01 00 00 20 00 00 36 d4 ac 4b of number packet do not meet the relevant P2P payload feature database of predefined file, turn to step 3.
Visible by the foregoing description, this file-level P 2 P network flow identification method of the present invention can accurately identify multiple P2P and use, and finds the concrete fileinfo of P2P flow transmission.
The above only is a preferred implementation of the present invention; Should be understood that; For those skilled in the art, under the prerequisite that does not break away from the principle of the invention, can also make some improvement; Perhaps part technical characterictic wherein is equal to replacement, these improvement and replacement also should be regarded as protection scope of the present invention.
Claims (3)
1. file-level P 2 P network flow identification method, it is characterized in that: its concrete operations step is following:
Step 1: set up a network flow table, this list structure comprises following field: the source IP of packet, source port, purpose IP, destination interface and file hash information;
Step 2: this step can with step 1 simultaneous operation: set up a P2P feature database, it only comprises the P2P payload characteristic information relevant with file; The structure of this P2P feature database comprises following field: P2P protocol type, payload characteristic;
Step 3: resolve in the packet header to the packet that receives, obtains upper strata transport protocol type, source IP, source port, purpose IP, the destination interface of this packet;
Step 4: whether the upper strata transport protocol type of judging this packet is TCP, if execution in step 5 then; Otherwise turn to step 3;
Step 5: whether inquiry exists a record in the network flow table that step 1 is set up; Source IP, source port, purpose IP, the destination interface of the packet that its source IP, source port, purpose IP, destination interface receive with step 3 respectively are identical, and perhaps purpose IP, destination interface, source IP, the source port of the packet that receives with step 3 respectively of its source IP, source port, purpose IP, destination interface are identical; If there is a such record, be that P2P uses then with the package identification that receives in the step 3, turn to step 3 then; Otherwise execution in step 6;
Step 6: the payload of the packet that payload feature field in the P2P feature database of successively step 2 being set up and step 3 receive is mated; If mate successfully; Be the successful pairing P2P protocol type of payload characteristic of coupling in the P2P feature database with this package identification then, execution in step 7 then; Otherwise turn to step 3;
Step 7: according to the step 6 pair P2P protocol type that this packet identified; Extraction document hash information from the payload of this packet; And with source IP, source port, purpose IP, destination interface and the file hash information of this packet as a new record; Add the network flow table to, forward step 3 then to.
2. a kind of file-level P 2 P network flow identification method as claimed in claim 1; It is characterized in that: said P2P feature database comprises the following P2P payload characteristic information relevant with file, and its P2P protocol type field is respectively with corresponding payload feature field:
1. P2P protocol type field: BitTorrent agreement; Corresponding payload feature field: the payload of packet starts with " 0x13BitTorrent protocol ";
2. P2P protocol type field: eDonkey/eMule agreement; Corresponding payload feature field: the payload of packet is " 0x47 " with " 0xe3 " beginning and the 6th byte, is " 0x81 " with " 0xc5 " beginning and the 6th byte perhaps;
3. P2P protocol type field: Gnutella agreement; Corresponding payload feature field: the payload of packet with " GET/uri-res/N2R? urn:sha1: " beginning;
4. P2P protocol type field: Fast Track agreement; Corresponding payload feature field: the payload of packet starts with " GET/.hash=";
5. P2P protocol type field: Direct Connect agreement; Corresponding payload feature field: the payload of packet is with “ $ADCGET file TTH/ " beginning;
6. P2P protocol type field: Ares agreement; Corresponding payload feature field: the payload of packet starts with " GET sha1: ".
3. according to claim 1 or claim 2 a kind of file-level P 2 P network flow identification method is characterized in that: described in the step 7 from the payload of packet the method for extraction document hash information be:
If the P2P protocol type of this package identification is BitTorrent, then, extract 20 character strings as the file hash information from the 29th beginning of the payload of this packet; If the P2P protocol type of this package identification is eDonkey/eMule, then, extract 16 character strings as the file hash information from the 7th beginning of the payload of this packet; If the P2P protocol type of this package identification is Gnutella, then, extract 32 character strings as the file hash information from the 27th beginning of the payload of this packet; If the P2P protocol type of this package identification is Fast Track, then, extract 40 character strings as the file hash information from the 12nd beginning of the payload of this packet; If the P2P protocol type of this package identification is Direct Connect, then, extract 39 character strings as the file hash information from the 18th beginning of the payload of this packet; If the P2P protocol type of this package identification is Ares, then, extract 28 character strings as the file hash information from the 10th beginning of the payload of this packet.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010101754826A CN101867601B (en) | 2010-05-14 | 2010-05-14 | File-level P2P network flow identification method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010101754826A CN101867601B (en) | 2010-05-14 | 2010-05-14 | File-level P2P network flow identification method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101867601A CN101867601A (en) | 2010-10-20 |
| CN101867601B true CN101867601B (en) | 2012-08-15 |
Family
ID=42959163
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010101754826A Expired - Fee Related CN101867601B (en) | 2010-05-14 | 2010-05-14 | File-level P2P network flow identification method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101867601B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025636B (en) * | 2010-12-09 | 2012-09-05 | 北京星网锐捷网络技术有限公司 | Message feature processing method and device as well as network equipment |
| CN103220329B (en) * | 2013-03-07 | 2017-02-08 | 汉柏科技有限公司 | P2P protocol identification method based on protocol content identification and behavior identification |
| CN103532779B (en) * | 2013-10-10 | 2017-07-18 | 北京锐安科技有限公司 | A kind of method and system of quick positioning shunting device packet loss |
| CN113709001A (en) * | 2021-09-01 | 2021-11-26 | 深圳市大洲智创科技有限公司 | Method for identifying p2p protocol in linux kernel |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1750538A (en) * | 2005-09-29 | 2006-03-22 | 西安交大捷普网络科技有限公司 | Method for discovering and controlling of producing flow based on P2P high speed unloading software |
| CN101192924A (en) * | 2006-11-24 | 2008-06-04 | 北京大学 | P2P storage system coding method based on Reed-Solomon code |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060265402A1 (en) * | 2005-05-20 | 2006-11-23 | Andrew Edmond | Grid network for distribution of files |
-
2010
- 2010-05-14 CN CN2010101754826A patent/CN101867601B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1750538A (en) * | 2005-09-29 | 2006-03-22 | 西安交大捷普网络科技有限公司 | Method for discovering and controlling of producing flow based on P2P high speed unloading software |
| CN101192924A (en) * | 2006-11-24 | 2008-06-04 | 北京大学 | P2P storage system coding method based on Reed-Solomon code |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101867601A (en) | 2010-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10652153B2 (en) | Apparatus, systems and methods utilizing dispersive networking | |
| Basescu et al. | SIBRA: Scalable internet bandwidth reservation architecture | |
| EP2258084B1 (en) | Technique for classifying network traffic and for validating a mechanism for calassifying network traffic | |
| KR101097548B1 (en) | Digital object title authentication | |
| CN102404396B (en) | Method, device and system for identifying peer-to-peer (P2P) flow and equipment | |
| CN101867601B (en) | File-level P2P network flow identification method | |
| US10701582B2 (en) | Dynamic application QoS profile provisioning | |
| Yiakoumis et al. | Neutral net neutrality | |
| François et al. | Network security through software defined networking: a survey | |
| EP3682669B1 (en) | Stateful application identification while roaming | |
| Szabo et al. | Traffic analysis of mobile broadband networks | |
| Mongkolluksamee et al. | Combining communication patterns & traffic patterns to enhance mobile traffic identification performance | |
| CN102082699A (en) | P2P (peer-to-peer) protocol identification method on basis of active detection mode | |
| Othman et al. | Design and implementation of application based routing using openflow | |
| KR101116109B1 (en) | Digital object title and transmission information | |
| Chung et al. | Measurement analysis of mobile traffic in enterprise networks | |
| JP2005295457A (en) | P2p traffic dealing router and p2p traffic information sharing system using same | |
| KR102376496B1 (en) | System for distributed forwarding service stream and method for the same | |
| CN103701713A (en) | QoS (Quality of Service) scheduling method based on WIFI (Wireless Fidelity) password of AP (Access Point) router | |
| CN101577644A (en) | Peer-to-peer network application traffic identification method | |
| CN102035750A (en) | Peer-to-peer (P2P) flow recognizing method and device | |
| Akpinar et al. | PPNet: Privacy protected CDN-ISP collaboration for QoS-aware multi-CDN adaptive video streaming | |
| CN101854366A (en) | Peer-to-peer network flow-rate identification method and device | |
| JPWO2017138403A1 (en) | Control device, control method, and storage medium for storing program | |
| JP2007228217A (en) | Traffic decision device, traffic decision method, and program therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120815 Termination date: 20130514 |