WO2016197628A1 - 终端会议负载均衡方法、装置及系统 - Google Patents

终端会议负载均衡方法、装置及系统 Download PDF

Info

Publication number
WO2016197628A1
WO2016197628A1 PCT/CN2016/074582 CN2016074582W WO2016197628A1 WO 2016197628 A1 WO2016197628 A1 WO 2016197628A1 CN 2016074582 W CN2016074582 W CN 2016074582W WO 2016197628 A1 WO2016197628 A1 WO 2016197628A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
resource
media
scheduler
server
Prior art date
Application number
PCT/CN2016/074582
Other languages
English (en)
French (fr)
Inventor
周运武
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP16806526.6A priority Critical patent/EP3293969A4/en
Priority to US15/579,951 priority patent/US10728050B2/en
Publication of WO2016197628A1 publication Critical patent/WO2016197628A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1827—Network arrangements for conference optimisation or adaptation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • 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
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/15—Conference systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/15—Conference systems
    • H04N7/152—Multipoint control units therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources

Definitions

  • the present invention relates to the field of communications, and in particular, to a terminal conference load balancing method, apparatus, and system.
  • video conferencing has entered the Internet field, enabling distributed and cloud-based deployment. It is bound to require the distributed and scalable call resources and media resources of the conference, so that call resources and media resources can be optimally used. .
  • the cloud conference limits the number of users accessing, and cannot fully realize the user's access anytime and anywhere, and does not exert great advantages in resource allocation. When the user is overloaded, it cannot be satisfactorily satisfied. A large number of users concurrently access.
  • the invention provides a terminal conference load balancing method, device and system, so as to at least solve the problem that the number of users accessed by the video conference system in the related art is limited.
  • a terminal conference load balancing method including:
  • the scheduler receives the call resource and the media resource reported by the server;
  • the scheduler receives a call resource request of the server, and the scheduler allocates, to the terminal managed by the server, an idle call resource access node in the call resource according to the call resource request;
  • the scheduler receives a media resource request of a call node corresponding to the call resource access node, and the scheduler allocates an idle media resource access node in the media resource to the terminal according to the media resource request. .
  • the method before the scheduler receives the call resource and the media resource reported by the server, the method includes:
  • the scheduler sends a call media resource request to the server, where the media resource request is used to instruct the server to report the call resource and the media resource to the scheduler.
  • the method before the scheduler receives the call resource and the media resource reported by the server, the method includes:
  • the scheduler receives the call resource and the media resource that are periodically reported by the server according to a preset time.
  • the assigning, by the scheduler, the call management resource access node in the call resource to the terminal managed by the server includes:
  • the scheduler allocates, to the terminal, an idle call resource access node in the call resource according to a route configuration rule of an area to which the server belongs.
  • the method comprises:
  • the scheduler allocates the idle call resource connection in the call resource to the terminal according to the route configuration rule of the server neighboring area. Into the node.
  • the assigning the terminal to the terminal to allocate an idle media resource access node in the media resource includes:
  • the scheduler allocates an idle media resource access node to the terminal according to an allocation rule of the media resource in an area to which the call resource access node belongs.
  • the method comprises:
  • the media resource in the area does not have an idle media resource access node, and the scheduler allocates idle media to the terminal according to an allocation rule of the media resource in a neighboring area of the call resource access node.
  • Resource access node
  • a terminal conference load balancing apparatus including:
  • a receiving module configured to receive, by the scheduler, a call resource and a media resource reported by the server;
  • a call distribution module configured to receive, by the scheduler, a call resource request of the server, where the scheduler allocates, to the terminal managed by the server, an idle call resource access node in the call resource according to the call resource request ;
  • a media allocation module configured to receive, by the scheduler, a media resource request of a call node corresponding to the call resource access node, where the scheduler allocates idleness in the media resource to the terminal according to the media resource request Media resource access node.
  • the device further includes:
  • the requesting module is configured to send a call media resource request to the server, where the media resource request is used to instruct the server to report the call resource and the media resource to the scheduler.
  • the device further includes:
  • the reporting module is configured to receive, by the scheduler, the call resource and the media resource that are periodically reported by the server according to a preset time.
  • the call distribution module comprises:
  • the first call distribution unit is configured to allocate, by the scheduler, the call resource access node that is idle in the call resource according to a route configuration rule of the area to which the server belongs.
  • the call distribution module comprises:
  • a second call distribution unit configured to allocate, according to a routing configuration rule of a neighboring area of the server, the terminal to the terminal, if there is no idle call resource access node in the call resource of the area An idle call resource access node in the call resource.
  • the media distribution module includes:
  • a first media allocation unit configured to allocate, by the scheduler, an idle media resource access node to the terminal according to an allocation rule of the media resource in an area to which the call resource access node belongs.
  • the media distribution module includes:
  • a second media allocation unit configured to: the media resource access node in the area where the media resource is not idle, and the scheduler according to the allocation rule of the media resource in a neighboring area of the call resource access node, The terminal is allocated an idle media resource access node.
  • a terminal conference load balancing system including: a scheduler, a server, and a terminal;
  • the scheduler receives the call resource and the media resource reported by the server;
  • the scheduler receives a call resource request of the server, and the scheduler allocates, to the terminal managed by the server, an idle call resource access node in the call resource according to the call resource request;
  • the scheduler receives a media resource request of a call node corresponding to the call resource access node, and the scheduler allocates an idle media resource access node in the media resource to the terminal according to the media resource request. .
  • the scheduler receives the call resource and the media resource reported by the server, and the scheduler receives the call resource request of the server, and the scheduler allocates the idle call in the call resource to the terminal managed by the server according to the call resource request.
  • a resource access node the scheduler receives a media resource request of a call node corresponding to the call resource access node, and the scheduler allocates an idle media resource access node in the media resource to the terminal according to the media resource request
  • FIG. 1 is a flowchart of a method for terminal conference load balancing according to an embodiment of the present invention
  • FIG. 2 is a structural block diagram of a terminal conference load balancing apparatus according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a general two-point conference according to the related art
  • FIG. 4 is a schematic diagram of a general multipoint conference according to the related art
  • FIG. 5 is a schematic illustration of a cloud conference in accordance with a preferred embodiment
  • FIG. 6 is a flow diagram of call media resource load balancing for a cloud conference in accordance with a preferred embodiment.
  • FIG. 1 is a flowchart of a terminal conference load balancing method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:
  • Step S102 The scheduler receives the call resource and the media resource reported by the server.
  • Step S104 The scheduler receives a call resource request of the server, and the scheduler allocates, to the terminal managed by the server, an idle call resource access node in the call resource according to the call resource request.
  • Step S106 The scheduler receives a media resource request of the call node corresponding to the call resource access node, and the scheduler allocates an idle media resource access node in the media resource to the terminal according to the media resource request.
  • the scheduler receives the call resource and the media resource reported by the server, and allocates the idle call resource access node and the idle media resource access to the terminal managed by the server according to the call resource request and the media resource request received by the server.
  • the node and the scheduler effectively allocate the call resources and the media resources on the server, which solves the problem that the number of users accessed by the video conference system is limited, and meets the conference access of a large number of users.
  • the scheduler may further send a call media resource request to the server, where the media resource request is used to instruct the server to report the call resource to the scheduler. And the media resource.
  • the scheduler may further receive the call resource and the media resource that are periodically reported by the server according to a preset time.
  • the scheduler can allocate a call resource access node that is idle in the call resource to the terminal managed by the server, where
  • the scheduler can allocate the call resource access node that is idle in the call resource to the terminal according to the route configuration rule of the area to which the server belongs.
  • the scheduler allocates the call resource access node that is idle in the call resource according to the route configuration rule of the neighboring area of the server.
  • the scheduler can allocate the idle media resource access node in the media resource to the terminal in a plurality of manners, where
  • the scheduler may allocate an idle media resource access node to the terminal according to the allocation rule of the media resource in the area to which the call resource access node belongs.
  • the media resource in the area does not have an idle media resource access node, and the scheduler allocates an idle media resource access node to the terminal according to the allocation rule of the media resource in the adjacent area of the call resource access node.
  • a terminal conference load balancing device is further provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 2 is a structural block diagram of a terminal conference load balancing apparatus according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes
  • the receiving module 22 is configured to receive, by the scheduler, the call resource and the media resource reported by the server;
  • the call distribution module 24 is configured to receive, by the scheduler, a call resource request of the server, and the scheduler allocates, to the terminal managed by the server, the call resource access node that is idle in the call resource according to the call resource request;
  • the media distribution module 26 is configured to receive, by the scheduler, a media resource request of the call node corresponding to the call resource access node, and the scheduler allocates the idle media resource access in the media resource to the terminal according to the media resource request. node.
  • the scheduler receives the call resource and the media resource reported by the server, and allocates the idle call resource access node and the idle media resource access to the terminal managed by the server according to the call resource request and the media resource request received by the server.
  • the node and the scheduler effectively allocate the call resources and the media resources on the server, which solves the problem that the number of users accessed by the video conference system is limited, and meets the conference access of a large number of users.
  • the device further includes:
  • the requesting module is configured to send a call media resource request to the server, where the media resource request is used to instruct the server to report the call resource and the media resource to the scheduler.
  • the reporting module is configured to receive, by the scheduler, the call resource and the media resource that are periodically reported by the server according to a preset time.
  • the call distribution module 24 includes:
  • the first call distribution unit is configured to allocate, by the scheduler, the call resource access node that is idle in the call resource according to a route configuration rule of the area to which the server belongs.
  • a second call distribution unit configured to allocate, in the call resource of the area, an idle call resource access node, the scheduler assigning the terminal idle in the call resource according to a route configuration rule of a neighboring area of the server Call the resource access node.
  • the media distribution module 26 includes:
  • the first media allocation unit is configured to allocate, by the scheduler, an idle media resource access node to the terminal according to the allocation rule of the media resource in the area to which the call resource access node belongs.
  • a second media allocation unit configured to: the media resource in the area has no idle media resource access node, and the scheduler allocates idle time to the terminal according to the media resource allocation rule of the call resource access node adjacent area Media resource access node.
  • a terminal conference load balancing system including: a scheduler, a server, and a terminal;
  • the scheduler receives the call resource and the media resource reported by the server;
  • the scheduler receives a call resource request of the server, and the scheduler allocates, to the terminal managed by the server, an idle call resource access node in the call resource according to the call resource request;
  • the scheduler receives a media resource request of the call node corresponding to the call resource access node, and the scheduler allocates an idle media resource access node in the media resource to the terminal according to the media resource request.
  • the call resources and the media resources can be seamlessly allocated to the servers of other idle resources, and the application scenarios of concurrently accessing a large number of users are solved.
  • Step 1 When the calling media resource scheduler is powered on, the cloud server is powered on to request the call media resource to report, and the cloud server allocates the call resource unit and the media resource unit according to the CPU core number of the cloud server, the memory, and the like. And reported to the call media resource scheduler;
  • Step 2 When the cloud server detects that there is a conference television terminal access, it acquires an idle call resource access node from the call media resource scheduler, and otherwise requests the call media scheduler to request the idle resource to report;
  • Step 3 After receiving the call resource access node request message, the call media resource scheduler allocates an idle call resource unit according to the area code. If the resource unit corresponding to the area code is already full, allocate an idle call resource from the area. Unit, if there is no idle call resource unit in the area, the access is allocated from other areas. If the resources of all areas have been used up, the call access is directly rejected, otherwise the call media resource scheduler allows access.
  • the address of the calling resource tells the terminal;
  • Step 4 The terminal acquires an idle media resource access node by calling the media resource scheduler through the call resource access node allocated in the C step.
  • Step 5 After receiving the message requested by the media node, the calling media resource scheduler first selects a corresponding idle media resource unit according to the access media capability. If found, the calling media resource scheduler notifies the terminal of the address of the media node, otherwise Directly reject access;
  • the call resources and the media resources can be allocated evenly, so that The conference resources are optimally used to ensure that the user's large capacity is concurrently accessed.
  • FIG. 3 is a schematic diagram of a common two-point conference according to the related art, as shown in FIG. 3, where A and B are ordinary terminals, because only a simple point-to-point conference, there is no terminal access after the resources are used up. , so there is no need to implement call media resource load balancing
  • FIG. 4 is a schematic diagram of a general multipoint conference according to the related art, as shown in FIG. 4, where A is a built-in MCU terminal or an MCU, and the others are ordinary terminals. If a common terminal has a large capacity concurrent access A, A will exist. If the call resources or the media resources are insufficient, the large-capacity access to the common terminal cannot be performed concurrently. The scalability of the service cannot be fully realized by adding the built-in MCU terminal or the MCU cascading mode. This affects other terminals and concurrently large-capacity. Access.
  • FIG. 5 is a schematic diagram of a cloud conference according to a preferred embodiment, as shown in FIG. 5, which is a schematic diagram of a cloud conference.
  • A is a resource scheduling server
  • B1 and B2 are both zone 1 cloud servers
  • C1 and C2 are both zone 2 cloud servers
  • D1, E1, F1, G1, H1, and L1 are common terminals of zone 1, D2, E2.
  • F2, G2, H2, and L2 are common terminals in Zone 2.
  • A is configured to access the cloud server of Zone 1 according to the routing rule, and the cloud server in Zone 1 is accessed. After the call and media resources are used up, you can find the cloud server in Zone 2.
  • A configures the cloud server of Zone 2 to access according to the routing rules. After the call and media resources of the cloud server in Zone 2 are used up, you can find the cloud server in Zone 1.
  • FIG. 6 is a flow chart of call media resource load balancing of a cloud conference according to a preferred embodiment.
  • the call media scheduler sends a message to each cloud server of the area to request resource reporting, and the cloud server of each area is based on
  • the resources of the CPU core, the memory, and the like are allocated to the call resource node and the media resource node, and are reported to the call media scheduler, and each cloud server in each area periodically detects whether there is a conference television terminal access, if there is no conference television terminal. If yes, the idle call resource node and the media resource node of the cloud server are reported in a fixed time.
  • the cloud server requests the call media scheduler to call the access resource node, and the call media scheduler routes according to the area to which the cloud server belongs.
  • the configuration rule allocates an idle call access resource node. If there is no idle call access resource node in the area, the allocation is continued from the adjacent area, and is returned to the terminal through the cloud server, and the terminal accesses the resource through the call.
  • the node accesses, and the conference television terminal accesses the resource node to the call through the call.
  • the media scheduler requests the media node, and the call media scheduler allocates the media resource node according to the media resource allocation rule, that is, first allocates the media node from the area where the call access resource node is located, if there is no free media resource in the area.
  • the node allocates a media resource node from the adjacent area, and returns the resource node through the call, and the conference television terminal transmits the code stream through the media resource node to ensure a normal conference of the cloud conference.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be Set to store program code for performing the above embodiments:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor executes the method of the above embodiment according to the stored program code in the storage medium.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the scheduler receives the call resource and the media resource reported by the server, the scheduler receives the call resource request of the server, and the scheduler allocates the terminal managed by the server according to the call resource request.
  • An idle call resource access node in the call resource the scheduler receives a media resource request of a call node corresponding to the call resource access node, and the scheduler allocates the idleness in the media resource to the terminal according to the media resource request.
  • the media resource access node solves the problem that the number of users accessing the video conference system is limited, and meets the conference access of a large number of users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本发明提供了一种终端会议负载均衡方法、装置及系统，其中，该方法通过调度器接收服务器上报的呼叫资源和媒体资源，该调度器接收该服务器的呼叫资源请求，该调度器根据该呼叫资源请求，给该服务器管理的终端分配该呼叫资源中空闲的呼叫资源接入节点，该调度器接收该呼叫资源接入节点对应的呼叫节点的媒体资源请求，该调度器根据该媒体资源请求，给该终端分配该媒体资源中的空闲的媒体资源接入节点，解决了视频会议系统接入的用户量有限的问题，满足了大量用户的会议接入。

