CN111262931A - Media resource deployment system, method, device, storage medium and processor - Google Patents

Media resource deployment system, method, device, storage medium and processor Download PDF

Info

Publication number
CN111262931A
CN111262931A CN202010044151.2A CN202010044151A CN111262931A CN 111262931 A CN111262931 A CN 111262931A CN 202010044151 A CN202010044151 A CN 202010044151A CN 111262931 A CN111262931 A CN 111262931A
Authority
CN
China
Prior art keywords
client
cloud server
private cloud
target
public cloud
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
Application number
CN202010044151.2A
Other languages
Chinese (zh)
Inventor
朱玉荣
刘洪献
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Anhui Wenxiang Information Technology Co Ltd
Original Assignee
Anhui Wenxiang Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Anhui Wenxiang Information Technology Co Ltd filed Critical Anhui Wenxiang Information Technology Co Ltd
Priority to CN202010044151.2A priority Critical patent/CN111262931A/en
Publication of CN111262931A publication Critical patent/CN111262931A/en
Withdrawn legal-status Critical Current

Links

Images

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/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
    • 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
    • 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
    • H04L67/61—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 taking into account QoS or priority requirements
    • 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/52—Network services specially adapted for the location of the user terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application discloses a media resource deployment system, a method, a device, a storage medium and a processor. The public cloud servers in the public cloud server cluster and the private cloud servers in the private cloud server cluster can be distributed by the scheduling system to transmit media resource data with the client according to requirements, so that connection with the MCU is not needed, and limitation of MCU port resources on data transmission is avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.

Description

