HLS intranet back-to-source method

Abstract

The invention discloses an HLS intranet back-to-source method, which comprises the following steps: S1, a client sends a resource acquisition request to an edge node, the edge node forwards the request to a scheduling center, and the scheduling center sends a resource address to the edge node; S2, the edge node sends the resource address to the connection pool and matches the resource address with tuple information in the connection pool; S3, the connection pool tuple forwards 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; and S5, the resource data are sent to the edge node through the connection pool, and the resource data are returned to the client by the edge node. The connection between the internal network and the external network is realized by setting the edge node, and the resource data are uniformly transmitted internally and externally through the edge node, so that the internal network resources are safer. And meanwhile, the edge node also has a storage function, so that the load of the dispatching center and the resource node is reduced.

Description

technical field [0001] The present invention relates to the technical field of wireless communication, and more specifically, relates to a method for back-to-source in an HLS intranet. Background technique [0002] Back-to-source is a means for the client to obtain resources. The existing method is that the client directly requests the dispatch 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. [0003] However, the above resource acquisition method has the following defects: 1. The scheduling center directly provides services to external clients, and there is a load problem; 2. Resource nodes directly provide services to external clients, and there are security issues; 3. To request any resource, you need to request the scheduling server first. , the actual resource address is obtained through the dispatch center, resulting in too long ...

AI Technical Summary

Problems solved by technology

[0003] However, the above resource acquisition method has the following defects: 1. The scheduling center directly provides services to external clients, and there is a load problem; 2. Resource nodes directly provide services to external clients, and there are security issues; 3. To request any resource, you need to request the scheduling server first. , the actual resource address is obtained through the dispatch center, resulting in too long resource links and large delays

Images