CN113727138A - HLS intranet source returning method - Google Patents
HLS intranet source returning method Download PDFInfo
- Publication number
- CN113727138A CN113727138A CN202111013451.5A CN202111013451A CN113727138A CN 113727138 A CN113727138 A CN 113727138A CN 202111013451 A CN202111013451 A CN 202111013451A CN 113727138 A CN113727138 A CN 113727138A
- Authority
- CN
- China
- Prior art keywords
- resource
- connection pool
- node
- connection
- tuple
- 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.)
- Withdrawn
Links
Images
Classifications
-
- 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/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- 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/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
- H04N21/23103—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion using load balancing strategies, e.g. by placing or distributing content on different disks, different memories or different servers
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an HLS intranet back-source method, which comprises the following steps: s1: the client sends a resource acquisition request to the edge node, the edge node forwards the request to a dispatching center, and the dispatching center sends a resource address to the edge node; s2: the edge node sends the resource address to the connection pool and matches the tuple information in the connection pool; s3: the connection pool tuple transfers the request information with the resource address to the resource node for matching; s4: the corresponding resource node sends the resource data to the connection pool; s5: and sending the resource data to the edge node through the connection pool, and returning the resource data to the client by the edge node. The connection between the inner domain network and the external network is realized by arranging the edge nodes, and the resource data is uniformly transmitted inside and outside through the edge nodes, so that the inner domain network resources are safer. Meanwhile, the edge nodes also have a storage function, so that the loads of the dispatching center and the resource nodes are reduced.
Description
Technical Field
The invention relates to the technical field of wireless communication, in particular to an HLS intranet return source method.
Background
The back source is a means for the client to obtain the resource, the existing method is that the client directly requests the scheduling center to obtain the address of the resource node, and the client initiates a request to the corresponding resource node according to the address of the resource node and pulls the resource.
However, the above resource acquisition method has the following disadvantages: 1, a scheduling center directly provides service to an external client side and has a load problem; 2, the resource node directly provides service to an external client, so that the safety problem exists; and 3, any resource is requested to request a scheduling server first, and the actual resource address is taken by a scheduling center, so that the resource link is too long and the delay is large.
Disclosure of Invention
The invention aims to provide an HLS intranet back-source method, which is used for solving the technical problems in the background technology.
The technical scheme of the invention is that an HLS intranet back-source method comprises the following steps:
s1: the client sends a resource acquisition request to the edge node, the edge node forwards the request to a dispatching center, and the dispatching center sends a resource address to the edge node;
s2: the edge node sends the resource address to a connection pool and matches the tuple information in the connection pool, the connection pool realizes the link connection between the edge node and the resource node, and the connection pool and the edge node have the function of storing the resource and can be directly called according to the resource address;
s3: the connection pool tuple transfers the request information with the resource address to the resource node for matching, and the request information is matched to the corresponding resource node through the resource address;
s4: the corresponding resource node sends the resource data to the connection pool and adds the resource data to the tuple information;
s5: and sending the resource data to the edge node through the connection pool, and returning the resource data to the client by the edge node.
In a preferred embodiment, the resource addresses are provided with flow ids for matching specific resource nodes, one for each resource node.
In a preferred embodiment, the construction process of the connection pool is as follows:
a1: establishing a database connection pool object;
a2, creating an initial number of database connections according to the maximum connection number specified in advance;
a3, creating a connection pool tuple according to the resource request data;
a4, establishing the connection of the connection pool with the edge node and the resource node.
In a preferred embodiment, a new connection pool tuple is created in a3 if there is no free connection tuple in the connection pool and the number of connection pool tuples is not maximized.
In a preferred embodiment, the connection pool tuple creation and resource calling process is:
b1: creating an initial connection pool tuple and setting the maximum connection number;
b2: storing resource data returned by the resource nodes, and only storing newly-increased resource information in the connection pool tuples until the storage quantity of the connection pool tuples reaches the maximum connection quantity, and establishing new connection pool tuples in the connection pool;
b3: the system firstly searches whether the connection pool tuple contains matched resource data or not according to the stream id in the resource address, if the matched resource data exists, the system is directly called, and if the matched resource data does not exist, the system further matches the resource data in the resource node and simultaneously stores the resource data in the connection pool tuple.
In a preferred embodiment, the edge node stores resource address information requested by the dispatching center.
The technical scheme of the invention has the beneficial effects that:
1. the connection between the inner domain network and the external network is realized by arranging the edge nodes, and the resource data is uniformly transmitted inside and outside through the edge nodes, so that the inner domain network resources are safer. Meanwhile, the edge nodes also have a storage function, so that the loads of the dispatching center and the resource nodes are reduced.
2. The link connection between the edge node and the resource node is realized by setting the connection pool, and the resource data stored in the connection pool can be directly called, so that the load of the resource node is further reduced, the time consumption of the link is reduced, and the resource calling rate is improved.
Drawings
Figure 1 is an overall flow chart of the present invention,
FIG. 2 is a diagram of the HLS intranet feed-back procedure of the present invention,
FIG. 3 is a flow chart of the construction of the connection pool according to the present invention,
FIG. 4 is a flow chart of connection pool tuple creation and resource invocation in accordance with the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments. The embodiments of the present invention have been presented for purposes of illustration and description, and are not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
The noun explains: returning a source: when the edge node does not find the resources requested by the client in the connection pool, initiating a request to the resource node, and pulling the resources; edge nodes: a node directly requested by a client; connecting the tanks: a pre-connection mechanism, which realizes the connection between edge nodes and resource nodes; the dispatching center: the resource management server records the storage positions of all resources; stream id, the unique identification of the video stream.
Referring to fig. 1-4, the HLS intranet back-source method according to the technical scheme of the present invention includes the following specific processes:
the client sends a resource acquisition request to the edge node, the edge node forwards the request to the dispatching center, and the dispatching center sends a resource address to the edge node. The edge node stores the resource address information requested by the dispatching center, and when the requested resource address is stored in the edge node, the resource address does not need to be acquired from the dispatching center, and the resource calling can be directly carried out through the edge node.
The edge node sends the resource address to the connection pool and matches the tuple information in the connection pool, the connection pool realizes the link connection between the edge node and the resource node, and the connection pool has the function of storing the resource and can be directly called according to the resource address. If the tuple information (here, the tuple information is resource storage information in the connection pool tuple hereinafter) contains the call resource, the resource is directly returned to the client through the edge node, and if the resource does not exist, the step S3 is continued.
The connection pool tuple transfers the request information with the resource address to the resource node for matching, and the request information is matched to the corresponding resource node through the resource address. Each resource address can be matched to a unique corresponding resource node because the resource address carries a flow id for matching a particular resource node, one for each resource node.
And the corresponding resource node sends the resource data to the connection pool and adds the resource data to the tuple information. The corresponding resource node is the node which requests to contain the requested resource data.
And sending the resource data to the edge node through the connection pool, and returning the resource data to the client by the edge node.
The connection between the inner domain network and the external network is realized by arranging the edge nodes, and the resource data is uniformly transmitted inside and outside through the edge nodes, so that the inner domain network resources are safer. Meanwhile, the edge nodes also have a storage function, so that the loads of the dispatching center and the resource nodes are reduced.
The link connection between the edge node and the resource node is realized by setting the connection pool, and the resource data stored in the connection pool can be directly called, so that the load of the resource node is further reduced, the time consumption of the link is reduced, and the resource calling rate is improved.
In a preferred embodiment, the construction process of the connection pool is as follows: a1: establishing a database connection pool object; a2, creating an initial number of database connections according to the maximum connection number specified in advance; a3, creating a connection pool tuple according to the resource request data; a4, establishing the connection of the connection pool with the edge node and the resource node.
In a preferred embodiment, a new connection pool tuple is created in a3 if there is no free connection tuple in the connection pool and the number of connection pool tuples is not maximized. Each connection pool tuple stores different resource data.
In a preferred embodiment, the connection pool tuple creation and resource calling process is:
b1: creating an initial connection pool tuple and setting the maximum connection number;
b2: storing resource data returned by the resource nodes, and only storing newly-increased resource information in the connection pool tuples until the storage quantity of the connection pool tuples reaches the maximum connection quantity, and establishing new connection pool tuples in the connection pool;
b3: the system firstly searches whether the connection pool tuple contains matched resource data or not according to the stream id in the resource address, if the matched resource data exists, the system is directly called, and if the matched resource data does not exist, the system further matches the resource data in the resource node and simultaneously stores the resource data in the connection pool tuple.
It is to be understood that the described embodiments are merely a few embodiments of the invention, and not all embodiments. All other embodiments, which can be derived by one of ordinary skill in the art and related arts based on the embodiments of the present invention without any creative effort, shall fall within the protection scope of the present invention. Structures, devices, and methods of operation not specifically described or illustrated herein are generally practiced in the art without specific recitation or limitation.
Claims (6)
1. An HLS intranet back-source method is characterized by comprising the following steps:
s1: the client sends a resource acquisition request to the edge node, the edge node forwards the request to a dispatching center, and the dispatching center sends a resource address to the edge node;
s2: the edge node sends the resource address to a connection pool and matches the tuple information in the connection pool, the connection pool realizes the link connection between the edge node and the resource node, and the connection pool and the edge node have the function of storing the resource and can be directly called according to the resource address;
s3: the connection pool tuple transfers the request information with the resource address to the resource node for matching, and the request information is matched to the corresponding resource node through the resource address;
s4: the corresponding resource node sends the resource data to the connection pool and adds the resource data to the tuple information;
s5: and sending the resource data to the edge node through the connection pool, and returning the resource data to the client by the edge node.
2. The HLS intranet back-source method according to claim 1, wherein the resource addresses are provided with stream ids for matching specific resource nodes, and each resource node corresponds to one stream id.
3. The HLS intranet back-source method according to claim 2, wherein the construction process of the connection pool is as follows:
a1: establishing a database connection pool object;
a2, creating an initial number of database connections according to the maximum connection number specified in advance;
a3, creating a connection pool tuple according to the resource request data;
a4, establishing the connection of the connection pool with the edge node and the resource node.
4. The HLS intranet feed-back method according to claim 3, wherein if there is no free connection tuple in the connection pool in A3 and the number of connection pool tuples does not reach the maximum, a new connection pool tuple is created.
5. The HLS intranet back-source method according to claim 3, wherein the connection pool tuple creation and resource calling process is as follows:
b1: creating an initial connection pool tuple and setting the maximum connection number;
b2: storing resource data returned by the resource nodes, and only storing newly-increased resource information in the connection pool tuples until the storage quantity of the connection pool tuples reaches the maximum connection quantity, and establishing new connection pool tuples in the connection pool;
b3: the system firstly searches whether the connection pool tuple contains matched resource data or not according to the stream id in the resource address, if the matched resource data exists, the system is directly called, and if the matched resource data does not exist, the system further matches the resource data in the resource node and simultaneously stores the resource data in the connection pool tuple.
6. The HLS intranet back-source method according to claim 1, wherein the edge node stores resource address information requested by a scheduling center.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111013451.5A CN113727138A (en) | 2021-08-31 | 2021-08-31 | HLS intranet source returning method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111013451.5A CN113727138A (en) | 2021-08-31 | 2021-08-31 | HLS intranet source returning method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113727138A true CN113727138A (en) | 2021-11-30 |
Family
ID=78679868
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111013451.5A Withdrawn CN113727138A (en) | 2021-08-31 | 2021-08-31 | HLS intranet source returning method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113727138A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114268799A (en) * | 2021-12-23 | 2022-04-01 | 杭州阿启视科技有限公司 | Streaming media transmission method and device, electronic equipment and medium |
-
2021
- 2021-08-31 CN CN202111013451.5A patent/CN113727138A/en not_active Withdrawn
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114268799A (en) * | 2021-12-23 | 2022-04-01 | 杭州阿启视科技有限公司 | Streaming media transmission method and device, electronic equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103780679B (en) | Long delay remote invocation method based on http protocol | |
| CN112788074B (en) | Data transmitting method, processing method, receiving method, apparatus thereof, and storage medium | |
| CN109189856A (en) | Distributed data base service management, device, server and storage medium | |
| CN110109766B (en) | Data interaction method and device based on cross-department and cross-platform data sharing exchange | |
| CN111901705B (en) | OMCI function virtualization system of OLT equipment | |
| CN107528891B (en) | Websocket-based automatic clustering method and system | |
| KR20070016040A (en) | A system server for data communication with multiple clients and a data processing method | |
| CN103795569A (en) | Server connection method and device based on connection pool | |
| CN103812838A (en) | Service calling method and device and system | |
| WO2016127612A1 (en) | Monitoring processing method and device | |
| CN102891768A (en) | Method and network element for network management | |
| WO2018000653A1 (en) | Information processing method for m2m application, cse and ae | |
| CN105635083A (en) | Service processing method and service processing system based on server and client architecture | |
| CN104836839A (en) | Universal user self-defining session system and session management method thereof | |
| CN102694824B (en) | User data storage system and data access method thereof | |
| CN105471700B (en) | A kind of methods, devices and systems of Message Processing | |
| CN109976924A (en) | Interface call method and device | |
| CN111343286A (en) | Network access system and network access method | |
| CN112565220A (en) | HTTP service gateway implementation method based on state network isolation device safety | |
| CN110417876B (en) | Session method, node server in distributed system and master control equipment | |
| US11777852B1 (en) | System and method for web service atomic transaction (WS-AT) affinity routing | |
| CN113727138A (en) | HLS intranet source returning method | |
| CN101778131A (en) | Data synchronization system | |
| CN108259605B (en) | Data calling system and method based on multiple data centers | |
| CN101789963A (en) | Data synchronization system |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20211130 |