Media resource deployment system, method, device, storage medium and processor
Technical Field
The present application relates to the internet field, and in particular, to a system, a method, an apparatus, a storage medium, and a processor for deploying a media resource.
Background
Currently, the transmission of media resources is usually handled by a Multipoint Control Unit (MCU), and each client is connected to the same MCU. However, the MCU has inherent physical bottleneck, for example, only 32-way or 64-way media resources can be provided, and it is difficult to meet the actual demand of a large number of clients for media resources distributed in a wide range due to insufficient port resources. When the MCU has no idle port resource, the client can only wait for the MCU port resource to appear idle again and then can carry out connection for data transmission, thus bringing great inconvenience to the user of the client, lacking flexibility and having long waiting time.
Furthermore, some organizations, such as schools, businesses, etc., often do not want to share their internal important resources to the outside world. Therefore, it is also important to ensure the security and privacy of the resources when media resources are transmitted.
Disclosure of Invention
Based on the above problems, the present application provides a system, a method, a device, a storage medium, and a processor for deploying media resources, which not only solve the problem of limited media resource transmission, but also ensure the security and privacy of the resources.
The embodiment of the application discloses the following technical scheme:
in a first aspect, the present application provides a media resource deployment system, including: the system comprises a global scheduling system, a public cloud server cluster and a private cloud server cluster, wherein the private cloud server cluster is deployed in a local area network; a public cloud server in the public cloud server cluster and a private cloud server in the private cloud server cluster are respectively in communication connection with the global scheduling system; the public cloud server cluster is in communication connection with the private cloud server cluster;
the global scheduling system is used for allocating a target public cloud server for a public cloud client from the public cloud server cluster or allocating a first target private cloud server for the public cloud client from the private cloud server cluster, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
the global scheduling system is further configured to allocate a second target private cloud server to the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the second target private cloud server.
Optionally, the global scheduling system is further configured to determine whether the public cloud client meets a preset sharing condition according to the location information or the IP of the public cloud client, and if so, allow the public cloud client to obtain the shared resource of the private cloud server cluster; and if not, forbidding the public cloud client to obtain the shared resources of the private cloud server cluster.
Optionally, the global scheduling system is further configured to obtain identification information of the private cloud client;
the global scheduling system is specifically configured to schedule the private cloud client to a server cluster in the private cloud server cluster that is matched with the identification information.
In a second aspect, the present application provides a media resource deployment system, comprising: the system comprises a first scheduling system, a second scheduling system, a public cloud server cluster and a private cloud server cluster, wherein the private cloud server cluster is deployed in a local area network; a public cloud server in the public cloud server cluster is in communication connection with the first scheduling system, and a private cloud server in the private cloud server cluster is in communication connection with the second scheduling system;
the first scheduling system is used for allocating a target public cloud server for a public cloud client from the public cloud server cluster so that the public cloud client can transmit media resource data by using the target public cloud server;
the second scheduling system is used for allocating a target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the target private cloud server.
In a third aspect, the present application provides a media resource deployment method, including:
judging whether the connected client is a public cloud client or a private cloud client;
for a public cloud client, allocating a target public cloud server for the public cloud client from a public cloud server cluster, or allocating a first target private cloud server for the public cloud client from a private cloud server cluster, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
and for the private cloud client, distributing a second target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the second target private cloud server.
Optionally, the method further comprises:
judging whether the public cloud client meets a preset sharing condition or not according to the position information or the IP of the public cloud client, and if so, sending an instruction allowing the public cloud client to obtain the shared resources of the private cloud server cluster to the target public cloud server or the first target private cloud server; and otherwise, sending an instruction for forbidding the public cloud client to obtain the shared resources of the private cloud server cluster to the target public cloud server or the first target private cloud server.
Optionally, the method further comprises:
obtaining identification information of the private cloud client;
the allocating a second target private cloud server for the private cloud client from the private cloud server cluster specifically includes:
scheduling the private cloud client to a server cluster matched with the identification information in the private cloud server cluster; and distributing the second target private cloud server for the private cloud client from the server cluster matched with the identification information.
In a fourth aspect, the present application provides a media resource deployment method, including:
judging whether the connected client is a public cloud client or a private cloud client;
for a public cloud client, distributing a target public cloud server for the public cloud client from a public cloud server cluster, so that the public cloud client transmits media resource data by using the target public cloud server;
and for the private cloud client, distributing a target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the target private cloud server.
In a fifth aspect, the present application provides a media resource deployment apparatus, including:
the judging module is used for judging whether the connected client is a public cloud client or a private cloud client;
the first distribution module is used for distributing a target public cloud server for the public cloud client from a public cloud server cluster or distributing a first target private cloud server for the public cloud client from a private cloud server cluster when the connected client is judged to be the public cloud client by the judgment module, so that the public cloud client utilizes the first target public cloud server or the target private cloud server to transmit media resource data;
and the second allocating module is used for allocating a second target private cloud server for the private cloud client from the private cloud server cluster when the connected client is judged to be the private cloud client by the judging module, so that the private cloud client transmits the media resource data by using the second target private cloud server.
In a sixth aspect, the present application provides a media resource deployment apparatus, including:
the judging module is used for judging whether the connected client is a public cloud client or a private cloud client;
the first distribution module is used for distributing a target public cloud server for the public cloud client from a public cloud server cluster when the connected client is judged to be the public cloud client by the judgment module so as to enable the public cloud client to transmit media resource data by using the target public cloud server;
and the second distribution module is used for distributing a target private cloud server for the private cloud client from the private cloud server cluster when the judgment module judges that the connected client is the private cloud client, so that the private cloud client utilizes the target private cloud server to transmit media resource data.
In a seventh aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, and when the program is executed by a processor, the media resource deployment method provided in the foregoing third or fourth aspect is implemented.
In an eighth aspect, the present application provides a processor for executing a computer program, where the program when executed performs the media resource deployment method provided in the foregoing third aspect or fourth aspect.
Compared with the prior art, the method has the following beneficial effects:
the present application provides a media resource deployment system, comprising: the system comprises a global scheduling system, a public cloud server cluster and a private cloud server cluster, wherein the private cloud server cluster is deployed in a local area network. In the media resource deployment system, the private cloud server cluster does not have an independent scheduling system, but the public cloud server cluster and the private cloud server cluster share a global scheduling system. The global scheduling system is used for allocating a target public cloud server for a public cloud client from a public cloud server cluster or allocating a first target private cloud server for the public cloud client from a private cloud server cluster so that the public cloud client can transmit media resource data by using the first target public cloud server or the target private cloud server; the global scheduling system is further configured to allocate a second target private cloud server to the private cloud client from the private cloud server cluster, so that the private cloud client transmits the media resource data by using the second target private cloud server.
The application provides another media resource deployment system which comprises a first scheduling system, a second scheduling system, a public cloud server cluster and a private cloud server cluster, wherein the private cloud server cluster is deployed in a local area network. The first scheduling system is a public cloud server cluster independent scheduling system, and the second scheduling system is a private cloud server cluster independent scheduling system. The first scheduling system is used for allocating a target public cloud server for the public cloud client from the public cloud server cluster so that the public cloud client can transmit media resource data by using the target public cloud server; and the second scheduling system is used for allocating the target private cloud server for the private cloud client from the private cloud server cluster so that the private cloud client transmits the media resource data by using the target private cloud server.
In the technical scheme provided by the application, the public cloud server in the public cloud server cluster and the private cloud server in the private cloud server cluster can be allocated by the scheduling system (whether the scheduling system is a global scheduling system or an independent scheduling system) so as to transmit media resource data with the client according to requirements, so that connection with the MCU is not required, and limitation of MCU port resources on data transmission is avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.
In addition, the application also correspondingly provides a media resource deployment method, a device, a storage medium and a processor.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic structural diagram of a media resource deployment system according to an embodiment of the present application;
fig. 2 is a schematic diagram illustrating a data transmission flow of a media resource according to an embodiment of the present application;
fig. 3 is a flowchart of a media resource deployment method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a media resource deployment apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another media resource deployment system according to an embodiment of the present application;
fig. 6 is a flowchart of another media resource deployment method provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of another media resource deployment apparatus according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, this figure is a schematic structural diagram of a media resource deployment system according to an embodiment of the present application.
As shown in fig. 1, the system includes:
the system comprises a global scheduling system 101, a public cloud server cluster 102 and a private cloud server cluster 103, wherein the private cloud server cluster 103 is deployed in a local area network; a public cloud server in the public cloud server cluster 102 and a private cloud server in the private cloud server cluster 103 are respectively in communication connection with the global scheduling system 101; the public cloud server cluster 102 is in communication connection with the private cloud server cluster 103;
the global scheduling system 101 is configured to allocate a target public cloud server to a public cloud client from the public cloud server cluster 102, or allocate a first target private cloud server to the public cloud client from the private cloud server cluster 103, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
the global scheduling system 101 is further configured to allocate a second target private cloud server to the private cloud client from the private cloud server cluster 103, so that the private cloud client transmits media resource data by using the second target private cloud server.
The media resource data mentioned in this embodiment may be in the form of audio, video, pictures, documents, and so on. The specific form of the media asset data is not limited herein.
In this embodiment, scheduling the client to the public cloud server and scheduling the client to the private cloud server are both implemented by the global scheduling system 101. In this embodiment, the private cloud server cluster 103 does not have an independent scheduling system, and therefore, the global scheduling system 101 is responsible for scheduling global servers, including scheduling public cloud servers of the public cloud server cluster 102 and scheduling private cloud servers of the private cloud server cluster 103.
The private cloud client mentioned in this embodiment refers to a client running on a device connected to a local area network; a public cloud client refers to a client running on a device connected to a wide area network. The public cloud servers in the public cloud server cluster 102 may be publishing servers and/or playing servers; similarly, the private cloud servers in the private cloud server cluster 103 may be publishing servers and/or playing servers. The publishing server has a function of receiving the uploaded media resource data, and the playing server has a function of sending the media resource data to the client.
For the former request, when the public cloud client is connected to the global scheduling system 101, the global scheduling system 101 needs to allocate a publishing server to the public cloud client from the public cloud server cluster 102; for the latter request, after the public cloud server is connected to the global scheduling system 101, the global scheduling system 101 needs to allocate a play server from the public cloud server cluster 102.
In addition, if the public cloud client requests to publish or play shared resources of the public cloud and the private cloud, the scheduling system may further allocate a first target private cloud server to the public cloud client from the private cloud server cluster 103.
Similarly, the access request of the private cloud client may be to publish media resource data or play media resource data, and for the former request, after the private cloud client is connected to the global scheduling system 101, the global scheduling system 101 needs to allocate a publication server to the private cloud client from the private cloud server cluster 103; for the latter request, after the private cloud servers are connected to the global scheduling system 101, the global scheduling system 101 needs to allocate a play server from the private cloud server cluster 103.
The first client corresponds to a client for realizing the data release of the media resources, and the second client corresponds to a client for realizing the playing of the media resources. In practical application, if the time for transmitting the media resource data is shorter, the transmission is quicker, and the waiting time of the first client is shorter; conversely, the slower the transmission, the longer the latency of the first client. Similarly, for the second client, before playing the media resource data, it needs to connect to a certain playing server, and then obtain the media resource data from the playing server. The connection form between the second client and the playing server may specifically be a telecommunication connection. In practical application, if the time for transmitting the media resource data is shorter, the transmission is quicker, and the waiting time of the second client is shorter; conversely, the slower the transmission, the longer the latency of the second client.
Based on the above reasons, that is, in the media resource deployment system, the usage requirement of the first client may not be satisfied by connecting any one publishing server with the first client, and the usage requirement of the second client may not be satisfied by connecting any one playing server with the second client. For this reason, the global scheduling system 101 plays a role in the present embodiment. All clients (e.g., the first client and the second client) requesting to publish or request to play the media asset data first need to connect with the scheduling system 101.
It is assumed that the public cloud server cluster 102 may be specifically subdivided into a publishing server cluster and a playing server cluster, and similarly, the private cloud server cluster 103 may also be specifically subdivided into a publishing server cluster and a playing server cluster.
An example implementation of allocating servers, scheduling clients to servers is described below.
The global scheduling system 101 is configured to allocate a target publishing server group for a first client from the publishing server cluster 102; the first client determines a target publishing server from a set of target publishing servers allocated to it by the global scheduling system 101.
The global scheduling system 101 is further configured to allocate a target play server group for the second client from the play server cluster; the second client determines a target playout server from the set of target playout servers allocated to it by the global scheduling system 101.
As an example, the publishing server cluster of the public cloud server cluster 102 specifically includes 20 publishing servers, the playing server cluster of the public cloud server cluster 102 specifically includes 20 playing servers, and the global scheduling system 101 allocates a target publishing server group including 5 publishing servers in total to the first client from the 20 publishing servers; and the global scheduling system 101 also allocates a target playout server group containing a total of 5 playout servers from the 20 playout servers to the second client. The target publishing server selected by the first client may be any one of a group of target publishing servers; the target playout server selected by the second client may be any one of a group of target playout servers.
There are many possible implementations of the distribution server. The following describes implementation manners for scheduling clients and allocating server addresses in combination with various possible implementation scenarios.
A first possible implementation: servers are allocated according to location or region, scheduled nearby.
The global scheduling system 101 is specifically configured to, after receiving the access request of the first client, if the access request carries location information of the client, obtain the location information. In addition, the regional information of the first client can be analyzed according to the IP address of the first client. The location information (or regional information) of each publishing server is known to the global scheduling system 101. The global scheduling system 101 sends the address of the target distribution server group to the first client according to the location information (or the region information) of the first client and the location information (or the region information) of the distribution server cluster. The sent address may be the address of a publishing server that is located closer to the first client in location (or region).
For example, the media resource deployment system has 5 publishing servers in the northeast region, 5 publishing servers in the southwest region, 5 publishing servers in the northwest region, and 5 publishing servers in the southeast region. The global scheduling system 101 analyzes that the regional information of the first client is urban, and since the urban areas are located in the southwest area, the publishing speed of the media resource data is faster after the publishing server located in the southwest area is connected with the first client. The global scheduling system 101 may send a set of addresses of 5 publication servers located in the southwest region to the first client in order for the first client to access and select a target publication server.
The global scheduling system 101 is specifically configured to, after receiving the access request of the second client, parse the region information of the second client according to the IP address of the second client. The regional information for each playout server is known to the global scheduling system 101. The global scheduling system 101 sends the address of the target playing server group to the second client according to the region information of the second client and the region information of the playing server cluster.
For example, the media asset deployment system has 5 playout servers in the northeast region, 5 playout servers in the southwest region, 5 playout servers in the northwest region, and 5 playout servers in the southeast region. The global scheduling system 101 analyzes that the region information of the second client is harbourne city, and since harbourne is located in the northeast region, the transmission and playing speed of the media resource data is faster after the playing server located in the northeast region is connected with the second client. The global scheduling system 101 may send a set of addresses of 5 publishing servers located in the northeast region to the second client for the second client to access and select the target playout server.
A second possible implementation: the bandwidth of the client is fixed, and the priority of the server is determined.
In specific implementation, for a publishing server cluster, the priority of each publishing server is determined; for a cluster of playout servers, the priority of each playout server has been determined. And, the bandwidth of the first client is fixed, and the bandwidth of the second client is also fixed.
In practical applications, the load carried by some (or a certain) publishing server or playing server may have reached a preset threshold, and the task of transmitting the media resource data cannot be continued. In practice, there are many ways to determine whether to overload, such as the number of connected terminals, the remaining bandwidth, etc.
For the above case, a plurality of available servers may be allocated to the client from among the plurality of servers by the global scheduling system 101. Or the client side judges whether the distributed servers are overloaded and selects the servers after confirming the priority of the distributed servers.
For example, a first client determines, from a group of distributed target distribution servers, a distribution server with a highest priority and a load that does not reach a preset threshold, and takes the distribution server as the target distribution server; and the second client determines the playing server with the highest priority and the load not reaching the preset threshold from the target playing server group, and takes the playing server as the target playing server.
A third possible implementation: and dispatching the client and the distribution server according to the consistent operator.
The global scheduling system 101 is specifically configured to analyze and determine an operator corresponding to the first client according to the IP of the first client, determine a publishing server corresponding to the operator from the publishing server cluster, and prioritize the publishing server into the target publishing server group. For example, the number of the allocated target publishing server groups is usually 5, and if the operator corresponding to the first client is the link, and if the number of the publishing servers determined from the plurality of servers and also corresponding to the link is greater than or equal to 5, 5 publishing servers are selected as the allocated target publishing server groups; and if the number of the determined publishing servers which also correspond to the link is less than 5, filling the vacancy by the BGP publishing server after listing the publishing servers in the target publishing server group. BGP publishing servers refer to publishing servers that transmit data according to the BGP protocol.
Similarly, the scheduling system is further configured to analyze and determine an operator corresponding to the second client according to the IP of the second client, determine a playing server corresponding to the operator from the playing server cluster, and preferentially list the playing server in the target playing server group.
It can be understood that, when media resource data transmission is performed, the client is consistent with an operator of the connected server, and the transmission speed can be improved.
A fourth possible implementation: and dispatching the private cloud client of the fixed establishment to the designated server cluster.
For example, an enterprise corresponds to a server cluster, and when a private cloud client running in the enterprise needs to publish or play media resource data, the global scheduling system 101 may first obtain identification information of the private cloud client. Since the identification information of the client has a corresponding relationship with the server cluster, after obtaining the identification information of the private cloud client, the global scheduling system 101 may schedule the private cloud client to the server cluster matched with the identification information in the private cloud server cluster 103.
The global scheduling system 101 determines that the identification information determines a corresponding server cluster, and then allocates a distribution server or a play server to the client from the cluster. In practical application, private cloud clients of the same organization may have the same identification information, and a corresponding relationship between the identification information and a certain server cluster is stored in the global scheduling system 101 in advance, so that the global scheduling system 101 can determine the server cluster serving the client of the organization by using the corresponding relationship after acquiring the identification information of the private cloud client, thereby implementing scheduling of the private cloud client.
The above lists alternative implementations of the global scheduling system 101 scheduling the first client and the second client and allocating servers to them, but the above implementations are merely examples and are not limited to specific implementations of the schemes.
In the technical scheme provided by the application, since the public cloud server in the public cloud server cluster 102 and the private cloud server in the private cloud server cluster 103 can be allocated by the global scheduling system 101 to perform transmission of media resource data with the client according to requirements, connection with the MCU is not required, and limitation of MCU port resources on data transmission is avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.
In this embodiment of the application, the global scheduling system 101 is further configured to determine whether the public cloud client meets a preset sharing condition according to the location information or the IP of the public cloud client, and if so, allow the public cloud client to obtain the shared resource of the private cloud server cluster 103; otherwise, the public cloud client is prohibited from obtaining the shared resource of the private cloud server cluster 103.
In practical applications, there are resources that can be shared between public cloud server cluster 102 and private cloud server cluster 103. Such as an introductory video for an organization (e.g., a business or school, etc.), etc. The mechanism has low requirements on the privacy and the safety of the media resources and can share the media resources to the users of the client of the public network.
If the public cloud client requests to play such media resources, the global scheduling system 101 may determine whether the public cloud client meets a preset sharing condition according to the location information or the IP of the public cloud client. As an example, the sharing condition may be a preset rule, for example, the terminal public network IP of the public cloud client is the terminal public network IP of the private cloud server cluster 103. This sharing condition is satisfied, which indicates that the public cloud client has just run from the local area network where the private cloud server cluster 103 is located, that is, the user of the client is the user in the organization corresponding to the private cloud server cluster 103. At this time, the shared resource may be shared to the client through data transmission according to the requirement of the client, and for this reason, the global scheduling system 101 may send, to the target public cloud server or the first target private cloud server, an instruction allowing the public cloud client to obtain the shared resource of the private cloud server cluster. If the sharing condition is not met, an instruction for prohibiting the public cloud client from obtaining the shared resources of the private cloud server cluster may be sent to a target public cloud server or the first target private cloud server.
The above sharing conditions are merely examples. As other examples, the sharing condition may also be that the verification passes or the distance is less than a preset distance threshold, and the like. The sharing condition is not particularly limited here.
As mentioned above, the global scheduling system 101 assigns a set of server addresses to clients. The following describes an implementation of the target-specific distribution server and the target-specific playback server.
After the global scheduling system 101 allocates the addresses of the target publishing server group to the first client, the first client may establish connections with the publishing servers respectively according to the addresses. The distributed target issuing server group is used for respectively receiving the speed measurement requests of the first client. After the speed measurement request is agreed, the first client can measure the speed of each distributed publishing server respectively, so that information such as data transmission performance of the current publishing server can be known. Finally, the first client may use the publishing server corresponding to the optimal speed measurement result as the target publishing server.
After the global scheduling system 101 allocates the addresses of the target playing server group to the second client, the second client may establish connections with the playing servers respectively according to the addresses. The distributed target playing server group is used for respectively receiving the speed measurement request of the second client. After the speed measurement request is agreed, the second client can measure the speed of each distributed playing server respectively, so that the information such as the data transmission performance of the current playing server can be known. Finally, the second client may use the playing server corresponding to the optimal speed measurement result as the target playing server.
Referring to fig. 2, a schematic diagram of a media resource data transmission flow according to an embodiment of the present application is shown. As shown in fig. 2:
media resource data is firstly issued to the target issuing server 202 by the first client 201 corresponding to the issuer, and a protocol adopted between the two devices during media resource data transmission may be a real-time transport protocol RTP or a real-time transport control protocol RTCP.
The target publishing server 202 then transmits the media resource data to the target playing server 203 at a frame level, during which the target publishing server 202 implements framing of video frames and audio frames, and the video may adopt an h.264 format and an audio-supported encoding format of opus and aac.
Finally, the second client 204 obtains the media resource data from the target playing server 203 and plays the media resource data. When the media resource data is transmitted, RTP or RTCP is used between the second client 204 and the target playing server 203.
In practical applications, the target publishing server 202 and the target playing server 203 may each interface the server components in units of frames, such as cdn component, reorder component, data analysis component, artificial intelligence component, and the like. The specific type of server component is not limited herein.
It is to be understood that if the first client 201 is a public cloud client, the target publishing server 202 may be a target public cloud server or a first target private cloud server; if the first client is a private cloud client, the target publication server 202 may be a second target private cloud server.
In practical application, when receiving the media resource data uploaded by the first client 201, the target distribution server 202 counts the received data packets without sorting, that is, only performs nack, and directly sends the received data packets to the target playing server 203.
When determining that the packet is lost, the target distribution server 202 sends a packet loss retransmission request to the first client 201, and then sends the data packet retransmitted by the first client 201 to the target playing server 203.
Because the target publishing server 202 does not sort the data packets when the packets are lost, and directly transmits the received data to the target playing server 203, the delay can be reduced, and the pause phenomenon of playing can be reduced. In addition, the direct audio and video transmission of the server is at the frame level, and the influence of diffused packet loss when the media resource data is played at the second client is avoided.
When packet loss and repopulation fail, the target playing server 203 may send a key frame request to the target publishing server 202 to request a key frame; the target publishing server 202 is further configured to notify the first client 201 to generate a key frame according to the key frame request, and send the key frame back to the target playing server 203. After obtaining the new key frame, the target playing server 203 may provide a new playing page to the second client 204 as soon as possible by using the key frame, so as to reduce the playing pause of the second client 204.
It should be noted that the target distribution server 202 and the target playback server 203 may also transmit control information in addition to media asset data.
In this embodiment, the target playing server 203 is further configured to respond to the bandwidth adjustment request of the second client 204 and feed back the bandwidth adjustment request to the target publishing server. For example, for the target playout server 203, the number of connected playout ends (i.e., the second client 204) is too large, and the bandwidth can be adjusted by adopting normal distribution. The bandwidth of the target playback server 203 has a lowest threshold and a highest threshold, and the bandwidth is adjusted between the lowest threshold and the highest threshold in the actual application.
In practical application, the media resource deployment system may further include an operation and maintenance server, where the operation and maintenance server is configured to monitor the usage bandwidths of the publishing server and the playing server through a script, and report the usage bandwidths to the scheduling system. The scheduling system may schedule the client according to the bandwidth used by each publishing server and the playing server, for example, when a certain publishing server is overloaded, the scheduling system will not allocate the publishing server to a new first client; when a playout server is overloaded, the scheduling system will not assign the playout server to a new second client. Therefore, the overload protection of each publishing server and each playing server in the media resource deployment system is realized.
Based on the media resource deployment system provided by the foregoing embodiment, correspondingly, the present application further provides a media resource deployment method.
Referring to fig. 3, this figure is a flowchart of a media resource deployment method provided in an embodiment of the present application.
As shown in fig. 3, the method includes:
step 301: judging whether the connected client is a public cloud client or a private cloud client, and if the connected client is the public cloud client, executing the step 302; if the client is a private cloud client, step 303 is performed.
Step 302: for a public cloud client, allocating a target public cloud server for the public cloud client from a public cloud server cluster, or allocating a first target private cloud server for the public cloud client from a private cloud server cluster, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
step 303: and for the private cloud client, distributing a second target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the second target private cloud server.
The public cloud servers in the public cloud server cluster and the private cloud servers in the private cloud server cluster can be distributed by the global scheduling system to transmit media resource data with the client according to requirements, so that connection with the MCU is not needed, and limitation of MCU port resources on data transmission is avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.
In order to further improve the privacy and security of the shared resources between the public cloud server cluster and the private cloud server cluster, the method may further include:
judging whether the public cloud client meets a preset sharing condition or not according to the position information or the IP of the public cloud client, and if so, sending an instruction for allowing the public cloud client to obtain the shared resources of the private cloud server cluster to the target public cloud server or the first target private cloud server; and if the judgment result is negative, sending an instruction for forbidding the public cloud client to obtain the shared resources of the private cloud server cluster to the target public cloud server or the first target private cloud server.
By sending the prohibition instruction when the sharing condition is not satisfied, the resource leakage propagation is avoided.
In practical application, if an organization has a corresponding private cloud server cluster, the method of this embodiment may further include:
obtaining identification information of the private cloud client;
step 303 may specifically include:
scheduling the private cloud client to a server cluster matched with the identification information in the private cloud server cluster;
and distributing the second target private cloud server for the private cloud client from the server cluster matched with the identification information.
As can be seen, the private cloud client in the organization may be configured to process the request of the client exclusively by the server in the corresponding private cloud server cluster, and perform transmission of media resource data with the client.
Based on the media resource deployment method provided by the foregoing embodiment, correspondingly, the present application further provides a media resource deployment device.
Referring to fig. 4, the structure of the device is schematically shown. As shown in fig. 4, the apparatus includes:
the determining module 401 is configured to determine that the connected client is a public cloud client or a private cloud client;
a first allocating module 402, configured to, when the determining module 401 determines that the connected client is a public cloud client, allocate a target public cloud server to the public cloud client from a public cloud server cluster, or allocate a first target private cloud server to the public cloud client from a private cloud server cluster, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
a second allocating module 403, configured to, when the determining module 401 determines that the connected client is a private cloud client, allocate a second target private cloud server to the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the second target private cloud server.
In the technical scheme provided by the application, since the public cloud server in the public cloud server cluster and the private cloud server in the private cloud server cluster can be allocated by the first allocation module 402 or the second allocation module 403 to perform transmission of media resource data with the client according to requirements, connection between the public cloud server and the client and connection between the private cloud server and the client and limitation of MCU port resources on data transmission are avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.
In addition, an embodiment of the present application further provides another media resource deployment system, see fig. 5, which is a schematic structural diagram of the system.
As shown in fig. 5, the media resource deployment system includes:
the system comprises a first scheduling system 501, a second scheduling system 502, a public cloud server cluster 503 and a private cloud server cluster 504, wherein the private cloud server cluster 504 is deployed in a local area network; a public cloud server in the public cloud server cluster 503 is in communication connection with the first scheduling system 501, and a private cloud server in the private cloud server cluster 504 is in communication connection with the second scheduling system 502;
the first scheduling system 501 is configured to allocate a target public cloud server for a public cloud client from the public cloud server cluster 503, so that the public cloud client transmits media resource data by using the target public cloud server;
the second scheduling system 502 is configured to allocate a target private cloud server for a private cloud client from the private cloud server cluster 504, so that the private cloud client transmits media resource data by using the target private cloud server.
In this embodiment, the first scheduling system 501 is configured to schedule the public cloud client to the target public cloud server, and is not responsible for scheduling the private cloud client. That is, the first scheduling system 501 is a scheduling system independently deployed by the public cloud server cluster 503. The second scheduling system 502 is configured to schedule the private cloud client to the target private cloud server, and is not responsible for scheduling the public cloud client. That is, the second scheduling system 502 is a scheduling system deployed independently by the private cloud server cluster 504.
In this embodiment, the private cloud server cluster 504 and the public cloud server cluster 503 do not share media resources because the public cloud and the private cloud deploy the scheduling system independently. Only private cloud clients and specific clients outside the local area network are allowed to share the resources if sharing conditions (or preset sharing rules) are met.
The public cloud server in the public cloud server cluster and the private cloud server in the private cloud server cluster can be distributed by the independent scheduling system to transmit media resource data with the client according to requirements, so that connection with the MCU is not needed, and limitation of MCU port resources on data transmission is avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.
Based on the media resource deployment system provided by the foregoing embodiment, correspondingly, the embodiment of the present application further provides a media resource deployment method. Referring to fig. 6, a flow chart of the method is shown.
As shown in fig. 6, the method includes:
step 601: judging whether the connected client is a public cloud client or a private cloud client, and if the connected client is the public cloud client, executing step 602; if the client is a private cloud client, step 603 is performed.
Step 602: for a public cloud client, distributing a target public cloud server for the public cloud client from a public cloud server cluster, so that the public cloud client transmits media resource data by using the target public cloud server;
step 603: and for the private cloud client, distributing a target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the target private cloud server.
Based on the media resource deployment system and method provided by the foregoing embodiments, correspondingly, the embodiments of the present application further provide a media resource deployment device. Referring to fig. 7, the structure of the device is schematically shown.
As shown in fig. 7, the apparatus includes:
a judging module 701, configured to judge that the connected client is a public cloud client or a private cloud client;
a first distribution module 702, configured to, when the determining module 701 determines that the connected client is a public cloud client, allocate a target public cloud server to the public cloud client from a public cloud server cluster, so that the public cloud client transmits media resource data by using the target public cloud server;
the second allocating module 703 is configured to, when the determining module 701 determines that the connected client is a private cloud client, allocate a target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the target private cloud server.
Since the public cloud server in the public cloud server cluster and the private cloud server in the private cloud server cluster can be allocated by the first allocation module 702 or the second allocation module 703 to perform transmission of media resource data with the client according to requirements, connection with the MCU is not required, and limitation of MCU port resources on data transmission is avoided. Even if the clients are numerous and the distribution range is wide, the scheduling can be flexibly carried out from the deployed server cluster, and the waiting time of the clients is reduced. In addition, the public cloud server and the private cloud server belong to different server clusters, the boundary is clear, the target server realizes the transmission of media resource data, and the risk that the private cloud server resources are randomly acquired is reduced.
Based on the media resource deployment system, method and apparatus provided in the foregoing embodiments, the present application also provides a computer-readable storage medium, in which a computer program is stored, and when the program is executed by a processor, the media resource deployment method provided in the foregoing method embodiments is implemented.
Based on the media resource deployment system, method and device provided by the foregoing embodiments, the present application further provides a processor, where the processor is configured to run a computer program, and the program executes the media resource deployment method provided by the foregoing method embodiments when running.
It should be noted that, in the present specification, all the embodiments are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the method and apparatus embodiments are substantially similar to the system embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related aspects. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts suggested as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only one specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (12)

