CN108270845A - A kind of P2P VOD systems and method based on RTSP - Google Patents
A kind of P2P VOD systems and method based on RTSP Download PDFInfo
- Publication number
- CN108270845A CN108270845A CN201711324332.5A CN201711324332A CN108270845A CN 108270845 A CN108270845 A CN 108270845A CN 201711324332 A CN201711324332 A CN 201711324332A CN 108270845 A CN108270845 A CN 108270845A
- Authority
- CN
- China
- Prior art keywords
- rtsp
- stb
- tracker
- peer
- peer nodes
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000003860 storage Methods 0.000 claims abstract description 26
- 230000011664 signaling Effects 0.000 claims description 17
- 239000012634 fragment Substances 0.000 claims description 8
- 230000005540 biological transmission Effects 0.000 claims description 4
- 230000008569 process Effects 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000003111 delayed effect Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 238000004146 energy storage Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- 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
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/6437—Real-time Transport Protocol [RTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
- H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a kind of P2P VOD systems and method based on RTSP, are related to field of Internet multimedia.The system includes STB, content source station, Tracker and several Peer nodes；When STB sends out RTSP requests according to user's program request to content source station, intercept the request and be redirected to Tracker；If program request for the first time, then the URL of content source station is returned to STB and played by Tracker；While broadcasting, Tracker caches corresponding RTSP contents, and distributes them to the Peer of selection；Tracker records the storage relationships of each Peer and RTSP contents to Peer lists；When program request content again, Tracker searches the Peer lists where all segments of the RTSP contents, and Peer nodes where STB choose Peer nodes according to the Peer lists asks it to go out stream.The present invention can realize that P2P is dispatched, and can make full use of the memory space of each Peer under user's unaware, realize the load balancing of Peer, caching capabilities are strong.
Description
Technical field
The present invention relates to field of Internet multimedia, are specifically that one kind is based on RTSP (Real Time Streaming
Protocol, real time streaming transport protocol) P2P (Peer to Peer, peer-to-peer network) VOD systems and method.
Background technology
P2P service technologies refer to the participant of network to share a part of hardware resource that they are possessed that (processing capacity is deposited
Energy storage power, network-connectivity, printer etc.), these shared resources, can be by other equities by network offering services and content
Node (Peer) is directly accessed without being subjected to intermediate entities.Participant in this network is both resource, service and content
Supplier (Server), and be that resource, service and content obtain taker (Client).
P2P flows increase with surprising rapidity before and after 2001, are even more to surmount http protocol application by 2004, become mutual
Most common application and bandwidth main consumer in networking.P2P flow growth trends start to slow down within 2007.But with regarding in recent years
The development of frequency industry, transmission of video increase year by year in internet traffic accounting, newest according to Cisco visual webs index (VNI)
Report point out that flow accounting of the video in Global Internet will rise to the 79% of 2020 by 63% in 2015.2020
Accounting of the internet video playback volume of year, high definition and ultra high-definition in total video flow will be risen to by 53% in 2015
82%.
CDN is the acceleration network for the content distribution for being now widely used for Streaming Media cloud industry, and P2P CDN are in CDN
Hold distribution to accelerate to introduce P2P technologies among network, cost is reduced while service ability is ensured by this pattern, is
The current optimal platform for realizing video traffic scene.
At present, P2P systems are typically all using subscriber terminal equipment (such as Intelligent set top box, intelligent gateway) etc. as Peer
(node in P2P peer-to-peer networks) storage device.The common characteristic of this kind equipment is that memory capacity is small, and performance is insufficient, into
And cause existing P2P order methods there are following defects in realization：
(1) existing P2P order methods need (such as program code of modifying to player end when realizing P2P scheduling
Modification), it is apparent not only to realize that complicated for operation but also user perceives, experience is bad.
(2) existing P2P order methods are in the caching for realizing source station content, dependent on depositing for current Peer storage devices
The factors such as capacity and performance of storage.And to be commonly stored capacity small for existing Peer storage devices, performance is insufficient, so that caching property
Can be limited, and then influence user's viewing quality.
(3) due to existing Peer storage devices, to be commonly stored capacity small so that the load excessive of single Peer, Wu Facheng
Carry the larger file storage of content.For example, the content to be watched of active user is 5G sizes, and the storage of Peer storage devices is held
It measures as 1G, then the Peer storage devices are can not to complete the storage of the content file.
Invention content
The purpose of the invention is to overcome the shortcomings of above-mentioned background technology, a kind of P2P program requests system based on RTSP is provided
System and method not only can realize P2P scheduling, and can effectively realize the load balancing of Peer in user's unaware, delay
It is strong to deposit ability.
To achieve the above objectives, the present invention provides a kind of P2P VOD systems based on RTSP, which includes client
STB, content source station, node administration dispatch server Tracker and several Peer nodes have in several Peer nodes
Peer node of one Peer node where STB；
STB sends out RTSP requests according to the content of user's program request to content source station；Peer nodes where STB intercept should
RTSP is asked, and is redirected to Tracker；When the Tracker judgement requested contents of STB are requested for the first time, Tracker makes
The URL of content source station is returned to STB with RTSP redirecting signalings to play out；
While STB is played, Tracker sends out on-demand content using the URL of RTSP requests intercepted to content source station
Request, and the corresponding complete RTSP contents of the request are cached；Tracker is according to specified cache policy from current institute
At least one Peer nodes are chosen in some Peer nodes, and the RTSP contents of caching are distributed to according to preset distribution rules
It is stored in the Peer nodes of selection；Each Peer nodes report Distribution Results, and to Tracker, Tracker is in preset Peer
Each Peer nodes and the correspondence of the RTSP contents of each Peer nodes storage are recorded in list；
When STB sends out identical RTSP requests again, the Peer nodes where STB intercept RTSP requests, and reset
To Tracker；STB is redirected to the Peer nodes where STB using RTSP redirecting signalings by Tracker, simultaneously
Tracker searches the Peer lists where all segments of the corresponding RTSP contents of RTSP requests, and is sent to where STB
Peer nodes；Peer nodes where STB go out Flow Policy and choose from the Peer lists that Tracker is sent to deposit according to specified
It contains the Peer nodes of the RTSP contents and it is asked to go out stream；Flow data is returned to STB again to play.
Based on the above technical solution, the Tracker is internally provided with signal server, cache server sum number
According to library server；The Tracker carries out the transmission of RTSP redirecting signalings using signal server, is delayed using cache server
The complete RTSP contents of user's request are deposited, each Peer nodes and the RTSP of each Peer nodes storage are recorded using database server
The correspondence of content.
The present invention also provides a kind of P2P order methods based on RTSP using above system, this method includes following step
Suddenly：S1, client STB send out RTSP requests according to the content of user's program request to content source station；Peer nodes where S2, STB
The RTSP requests that STB is sent out are intercepted, and are redirected to Tracker；S3, Tracker judgement the requested contents of STB be for the first time by
During request, the URL of content source station is returned to STB using RTSP redirecting signalings and played out by Tracker；What S4, STB were played
Meanwhile Tracker sends out the request of on-demand content to content source station, and this is asked using the URL of RTSP requests intercepted
Corresponding complete RTSP contents are cached；S5, Tracker are according to specified cache policy from current all Peer nodes
At least one Peer nodes are selected, and the RTSP contents cached in step S4 are distributed to selection according to preset distribution rules
Peer nodes in stored；S6, each Peer nodes report Distribution Results to be arranged to Tracker, Tracker in preset Peer
Each Peer nodes and the correspondence of the RTSP contents of each Peer nodes storage are recorded in table；S7, when STB send out again it is identical
When RTSP is asked, the Peer nodes where STB intercept RTSP requests, and are redirected to Tracker；S8, Tracker are used
STB is redirected to the Peer nodes where STB by RTSP redirecting signalings, while Tracker is searched corresponding to RTSP requests
RTSP contents all segments where Peer lists, and be sent to the Peer nodes where STB；Peer where S9, STB
Node goes out Flow Policy and chooses from the Peer lists that Tracker is sent to be stored with the Peer nodes of the RTSP contents according to specified
And it is asked to go out stream；Flow data is returned to STB again to play.
Based on the above technical solution, in step S2 and S7, the Peer nodes where STB utilize preset abduction journey
Sequence intercepts the RTSP requests that STB is sent out.
Based on the above technical solution, in step S3, when the Tracker judgement requested contents of STB are not for the first time
When requested, step S7 is transferred to, is handled according to the process flow asked again.
Based on the above technical solution, in step S5, Tracker is by the RTSP contents of caching according to preset distribution
Rule is distributed to when being stored in the Peer nodes of selection, and each Peer nodes can store the part of same RTSP contents
Or all, different Peer nodes can store the segment of identical RTSP contents.
Based on the above technical solution, step S9 includes below scheme：Peer nodes where S901, STB from
In the Peer lists that Tracker is sent, go out Flow Policy and choose one or more to be stored with the RTSP contents according to specified
The Peer nodes of different fragments, and it is asked to go out stream；Peer nodes where S902, STB while receiving stream media content,
The splicing of the different fragments of RTSP contents is completed, and is returned to STB and plays out.
Based on the above technical solution, in step S902, the Peer nodes where STB complete the difference of RTSP contents
After the splicing of segment, can check splicing RTSP contents integrality after be returned to client again and play out.
Based on the above technical solution, in step S5, the content of cache policy and the content of distribution rules are wrapped
It includes：Storage idle capacity information, content information, number of concurrent information and the network bandwidth information of Peer nodes.
Based on the above technical solution, in step S5, the cache policy specified is the group of a variety of cache policies
It closes；The preset distribution rules are the combination of a variety of distribution rules.
The beneficial effects of the present invention are：
(1) present invention is asked, and be redirected to using the RTSP that the abduction program intercepts client on Peer nodes is sent out
Node administration dispatch server is realized that the scheduling of RTSP contents caches using node administration dispatch server, is broadcast without change
Device end is put, can realize P2P scheduling in user's unaware, user experience is good.
(2) caching of source station content is not single according to being stored in certain strategy distribution to several Peer nodes
Pure memory capacity and performance dependent on current Peer storage devices so that caching performance substantially enhances, and can not influence user
Caching and distribution are realized in the case of viewing, ensure that user's viewing quality.Meanwhile RTSP contents are stored in different Peer
On, it realizes a kind of distribution to RTSP contents and stores, can adequately utilize the memory space of each Peer, and effectively realize
The load balancing of Peer.
Description of the drawings
Fig. 1 is the structure diagram of the P2P VOD systems based on RTSP in the embodiment of the present invention；
Fig. 2 is the schematic diagram of interior joint management and dispatching server of embodiment of the present invention Tracker；
Fig. 3 is the flow chart of the P2P order methods based on RTSP in the embodiment of the present invention；
Fig. 4 is the exemplary plot that several Peer nodes store RTSP contents；
Fig. 5 is the exemplary plot of Peer lists.
Specific embodiment
Below in conjunction with the accompanying drawings and specific embodiment the present invention is described in further detail.
Shown in Figure 1, the embodiment of the present invention provides a kind of P2P VOD systems based on RTSP, which includes client
Hold (STB), content source station, node administration dispatch server (Tracker) and several Peer nodes, several Peer sections
Peer nodes in point there are one Peer nodes where the client.
Further, it is shown in Figure 2, in one embodiment, the node administration dispatch server (Tracker)
It is internally provided with signal server, cache server and database server.The node administration dispatch server (Tracker)
The transmission of RTSP redirecting signalings (i.e. 302 signalings of RTSP of standard) is carried out using signal server；Delayed using cache server
Deposit the complete RTSP contents of user's request；Each Peer nodes and the RTSP of each Peer nodes storage are recorded using database server
The correspondence of content.It is understood that in practical operation, the cache server and database server are alternatively not
(i.e. self-existent server is set the common server or equipment being arranged in node administration dispatch server (Tracker)
It is standby)；That is, realize the function of above-mentioned cache server and database server using common server or equipment.
Shown in Figure 3, the embodiment of the present invention also provides a kind of P2P program request sides based on RTSP using above system
Method, this method include the following steps：
Step S1, client (STB) sends out corresponding RTSP to content source station according to the content of user's program request and asks, and is transferred to
Step S2.For example, the RTSP request URLs according to corresponding to the content of user's program request are rtsp://srcip:srcport/
01.mp4。
Step S2, the Peer nodes where client (STB) are sent out using preset abduction program intercepts client (STB)
RTSP requests, and be redirected to node administration dispatch server (Tracker), be transferred to step S3.
For example, former request URL is rtsp://srcip:Srcport/01.mp4, the Peer nodes where client (STB)
Abduction program this URL is kidnapped, and using RTSP redirecting signalings (i.e. 302 signalings of RTSP of standard) replied：
Such as Location:"rtsp://trackerIP:trackerPortFvpxx=rtsp://srcip:srcport/01.mp4".
The URL that client (STB) is indicated using this Location initiates to ask again, according to trackerIP (node administration scheduling clothes
Business device IP) and trackerPort (node administration dispatch server port numbers) be redirected to node administration dispatch server
(Tracker)。
In practical operation, in step S2, the preset abduction program can pass through equipment (such as subscriber computer in Peer nodes
The equipment such as top box or intelligent gateway) on P2P plug-in units are installed in advance to realize.It is realized on Peer nodes using abduction program
The abduction of RTSP requests, can avoid client player from being changed for URL, without changing player end, so as in user
P2P scheduling is realized in the case of unaware, user experience is good.
Step S3, node administration dispatch server (Tracker) judges whether client (STB) requested content is first
It is secondary requested, if so, the URL of content source station is returned to using RTSP redirecting signalings (i.e. 302 signalings of RTSP of standard)
Client (STB)；Client (STB) then carries out normal play according to the URL of content source station, is transferred to step S4；If it is not, it is then transferred to
Step S7.
For example, node administration dispatch server (Tracker) receives request (rtsp://trackerIP:
trackerPortFvpxx=rtsp://srcip:It srcport/01.mp4, can be according to the URL of content source station in database after)
Corresponding contents are searched in server.If not finding corresponding contents, show client (STB) requested content be for the first time by
It asks (not being requested before, so not doing the caching of corresponding contents), then believes the URL of content source station RTSP 302
Order returns to client (STB), such as returns to RTSP 302Location:"rtsp://srcip:srcport/01.mp4"；Client
After end (STB) receives this reply, corresponding contents are got in content source station with this URL, carry out back source broadcasting.If it finds
Corresponding contents, it is not requested for the first time (be requested before, so doing to show client (STB) requested content
The caching of corresponding contents), then step S7 is transferred to, at the process flow (process flow cached) asked again
Reason.
Step S4, while client (STB) plays, node administration dispatch server (Tracker) utilizes what is intercepted
The URL of RTSP requests sends out the request of corresponding on-demand content to content source station, and the corresponding complete RTSP contents of the request are delayed
It is stored in cache server, as shown in Fig. 2, being transferred to step S5.
Step S5, node administration dispatch server (Tracker) according to specified cache policy from current all Peer
At least one Peer nodes are chosen in node, and the RTSP contents cached in step S4 are distributed to according to preset distribution rules
It is stored in the Peer nodes of selection；Each Peer nodes can store some or all of of same RTSP contents, no
The segment of identical RTSP contents can be stored with Peer nodes, is transferred to step S6.
It is understood that in step S5, the content of the cache policy includes but not limited to：The storage of Peer nodes is empty
Not busy capacity information, content information, number of concurrent information and network bandwidth information etc..Also, node administration dispatch server
(Tracker) when choosing at least one Peer nodes from current all Peer nodes according to specified cache policy, may be used also
It is chosen in a manner of being combined according to a variety of cache policies, i.e., the described cache policy specified is the group of a variety of cache policies
It closes.For example, a Peer node or the multiple Peer nodes of idle capacity maximum and number of concurrent minimum are chosen every time.Similarly,
The content of the distribution rules includes but not limited to：Storage idle capacity information, content information, the number of concurrent information of Peer nodes
And network bandwidth information etc..Node administration dispatch server (Tracker) is by the RTSP contents cached in step S4 according to pre-
If distribution rules be distributed to when being stored in the Peer nodes of selection, also can in a manner that a variety of distribution rules combine into
Row distribution, i.e., described preset distribution rules are the combination of a variety of distribution rules.
In addition, shown in Figure 4, each Peer nodes store RTSP contents, each Peer with the structure of class HLS files
Node can store some or all of of same RTSP contents, and different Peer nodes can store the piece of identical RTSP contents
Section.Such as file A-1.mp4, B-1.mp4 are stored on Peer-1；A-2.mp4, C-1.mp4 are stored on Peer-2；Peer-N
On store file X-N.mp4, Y-M.mp4 etc..
Step S6, each Peer nodes report Distribution Results to give node administration dispatch server (Tracker), node administration tune
Degree server (Tracker) records each Peer nodes and the RTSP contents of each Peer nodes storage in preset Peer lists
Correspondence is transferred to step S7.It is understood that in practical operation, the preset Peer lists are storable in database
In server, and Peer lists are the segments of perhaps different RTSP contents in that is, different RTSP using single content as granularity,
As different entries, as shown in Figure 5.Pass through Peer lists as shown in Figure 5, node administration dispatch server (Tracker)
It is known that Peer-1 nodes store the content of A-1.mp4 and B-1.mp4.
Step S7, when client (STB) sends out identical RTSP requests again (i.e. user by client (STB) again
During the RTSP contents that secondary program request has been cached), the Peer nodes where client (STB) utilize preset abduction program intercepts
The RTSP requests that client (STB) is sent out, and it is redirected to node administration dispatch server (Tracker).
Step S8, node administration dispatch server (Tracker) uses RTSP redirecting signalings (the i.e. RTSP 302 of standard
Signaling) client (STB) is redirected to the Peer nodes where client (STB)；Node administration dispatch server simultaneously
(Tracker) the Peer lists where all segments of the corresponding RTSP contents of RTSP requests are searched, and are sent to client
The Peer nodes where (STB) are held, are transferred to step S9.
Step S9, the Peer nodes where client (STB) are stored with according to the Peer lists of return selection in the RTSP
The Peer nodes of appearance simultaneously ask it to go out stream；Flow data is returned to client (STB) again to play out, is terminated.
Specifically, step S9 includes below scheme：
Step S901, the Peer nodes where client (STB) are sent from node administration dispatch server (Tracker)
In Peer lists, according to the specified Peer for going out Flow Policy and choosing one or more different fragments for being stored with the RTSP contents
Node, and it is asked to go out stream.
It is understood that in step S901, it is described go out Flow Policy content include but not limited to：The storage of Peer nodes
Idle capacity information, content information, number of concurrent information and network bandwidth information etc..Also, what this was specified go out Flow Policy can be with
For it is a variety of go out Flow Policy combination, such as：Choose the Peer nodes that idle capacity is maximum and Netowrk tape is roomy.
Step S902, the Peer nodes where client (STB) complete RTSP contents while receiving stream media content
Different fragments splicing, and be returned to client (STB) and play out.
Further, during practical operation, the Peer nodes in step S902 where client (STB) complete RTSP contents
Different fragments splicing after, can check splicing RTSP contents integrality after be returned to client again and play out.
For example, when user asks to play A.MP4, the Peer nodes where client (STB) will be from Peer-2 and other storages
Have and streaming medium content is pulled on the Peer nodes of A.MP4 associated clips, complete to splice simultaneously checked for integrity and then return to visitor
Family end (STB) plays.
The P2P order methods based on RTSP of the present invention utilize the abduction program on Peer nodes when realizing P2P program requests
The RTSP requests that client is sent out are intercepted, and are redirected to node administration dispatch server, utilize node administration dispatch server
Come realize the scheduling of RTSP contents cache, without changing player end, can in the case that user's unaware realize P2P scheduling；And
And the caching of source station content does not depend on merely according to being stored in certain strategy distribution to several Peer nodes
The memory capacity and performance of current Peer storage devices so that caching performance substantially enhances, can be in the feelings for not influencing user's viewing
Caching and distribution are realized under condition, ensure that user's viewing quality.Meanwhile be stored in RTSP contents on different Peer, it realizes
A kind of distribution to RTSP contents stores, and can adequately utilize the memory space of each Peer, and effectively realizes Peer's
Load balancing.
The present invention is not limited to the above-described embodiments, for those skilled in the art, is not departing from
Under the premise of the principle of the invention, several improvements and modifications can also be made, these improvements and modifications are also considered as the protection of the present invention
Within the scope of.
The content not being described in detail in this specification belongs to the prior art well known to professional and technical personnel in the field.
Claims (10)
1. a kind of P2P VOD systems based on RTSP, it is characterised in that：The system includes client STB, content source station, node
Management and dispatching server Tracker and several Peer nodes there are one Peer nodes are STB in several Peer nodes
The Peer nodes at place；
STB sends out RTSP requests according to the content of user's program request to content source station；Peer nodes where STB intercept the RTSP please
It asks, and is redirected to Tracker；When the Tracker judgement requested contents of STB are requested for the first time, Tracker uses RTSP
The URL of content source station is returned to STB and played out by redirecting signaling；
While STB is played, Tracker sends out asking for on-demand content using the URL of RTSP requests intercepted to content source station
It asks, and the corresponding complete RTSP contents of the request is cached；Tracker is according to specified cache policy from current all
At least one Peer nodes are chosen in Peer nodes, and the RTSP contents of caching are distributed to selection according to preset distribution rules
Peer nodes in stored；Each Peer nodes report Distribution Results, and to Tracker, Tracker is in preset Peer lists
It is middle to record each Peer nodes and the correspondence of the RTSP contents of each Peer nodes storage；
When STB sends out identical RTSP requests again, the Peer nodes where STB intercept RTSP requests, and are redirected to
Tracker；STB is redirected to the Peer nodes where STB using RTSP redirecting signalings by Tracker, while Tracker is looked into
Peer lists where all segments for the RTSP contents for looking for RTSP requests corresponding, and it is sent to the Peer sections where STB
Point；Peer nodes where STB go out Flow Policy and choose from the Peer lists that Tracker is sent to be stored with this according to specified
The Peer nodes of RTSP contents simultaneously ask it to go out stream；Flow data is returned to STB again to play.
2. the P2P VOD systems based on RTSP as described in claim 1, it is characterised in that：The Tracker is internally provided with
Signal server, cache server and database server；The Tracker carries out RTSP using signal server and redirects letter
The transmission of order, the complete RTSP contents asked using cache server cache user, each Peer is recorded using database server
Node and the correspondence of the RTSP contents of each Peer nodes storage.
3. a kind of P2P order methods based on RTSP using system described in claim 1, which is characterized in that this method includes
Following steps：
S1, client STB send out RTSP requests according to the content of user's program request to content source station；
Peer nodes where S2, STB intercept the RTSP requests that STB is sent out, and are redirected to Tracker；
When S3, Tracker judgement requested contents of STB are requested for the first time, Tracker is using RTSP redirecting signalings by
The URL of appearance source station returns to STB and plays out；
While S4, STB are played, Tracker sends out on-demand content using the URL of RTSP requests intercepted to content source station
Request, and the corresponding complete RTSP contents of the request are cached；
S5, Tracker select at least one Peer nodes according to specified cache policy from current all Peer nodes,
And the RTSP contents cached in step S4 are distributed to according to preset distribution rules in the Peer nodes of selection and are stored；
S6, each Peer nodes report Distribution Results to Tracker, and Tracker records each Peer sections in preset Peer lists
The correspondence of RTSP contents that point is stored with each Peer nodes；
S7, when STB sends out identical RTSP requests again, the Peer nodes where STB intercept RTSP requests, and redirect
To Tracker；
STB is redirected to the Peer nodes where STB using RTSP redirecting signalings by S8, Tracker, while Tracker is looked into
Peer lists where all segments for the RTSP contents for looking for RTSP requests corresponding, and it is sent to the Peer sections where STB
Point；
Peer nodes where S9, STB go out Flow Policy and choose from the Peer lists that Tracker is sent to be stored with according to specified
The Peer nodes of the RTSP contents simultaneously ask it to go out stream；Flow data is returned to STB again to play.
4. the P2P order methods based on RTSP as claimed in claim 3, it is characterised in that：In step S2 and S7, where STB
The RTSP that is sent out using preset abduction program intercepts STB of Peer nodes ask.
5. the P2P order methods based on RTSP as claimed in claim 3, it is characterised in that：In step S3, when Tracker sentences
When to determine the requested contents of STB be not requested for the first time, step S7 is transferred to, is handled according to the process flow asked again.
6. the P2P order methods based on RTSP as claimed in claim 3, it is characterised in that：In step S5, Tracker will delay
The RTSP contents deposited are distributed to according to preset distribution rules when being stored in the Peer nodes of selection, and each Peer nodes can
To store some or all of of same RTSP contents, different Peer nodes can store the segment of identical RTSP contents.
7. the P2P order methods based on RTSP as claimed in claim 3, which is characterized in that step S9 includes below scheme：
Peer nodes where S901, STB choose one from the Peer lists that Tracker is sent, according to the specified Flow Policy that goes out
The Peer nodes of a or multiple different fragments for being stored with the RTSP contents, and it is asked to go out stream；
Peer nodes where S902, STB complete the spelling of the different fragments of RTSP contents while receiving stream media content
It connects, and is returned to STB and plays out.
8. the P2P order methods based on RTSP as claimed in claim 7, it is characterised in that：In step S902, where STB
Peer nodes complete RTSP contents different fragments splicing after, can check splicing RTSP contents integrality after returned again
It is played out back to client.
9. the P2P order methods based on RTSP as described in any one of claim 3 to 8, it is characterised in that：In step S5,
The content of cache policy and the content of distribution rules include：The storage idle capacity information of Peer nodes, content information, simultaneously
Send out number information and network bandwidth information.
10. the P2P order methods based on RTSP as described in any one of claim 3 to 8, it is characterised in that：In step S5,
The cache policy specified is the combination of a variety of cache policies；The preset distribution rules are the group of a variety of distribution rules
It closes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711324332.5A CN108270845A (en) | 2017-12-13 | 2017-12-13 | A kind of P2P VOD systems and method based on RTSP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711324332.5A CN108270845A (en) | 2017-12-13 | 2017-12-13 | A kind of P2P VOD systems and method based on RTSP |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108270845A true CN108270845A (en) | 2018-07-10 |
Family
ID=62771930
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711324332.5A Pending CN108270845A (en) | 2017-12-13 | 2017-12-13 | A kind of P2P VOD systems and method based on RTSP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108270845A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112822510A (en) * | 2020-12-30 | 2021-05-18 | 深圳市亿联智能有限公司 | Content distribution acceleration method of intelligent set top box |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080183641A1 (en) * | 2007-01-25 | 2008-07-31 | Chang Bin Tang | Generalized application virtualization method for business use on the web and the mini server using this method |
| CN101534326A (en) * | 2009-04-21 | 2009-09-16 | 华为技术有限公司 | An access method, a device and a system for an RTSP terminal |
| CN101699860A (en) * | 2009-10-21 | 2010-04-28 | 南京邮电大学 | Implement method for mixing network TV stream media server of peer-to-peer computing network |
| CN101742238A (en) * | 2008-11-26 | 2010-06-16 | 深圳市彪骐数码科技有限公司 | Streaming media on-demand method and device combining RTS with P2P |
| EP2618539B1 (en) * | 2009-07-01 | 2015-02-18 | Huawei Technologies Co., Ltd. | Method, system, and proxy node for P2P streaming media data distribution |
| CN106789956A (en) * | 2016-12-01 | 2017-05-31 | 武汉市烽视威科技有限公司 | A kind of P2P order methods and system based on HLS |
-
2017
- 2017-12-13 CN CN201711324332.5A patent/CN108270845A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080183641A1 (en) * | 2007-01-25 | 2008-07-31 | Chang Bin Tang | Generalized application virtualization method for business use on the web and the mini server using this method |
| CN101742238A (en) * | 2008-11-26 | 2010-06-16 | 深圳市彪骐数码科技有限公司 | Streaming media on-demand method and device combining RTS with P2P |
| CN101534326A (en) * | 2009-04-21 | 2009-09-16 | 华为技术有限公司 | An access method, a device and a system for an RTSP terminal |
| EP2618539B1 (en) * | 2009-07-01 | 2015-02-18 | Huawei Technologies Co., Ltd. | Method, system, and proxy node for P2P streaming media data distribution |
| CN101699860A (en) * | 2009-10-21 | 2010-04-28 | 南京邮电大学 | Implement method for mixing network TV stream media server of peer-to-peer computing network |
| CN106789956A (en) * | 2016-12-01 | 2017-05-31 | 武汉市烽视威科技有限公司 | A kind of P2P order methods and system based on HLS |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112822510A (en) * | 2020-12-30 | 2021-05-18 | 深圳市亿联智能有限公司 | Content distribution acceleration method of intelligent set top box |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11539768B2 (en) | System and method of minimizing network bandwidth retrieved from an external network | |
| US10218806B2 (en) | Handling long-tail content in a content delivery network (CDN) | |
| EP2288085B1 (en) | P2p based method, device and system for playing media | |
| US20210368239A1 (en) | Distributing method, system, edge node, and central scheduling system for streaming media resource | |
| CN107707926A (en) | A kind of live TV stream transmission method, device and system | |
| KR20100105679A (en) | Method for distributing content data packages originated by users of a super peer-to-peer network | |
| US20060005224A1 (en) | Technique for cooperative distribution of video content | |
| CN104301741A (en) | Data live broadcast system and method | |
| CN107835437A (en) | Dispatching method and device based on more caching servers | |
| JP2013516854A (en) | Edge content distribution device and content distribution network for IPTV system | |
| US12250254B2 (en) | System and method of minimizing network bandwidth retrieved from an external network | |
| JP3964751B2 (en) | Network quality estimation control method | |
| CN107317809A (en) | A kind of information centre's Multi-Layer Networks time video media system and its application method | |
| Noh et al. | Progressive caching system for video streaming services over content centric network | |
| CN108270845A (en) | A kind of P2P VOD systems and method based on RTSP | |
| Sakashita et al. | A data reception method to reduce interruption time in P2P streaming environments | |
| Ku et al. | Adaptive cache deploying architecture using big-data framework for CDN | |
| Fouda et al. | A novel P2P VoD streaming technique integrating localization and congestion awareness strategies | |
| Alubady et al. | The role of management techniques for high-performance pending interest table: A survey | |
| Okada et al. | A color-based cooperative caching strategy for time-shifted live video streaming | |
| CN100559870C (en) | Video-on-demand system and method for realizing data deployment of the system | |
| Satsiou et al. | Efficient caching of video content to an architecture of proxies according to a frequency-based cache management policy | |
| CN102571842B (en) | Memory content deletion method, system and equipment | |
| Lei et al. | NDN-Hippo: A streaming media system over named data networking | |
| Abd-Elrahman et al. | Optimization of quality of experience through file duplication in video sharing servers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180710 |
|
| RJ01 | Rejection of invention patent application after publication |