Description

终端会议负载均衡方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种终端会议负载均衡方法、装置及系统。
背景技术
目前，视频会议已经迈向互联网领域，实现了可分布式，可云化部署，势必要求会议的呼叫资源和媒体资源的可分布式，可伸缩性，使呼叫资源和媒体资源能够达到最优使用。
在相关技术中，云会议限制了接入的用户量，无法全面实现了用户随时随地接入，而且在资源调配方面，没有发挥很大的优势，当用户过载的时候，就无法很好地满足于大量用户并发接入。
针对相关技术中，视频会议系统接入的用户量有限的问题，目前尚未提出有效的解决方案。
发明内容
本发明提供了一种终端会议负载均衡方法、装置及系统，以至少解决相关技术中视频会议系统接入的用户量有限的问题。
根据本发明的一个实施例，提供了一种终端会议负载均衡方法，包括：
调度器接收服务器上报的呼叫资源和媒体资源；
所述调度器接收所述服务器的呼叫资源请求，所述调度器根据所述呼叫资源请求，给所述服务器管理的终端分配所述呼叫资源中空闲的呼叫资源接入节点；
所述调度器接收所述呼叫资源接入节点对应的呼叫节点的媒体资源请求，所述调度器根据所述媒体资源请求，给所述终端分配所述媒体资源中的空闲的媒体资源接入节点。
在本发明的实施例中，所述调度器接收服务器上报的呼叫资源和媒体资源之前，所述方法包括：
调度器向服务器发送呼叫媒体资源请求，所述媒体资源请求用于指示所述服务器给所述调度器上报所述呼叫资源和所述媒体资源。
在本发明的实施例中，所述调度器接收服务器上报的呼叫资源和媒体资源之前，所述方法包括：
所述调度器接收所述服务器依据预设时间循环上报的所述呼叫资源和所述媒体资源。
在本发明的实施例中，所述调度器给所述服务器管理的终端分配所述呼叫资源中空闲的呼叫资源接入节点包括：
所述调度器根据所述服务器所属区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
在本发明的实施例中，所述方法包括：
在所述区域的呼叫资源中没有空闲的呼叫资源接入节点的情况下，所述调度器根据所述服务器相邻区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
在本发明的实施例中，所述调度器给所述终端分配所述媒体资源中的空闲的媒体资源接入节点包括：
所述调度器根据所述呼叫资源接入节点所属区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
在本发明的实施例中，所述方法包括：
在所述区域的所述媒体资源没有空闲的媒体资源接入节点，所述调度器根据所述呼叫资源接入节点相邻区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
根据本发明的另一个实施例，还提供了一种终端会议负载均衡装置，包括：
接收模块，设置为调度器接收服务器上报的呼叫资源和媒体资源；
呼叫分配模块，设置为所述调度器接收所述服务器的呼叫资源请求，所述调度器根据所述呼叫资源请求，给所述服务器管理的终端分配所述呼叫资源中空闲的呼叫资源接入节点；
媒体分配模块，设置为所述调度器接收所述呼叫资源接入节点对应的呼叫节点的媒体资源请求，所述调度器根据所述媒体资源请求，给所述终端分配所述媒体资源中的空闲的媒体资源接入节点。
在本发明的实施例中，所述装置还包括：
请求模块，设置为调度器向服务器发送呼叫媒体资源请求，所述媒体资源请求用于指示所述服务器给所述调度器上报所述呼叫资源和所述媒体资源。
在本发明的实施例中，所述装置还包括：
上报模块，设置为所述调度器接收所述服务器依据预设时间循环上报的所述呼叫资源和所述媒体资源。
在本发明的实施例中，所述呼叫分配模块包括：
第一呼叫分配单元，设置为所述调度器根据所述服务器所属区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
在本发明的实施例中，所述呼叫分配模块包括：
第二呼叫分配单元，设置为在所述区域的呼叫资源中没有空闲的呼叫资源接入节点的情况下，所述调度器根据所述服务器相邻区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
在本发明的实施例中，所述媒体分配模块包括：
第一媒体分配单元，设置为所述调度器根据所述呼叫资源接入节点所属区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
在本发明的实施例中，所述媒体分配模块包括：
第二媒体分配单元，设置为在所述区域的所述媒体资源没有空闲的媒体资源接入节点，所述调度器根据所述呼叫资源接入节点相邻区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
根据本发明的另一个实施例，还提供了一种终端会议负载均衡系统，包括：调度器，服务器，终端；
所述调度器接收所述服务器上报的呼叫资源和媒体资源；
所述调度器接收所述服务器的呼叫资源请求，所述调度器根据所述呼叫资源请求，给所述服务器管理的所述终端分配所述呼叫资源中空闲的呼叫资源接入节点；
所述调度器接收所述呼叫资源接入节点对应的呼叫节点的媒体资源请求，所述调度器根据所述媒体资源请求，给所述终端分配所述媒体资源中的空闲的媒体资源接入节点。
通过本发明，调度器接收服务器上报的呼叫资源和媒体资源，该调度器接收该服务器的呼叫资源请求，该调度器根据该呼叫资源请求，给该服务器管理的终端分配该呼叫资源中空闲的呼叫资源接入节点，该调度器接收该呼叫资源接入节点对应的呼叫节点的媒体资源请求，该调度器根据该媒体资源请求，给该终端分配该媒体资源中的空闲的媒体资源接入节点，解决了视频会议系统接入的用户量有限的问题，满足了大量用户的会议接入。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的一种终端会议负载均衡方法的流程图；
图2是根据本发明实施例的一种终端会议负载均衡装置的结构框图；
图3是根据相关技术中普通两点会议的示意图；
图4是根据相关技术中普通多点会议的示意图；
图5是根据优选实施例中云会议的示意图；
图6是根据优选实施例中云会议的呼叫媒体资源负载均衡的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种终端会议负载均衡方法，图1是根据本发明实施例的一种终端会议负载均衡方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，调度器接收服务器上报的呼叫资源和媒体资源；
步骤S104，调度器接收该服务器的呼叫资源请求，该调度器根据该呼叫资源请求，给该服务器管理的终端分配该呼叫资源中空闲的呼叫资源接入节点；
步骤S106，调度器接收该呼叫资源接入节点对应的呼叫节点的媒体资源请求，该调度器根据该媒体资源请求，给该终端分配该媒体资源中的空闲的媒体资源接入节点。
通过上述步骤，调度器接收服务器上报的呼叫资源和媒体资源，根据接收该服务器的呼叫资源请求和媒体资源请求，给该服务器管理的终端分配空闲的呼叫资源接入节点和空闲的媒体资源接入节点，调度器将该服务器上的呼叫资源和媒体资源进行有效地调配，解决了视频会议系统接入的用户量有限的问题，满足了大量用户的会议接入。
在本发明实施例中，在调度器接收服务器上报的呼叫资源和媒体资源之前，调度器还可以向服务器发送呼叫媒体资源请求，该媒体资源请求用于指示该服务器给该调度器上报该呼叫资源和该媒体资源。还可以该调度器接收该服务器依据预设时间循环上报的该呼叫资源和该媒体资源。
在本实施例中，该调度器给该服务器管理的终端分配该呼叫资源中空闲的呼叫资源接入节点可以有很多种方式，其中，
该调度器可以根据该服务器所属区域的路由配置规则给该终端分配该呼叫资源中空闲的呼叫资源接入节点。
在该区域的呼叫资源中没有空闲的呼叫资源接入节点的情况下，该调度器根据该服务器相邻区域的路由配置规则给该终端分配该呼叫资源中空闲的呼叫资源接入节点。
在本实施例中，该调度器给该终端分配该媒体资源中的空闲的媒体资源接入节点可以有很多种方式，其中，
该调度器可以根据该呼叫资源接入节点所属区域的该媒体资源的分配规则，给该终端分配空闲的媒体资源接入节点。
在该区域的该媒体资源没有空闲的媒体资源接入节点，该调度器根据该呼叫资源接入节点相邻区域的该媒体资源的分配规则，给该终端分配空闲的媒体资源接入节点。
在本实施例中还提供了一种终端会议负载均衡装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图2是根据本发明实施例的一种终端会议负载均衡装置的结构框图，如图2所示，该装置包括
接收模块22，设置为调度器接收服务器上报的呼叫资源和媒体资源；
呼叫分配模块24，设置为该调度器接收该服务器的呼叫资源请求，该调度器根据该呼叫资源请求，给该服务器管理的终端分配该呼叫资源中空闲的呼叫资源接入节点；
媒体分配模块26，设置为该调度器接收该呼叫资源接入节点对应的呼叫节点的媒体资源请求，该调度器根据该媒体资源请求，给该终端分配该媒体资源中的空闲的媒体资源接入节点。
通过上述装置，调度器接收服务器上报的呼叫资源和媒体资源，根据接收该服务器的呼叫资源请求和媒体资源请求，给该服务器管理的终端分配空闲的呼叫资源接入节点和空闲的媒体资源接入节点，调度器将该服务器上的呼叫资源和媒体资源进行有效地调配，解决了视频会议系统接入的用户量有限的问题，满足了大量用户的会议接入。
在本发明实施例中，该装置还包括：
请求模块，设置为调度器向服务器发送呼叫媒体资源请求，该媒体资源请求用于指示该服务器给该调度器上报该呼叫资源和该媒体资源。
上报模块，设置为该调度器接收该服务器依据预设时间循环上报的该呼叫资源和该媒体资源。
在本发明实施例中，该呼叫分配模块24包括：
第一呼叫分配单元，设置为该调度器根据该服务器所属区域的路由配置规则给该终端分配该呼叫资源中空闲的呼叫资源接入节点。
第二呼叫分配单元，设置为在该区域的呼叫资源中没有空闲的呼叫资源接入节点的情况下，该调度器根据该服务器相邻区域的路由配置规则给该终端分配该呼叫资源中空闲的呼叫资源接入节点。
在本发明实施例中，该媒体分配模块26包括：
第一媒体分配单元，设置为该调度器根据该呼叫资源接入节点所属区域的该媒体资源的分配规则，给该终端分配空闲的媒体资源接入节点。
第二媒体分配单元，设置为在该区域的该媒体资源没有空闲的媒体资源接入节点，该调度器根据该呼叫资源接入节点相邻区域的该媒体资源的分配规则，给该终端分配空闲的媒体资源接入节点。
在本发明实施例中，还提供了一种终端会议负载均衡系统，包括：调度器，服务器，终端；
该调度器接收该服务器上报的呼叫资源和媒体资源；
该调度器接收该服务器的呼叫资源请求，该调度器根据该呼叫资源请求，给该服务器管理的该终端分配该呼叫资源中空闲的呼叫资源接入节点；
该调度器接收该呼叫资源接入节点对应的呼叫节点的媒体资源请求，该调度器根据该媒体资源请求，给该终端分配该媒体资源中的空闲的媒体资源接入节点。
下面结合优选实施例和实施方式对本发明进行详细说明。
通过了本发明优选实施例，当云会议中有过多终端接入的时候，可以无缝地把呼叫资源和媒体资源分配到其他空闲资源的服务器上，解决了大量用户并发接入的应用场景
本优选实施例采用的技术方法包括以下步骤：
步骤1.当呼叫媒体资源调度器上电的时候，就向云服务器上电请求呼叫媒体资源上报，云服务器根据云服务器的CPU内核核数、内存等等资源分配了呼叫资源单元和媒体资源单元，并且上报给呼叫媒体资源调度器；
步骤2.当云服务器检测到有会议电视终端接入的时候，就向呼叫媒体资源调度器获取空闲的呼叫资源接入节点，否则就定时间向呼叫媒体调度器请求空闲资源上报；
步骤3.呼叫媒体资源调度器收到呼叫资源接入节点请求消息之后，先根据区号来分配空闲呼叫资源单元，如果区号对应的资源单元已经用满了，则从区域中分配一个空闲的呼叫资源单元，如果区域中无空闲的呼叫资源单元了，则从其他区域中分配接入，如果所有区域的资源都已经用完了，则直接拒绝呼叫接入，否则呼叫媒体资源调度器就把允许接入的呼叫资源的地址告诉终端；
步骤4.终端通过C步骤中分配的呼叫资源接入节点向叫媒体资源调度器获取空闲的媒体资源接入节点；
步骤5.呼叫媒体资源调度器收到媒体节点请求的消息之后，先根据接入媒体能力来选择对应的空闲媒体资源单元，如果找到，呼叫媒体资源调度器把媒体节点的地址告诉终端，否则就直接拒绝接入；
通过上述实施例，在云会议中资源过载的时候，可以均衡分配呼叫资源和媒体资源，使 会议资源得到最优使用，保证用户的大容量并发正常接入。
图3是根据相关技术中普通两点会议的示意图，如图3所示，其中，A和B都是普通终端，因为只是简单点对点的会议，不存在资源用完之后还有终端接入的情况，所以不需要实现呼叫媒体资源负载均衡
图4是根据相关技术中普通多点会议的示意图，如图4所示，其中，A为内置MCU终端或者为MCU，其它都为普通终端，假如普通终端大容量并发接入A，A会存在呼叫资源或者媒体资源不足的情况，造成了无法并发大容量接入普通终端，通过新增内置MCU终端或者MCU的级联方式也无法全面实现业务的可伸缩性，这样会影响其他终端并发大容量接入。
图5是根据优选实施例中云会议的示意图，如图5所示，是云会议的示意图。其中A为资源调度服务器，B1和B2均为1区云服务器，C1和C2均为2区云服务器，D1、E1、F1、G1、H1和L1均为1区的普通终端，D2、E2、F2、G2、H2和L2均为2区的普通终端，当1区的普通终端接入到云会议的时候，A根据路由规则配置找1区的云服务器来接入，当1区的云服务器的呼叫和媒体资源用完之后，可以找2区的云服务器接入，同理，当2区的普通终端接入云会议的时候，A根据路由规则配置找2区的云服务器来接入，当2区的云服务器的呼叫和媒体资源用完之后，可以找1区的云服务器接入。
图6是根据优选实施例中云会议的呼叫媒体资源负载均衡的流程图，如图6所示，呼叫媒体调度器发消息给每个区域的云服务器请求资源上报，每个区域的云服务器根据CPU核数、内存等资源分配了呼叫资源节点和媒体资源节点，并且上报给呼叫媒体调度器，每个区域中的每个云服务器定期检测是否有会议电视终端接入，如没有会议电视终端接入，则定时间循环上报该云服务器的空闲的呼叫资源节点和媒体资源节点，否则，云服务器则向呼叫媒体调度器请求呼叫接入资源节点，呼叫媒体调度器根据云服务器所属的区域的路由配置规则分配了空闲的呼叫接入资源节点，如果该区域没有空闲的呼叫接入资源节点，则从相邻的区域中继续分配，并且通过云服务器返回给终端，该终端通过该呼叫接入资源节点接入，会议电视终端再通过该呼叫接入资源节点向呼叫媒体调度器请求媒体节点，呼叫媒体调度器根据媒体资源分配规则分配了媒体资源节点，也就是先从该呼叫接入资源节点所在的区域中分配了媒体节点，如果该区域中没有空闲的媒体资源节点，则从相邻的区域中分配了媒体资源节点，并且通过该呼叫接入资源节点返回，会议电视终端通过该媒体资源节点传送码流，保证了云会议的正常会议。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被 设置为存储用于执行上述实施例的程序代码：
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述实施例的方法。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，调度器接收服务器上报的呼叫资源和媒体资源，该调度器接收该服务器的呼叫资源请求，该调度器根据该呼叫资源请求，给该服务器管理的终端分配该呼叫资源中空闲的呼叫资源接入节点，该调度器接收该呼叫资源接入节点对应的呼叫节点的媒体资源请求，该调度器根据该媒体资源请求，给该终端分配该媒体资源中的空闲的媒体资源接入节点，解决了视频会议系统接入的用户量有限的问题，满足了大量用户的会议接入。