1. A media resource deployment system, comprising: the system comprises a global scheduling system, a public cloud server cluster and a private cloud server cluster, wherein the private cloud server cluster is deployed in a local area network; a public cloud server in the public cloud server cluster and a private cloud server in the private cloud server cluster are respectively in communication connection with the global scheduling system; the public cloud server cluster is in communication connection with the private cloud server cluster;
the global scheduling system is used for allocating a target public cloud server for a public cloud client from the public cloud server cluster or allocating a first target private cloud server for the public cloud client from the private cloud server cluster, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
the global scheduling system is further configured to allocate a second target private cloud server to the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the second target private cloud server.
2. The system according to claim 1, wherein the global scheduling system is further configured to determine whether the public cloud client meets a preset sharing condition according to the location information or the IP of the public cloud client, and if so, allow the public cloud client to obtain the shared resource of the private cloud server cluster; and if not, forbidding the public cloud client to obtain the shared resources of the private cloud server cluster.
3. The system of claim 1, wherein the global scheduling system is further configured to obtain identification information of the private cloud client;
the global scheduling system is specifically configured to schedule the private cloud client to a server cluster in the private cloud server cluster that is matched with the identification information.
4. A media resource deployment system, comprising: the system comprises a first scheduling system, a second scheduling system, a public cloud server cluster and a private cloud server cluster, wherein the private cloud server cluster is deployed in a local area network; a public cloud server in the public cloud server cluster is in communication connection with the first scheduling system, and a private cloud server in the private cloud server cluster is in communication connection with the second scheduling system;
the first scheduling system is used for allocating a target public cloud server for a public cloud client from the public cloud server cluster so that the public cloud client can transmit media resource data by using the target public cloud server;
the second scheduling system is used for allocating a target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the target private cloud server.
5. A method for deploying a media resource, comprising:
judging whether the connected client is a public cloud client or a private cloud client;
for a public cloud client, allocating a target public cloud server for the public cloud client from a public cloud server cluster, or allocating a first target private cloud server for the public cloud client from a private cloud server cluster, so that the public cloud client transmits media resource data by using the first target public cloud server or the target private cloud server;
and for the private cloud client, distributing a second target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the second target private cloud server.
6. The method of claim 5, further comprising:
judging whether the public cloud client meets a preset sharing condition or not according to the position information or the IP of the public cloud client, and if so, sending an instruction allowing the public cloud client to obtain the shared resources of the private cloud server cluster to the target public cloud server or the first target private cloud server; and otherwise, sending an instruction for forbidding the public cloud client to obtain the shared resources of the private cloud server cluster to the target public cloud server or the first target private cloud server.
7. The method of claim 5, further comprising:
obtaining identification information of the private cloud client;
the allocating a second target private cloud server for the private cloud client from the private cloud server cluster specifically includes:
scheduling the private cloud client to a server cluster matched with the identification information in the private cloud server cluster; and distributing the second target private cloud server for the private cloud client from the server cluster matched with the identification information.
8. A method for deploying a media resource, comprising:
judging whether the connected client is a public cloud client or a private cloud client;
for a public cloud client, distributing a target public cloud server for the public cloud client from a public cloud server cluster, so that the public cloud client transmits media resource data by using the target public cloud server;
and for the private cloud client, distributing a target private cloud server for the private cloud client from the private cloud server cluster, so that the private cloud client transmits media resource data by using the target private cloud server.
9. A media resource deployment apparatus, comprising:
the judging module is used for judging whether the connected client is a public cloud client or a private cloud client;
the first distribution module is used for distributing a target public cloud server for the public cloud client from a public cloud server cluster or distributing a first target private cloud server for the public cloud client from a private cloud server cluster when the connected client is judged to be the public cloud client by the judgment module, so that the public cloud client utilizes the first target public cloud server or the target private cloud server to transmit media resource data;
and the second allocating module is used for allocating a second target private cloud server for the private cloud client from the private cloud server cluster when the connected client is judged to be the private cloud client by the judging module, so that the private cloud client transmits the media resource data by using the second target private cloud server.
10. A media resource deployment apparatus, comprising:
the judging module is used for judging whether the connected client is a public cloud client or a private cloud client;
the first distribution module is used for distributing a target public cloud server for the public cloud client from a public cloud server cluster when the connected client is judged to be the public cloud client by the judgment module so as to enable the public cloud client to transmit media resource data by using the target public cloud server;
and the second distribution module is used for distributing a target private cloud server for the private cloud client from the private cloud server cluster when the judgment module judges that the connected client is the private cloud client, so that the private cloud client utilizes the target private cloud server to transmit media resource data.
11. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out a method for deploying a media resource according to any one of claims 5 to 8.
12. A processor configured to run a computer program, the program when executed performing the media asset deployment method of any of claims 5-8.
CN202010044151.2A 2020-01-15 2020-01-15 Media resource deployment system, method, device, storage medium and processor Withdrawn CN111262931A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010044151.2A CN111262931A (en) 2020-01-15 2020-01-15 Media resource deployment system, method, device, storage medium and processor

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010044151.2A CN111262931A (en) 2020-01-15 2020-01-15 Media resource deployment system, method, device, storage medium and processor

