WO2017215415A1 - 一种资源控制方法、装置和iptv服务器 - Google Patents

一种资源控制方法、装置和iptv服务器 Download PDF

Info

Publication number
WO2017215415A1
WO2017215415A1 PCT/CN2017/085556 CN2017085556W WO2017215415A1 WO 2017215415 A1 WO2017215415 A1 WO 2017215415A1 CN 2017085556 W CN2017085556 W CN 2017085556W WO 2017215415 A1 WO2017215415 A1 WO 2017215415A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
request
node
size
occupied
Prior art date
Application number
PCT/CN2017/085556
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 中兴通讯股份有限公司
Publication of WO2017215415A1 publication Critical patent/WO2017215415A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2385—Channel allocation; Bandwidth allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/242—Synchronization processes, e.g. processing of PCR [Program Clock References]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/26208—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints
    • H04N21/26216—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints involving the channel capacity, e.g. network bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
    • H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet

Definitions

  • IPTV Internet Protocol Television
  • the solution in the related art adopts a centralized resource allocation method, and deploys a load balancing server (LSB) for deployment.
  • LSB load balancing server
  • the LSB plans to configure the size of the resources that can be used by each node in the multiple nodes.
  • Each node periodically reports the size of the resources that can be used by itself and the used resources to the LSB.
  • the user request directly initiates a service location request to the LSB, and the LSB allocates a service node to the user according to the resource condition reported by each node.
  • the node collects the change of the used resource size of the node, and reports the size of the resource that can be used by the node and the size of the used resource to the LSB in the next periodic report.
  • the LSB updates the resource status of the node, and performs policy selection and use when the next user requests.
  • a technical problem to be solved by the embodiments of the present invention is to provide a resource control method and device, and an IPTV server.
  • a centralized resource allocation manner is adopted to make a certain Some users' requests are not processed in time, resulting in poor user experience.
  • an embodiment of the present invention provides a resource control method, including:
  • the size of the remaining resources is determined according to the total resource size, the size of the resources occupied by the node, and the size of the resources occupied by the cooperative processing node;
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, the resource control method being implemented when the computer executable instructions are executed.
  • an embodiment of the present invention provides a resource control apparatus, including:
  • the resource acquisition module is configured to: collect the resource size occupied by the node, obtain the resource size occupied by all the cooperative processing nodes, and the total resource size allocated by the management platform;
  • the remaining resource determining module is configured to: determine the size of the remaining resources according to the total resource size, the resource size occupied by the node, and the resource size occupied by the collaborative processing node;
  • the receiving module is configured to: receive a resource adjustment request
  • the adjustment module is set to: adjust the remaining resources according to the resource adjustment request.
  • an embodiment of the present invention further provides an IPTV server, including the foregoing resource control apparatus.
  • an embodiment of the present invention further provides a computer storage medium.
  • the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the resource control method according to any one of the foregoing.
  • the resource control method and device and the IPTV server acquire the resource size occupied by all the cooperative processing nodes and the total resource size allocated by the management platform by collecting the resource size occupied by the node, according to the total resource size and the local resource size.
  • the size of the resource occupied by the node and the size of the resource occupied by the cooperating processing node determine the size of the remaining resource, receive the resource adjustment request, and adjust the remaining resource according to the resource adjustment request.
  • the resource data synchronization mechanism between nodes is used to synchronize the resource sizes occupied by each node in multiple nodes in time.
  • each node can directly respond to the resource adjustment request, thereby Multi-node distributed resource control is realized.
  • multiple nodes cooperate to process resource allocation, which effectively improves the level of node concurrency control, so that the user's request can be responded in time. Processing efficiency greatly improves the accuracy of node capability control and improves The user experience avoids performance bottlenecks caused by centralized resource control.
  • FIG. 1 is a flowchart of a resource control method according to Embodiment 1 of the present invention.
  • FIG. 2 is a topological relationship diagram according to Embodiment 1 of the present invention.
  • FIG. 3 is a schematic structural diagram of a resource control apparatus according to Embodiment 2 of the present invention.
  • module may implement a combination of software and/or hardware of a predetermined function.
  • this embodiment provides a resource control method. Referring to FIG. 1, the following steps are included:
  • S101 Collect the resource size occupied by the node, obtain the resource size occupied by all the cooperative processing nodes, and the total resource size allocated by the management platform.
  • the node refers to the IPTV server
  • the size of the resource occupied by the local node refers to the size of the resource occupied by the IPTV server.
  • the management platform manages the local node and all the cooperative processing nodes.
  • each node is not pre-allocated a fixed-size allowed resource size, but the management platform allocates a fixed-size total resource size to all nodes.
  • the sum of the resource sizes allowed by each node is the total resource size allocated by the management platform. When resource allocation is performed, only the total remaining resources are considered to be insufficient for the requested resource size.
  • the solution of the embodiment is more flexible in resource allocation when the resource size of the fixed size is allocated to each node in advance in the related art.
  • the management platform manages two nodes, node 1 and node 2, and the total resource size allocated is 5G.
  • Node 1 and node 2 occupy 1G respectively.
  • 3G resources are requested at node 1, and node 1 is determined.
  • node 1 After the total remaining resource size is 3G, node 1 directly allocates the total remaining resources 3G to the requesting party.
  • the collaborative processing node refers to a node that synchronizes resource data between the two nodes and shares the resource size allocated by the same management platform.
  • the management platform manages three nodes, and the management platform allocates to three nodes.
  • the total resource size of each node is 12G, and each node synchronizes the resource size occupied by the node to the other two nodes. In this case, three nodes Interacting with each other as a node.
  • the management platform manages the node and all the co-processing nodes, the management platform allocates the total resource size allowed by the node and all the co-processing nodes. In order to accurately determine the size of the remaining resources, the resource allocation is performed at the node. It is necessary to obtain the resource size occupied by all co-processing nodes.
  • the sequence of three steps of collecting the resource size occupied by the node, obtaining the resource size occupied by all the cooperative processing nodes, and obtaining the total resource size allocated by the management platform may be arbitrary or simultaneous.
  • the size of the resources occupied by the node can be obtained by periodically collecting the performance data related to the service of the node.
  • the collected performance data includes but is not limited to: the central processing unit (cpu) usage rate and memory usage rate of the node.
  • the collected resource size of the node is updated and stored on the node.
  • the resource data synchronization is triggered at the same time, and the node is occupied.
  • the co-processing node updates the resource occupancy on the node after receiving the resource data update synchronization, so that the subsequent resources can be judged and used.
  • the resource data synchronization mechanism between nodes to synchronize the resource sizes occupied by each node in multiple nodes in time.
  • Obtaining the resource size occupied by all the co-processing nodes may include: acquiring the occupied resource size periodically sent by all the co-processing nodes; and/or receiving the occupied resources sent by the co-processing node for the co-processing node with the occupied resource size update Size update information.
  • the node can immediately synchronize the updated resource size to other co-processing nodes, so that other co-processing nodes can know the resource size occupied by all nodes in time, in subsequent processing.
  • the resource adjustment request is made, the allocation of the remaining resources can be more accurate, and the problem of delaying the resource capability control when the multi-node concurrent processing is effectively solved is improved, and the processing efficiency is improved.
  • the acquired resource size of the co-processing node is updated and stored on the local node in time, so that each node of the multiple nodes can be fast when performing the service service. Understand the resource size occupied by the collaborative processing node, effectively solve the problem of delaying the resource capability control when multi-node concurrent processing, and improve the processing efficiency.
  • the management platform can issue a resource size that allows all nodes to use a total of each node, and each node can be stored after receiving it as a basis for subsequent resource judgment.
  • S102 Determine, according to the total resource size, the size of the resource occupied by the node, and the size of the resource occupied by the collaborative processing node, the size of the remaining resource.
  • the size of the remaining resources of all nodes can be obtained by calculating the sum of the resource size occupied by the node and the resource size occupied by the cooperative processing node, obtaining the resource size occupied by all nodes, and then calculating the resource size allowed by all nodes.
  • the difference between the resource sizes occupied by all the nodes obtained above obtains the size of the remaining resources of all the nodes.
  • the amount of remaining resources of all nodes can reflect how many resources all nodes can provide to users.
  • S103 Receive a resource adjustment request, and adjust remaining resources according to the resource adjustment request.
  • the requested service and the required resource size may be parsed to confirm which resource items are needed for the service, for example, the service requested by the user is an on-demand service, and the user needs to occupy 0.1% of the cpu.
  • a plurality of service function modes may be provided to the user, where the resource adjustment request may include an access request, an exit request, a resource enlargement request, and a resource down request.
  • the resource may be allocated from the remaining resources according to the resource size that needs to be adjusted in the request. If the allocation is unsuccessful, the insufficient resource information is fed back to the requesting party, and the requesting party is notified to perform the request redirection.
  • the node may determine whether the remaining resource size is greater than the required resource size; if yes, allocate the current required resource size from the remaining resources.
  • the requesting party reduces the remaining resources; if not, the current service resource application process is terminated, and the respondent's insufficient resource response is returned, and the requesting party goes through the redirecting process.
  • the requesting party is allowed to use the remaining resources at the local node, and when the remaining resources are insufficient to satisfy the required resource size of the requesting party, the insufficient resource information is timely fed back to the request.
  • the party informs the requesting party to perform the request redirection, and the node can directly respond to the resource adjustment request, thereby effectively improving the node concurrency capability control level and improving the processing efficiency.
  • the resource size that needs to be adjusted in the request may be reclaimed from the resources occupied by the node, and is allocated to the remaining resources.
  • the resource size initially allocated to the requesting party may be reclaimed at the local node, so that the remaining resources are increased;
  • the initial allocation may be The resource of the requester is reclaimed from the resource of the requester, so that the remaining resources are increased.
  • the resource size that needs to be adjusted in the request is reclaimed at the local node, and is allocated to the remaining resources, and the node can directly respond to the resource adjustment request, thereby effectively improving the node concurrency capability control level and improving the processing. effectiveness.
  • multiple access requests and/or resource amplification requests may be ordered, and resources are sequentially allocated from remaining resources. If the allocation is unsuccessful, the insufficient resource information may be fed back to the corresponding requesting party.
  • multiple exit requests and/or resource down requests may be sorted, and the exit requests and/or resource adjustments are sequentially retrieved from the resources occupied by the node. The size of the resource that needs to be adjusted in the small request and is included in the remaining resources.
  • the exit request may be preferentially processed; then, the resource is allocated from the remaining resources, and if the allocation is unsuccessful, the insufficient resource information may be fed back to the corresponding requester.
  • the multiple access requests and/or resource amplification requests may be arranged in an order, and the remaining orders are sequentially determined according to the order of the arrangement. Whether the resource is larger than the current required resource size; if yes, the current required resource size is allocated from the remaining resources to the requesting party, so that the remaining resources are reduced; if not, the current service resource application process is terminated, and the requesting party is insufficiently returned. The response, let the requester go through the redirect process.
  • multiple exit requests and/or resource down requests may be sorted in order, and the exit requests are sequentially retrieved from the resources occupied by the node in the order of arrangement. And / or resource down the size of the resource that needs to be adjusted in the request and into the remaining resources.
  • the exit request may be preferentially processed, and the resource size that needs to be adjusted in the exit request is recovered from the resources occupied by the node, and is allocated to the remaining resources. Then processing the access request to determine whether the remaining resources are larger than the current required resource size; if yes, allocating the current required resource size from the remaining resources to the requesting party, so that the remaining resources are reduced; if not, ending the current service resource Apply the process and return a response to the requestor with insufficient resources to let the requester go through the redirect process.
  • the access request and the exit request are received at the same time, and the current remaining resource is 0, the resource required for the access request is 2G, and the required resource for the exit request is 2G, and the exit request is preferentially processed, and the resource occupied by the node is recovered.
  • the size of the resource to be adjusted in the exit request is 2G, and is allocated to the remaining resources.
  • the size of the remaining resources is 2G, and then the access request is processed, and the remaining resources are allocated to the current required resource size 2G to the requesting party.
  • the exit request is processed preferentially, and the size of the remaining resources is ensured when the access request is processed.
  • the N users are allowed to use the remaining resources at the local node, and the remaining resources are insufficient to satisfy the resources required by the N+1th user.
  • the user is informed in time to request the redirection.
  • the node can directly respond to the resource adjustment request, effectively improving the level of node concurrency control, and effectively solving the problem of delaying the resource capability control when the multi-node concurrent processing is performed. , improve processing efficiency.
  • the method may further include: synchronizing the updated resource size occupied by the node All the co-processing nodes are enabled, so that other co-processing nodes can also know the change of the resource occupancy size of the node in time.
  • the management platform manages the three nodes of the first node, the second node, and the third node, and the three nodes perform collaborative processing of resources, and trigger a process of updating the resource size on the first node, and the first node simultaneously
  • the local data after the resource change is synchronized to the second node and the third node, and after receiving the synchronized resource update message, the second node and the third node may update the resource occupancy of the first node stored by the node, and use Subsequent resource judgments are used.
  • the resource occupancy data of the node may be synchronized to the first node and the third node.
  • the node and the third node may update the resource occupation status of the second node stored by the node, so as to facilitate subsequent node resource judgment and use.
  • the order of receiving the resource adjustment request and the S101-S102 can be reversed, any one of the preceding ones, and can be performed in the order of S101-S102-S103, that is, the resource size occupied by the node is collected first, and all the synergies are obtained.
  • the resource adjustment request may be received first, and then the resource size occupied by the node is collected, the resource size occupied by all the cooperative processing nodes, and the total resource size allocated by the management platform are acquired; then, according to the total resource size, the resource size occupied by the node, and Cooperating with the size of the resources occupied by the node, determining the size of the remaining resources; and then adjusting the remaining resources according to the resource adjustment request.
  • the execution bodies of the above S101, S102, and S103 may all be the own nodes, that is, the processing performed by the local node.
  • This embodiment also cites a specific example for explanation. Referring to FIG. 2,
  • the IPTV management platform is responsible for managing the IPTV server node 1 and the IPTV server node 2.
  • the IPTV management platform is a background management platform of the IPTV server node 1 and the IPTV server node 2, and the node 1 and the node 2 are mutually cooperative nodes, so that the node 1 and the node 2 become Organic overall, collaborative control of node resource capabilities.
  • Both node 1 and node 2 include agent access, which is generally responsible for receiving each management instruction in a plurality of management instructions issued by the management platform, and parsing and executing the management instructions.
  • the management platform delivers the bandwidth of the live broadcast service capability of the management platform to the node 1 and the node 2, for example, the bandwidth capability of the live broadcast 12G network port, and the node 1 and the node 2 jointly provide the bandwidth of the 12G network port.
  • each node correspondingly updates and stores the live broadcast service capability that the node 1 and the node 2 jointly allow.
  • Node 1 and Node 2 both use timers to periodically collect the live bandwidth service capabilities currently provided by the node, and store them on the local node and synchronize them to the other node.
  • node 1 currently provides 6G live bandwidth capability
  • node 2 provides 5G.
  • the live broadcast bandwidth capability using the means of synchronizing the cooperative node capability, the node 1 stores the 6G live broadcast bandwidth capability data provided by the node 1, and the node 2 has provided the 5G live broadcast bandwidth capability data; the node 2 also stores the node 2 to provide the 5G live broadcast. Data on bandwidth capabilities, as well as data that Node 1 has provided 6G live bandwidth capabilities.
  • the IPTV user network access is responsible for accessing the IPTV user service network.
  • the signaling branching server is responsible for the distribution processing of the Real Time Streaming Protocol (RTSP) signaling, and the signaling is separately transferred according to the policy.
  • RTSP Real Time Streaming Protocol
  • Different IPTV server nodes. Node 1 and Node 2 also include RTSP access, which is roughly responsible for RTSP protocol processing and service analysis.
  • the network port bandwidth service of 512 M is obtained by analyzing the live broadcast service of the user and the bandwidth required by the user.
  • the service capacity of the 12G service that is allowed to be used by the node 1 and the node 2 on the node 1 and the difference between the bandwidth of the node 1 and the node 2 are 11G, and the service capacity of the remaining bandwidth is 1G, and the user only needs the 512M network port.
  • the bandwidth and node capacity can meet the user's service requirements. Therefore, the node 1 performs resource preemption according to the 512M bandwidth resource, and updates the service capability of the node 1 and changes at the same time.
  • the node 2 After the used bandwidth of 6.5G of the node 1 is synchronized to the node 2, after receiving the synchronization message, the node 2 updates the live broadcast bandwidth usage of the stored node 1 in time 2, so as to facilitate the use of the live broadcast bandwidth resource of the subsequent node.
  • the node 1 stores the 6.5G live bandwidth capability data provided by the node 1, and the node 2 has provided the 5G live bandwidth capability data; the node 2 also stores the data of the node 2 providing the 5G live broadcast bandwidth capability, and the node 1 Data for 6.5G live bandwidth capability has been provided.
  • the user can obtain the bandwidth of the 600M network port by analyzing the live broadcast service of the user and the bandwidth required by the user.
  • Service node 2 through the calculation of the 12G service capacity that node 1 and node 2 jointly allow, and the difference between the bandwidth of node 1 and node 2 used by 11.5G, the remaining bandwidth is 0.5G service capability, and the remaining bandwidth is insufficient. If the network port bandwidth service of the user 600M is provided, the information returned to the user is insufficient, and the user is redirected to the node service.
  • the resource size occupied by the node is collected, and the resource size occupied by all the cooperative processing nodes and the total resource size allocated by the management platform are obtained, according to the total resource size and the resource size occupied by the node. And the size of the resource occupied by the collaborative processing node, determining the remaining resource size, receiving the resource adjustment request, and adjusting the remaining resources according to the resource adjustment request.
  • the resource data synchronization mechanism between nodes is used to synchronize the resource sizes occupied by each node in multiple nodes in time. Through such an efficient resource data synchronization mechanism, each node can directly respond to the resource adjustment request, thereby Multi-node distributed resource control is realized.
  • multiple nodes cooperate to process resource allocation, which effectively improves the level of node concurrency control, so that the user's request can be responded in time.
  • the processing efficiency greatly improves the accuracy of node capability control, improves the user experience, and avoids the performance bottleneck caused by centralized resource control.
  • the present embodiment provides a resource control apparatus.
  • the resource control apparatus 30 can include a processor, and the processor is configured to perform storage.
  • the following module in the memory: the resource obtaining module 301 is configured to: collect the resource size occupied by the node, obtain the resource size occupied by all the cooperative processing nodes, and the total resource size allocated by the management platform.
  • the remaining resource determining module 302 is configured to: determine the size of the remaining resources according to the total resource size, the resource size occupied by the node, and the resource size occupied by the cooperative processing node.
  • the receiving module 303 is configured to: receive a resource adjustment request.
  • the adjustment module 304 is configured to: adjust remaining resources according to the resource adjustment request.
  • the node refers to the IPTV server
  • the size of the resource occupied by the local node refers to the size of the resource occupied by the IPTV server.
  • the management platform manages the local node and all the cooperative processing nodes.
  • each node is not pre-allocated a fixed-size allowed resource size, but the management platform allocates a fixed-size total resource size to all nodes.
  • the sum of the resource sizes allowed by each node is the total resource size allocated by the management platform. When resource allocation is performed, only the total remaining resources are considered to be insufficient for the requested resource size.
  • the solution of the embodiment is more flexible in resource allocation when the resource size of the fixed size is allocated to each node in advance in the related art.
  • the management platform manages two nodes, node 1 and node 2, and the total resource size allocated is 5G.
  • Node 1 and node 2 occupy 1G respectively.
  • 3G resources are requested at node 1, and node 1 is determined.
  • node 1 After the total remaining resource size is 3G, node 1 directly allocates the total remaining resources 3G to the requesting party.
  • the collaborative processing node refers to a node that synchronizes resource data between the two nodes and shares the resource size allocated by the same management platform.
  • the management platform manages three nodes, and the management platform allocates to three nodes.
  • the total resource size of each node is 12G, and each node synchronizes the resource size occupied by the node to the other two nodes. In this case, three nodes Interacting with each other as a node.
  • the management platform manages the node and all the co-processing nodes, the management platform allocates the total resource size allowed by the node and all the co-processing nodes. In order to accurately determine the size of the remaining resources, the resource allocation is performed at the node. It is necessary to obtain the resource size occupied by all co-processing nodes.
  • the synchronization module 305 is further included, and the adjustment module 304 adjusts the remaining according to the resource adjustment request.
  • the updated resource size occupied by the node is synchronized to all the cooperative processing nodes, so that other coordinated processing nodes can also timely understand the change of the resource occupancy size of the node.
  • the resource size occupied by the node can be obtained by periodically collecting the performance data related to the service of the node.
  • the performance data collected by the resource obtaining module 301 includes but is not limited to: the CPU usage rate, memory usage rate, network port traffic, and node of the node. Read and write IO capabilities.
  • the collected resource occupancy size of the node is updated and stored on the node, and when the resource occupancy size of the node is updated, the synchronization module 305 is triggered to synchronize the resource data. Synchronize the resource size occupied by the node to the co-processing node co-processed with the node.
  • the co-processing node After receiving the resource data update synchronization, the co-processing node updates the resource occupancy on the node to facilitate subsequent resource judgment.
  • the resource data synchronization mechanism between nodes to synchronize the resource occupancy of each node in multiple nodes in time.
  • Each of the multiple nodes can quickly understand the resource size occupied by the cooperative processing node, improve the processing efficiency, and greatly improve the accuracy of the node capability control.
  • the resource obtaining module 301 may be configured to: acquire the occupied resource size periodically sent by all the cooperative processing nodes; and/or receive the occupied resource size update information sent by the coordinated processing node for the coordinated processing node that has the occupied resource size update.
  • the node can immediately synchronize the updated resource size to other co-processing nodes, so that other co-processing nodes can know the resource size occupied by all nodes in time, in subsequent processing.
  • the resource adjustment request is made, the allocation of the remaining resources can be more accurate, and the problem of delaying the resource capability control when the multi-node concurrent processing is effectively solved is improved, and the processing efficiency is improved.
  • the resource acquisition module 301 After the resource acquisition module 301 obtains the resource size occupied by all the co-processing nodes, the resource size occupied by the acquired co-processing node is updated and stored on the local node in time, so that each of the multiple nodes is used when performing the service service.
  • the nodes can quickly understand the resource size occupied by the co-processing node, effectively solve the problem of delaying the resource capability control when multi-node concurrent processing, and improve the processing efficiency.
  • the management platform can issue a resource size that allows all nodes to use a total of each node, and each node can be stored after receiving it as a basis for subsequent resource judgment.
  • the remaining resource determining module 302 can obtain the remaining resources of all nodes by calculating the sum of the resource size occupied by the node and the resource size occupied by the cooperative processing node, obtaining the resource size occupied by all nodes, and then calculating the allowed use of all the nodes.
  • Resource size and above The difference between the resource sizes occupied by all the nodes obtained, and the size of the remaining resources of all the nodes.
  • the amount of remaining resources of all nodes can reflect how many resources all nodes can provide to users.
  • the node parses the requested service and the required resource size, and determines which resource items are needed for the service, for example, the service requested by the user is an on-demand service.
  • the user needs to occupy 0.1% of the CPU usage, 2Mb of memory usage, 2Mb of network port outgoing traffic, 2Mb of network port incoming traffic, and 4Mb of node read and write IO capability.
  • a plurality of service function modes may be provided to the user, where the resource adjustment request may include an access request, an exit request, a resource enlargement request, and a resource down request.
  • the adjusting module 304 may be configured to allocate, according to the resource size that needs to be adjusted in the request, from the remaining resources for the access request or the resource enlargement request, and if the allocation is unsuccessful, feed back the insufficient information to the requesting party, and notify the requesting party to make the request. Redirection.
  • the adjusting module 304 is configured to: when the resource adjustment request is an access request or a resource adjustment request, determine, at the local node, whether the remaining resource size is greater than a required resource size; if yes, from the remaining resources. Allocating the current required resource size to the requesting party, so that the remaining resources are reduced; if not, ending the current service resource application process, and returning the responding party with insufficient resource response, and letting the requesting party go through the redirecting process.
  • the requesting party is allowed to use the remaining resources at the local node, and when the remaining resources are insufficient to satisfy the required resource size of the requesting party, the insufficient resource information is timely fed back to the request.
  • the party informs the requesting party to perform the request redirection, and the node can directly respond to the resource adjustment request, thereby effectively improving the node concurrency capability control level and improving the processing efficiency.
  • the adjustment module 304 can be configured to: for the exit request or the resource down request, reclaim the resource size that needs to be adjusted in the request from the resources occupied by the node, and allocate the resource into the remaining resources.
  • the adjusting module 304 is configured to: when the resource adjustment request is an exit request, reclaim the resource size initially allocated to the user at the local node, so that the remaining resources are increased; when the user requests the resource to reduce the request, the The resource initially allocated to the requester reclaims the resource size of the current request adjustment, so that the remaining resources increase.
  • the resource size that needs to be adjusted in the request is reclaimed at the node, and is allocated to the remaining resources, and the node can directly respond to the resource adjustment request, thereby effectively improving the level of node concurrency control and improving the processing efficiency.
  • the adjustment module 304 can be configured to: when the receiving module 303 receives multiple access requests and/or resource amplification requests simultaneously, sorting multiple access requests and/or resource amplification requests And sequentially allocate resources from the remaining resources, and if the allocation is unsuccessful, feedback insufficient information to the corresponding requesting party.
  • the adjustment module 304 can be configured to: when multiple exit requests and/or resource down requests are received at the same time, sort the multiple exit requests and/or the resource down requests, and sequentially withdraw from the resources occupied by the node.
  • the request and/or resource downsizes the size of the resource that needs to be adjusted and allocates it to the remaining resources.
  • the adjusting module 304 may be configured to: when receiving the access request and the exit request, preferentially processing the exit request; and then allocating resources from the remaining resources; if the allocation is unsuccessful, the insufficient resource information is fed back to the corresponding requesting party.
  • the adjusting module 304 is configured to: when the receiving module 303 receives the multiple access requests and/or the resource augmentation requests simultaneously, the multiple access requests and/or the resource adjustment requests are arranged in an order, And determining, according to the order of the arrangement, whether the remaining resources are greater than the current required resource size; if yes, allocating the current required resource size to the requesting party from the remaining resources, so that the remaining resources are reduced; if not, ending the current service resource application The process returns a response to the requestor with insufficient resources, allowing the requestor to go through the redirect process.
  • the adjusting module 304 is configured to: when receiving multiple exit requests and/or resource down requests simultaneously, sorting the multiple exit requests and/or resource down requests in order of arrangement
  • the resources that need to be adjusted in the exit request and/or the resource down request are retrieved from the resources occupied by the node in turn, and are allocated to the remaining resources.
  • the adjusting module 304 is configured to: when receiving the access request and the exit request at the same time, in order to ensure the accuracy of the remaining resources, preferentially processing the exit request, and recovering the exit request from the resources occupied by the node Adjusting the size of the resource and dividing it into the remaining resources; then processing the access request to determine whether the remaining resource is larger than the current required resource size; if yes, allocating the current required resource size from the remaining resources to the requesting party, so that the remaining The resource is reduced; if not, the current service resource application process is terminated, and the response to the requester's insufficient resources is returned, and the requester goes through the redirect process.
  • the access request and the exit request are received at the same time, and the remaining resources are currently 0, and the access is
  • the resource required for the request is 2G
  • the required resource for the exit request is 2G.
  • the adjustment module 304 preferentially processes the exit request, and recovers the resource size 2G that needs to be adjusted in the exit request from the resources occupied by the node, and allocates the remaining resource to the remaining resource.
  • the size of the remaining resources is 2G, and then the access request is processed, and the remaining resources are allocated to the requester by the current required resource size of 2G.
  • the exit request is preferentially processed.
  • the size of the remaining resources is accurate when processing access requests.
  • the N users are allowed to use the remaining resources at the local node, and the remaining resources are insufficient to satisfy the resources required by the N+1th user.
  • the user is informed in time to request the redirection.
  • the node can directly respond to the resource adjustment request, effectively improving the level of node concurrency control, and effectively solving the problem of delaying the resource capability control when the multi-node concurrent processing is performed. , improve processing efficiency.
  • the management platform manages the first node, the second node, and the third node.
  • Three nodes which perform coordinated processing of resources, trigger a process of updating the resource occupancy size on the first node, and the first node simultaneously synchronizes the local data of the current resource to the second node and the third node.
  • the node, the second node, and the third node may update the resource usage of the first node stored by the node, and use it for subsequent resource determination.
  • the resource occupancy data of the node may be synchronized to the first node and the third node.
  • the first node and the third node may update the resource occupation status of the second node stored by the node, so as to facilitate subsequent node resource judgment and use.
  • the resource acquisition module 301 collects the resource size occupied by the node, acquires the resource size occupied by all the cooperative processing nodes, and the total resource size allocated by the management platform, and the remaining resource determining module 302 according to the total
  • the size of the resource, the size of the resource occupied by the node, and the size of the resource occupied by the coordinating node determine the remaining resource size.
  • the receiving module 303 receives the resource adjustment request, and the adjusting module 304 adjusts the remaining resource according to the resource adjustment request.
  • each node can directly respond to the resource adjustment request, thereby Multi-node distributed resource control is realized.
  • multiple nodes cooperate to process resource allocation, which effectively improves the level of node concurrency control, so that the user's request can be responded in time.
  • the processing efficiency greatly improves the accuracy of the node capability control, improves the user experience, and avoids the performance bottleneck caused by centralized resource control.
  • the resource control device may be a device corresponding to the foregoing resource control method, and all the implementation manners in the foregoing method embodiments may be applicable to the embodiment of the device, and the same technical effect can be achieved.
  • an IPTV server including the resource control device 30 in the second embodiment, and all the foregoing nodes may be an IPTV server.
  • a computer storage medium is stored, the computer storage medium storing computer executable instructions for performing the resource control method of any one of the first embodiments.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, the resource control method being implemented when the computer executable instructions are executed.
  • modules or steps of the embodiments of the present invention may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they can be implemented by program code executable by the computing device, so that they can be stored in a storage medium (Read-Only Memory (ROM), Random Access Memory (RAM), The magnetic disk, the optical disk is executed by a computing device, and in some cases, the steps shown or described may be performed in an order different from that herein, or they may be separately fabricated into different integrated circuit modules, or they may be Multiple modules or steps in the fabrication are implemented as a single integrated circuit module. Therefore, embodiments of the invention are not limited to any particular combination of hardware and software.
  • the computer program can be implemented in a computer readable storage medium, the computer program being executed on a corresponding hardware platform (such as a system, device, device, device, processor, etc.), executing Including one or a combination of the steps of the method embodiments.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the resource control method and device and the IPTV server acquire the resource size occupied by all the cooperative processing nodes and the total resource size allocated by the management platform by collecting the resource size occupied by the node, according to the total resource size and the local resource size.
  • the size of the resource occupied by the node and the size of the resource occupied by the cooperating processing node determine the size of the remaining resource, receive the resource adjustment request, and adjust the remaining resource according to the resource adjustment request.
  • the resource data synchronization mechanism between nodes is used to synchronize the resource sizes occupied by each node in multiple nodes in time.
  • each node can directly respond to the resource adjustment request, thereby Multi-node distributed resource control is realized.
  • multiple nodes cooperate to process resource allocation, which effectively improves the level of node concurrency control, so that the user's request can be responded in time.
  • the processing efficiency greatly improves the accuracy of the node capability control, improves the user experience, and avoids the performance bottleneck caused by centralized resource control.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种资源控制方法包括采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小，根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小，接收资源调整请求，根据资源调整请求调整剩余资源。

Description

一种资源控制方法、装置和IPTV服务器 技术领域
本发明实施例涉及但不限于交互式网络电视(IPTV，Internet Protocol Television)领域，尤其是一种资源控制方法、装置和IPTV服务器。
背景技术
在相关技术中的IPTV业务领域中，在为用户分配资源时，相关技术中解决方案中均是采用集中式的资源分配方法，利用部署一台负载均衡服务器(Load Service Blance，简称LSB)来进行并发资源控制。首先LSB规划配置多个节点中每个节点能够使用的资源大小，每个节点会定时上报自身能够使用的资源大小以及已使用资源大小给LSB。当有用户请求时，用户请求会直接向该LSB发起服务定位请求，LSB根据每个节点上报的资源情况，为该用户分配服务节点。用户在节点接受服务后，该节点收集本节点的已使用资源大小变化情况，并在下一次定时上报过程中，将该节点的自身能够使用的资源大小以及已使用资源大小变化情况上报给LSB。LSB收到上报数据后，更新该节点的资源情况，在下一次用户请求时，进行策略选择使用。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例大致解决的技术问题是，提供一种资源控制方法、装置和IPTV服务器，解决相关技术中，当有多个用户同时请求资源的分配时，采用集中式的资源分配方式，使得某些用户的请求处理不及时，造成用户体验差的问题。
为解决上述技术问题，本发明实施例提供一种资源控制方法，包括：
采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小；
根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小；
接收资源调整请求，根据资源调整请求调整剩余资源。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述资源控制方法。
为解决上述技术问题，本发明实施例提供一种资源控制装置，包括：
资源获取模块，设置为：采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小；
剩余资源确定模块，设置为：根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小；
接收模块，设置为：接收资源调整请求；
调整模块，设置为：根据资源调整请求调整剩余资源。
为解决上述技术问题，本发明实施例还提供一种IPTV服务器，包括上述的资源控制装置。
为解决上述技术问题，本发明实施例还提供一种计算机存储介质，计算机存储介质中存储有计算机可执行指令，计算机可执行指令用于执行前述的任一项的资源控制方法。
本发明实施例的有益效果是：
根据本发明实施例提供的资源控制方法、装置和IPTV服务器，通过采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小，根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小，接收资源调整请求，根据资源调整请求调整剩余资源。采用上述方案，利用节点间资源数据同步机制，及时将多个节点中每个节点占用的资源大小进行同步，通过这样高效的资源数据同步机制，每个节点均可以直接响应资源调整请求，由此实现多节点分布式资源控制，当有多个用户同时请求资源的分配时，由多个节点协同进行资源分配的处理，有效提升了节点并发能力控制水平，使得能及时响应用户的请求，提高了处理效率，极大的提高了节点能力控制的准确性，提升 了用户体验，避免了利用集中式资源控制所带来的性能瓶颈问题。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明实施例一提供的一种资源控制方法的流程图；
图2为本发明实施例一提供的拓扑关系图；
图3为本发明实施例二提供的一种资源控制装置的结构示意图。
本发明的较佳实施方式
下面结合附图对本发明的实施方式进行描述。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的各种方式可以相互组合。
需要说明的是，本文中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。
在相关技术中的集中式资源分配方案中，由于所有的用户都要经过LSB进行服务定位，以及所有节点都要上报本节点已使用资源大小到LSB，由此会导致大量的消息集中在LSB处理，而LSB的处理能力是有限的，所以当有多个用户同时请求资源的分配时，LSB会处理不过来，使得不能及时处理某些用户的请求，造成用户体验差。
针对上述问题，提出一种分布式的资源控制方法，是本领域技术人员亟待解决的技术问题。
实施例一
为了避免集中式资源控制所带来的性能瓶颈问题，本实施例提供一种资源控制方法，请参见图1，包括以下步骤：
S101：采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小。
可以理解的是，节点指的是IPTV服务器，采集本节点占用的资源大小是指由IPTV服务器采集自身所占用的资源大小。其中，由管理平台管理本节点和所有协同处理节点，本实施例的方案，每个节点不是预先分配固定大小的允许占用的资源大小，而是由管理平台分配固定大小的总资源大小给所有节点，每个节点允许占用的资源大小之和为管理平台分配的总资源大小，在进行资源分配时，只用考虑总的剩余资源够不够请求的资源大小即可。相对于相关技术中预先给每个节点分配固定大小的允许占用的资源大小，采用本实施例的方案在进行资源分配时更加灵活。例如管理平台管理了节点1、节点2这两个节点，分配的总资源大小为5G，节点1、节点2分别占用了1G，此时在节点1处请求3G的资源，则节点1在确定出总的剩余资源的大小为3G后，节点1直接分配总的剩余资源3G给请求方。
可以理解的是，协同处理节点指的是，两两节点之间有进行资源数据的同步、共享同一个管理平台分配的资源大小的节点，比如管理平台管理了三个节点，管理平台分配给三个节点一共12G的资源大小，这三个节点能使用的最大的资源大小为12G，且每个节点均会将本节点占用的资源大小同步到另两个节点，这种情况下，三个节点互为协同处理节点。
因为是由管理平台管理本节点和所有协同处理节点，由管理平台分配本节点和所有协同处理节点一共允许占用的资源大小，为了准确地确定出剩余资源的大小，在本节点处进行资源分配时，有必要获取所有协同处理节点占用的资源大小。
采集本节点占用的资源大小、获取所有协同处理节点占用的资源大小、获取管理平台分配的总资源大小这三个步骤执行的顺序可以是任意的，也可以是同时进行。
其中，本节点占用的资源大小可以通过定时采集本节点业务相关的性能数据得到，采集的性能数据包括但不限于：本节点的中央处理器(central processing unit，cpu)使用率、内存使用率、网口流量、节点读写磁盘输入输出(Input/Output，IO)能力。在采集到了本节点占用的资源大小之后，将采集到的本节点占用的资源大小更新并存储在本节点上，在更新完本节点占用的资源大小时，同时触发资源数据同步，将本节点占用的资源大小同步 到与本节点协同处理的协同处理节点上，协同处理节点在接收到资源数据更新同步后，对应更新该节点上的资源占用情况，便于后续资源判断使用。为了实现多个节点协同控制资源并发，需要采用节点间资源数据同步机制，及时将多个节点中每个节点占用的资源大小进行同步，通过这样高效的资源数据同步机制，在进行业务服务时，多个节点中每个节点都能快速了解到协同处理节点占用的资源大小，提高了处理效率，极大地提高了节点能力控制的准确性。
获取所有协同处理节点占用的资源大小可包括：获取所有协同处理节点定时发送的占用的资源大小；和/或，对于有占用的资源大小更新的协同处理节点，接收该协同处理节点发送的占用资源大小更新信息。对于有资源大小更新的任何一个协同处理节点，该节点可立即将更新后的资源大小同步到其他协同处理节点，使得其他协同处理节点能及时地了解到所有节点已占用的资源大小，在后续处理资源调整请求时，能对剩余资源的分配更加准确，有效地解决了多节点并发处理过程时，对资源能力控制延迟的问题，提高了处理效率。
在获取到所有协同处理节点占用的资源大小之后，及时将获取到的协同处理节点占用的资源大小更新并存储在本节点上，以便在进行业务服务时，多个节点中每个节点都能快速了解到协同处理节点占用的资源大小，有效地解决了多节点并发处理过程时，对资源能力控制延迟的问题，提高处理效率。
管理平台可以下发允许所有节点一共使用的资源大小给每个节点，每个节点接收到后可进行存储，作为后续资源判断的依据。
S102：根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小。
所有节点的剩余资源的大小可以通过以下计算方法得到：计算本节点的占用的资源大小与协同处理节点占用的资源大小之和，得到所有节点占用的资源大小，然后计算所有节点允许使用的资源大小与上述得到的所有节点占用的资源大小之差，得到所有节点剩余资源的大小。所有节点的剩余资源的多少可以反映出所有节点还能提供给用户多少的资源。
S103：接收资源调整请求，根据资源调整请求调整剩余资源。
在本节点处接收到资源调整请求后，可以对请求的业务和所需资源大小进行解析，确认该业务需要哪些资源项目，比如用户所请求的业务为点播业务，该用户需要占用0.1％的cpu使用率、2Mb的内存占用、2Mb的网口出向流量、2Mb的网口入向流量、4Mb的节点读写IO能力。
为了实现业务功能的多样化、可以提供给用户多种业务功能方式，其中，资源调整请求可以包括接入请求、退出请求、资源调大请求、资源调小请求。
对于接入请求或资源调大请求，可以根据请求中需要调整的资源大小从剩余资源中进行分配，若分配不成功则反馈资源不足信息给请求方，告知请求方进行请求的重定向。
可选地，其中，资源调整请求为接入请求或资源调大请求时，在本节点处可以判断剩余资源大小是否大于所需资源大小；若是，则从剩余资源中分配当前所需资源大小给请求方，使得剩余资源减少；若否，则结束本次业务资源申请流程，并返回给请求方资源不足的应答，让请求方走重定向流程。
通过上述的资源分配方式，在剩余资源充足的情况下，在本节点处允许请求方使用该剩余资源，在剩余资源不足以满足请求方所需资源大小的情况下，及时反馈资源不足信息给请求方，告知请求方进行请求的重定向，该节点可以直接响应资源调整请求，有效提升了节点并发能力控制水平，提高了处理效率。
对于退出请求或资源调小请求，可以从本节点占用的资源中收回请求中需要调整的资源大小，并将其划入剩余资源中。
可选地，其中，资源调整请求为退出请求时，可以在本节点处将初始分配给请求方的资源大小收回，使得剩余资源增加；资源调整请求为资源调小请求时，可以从初始分配给请求方的资源中收回当前请求调整的资源大小，使得剩余资源增加。
通过上述的资源回收方式，在本节点处收回请求中需要调整的资源大小，并将其划入剩余资源中，该节点可以直接响应资源调整请求，有效提升了节点并发能力控制水平，提高了处理效率。
在另一实施例中，当同时接收到多个接入请求和/或资源调大请求时，可以对多个接入请求和/或资源调大请求进行排序，并依次从剩余资源中分配资源，若分配不成功则可以反馈资源不足信息给对应的请求方。当同时接收到多个退出请求和/或资源调小请求时，可以对多个退出请求和/或资源调小请求进行排序，并依次从本节点占用的资源中收回退出请求和/或资源调小请求中需要调整的资源大小，并将其划入剩余资源中。当同时接收到接入请求和退出请求时，可以优先处理退出请求；然后从剩余资源中分配资源，若分配不成功则可以反馈资源不足信息给对应的请求方。
可选地，其中，当同时接收到多个接入请求和/或资源调大请求时，可以对多个接入请求和/或资源调大请求排列顺序，并按照排列的顺序，依次判断剩余资源是否大于当前所需资源大小；若是，则从剩余资源中分配当前所需资源大小给请求方，使得剩余资源减少；若否，则结束本次业务资源申请流程，并返回给请求方资源不足的应答，让请求方走重定向流程。
当同时接收到多个退出请求和/或资源调小请求时，可以对多个退出请求和/或资源调小请求排列顺序，并按照排列的顺序，依次从本节点占用的资源中收回退出请求和/或资源调小请求中需要调整的资源大小，并将其划入剩余资源中。
当同时接收到接入请求和退出请求时，为了保证剩余资源的准确性，可以优先处理退出请求，从本节点占用的资源中收回退出请求中需要调整的资源大小，并将其划入剩余资源中；然后处理接入请求，判断剩余资源是否大于当前所需资源大小；若是，则从剩余资源中分配当前所需资源大小给请求方，使得剩余资源减少；若否，则结束本次业务资源申请流程，并返回给请求方资源不足的应答，让请求方走重定向流程。例如同时接收到接入请求和退出请求，而目前剩余资源为0，接入请求所需资源为2G，退出请求所需调整资源为2G，则优先处理退出请求，从本节点占用的资源中收回退出请求中需要调整的资源大小2G，并将其划入剩余资源中，此时剩余资源的大小为2G，然后处理接入请求，则将剩余资源分配当前所需资源大小2G给请求方，当同时接收到接入请求和退出请求时，优先处理退出请求，保证了在处理接入请求时，剩余资源的大小是准确的。
通过上述的资源分配方式，在剩余资源能够满足N个用户同时使用的情况下，在本节点处允许这N个用户使用该剩余资源，在剩余资源不足以满足第N+1个用户所需资源大小的情况下，及时告知用户进行请求的重定向，该节点可以直接响应资源调整请求，有效提升了节点并发能力控制水平，有效的解决了多节点并发处理过程时，对资源能力控制延迟的问题，提高了处理效率。
若本节点的资源占用大小有变动，为了便于后续资源判断使用，同时也为了提高节点能力控制的实时性和准确性，在S103之后，还可包括：将更新后的本节点占用的资源大小同步到所有协同处理节点，使得其他协同处理节点也能及时了解到本节点的资源占用大小变动情况。
比如管理平台管理了第一节点、第二节点、第三节点这三个节点，这三个节点进行资源的协同处理，在第一节点上触发了一次资源大小更新的流程，第一节点同时将本次资源变动后的本地数据同步到第二节点、第三节点，第二节点、第三节点收到同步的资源更新消息后，可更新本节点存储的第一节点的资源占用情况，用于后续的资源判断使用。
当第二节点上也触发了一次资源大小更新的流程时，第二节点更新完成本节点资源占用情况后，可将本节点的资源占用数据，同步到第一节点、第三节点上，第一节点、第三节点收到第二节点发来的同步的资源更新消息后，可更新本节点存储的第二节点的资源占用情况，便于后续节点资源判断使用。
可以理解的是，接收资源调整请求与S101-S102的顺序是可以颠倒、任何一个在前的，可以是按照S101-S102-S103的顺序执行，即先采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小；然后根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小；然后接收资源调整请求，根据资源调整请求调整剩余资源。也可以是先接收资源调整请求，然后采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小；然后根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小；然后根据资源调整请求调整剩余资源。
上述S101、S102、S103的执行主体可以都是本节点，即都是由本节点所做的处理。
本实施例还列举一个具体的例子进行说明，参见图2，
IPTV管理平台负责管理IPTV服务器节点1和IPTV服务器节点2，IPTV管理平台是IPTV服务器节点1和IPTV服务器节点2的后台管理平台，节点1和节点2互为协同节点，使得节点1、节点2成为有机整体，协同控制节点资源能力。
节点1和节点2中，均包含有代理(Agent)接入，大致负责接收管理平台下发的多项管理指令中每项管理指令，并对管理指令进行解析和执行。管理平台下发本管理平台的直播服务能力带宽配置给节点1和节点2，比如直播12G网口出向带宽能力，则视为节点1、节点2共同提供12G的网口出向带宽能力，节点1、节点2收到后，每个节点对应更新并存储节点1、节点2共同允许使用的直播服务能力。
节点1、节点2均利用定时器，定时收集本节点目前提供的直播带宽服务能力，并存储在本节点上，并同步到对方节点上，比如节点1目前提供6G直播带宽能力，节点2提供5G直播带宽能力，利用协同节点能力同步的手段，节点1上存储有节点1提供的6G直播带宽能力数据，以及节点2已提供5G直播带宽能力的数据；节点2上同样存储有节点2提供5G直播带宽能力的数据，以及节点1已提供6G直播带宽能力的数据。
IPTV用户网络接入是负责接入IPTV用户服务网络的入口，信令分转服务器是负责实时流传输协议(RTSP，Real Time Streaming Protocol)信令的分发处理，按照策略将信令分别分转到不同的IPTV服务器节点上。节点1、节点2中，还包含有RTSP接入，大致负责RTSP协议处理，以及业务分析。
当有1个直播用户通过信令分转服务器呼叫到节点1时，通过解析该用户的直播业务，以及该用户所需的带宽，可以得到其需要512M的网口带宽服务。节点1上通过计算节点1、节点2共同允许使用的12G的服务能力，与节点1、节点2已用带宽总和11G的差值，得到剩余带宽为1G的服务能力，而用户只需要512M网口带宽，节点能力能够满足用户业务需求，因此节点1按照512M的带宽资源进行资源预占，更新节点1的服务能力，并同时将变化 后的节点1的已用带宽6.5G同步给节点2，节点2收到同步消息后，及时在节点2更新存储的节点1的直播带宽使用情况，便于后续节点直播带宽资源限制使用。此时，节点1上存储有节点1提供的6.5G直播带宽能力数据，以及节点2已提供5G直播带宽能力的数据；节点2上同样存储有节点2提供5G直播带宽能力的数据，以及节点1已提供6.5G直播带宽能力的数据。
在此之后，当有1个直播用户通过信令分转服务器呼叫到节点2时，通过解析该用户的直播业务，以及该用户所需的带宽，可以得到该用户所需要的是600M网口带宽服务，节点2通过计算节点1、节点2共同允许使用的12G的服务能力，与节点1、节点2已用带宽总和11.5G的差值，得到剩余带宽为0.5G的服务能力，剩余带宽不足以提供用户600M的网口带宽服务，则返回给用户资源不足的信息，触发用户重新定位节点服务。
根据本发明实施例提供的资源控制方法，通过采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小，根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源大小，接收资源调整请求，根据资源调整请求调整剩余资源。采用上述方案，利用节点间资源数据同步机制，及时将多个节点中每个节点占用的资源大小进行同步，通过这样高效的资源数据同步机制，每个节点均可以直接响应资源调整请求，由此实现多节点分布式资源控制，当有多个用户同时请求资源的分配时，由多个节点协同进行资源分配的处理，有效提升了节点并发能力控制水平，使得能及时响应用户的请求，提高了处理效率，极大地提高了节点能力控制的准确性，提升了用户体验，避免了利用集中式资源控制所带来的性能瓶颈问题。
实施例二
为了避免集中式资源控制所带来的性能瓶颈问题，本实施例提供一种资源控制装置，请参见图3，可以理解的是，该资源控制装置30可以包括处理器，处理器设置为执行存储在存储器中的以下模块：资源获取模块301，设置为：采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小。
剩余资源确定模块302，设置为：根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小。
接收模块303，设置为：接收资源调整请求。
调整模块304，设置为：根据资源调整请求调整剩余资源。
可以理解的是，节点指的是IPTV服务器，采集本节点占用的资源大小是指由IPTV服务器采集自身所占用的资源大小。其中，由管理平台管理本节点和所有协同处理节点，本实施例的方案，每个节点不是预先分配固定大小的允许占用的资源大小，而是由管理平台分配固定大小的总资源大小给所有节点，每个节点允许占用的资源大小之和为管理平台分配的总资源大小，在进行资源分配时，只用考虑总的剩余资源够不够请求的资源大小即可。相对于相关技术中预先给每个节点分配固定大小的允许占用的资源大小，采用本实施例的方案在进行资源分配时更加灵活。例如管理平台管理了节点1、节点2这两个节点，分配的总资源大小为5G，节点1、节点2分别占用了1G，此时在节点1处请求3G的资源，则节点1在确定出总的剩余资源的大小为3G后，节点1直接分配总的剩余资源3G给请求方。
可以理解的是，协同处理节点指的是，两两节点之间有进行资源数据的同步、共享同一个管理平台分配的资源大小的节点，比如管理平台管理了三个节点，管理平台分配给三个节点一共12G的资源大小，这三个节点能使用的最大的资源大小为12G，且每个节点均会将本节点占用的资源大小同步到另两个节点，这种情况下，三个节点互为协同处理节点。
因为是由管理平台管理本节点和所有协同处理节点，由管理平台分配本节点和所有协同处理节点一共允许占用的资源大小，为了准确地确定出剩余资源的大小，在本节点处进行资源分配时，有必要获取所有协同处理节点占用的资源大小。
若本节点的资源占用大小有变动，为了便于后续资源判断使用，同时也为了提高节点能力控制的实时性和准确性，还包括同步模块305，设置为：在调整模块304根据资源调整请求调整剩余资源之后，将更新后的本节点占用的资源大小同步到所有协同处理节点，使得其他协同处理节点也能及时了解到本节点的资源占用大小变动情况。
其中，本节点占用的资源大小可以通过定时采集本节点业务相关的性能数据得到，资源获取模块301采集的性能数据包括但不限于：本节点的cpu使用率、内存使用率、网口流量、节点读写IO能力。在采集到了本节点占用的资源大小之后，将采集到的本节点的资源占用大小更新并存储在本节点上，更新完本节点的资源占用大小时，同时触发同步模块305进行资源数据的同步，将本节点占用的资源大小同步到与本节点协同处理的协同处理节点上，协同处理节点在接收到资源数据更新同步后，对应更新该节点上的资源占用情况，便于后续资源判断使用。为了实现多个节点协同控制资源并发，需要采用节点间资源数据同步机制，及时将多个节点中每个节点的资源占用大小进行同步，通过这样高效的资源数据同步机制，在进行业务服务时，多个节点中每个节点都能快速了解到协同处理节点占用的资源大小，提高了处理效率，极大地提高了节点能力控制的准确性。
资源获取模块301可设置为：获取所有协同处理节点定时发送的占用的资源大小；和/或，对于有占用的资源大小更新的协同处理节点，接收该协同处理节点发送的占用资源大小更新信息。对于有资源大小更新的任何一个协同处理节点，该节点可立即将更新后的资源大小同步到其他协同处理节点，使得其他协同处理节点能及时地了解到所有节点已占用的资源大小，在后续处理资源调整请求时，能对剩余资源的分配更加准确，有效地解决了多节点并发处理过程时，对资源能力控制延迟的问题，提高了处理效率。
在资源获取模块301获取到所有协同处理节点占用的资源大小之后，及时将获取到的协同处理节点占用的资源大小更新并存储在本节点上，以便在进行业务服务时，多个节点中每个节点都能快速了解到协同处理节点占用的资源大小，有效地解决了多节点并发处理过程时，对资源能力控制延迟的问题，提高处理效率。
管理平台可以下发允许所有节点一共使用的资源大小给每个节点，每个节点接收到后可进行存储，作为后续资源判断的依据。
剩余资源确定模块302可以通过以下计算方法得到所有节点的剩余资源：计算本节点的占用的资源大小与协同处理节点占用的资源大小之和，得到所有节点占用的资源大小，然后计算所有节点允许使用的资源大小与上述 得到的所有节点占用的资源大小之差，得到所有节点剩余资源的大小。所有节点的剩余资源的多少可以反映出所有节点还能提供给用户多少的资源。
可选地，在本节点的接收模块303接收到资源调整请求后，本节点会对请求的业务和所需资源大小进行解析，确认该业务需要哪些资源项目，比如用户所请求的业务为点播业务，该用户需要占用0.1％的cpu使用率、2Mb的内存占用、2Mb的网口出向流量、2Mb的网口入向流量、4Mb的节点读写IO能力。
为了实现业务功能的多样化、可以提供给用户多种业务功能方式，其中，资源调整请求可以包括接入请求、退出请求、资源调大请求、资源调小请求。
调整模块304可设置为：对于接入请求或资源调大请求，根据请求中需要调整的资源大小从剩余资源中进行分配，若分配不成功则反馈资源不足信息给请求方，告知请求方进行请求的重定向。
可选地，其中，调整模块304是设置为：资源调整请求为接入请求或资源调大请求时，在本节点处可以判断剩余资源大小是否大于所需资源大小；若是，则从剩余资源中分配当前所需资源大小给请求方，使得剩余资源减少；若否，则结束本次业务资源申请流程，并返回给请求方资源不足的应答，让请求方走重定向流程。
通过上述的资源分配方式，在剩余资源充足的情况下，在本节点处允许请求方使用该剩余资源，在剩余资源不足以满足请求方所需资源大小的情况下，及时反馈资源不足信息给请求方，告知请求方进行请求的重定向，该节点可以直接响应资源调整请求，有效提升了节点并发能力控制水平，提高了处理效率。
调整模块304可设置为：对于退出请求或资源调小请求，从本节点占用的资源中收回请求中需要调整的资源大小，并将其划入剩余资源中。
可选地，其中，调整模块304是设置为：资源调整请求为退出请求时，在本节点处将初始分配给用户的资源大小收回，使得剩余资源增加；用户请求为资源调小请求时，从初始分配给请求方的资源中收回当前请求调整的资源大小，使得剩余资源增加。
通过上述的资源回收方式，在本节点处收回请求中需要调整的资源大小，并将其划入剩余资源，该节点可以直接响应资源调整请求，有效提升了节点并发能力控制水平，提高了处理效率。
在另一实施例中，调整模块304可设置为：当接收模块303同时接收到多个接入请求和/或资源调大请求时，对多个接入请求和/或资源调大请求进行排序；并依次从剩余资源中分配资源，若分配不成功则反馈资源不足信息给对应的请求方。调整模块304可设置为：当同时接收到多个退出请求和/或资源调小请求时，对多个退出请求和/或资源调小请求进行排序，并依次从本节点占用的资源中收回退出请求和/或资源调小请求中需要调整的资源大小，并将其划入剩余资源中。调整模块304可设置为：当同时接收到接入请求和退出请求时，优先处理退出请求；再从剩余资源中分配资源，若分配不成功则反馈资源不足信息给对应的请求方。
可选地，其中，调整模块304是设置为：当接收模块303同时接收到多个接入请求和/或资源调大请求时，对多个接入请求和/或资源调大请求排列顺序，并按照排列的顺序，依次判断剩余资源是否大于当前所需资源大小；若是，则从剩余资源中分配当前所需资源大小给请求方，使得剩余资源减少；若否，则结束本次业务资源申请流程，并返回给请求方资源不足的应答，让请求方走重定向流程。
可选地，其中，调整模块304是设置为：当同时接收到多个退出请求和/或资源调小请求时，对多个退出请求和/或资源调小请求排列顺序，并按照排列的顺序，依次从本节点占用的资源中收回退出请求和/或资源调小请求中需要调整的资源大小，并将其划入剩余资源中。
可选地，其中，调整模块304是设置为：当同时接收到接入请求和退出请求时，为了保证剩余资源的准确性，优先处理退出请求，从本节点占用的资源中收回退出请求中需要调整的资源大小，并将其划入剩余资源中；然后处理接入请求，判断剩余资源是否大于当前所需资源大小；若是，则从剩余资源中分配当前所需资源大小给请求方，使得剩余资源减少；若否，则结束本次业务资源申请流程，并返回给请求方资源不足的应答，让请求方走重定向流程。例如同时接收到接入请求和退出请求，而目前剩余资源为0，接入 请求所需资源为2G，退出请求所需调整资源为2G，则调整模块304优先处理退出请求，从本节点占用的资源中收回退出请求中需要调整的资源大小2G，并将其划入剩余资源中，此时剩余资源的大小为2G，然后处理接入请求，则将剩余资源分配当前所需资源大小2G给请求方，当同时接收到接入请求和退出请求时，优先处理退出请求，保证了在处理接入请求时，剩余资源的大小是准确的。
通过上述的资源分配方式，在剩余资源能够满足N个用户同时使用的情况下，在本节点处允许这N个用户使用该剩余资源，在剩余资源不足以满足第N+1个用户所需资源大小的情况下，及时告知用户进行请求的重定向，该节点可以直接响应资源调整请求，有效提升了节点并发能力控制水平，有效的解决了多节点并发处理过程时，对资源能力控制延迟的问题，提高了处理效率。
为了便于对同步模块305在对更新资源大小后进行同步的过程的理解，下面例举一个例子对更新后进行同步的过程进行说明，管理平台管理了第一节点、第二节点、第三节点这三个节点，这三个节点进行资源的协同处理，在第一节点上触发了一次资源占用大小更新的流程，第一节点同时将本次资源变动后的本地数据同步到第二节点、第三节点，第二节点、第三节点收到同步的资源更新消息后，可更新本节点存储的第一节点的资源占用情况，用于后续的资源判断使用。
当第二节点上也触发了一次资源占用大小更新的流程时，第二节点更新完成本节点资源占用情况后，可将本节点的资源占用数据，同步到第一节点、第三节点上，第一节点、第三节点收到第二节点发来的同步的资源更新消息后，可更新本节点存储的第二节点的资源占用情况，便于后续节点资源判断使用。
根据本发明实施例提供的资源控制装置，通过资源获取模块301采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小，剩余资源确定模块302根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源大小，接收模块303接收资源调整请求，调整模块304根据资源调整请求调整剩余资源。 采用上述方案，利用节点间资源数据同步机制，及时将多个节点中每个节点占用的资源大小进行同步，通过这样高效的资源数据同步机制，每个节点均可以直接响应资源调整请求，由此实现多节点分布式资源控制，当有多个用户同时请求资源的分配时，由多个节点协同进行资源分配的处理，有效提升了节点并发能力控制水平，使得能及时响应用户的请求，提高了处理效率，极大的提高了节点能力控制的准确性，提升了用户体验，避免了利用集中式资源控制所带来的性能瓶颈问题。
需要说明的是，该资源控制装置可以是与上述资源控制方法相对应的装置，其中上述方法实施例中所有实现方式可以均适用于该装置的实施例中，也能达到同样的技术效果。
在另一实施例中还提供一种IPTV服务器，包括实施例二中的资源控制装置30，上述所有节点都可以为IPTV服务器。
在另一实施例中还提供一种计算机存储介质，计算机存储介质中存储有计算机可执行指令，计算机可执行指令用于执行实施例一中任一项的资源控制方法。
本发明实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述资源控制方法。
本领域的技术人员可以明白，上述本发明实施例的模块或步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储介质(只读存储器(ROM，Read-Only Memory)/随机存取存储器(RAM，Random Access Memory)、磁碟、光盘)中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成不同集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。所以，本发明实施例不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本发明实施例所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计 算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件、处理器等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
根据本发明实施例提供的资源控制方法、装置和IPTV服务器，通过采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小，根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小，接收资源调整请求，根据资源调整请求调整剩余资源。采用上述方案，利用节点间资源数据同步机制，及时将多个节点中每个节点占用的资源大小进行同步，通过这样高效的资源数据同步机制，每个节点均可以直接响应资源调整请求，由此实现多节点分布式资源控制，当有多个用户同时请求资源的分配时，由多个节点协同进行资源分配的处理，有效提升了节点并发能力控制水平，使得能及时响应用户的请求，提高了处理效率，极大的提高了节点能力控制的准确性，提升了用户体验，避免了利用集中式资源控制所带来的性能瓶颈问题。

Claims (13)

  1. 一种资源控制方法，包括：
    采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小；
    根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小；
    接收资源调整请求，根据所述资源调整请求调整所述剩余资源。
  2. 如权利要求1所述的资源控制方法，其中，所述资源调整请求包括：接入请求、退出请求、资源调大请求和资源调小请求；所述根据所述资源调整请求调整所述剩余资源包括：
    对于接入请求或资源调大请求，根据请求中需要调整的资源大小从所述剩余资源中进行分配，当分配不成功时，反馈资源不足信息给请求方；
    对于退出请求或资源调小请求，从本节点占用的资源中收回请求中需要调整的资源大小，并将其划入所述剩余资源中。
  3. 如权利要求2所述的资源控制方法，其中，所述根据所述资源调整请求调整所述剩余资源包括：
    当同时接收到多个所述接入请求和/或所述资源调大请求时，对多个所述接入请求和/或所述资源调大请求进行排序，并依次从所述剩余资源中分配资源，当分配不成功时，反馈资源不足信息给对应的请求方。
  4. 如权利要求2所述的资源控制方法，其中，所述根据所述资源调整请求调整所述剩余资源包括：
    当同时接收到所述接入请求和所述退出请求时，优先处理所述退出请求；然后从所述剩余资源中分配资源，当分配不成功时，反馈资源不足信息给对应的请求方；
    当同时接收到多个所述退出请求和/或所述资源调小请求时，对多个所述退出请求和/或所述资源调小请求进行排序，并依次从本节点占用的资源中收回请求中需要调整的资源大小，并将其划入所述剩余资源中。
  5. 如权利要求1-4任一项所述的资源控制方法，在所述根据所述资源调整请求调整所述剩余资源之后，还包括：将更新后的本节点占用的资源大小同步到所有协同处理节点。
  6. 如权利要求1-4任一项所述的资源控制方法，其中，所述获取所有协同处理节点占用的资源大小包括：
    获取所有协同处理节点定时发送的占用的资源大小；
    和/或，对于有占用的资源大小更新的协同处理节点，接收该协同处理节点发送的占用资源大小更新信息。
  7. 一种资源控制装置，包括：
    资源获取模块，设置为：采集本节点占用的资源大小，获取所有协同处理节点占用的资源大小，以及管理平台分配的总资源大小；
    剩余资源确定模块，设置为：根据总资源大小、本节点占用的资源大小以及协同处理节点占用的资源大小，确定出剩余资源的大小；
    接收模块，设置为：接收资源调整请求；
    调整模块，设置为：根据所述资源调整请求调整所述剩余资源。
  8. 如权利要求7所述的资源控制装置，其中，所述资源调整请求包括：接入请求、退出请求、资源调大请求和资源调小请求；
    所述调整模块是设置为：对于接入请求或资源调大请求，根据请求中需要调整的资源大小从所述剩余资源中进行分配，当分配不成功时，反馈资源不足信息给请求方；对于退出请求或资源调小请求，从本节点占用的资源中收回请求中需要调整的资源大小，并将其划入所述剩余资源中。
  9. 如权利要求8所述的资源控制装置，其中，所述调整模块是设置为：当所述接收模块同时接收到多个所述接入请求和/或所述资源调大请求时，对多个所述接入请求和/或所述资源调大请求进行排序，并依次从所述剩余资源中分配资源，当分配不成功时，反馈资源不足信息给对应的请求方。
  10. 如权利要求8所述的资源控制装置，其中，所述调整模块是设置为：当同时接收到所述接入请求和所述退出请求时，优先处理所述退出请求；然后从所述剩余资源中分配资源，当分配不成功时，反馈资源不足信息给对应 的请求方；当同时接收到多个所述退出请求和/或所述资源调小请求时，对多个所述退出请求和/或所述资源调小请求进行排序，并依次从本节点占用的资源中收回请求中需要调整的资源大小，并将其划入所述剩余资源中。
  11. 如权利要求7-10任一项所述的资源控制装置，还包括同步模块，设置为：在所述调整模块根据所述资源调整请求调整所述剩余资源之后，将更新后的本节点占用的资源大小同步到所有协同处理节点。
  12. 如权利要求7-10任一项所述的资源控制装置，其中，所述资源获取模块是设置为：获取所有协同处理节点定时发送的占用的资源大小；
    和/或，对于有占用的资源大小更新的协同处理节点，接收该协同处理节点发送的占用资源大小更新信息。
  13. 一种IPTV服务器，包括如权利要求7-12中任一项所述的资源控制装置。
PCT/CN2017/085556 2016-06-13 2017-05-23 一种资源控制方法、装置和iptv服务器 WO2017215415A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610410078.X 2016-06-13
CN201610410078.XA CN107493485B (zh) 2016-06-13 2016-06-13 一种资源控制方法、装置和iptv服务器

Publications (1)

Publication Number Publication Date
WO2017215415A1 true WO2017215415A1 (zh) 2017-12-21

Family

ID=60642740

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085556 WO2017215415A1 (zh) 2016-06-13 2017-05-23 一种资源控制方法、装置和iptv服务器

Country Status (2)

Country Link
CN (1) CN107493485B (zh)
WO (1) WO2017215415A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113630628A (zh) * 2020-05-07 2021-11-09 杭州海康威视数字技术股份有限公司 一种媒体流发送方法、系统、处理设备及存储介质
CN115174395A (zh) * 2022-07-01 2022-10-11 深圳致星科技有限公司 基于隐私计算平台的资源配置调整方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109728933B (zh) * 2018-11-21 2021-09-24 电信科学技术第五研究所有限公司 分布式应用软件网络流量控制方法
CN112506654B (zh) * 2020-12-07 2023-07-18 中国船舶集团有限公司第七一六研究所 一种工业机器人分布式协同调试方法及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060095917A1 (en) * 2004-11-01 2006-05-04 International Business Machines Corporation On-demand application resource allocation through dynamic reconfiguration of application cluster size and placement
CN101365103A (zh) * 2007-08-06 2009-02-11 中国科学院声学研究所 一种有线电视网络互动业务的管理方法
CN101697548A (zh) * 2009-10-23 2010-04-21 中兴通讯股份有限公司 节点协作的实现方法和管理系统
CN104731657A (zh) * 2013-12-24 2015-06-24 中国移动通信集团山西有限公司 一种资源调度方法和系统
CN104836819A (zh) * 2014-02-10 2015-08-12 阿里巴巴集团控股有限公司 动态负载均衡的方法、系统及监控调度设备
CN105323650A (zh) * 2014-06-27 2016-02-10 中兴通讯股份有限公司 带宽控制方法、iptv终端设备及通信系统

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6229795B1 (en) * 1999-01-13 2001-05-08 Qualcomm Incorporated System for allocating resources in a communication system
CN1254937C (zh) * 2003-07-01 2006-05-03 大唐移动通信设备有限公司 时分复用同步码分多址系统中物理信道帧分配的方法
CN100338911C (zh) * 2004-04-30 2007-09-19 武汉烽火网络有限责任公司 网际协议电信网上动态带宽分配的方法和装置
KR100686157B1 (ko) * 2005-05-04 2007-02-26 엘지전자 주식회사 디지털 멀티미디어 데이터 녹화기능을 갖는 이동 단말기 및 이를 이용한 디지털 멀티미디어 데이터 녹화방법
US8612330B1 (en) * 2010-09-14 2013-12-17 Amazon Technologies, Inc. Managing bandwidth for shared resources
US8533103B1 (en) * 2010-09-14 2013-09-10 Amazon Technologies, Inc. Maintaining latency guarantees for shared resources
CN102014159A (zh) * 2010-11-29 2011-04-13 华中科技大学 一种云计算环境下的分层资源预留系统
CN102833289B (zh) * 2011-06-16 2016-02-17 浙江速腾电子有限公司 一种分布式云计算资源组织和任务分配方法
US9183016B2 (en) * 2013-02-27 2015-11-10 Vmware, Inc. Adaptive task scheduling of Hadoop in a virtualized environment
CN104079503B (zh) * 2013-03-27 2018-07-20 华为技术有限公司 一种资源分配方法及装置
CN104348754B (zh) * 2013-07-26 2019-08-23 中兴通讯股份有限公司 一种光突发环网的带宽分配方法和装置
CN104469960B (zh) * 2013-09-25 2019-12-10 中兴通讯股份有限公司 调度配置方法与装置
CN104639594A (zh) * 2013-11-15 2015-05-20 中国电信股份有限公司 分配物理资源和虚拟资源的系统和方法
CN104754008B (zh) * 2013-12-26 2019-03-08 伊姆西公司 网络存储节点、网络存储系统以及用于网络存储节点的装置和方法
CN104750558B (zh) * 2013-12-31 2018-07-03 伊姆西公司 在分层配额系统中管理资源分配的方法和装置
CN105373492A (zh) * 2014-08-19 2016-03-02 西安慧泽知识产权运营管理有限公司 一种面向任务流的基于寄存器文件的快速数据交换结构
CN105516214B (zh) * 2014-09-22 2020-05-15 电信科学技术研究院 一种车联网系统中的信息上报和资源分配方法、装置
CN104881325B (zh) * 2015-05-05 2018-09-21 中国联合网络通信集团有限公司 一种资源调度方法和资源调度系统
CN105068874B (zh) * 2015-08-12 2018-11-30 国家电网公司 一种结合Docker技术的资源按需动态分配方法
CN111865657B (zh) * 2015-09-28 2022-01-11 华为技术有限公司 一种加速管理节点、加速节点、客户端及方法
CN105357322B (zh) * 2015-12-11 2019-04-26 中国科学院信息工程研究所 一种基于拓扑划分的虚拟机分配方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060095917A1 (en) * 2004-11-01 2006-05-04 International Business Machines Corporation On-demand application resource allocation through dynamic reconfiguration of application cluster size and placement
CN101365103A (zh) * 2007-08-06 2009-02-11 中国科学院声学研究所 一种有线电视网络互动业务的管理方法
CN101697548A (zh) * 2009-10-23 2010-04-21 中兴通讯股份有限公司 节点协作的实现方法和管理系统
CN104731657A (zh) * 2013-12-24 2015-06-24 中国移动通信集团山西有限公司 一种资源调度方法和系统
CN104836819A (zh) * 2014-02-10 2015-08-12 阿里巴巴集团控股有限公司 动态负载均衡的方法、系统及监控调度设备
CN105323650A (zh) * 2014-06-27 2016-02-10 中兴通讯股份有限公司 带宽控制方法、iptv终端设备及通信系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113630628A (zh) * 2020-05-07 2021-11-09 杭州海康威视数字技术股份有限公司 一种媒体流发送方法、系统、处理设备及存储介质
CN115174395A (zh) * 2022-07-01 2022-10-11 深圳致星科技有限公司 基于隐私计算平台的资源配置调整方法及装置

Also Published As

Publication number Publication date
CN107493485A (zh) 2017-12-19
CN107493485B (zh) 2021-11-05

Similar Documents

Publication Publication Date Title
US8819080B2 (en) System and method for collection, retrieval, and distribution of data
EP3669273B1 (en) Routing and filtering event notifications
WO2017215415A1 (zh) 一种资源控制方法、装置和iptv服务器
EP3296870A1 (en) Cdn-based content management system
US20020131423A1 (en) Method and apparatus for real-time parallel delivery of segments of a large payload file
CN102244685A (zh) 一种支持负载均衡的分布式缓存动态伸缩方法及系统
CN107451853B (zh) 一种红包实时派发的方法、装置、系统及存储介质
CN106375471B (zh) 一种边缘节点确定方法及装置
CN112468310B (zh) 流媒体集群节点管理方法、装置及存储介质
CN104202386B (zh) 一种高并发量分布式文件系统及其二次负载均衡方法
WO2016045367A1 (zh) 一种多数据源数据融合的方法及装置
Kothari et al. Dqs-cloud: A data quality-aware autonomic cloud for sensor services
CN111475315A (zh) 服务器及订阅通知推送控制、执行方法
JP2014531072A (ja) 多数のデバイスへのイベントの配信
WO2017045640A1 (zh) 一种数据中心内关联流的带宽调度方法及装置
CN113364888B (zh) 服务调度方法、系统、电子设备及计算机可读存储介质
US11606415B2 (en) Method, apparatus and system for processing an access request in a content delivery system
CN114610765B (zh) 流计算方法、装置、设备及存储介质
CN112995241A (zh) 服务调度方法和装置
WO2024188037A1 (zh) 函数缓存的方法及系统
CN116800666A (zh) 一种路由信息同步方法及相关设备
CN112596875A (zh) 数据批量处理方法和装置
CN114285745A (zh) 一种节点更新方法和装置
CN118631705A (zh) 一种数据流的状态参数获取方法、系统及计算机程序产品
Bonthu et al. An Adaptive Downloading Service from Object Storage Cloud

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17812526

Country of ref document: EP

Kind code of ref document: A1