Claims (15)

  1. 一种终端会议负载均衡方法，包括：
    调度器接收服务器上报的呼叫资源和媒体资源；
    所述调度器接收所述服务器的呼叫资源请求，所述调度器根据所述呼叫资源请求，给所述服务器管理的终端分配所述呼叫资源中空闲的呼叫资源接入节点；
    所述调度器接收所述呼叫资源接入节点对应的呼叫节点的媒体资源请求，所述调度器根据所述媒体资源请求，给所述终端分配所述媒体资源中的空闲的媒体资源接入节点。
  2. 根据权利要求1所述的方法，其中，所述调度器接收服务器上报的呼叫资源和媒体资源之前，所述方法包括：
    调度器向服务器发送呼叫媒体资源请求，所述媒体资源请求用于指示所述服务器给所述调度器上报所述呼叫资源和所述媒体资源。
  3. 根据权利要求1所述的方法，其中，所述调度器接收服务器上报的呼叫资源和媒体资源之前，所述方法包括：
    所述调度器接收所述服务器依据预设时间循环上报的所述呼叫资源和所述媒体资源。
  4. 根据权利要求1所述的方法，其中，所述调度器给所述服务器管理的终端分配所述呼叫资源中空闲的呼叫资源接入节点包括：
    所述调度器根据所述服务器所属区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
  5. 根据权利要求4所述的方法，其中，所述方法包括：
    在所述区域的呼叫资源中没有空闲的呼叫资源接入节点的情况下，所述调度器根据所述服务器相邻区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
  6. 根据权利要求1所述的方法，其中，所述调度器给所述终端分配所述媒体资源中的空闲的媒体资源接入节点包括：
    所述调度器根据所述呼叫资源接入节点所属区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
  7. 根据权利要求6所述的方法，其中，所述方法包括：
    在所述区域的所述媒体资源没有空闲的媒体资源接入节点，所述调度器根据所述呼叫资源接入节点相邻区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
  8. 一种终端会议负载均衡装置，包括：
    接收模块，设置为调度器接收服务器上报的呼叫资源和媒体资源；
    呼叫分配模块，设置为所述调度器接收所述服务器的呼叫资源请求，所述调度器根据所述呼叫资源请求，给所述服务器管理的终端分配所述呼叫资源中空闲的呼叫资源接入节点；
    媒体分配模块，设置为所述调度器接收所述呼叫资源接入节点对应的呼叫节点的媒体资源请求，所述调度器根据所述媒体资源请求，给所述终端分配所述媒体资源中的空闲的媒体资源接入节点。
  9. 根据权利要求8所述的装置，其中，所述装置还包括：
    请求模块，设置为调度器向服务器发送呼叫媒体资源请求，所述媒体资源请求用于指示所述服务器给所述调度器上报所述呼叫资源和所述媒体资源。
  10. 根据权利要求8所述的装置，其中，所述装置还包括：
    上报模块，设置为所述调度器接收所述服务器依据预设时间循环上报的所述呼叫资源和所述媒体资源。
  11. 根据权利要求8所述的装置，其中，所述呼叫分配模块包括：
    第一呼叫分配单元，设置为所述调度器根据所述服务器所属区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
  12. 根据权利要求11所述的装置，其中，所述呼叫分配模块包括：
    第二呼叫分配单元，设置为在所述区域的呼叫资源中没有空闲的呼叫资源接入节点的情况下，所述调度器根据所述服务器相邻区域的路由配置规则给所述终端分配所述呼叫资源中空闲的呼叫资源接入节点。
  13. 根据权利要求12所述的装置，其中，所述媒体分配模块包括：
    第一媒体分配单元，设置为所述调度器根据所述呼叫资源接入节点所属区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
  14. 根据权利要求13所述的装置，其中，所述媒体分配模块包括：
    第二媒体分配单元，设置为在所述区域的所述媒体资源没有空闲的媒体资源接入节点，所述调度器根据所述呼叫资源接入节点相邻区域的所述媒体资源的分配规则，给所述终端分配空闲的媒体资源接入节点。
  15. 一种终端会议负载均衡系统，包括：调度器，服务器，终端；
    所述调度器接收所述服务器上报的呼叫资源和媒体资源；
    所述调度器接收所述服务器的呼叫资源请求，所述调度器根据所述呼叫资源请求， 给所述服务器管理的所述终端分配所述呼叫资源中空闲的呼叫资源接入节点；
    所述调度器接收所述呼叫资源接入节点对应的呼叫节点的媒体资源请求，所述调度器根据所述媒体资源请求，给所述终端分配所述媒体资源中的空闲的媒体资源接入节点。