Publications (1)

Publication Number Publication Date
CN111262931A true CN111262931A (en) 2020-06-09

Family

ID=70952134

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010044151.2A Withdrawn CN111262931A (en) 2020-01-15 2020-01-15 Media resource deployment system, method, device, storage medium and processor

Country Status (1)

Country Link
CN (1) CN111262931A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810651A (en) * 2021-08-24 2021-12-17 中国人寿保险股份有限公司上海数据中心 Video communication system and method based on multi-cloud mixed deployment
CN114615272A (en) * 2022-01-29 2022-06-10 杭州华橙软件技术有限公司 Media data forwarding server scheduling method and system
CN115604120A (en) * 2022-11-30 2023-01-13 苏州浪潮智能科技有限公司（Cn） Multi-cloud cluster resource sharing method, device, equipment and storage medium

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179536A (en) * 2006-12-22 2008-05-14 腾讯科技（深圳）有限公司 Method and system for implementing instant communication between external network user and LAN user
WO2010031280A1 (en) * 2008-09-16 2010-03-25 中兴通讯股份有限公司 File transferring method of nat traversal
US20150143501A1 (en) * 2013-11-19 2015-05-21 Cisco Technology, Inc. Path selection in a multi-service and multi-tenant secure cloud environment
CN107104958A (en) * 2017-04-14 2017-08-29 深圳市先河***技术有限公司 Manage the method, private clound and public cloud equipment and storage device of private clound equipment
CN107239329A (en) * 2016-03-29 2017-10-10 西门子公司 Unified resource dispatching method and system under cloud environment
CN107566533A (en) * 2017-10-26 2018-01-09 南威软件股份有限公司 A kind of intranet and extranet shared file system realized based on NAS
CN109587254A (en) * 2018-12-11 2019-04-05 深圳市口袋网络科技有限公司 Cloud Server access method, device, Cloud Server and storage medium
CN110430281A (en) * 2019-08-15 2019-11-08 深圳市般若大数据技术有限公司 Method, apparatus, equipment and the storage medium of public cloud acquisition private clound data

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179536A (en) * 2006-12-22 2008-05-14 腾讯科技（深圳）有限公司 Method and system for implementing instant communication between external network user and LAN user
WO2010031280A1 (en) * 2008-09-16 2010-03-25 中兴通讯股份有限公司 File transferring method of nat traversal
US20150143501A1 (en) * 2013-11-19 2015-05-21 Cisco Technology, Inc. Path selection in a multi-service and multi-tenant secure cloud environment
CN107239329A (en) * 2016-03-29 2017-10-10 西门子公司 Unified resource dispatching method and system under cloud environment
CN107104958A (en) * 2017-04-14 2017-08-29 深圳市先河***技术有限公司 Manage the method, private clound and public cloud equipment and storage device of private clound equipment
CN107566533A (en) * 2017-10-26 2018-01-09 南威软件股份有限公司 A kind of intranet and extranet shared file system realized based on NAS
CN109587254A (en) * 2018-12-11 2019-04-05 深圳市口袋网络科技有限公司 Cloud Server access method, device, Cloud Server and storage medium
CN110430281A (en) * 2019-08-15 2019-11-08 深圳市般若大数据技术有限公司 Method, apparatus, equipment and the storage medium of public cloud acquisition private clound data

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810651A (en) * 2021-08-24 2021-12-17 中国人寿保险股份有限公司上海数据中心 Video communication system and method based on multi-cloud mixed deployment
CN114615272A (en) * 2022-01-29 2022-06-10 杭州华橙软件技术有限公司 Media data forwarding server scheduling method and system
CN114615272B (en) * 2022-01-29 2024-05-03 杭州华橙软件技术有限公司 Method and system for scheduling media data forwarding server
CN115604120A (en) * 2022-11-30 2023-01-13 苏州浪潮智能科技有限公司（Cn） Multi-cloud cluster resource sharing method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
AU2013351670B2 (en) Business scheduling method and apparatus and convergence device
CN111262931A (en) Media resource deployment system, method, device, storage medium and processor
US9264369B2 (en) Technique for managing traffic at a router
CN110417676B (en) Scheduling method, device and scheduling network
CN111937364A (en) Method and system for processing data path creation in wireless network system
CN110022269B (en) Communication data processing method, device and equipment
CN108848530B (en) Method and device for acquiring network resources and scheduling server
JP2014239521A (en) Data transmission over network with channel bonding
WO2016197628A1 (en) Method of terminal-based conference load-balancing, and device and system utilizing same
WO2015096680A1 (en) Node distribution method and control center
KR20130055423A (en) Apparatus and method for supporting qos in middleware for data distribution service
CN111314293A (en) Media resource service system, method, device, storage medium and processor
WO2016107598A1 (en) Service acceleration method and apparatus
CN103986741A (en) Cloud data system, cloud data center, and resource management method of the cloud data center
US9596063B2 (en) Dynamically allocating network resources for communication session
CN106534216B (en) Server deployment system
Giannone et al. Orchestrating heterogeneous MEC-based applications for connected vehicles
CN113938435A (en) Data transmission method, data transmission device, electronic device, storage medium, and program product
Nahrstedt et al. QoS and resource management in distributed interactive multimedia environments
CN109640357B (en) Priority-based wireless sensor network optimal resource reservation method suitable for electric power Internet of things environment
KR102494603B1 (en) Distribution of bandwidth in the network
CN107438098B (en) Dynamic content distribution method and system
US20130170442A1 (en) Content-based network system and method of controlling transmission of content therein
CN113810442B (en) Resource reservation method, device, terminal and node equipment
CN112866390A (en) Data transmission method, device, terminal equipment and storage medium

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: 20200609