PCT/CN2016/074582 2015-06-10 2016-02-25 终端会议负载均衡方法、装置及系统 WO2016197628A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16806526.6A EP3293969A4 (en) 2015-06-10 2016-02-25 Method of terminal-based conference load-balancing, and device and system utilizing same
US15/579,951 US10728050B2 (en) 2015-06-10 2016-02-25 Method of terminal-based conference load-balancing, and device and system utilizing same

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510317794.9 2015-06-10
CN201510317794.9A CN106303360A (zh) 2015-06-10 2015-06-10 终端会议负载均衡方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2016197628A1 true WO2016197628A1 (zh) 2016-12-15

Family

ID=57504299

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/074582 WO2016197628A1 (zh) 2015-06-10 2016-02-25 终端会议负载均衡方法、装置及系统

Country Status (4)

Country Link
US (1) US10728050B2 (zh)
EP (1) EP3293969A4 (zh)
CN (1) CN106303360A (zh)
WO (1) WO2016197628A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111352725A (zh) * 2018-12-24 2020-06-30 杭州海康威视系统技术有限公司 存储负载均衡的方法和装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107317825B (zh) * 2017-08-09 2021-03-02 贵阳朗玛信息技术股份有限公司 多人语音会议聊天方法及装置
CN108965372A (zh) * 2017-12-20 2018-12-07 北京视联动力国际信息技术有限公司 一种服务调度方法和装置
CA3037160A1 (en) 2018-03-19 2019-09-19 Mitel Networks Corporation Electronic collaboration and communication method and system
CN110324286B (zh) * 2018-03-30 2022-02-22 视联动力信息技术股份有限公司 一种会议控制系统和方法
NO344692B1 (en) * 2018-06-27 2020-03-09 Pexip AS Automatic deployment of distributed video conference system
CN110475091B (zh) * 2019-08-13 2021-07-09 国家电网有限公司 视频会议的处理方法及装置
CN111432158B (zh) * 2020-02-28 2022-02-08 浙江华创视讯科技有限公司 媒体节点的负载均衡方法及装置、存储介质、电子装置
CN112202755B (zh) * 2020-09-25 2022-08-23 浙江华创视讯科技有限公司 一种服务器分配方法、装置、设备及介质
CN115914539B (zh) * 2022-09-30 2023-11-03 广州云视通科技有限公司 音视频设备资源调度的方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1976435A (zh) * 2006-12-04 2007-06-06 中国联合通信有限公司 一种视频会议中资源调配的方法
CN101047531A (zh) * 2006-03-31 2007-10-03 联想(北京)有限公司 分布式会议系统
US20080112337A1 (en) * 2006-11-10 2008-05-15 Shmuel Shaffer Method and system for allocating, revoking and transferring resources in a conference system
CN102025971A (zh) * 2010-12-15 2011-04-20 广东威创视讯科技股份有限公司 一种视频会议媒体服务器资源的动态分配方法
CN102571686A (zh) * 2010-12-09 2012-07-11 中国科学院沈阳计算技术研究所有限公司 云会议系统的实现方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0219947D0 (en) * 2002-08-28 2002-10-02 Nokia Corp Conferencing system
US8150917B2 (en) * 2006-09-22 2012-04-03 Microsoft Corporation High availability conferencing
US20100034196A1 (en) * 2008-08-08 2010-02-11 Kamala Prasad Das RPH mapping and defaulting behavior
CN101370113B (zh) * 2008-10-08 2010-06-09 广东威创视讯科技股份有限公司 一种视频会议接入媒体服务器的资源管理方法及其装置
CN101707687B (zh) * 2009-11-10 2013-01-16 中兴通讯股份有限公司 一种会议电视业务调度方法和会议电视系统
US20130215215A1 (en) * 2011-11-01 2013-08-22 Teliris, Inc. Cloud-based interoperability platform using a software-defined networking architecture
US20140280595A1 (en) * 2013-03-15 2014-09-18 Polycom, Inc. Cloud Based Elastic Load Allocation for Multi-media Conferencing
WO2014150992A1 (en) * 2013-03-15 2014-09-25 Teliris, Inc. Cloud-based interoperability platform using a software-defined networking architecture
GB2521192B (en) * 2013-12-12 2021-07-21 Metaswitch Networks Ltd Resource allocation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047531A (zh) * 2006-03-31 2007-10-03 联想(北京)有限公司 分布式会议系统
US20080112337A1 (en) * 2006-11-10 2008-05-15 Shmuel Shaffer Method and system for allocating, revoking and transferring resources in a conference system
CN1976435A (zh) * 2006-12-04 2007-06-06 中国联合通信有限公司 一种视频会议中资源调配的方法
CN102571686A (zh) * 2010-12-09 2012-07-11 中国科学院沈阳计算技术研究所有限公司 云会议系统的实现方法
CN102025971A (zh) * 2010-12-15 2011-04-20 广东威创视讯科技股份有限公司 一种视频会议媒体服务器资源的动态分配方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3293969A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111352725A (zh) * 2018-12-24 2020-06-30 杭州海康威视系统技术有限公司 存储负载均衡的方法和装置
CN111352725B (zh) * 2018-12-24 2023-08-18 杭州海康威视系统技术有限公司 存储负载均衡的方法和装置

Also Published As

Publication number Publication date
EP3293969A1 (en) 2018-03-14
CN106303360A (zh) 2017-01-04
US20180227139A1 (en) 2018-08-09
EP3293969A4 (en) 2018-04-25
US10728050B2 (en) 2020-07-28

Similar Documents

Publication Publication Date Title
WO2016197628A1 (zh) 终端会议负载均衡方法、装置及系统
Hoang et al. Optimal admission control policy for mobile cloud computing hotspot with cloudlet
CN110795244B (zh) 一种任务分配方法、装置、设备及介质
US9425972B2 (en) Method, device, and system for establishing cascade of multipoint control servers
US20150317583A1 (en) Business Scheduling Method and Apparatus and Convergence Device
CN110225146B (zh) 内外网映射方法、装置、电子设备、介质及视频会议系统
CN110071965B (zh) 一种基于云平台的数据中心管理系统
US11902108B2 (en) Dynamic adaptive network
US20140379928A1 (en) Method for implementing network using distributed virtual switch, apparatus for performing the same, and network system based on distributed virtual switch
CN109802895B (zh) 数据处理系统、方法及令牌管理方法
WO2016095524A1 (zh) 资源分配方法及装置
WO2016180151A1 (zh) 会议终端权限的控制方法、系统、装置及存储介质
WO2017075967A1 (zh) 在线媒体服务的带宽分配方法及系统
CN111158909A (zh) 集群资源分配处理方法、装置、设备及存储介质
KR20170014804A (ko) 클라우드 서비스를 위한 가상 머신 프로비저닝 시스템 및 방법
US9203706B2 (en) System and method for enabling demand-based pooling of endpoint resources in a multi-application environment
CN107438098B (zh) 一种动态内容分发方法及其系统
WO2018019309A1 (zh) 一种云会议的媒体资源管理方法及装置
KR101237873B1 (ko) 다중 네트워크 인터페이스를 구비한 이동 단말의 네트워크 인터페이스 매핑 방법
RU2522995C2 (ru) Способ и устройство создания одноранговой группы в одноранговом приложении и способ применения одноранговой группы
KR102234089B1 (ko) 컨퍼런스 접속 방법 및 이를 수행하기 위한 단말
JP6511006B2 (ja) リソース割当管理装置および割当て先サーバ決定方法
Taka et al. Joint service placement and user assignment model in multi‐access edge computing networks against base‐station failure
JP2012039325A (ja) ネットワーク制御方法及びシステム
CN117319359A (zh) 一种资源管理方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16806526

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2016806526

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15579951

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE