WO2015062492A1 - 一种业务处理方法、系统及设备 - Google Patents
一种业务处理方法、系统及设备 Download PDFInfo
- Publication number
- WO2015062492A1 WO2015062492A1 PCT/CN2014/089759 CN2014089759W WO2015062492A1 WO 2015062492 A1 WO2015062492 A1 WO 2015062492A1 CN 2014089759 W CN2014089759 W CN 2014089759W WO 2015062492 A1 WO2015062492 A1 WO 2015062492A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- slave
- processing
- master device
- remaining
- service
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/781—Centralised allocation of resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
-
- 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/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
Definitions
- the present invention relates to the field of computer technologies, and in particular, to a service processing method, system, and device.
- IPCs IP Camra
- IP Camra IP Camra
- these IPCs have a large number of physical and spatial distribution characteristics, and each IPC individual has relatively weak analysis and processing capabilities, and cannot complete complex intelligent analysis independently except for completing its own video collection and simple processing and code stream transmission, or Computationally intensive features such as transcoding. Therefore, you need to set up a dedicated server on the back end of the system to complete these complex calculations.
- the server at the back end of the system adopts a centralized or distributed intensive processing method, and uses a server stacking method to complete complex calculations through high-intensity processing.
- the embodiment of the invention provides a service processing method, system and device, which can save a large number of system back-end servers and simplify the structure of the distributed system.
- a service processing method for use in a video surveillance system, including:
- the master device in the resource pool receives the service processing request
- the master device allocates the service to the corresponding slave device for processing
- the master device and the slave device are video surveillance front-end devices, and the master device determines, as the slave device, the device in which the remaining resources of the front-end device meet the preset threshold, the master device and the slave device. Form the resource pool.
- the master device determines, as the slave device, a device that meets a preset threshold in a remaining resource of the front-end device, where the master device and the slave device are configured.
- the resource pool including:
- the front-end device converts the remaining resources of the user into a corresponding remaining processing capability value according to the preset remaining capability reference, and reports the remaining processing capability value to the master device;
- the master device and the slave device form the resource pool.
- the master device determines resources required by the service, and determines, according to remaining resources of each slave device in the resource pool, that the service is required to meet the service
- the slave device of the resource includes:
- the master device divides the task into multiple subtasks according to various processing capabilities required by the task, according to the size of the corresponding processing capability required to complete the multiple subtasks, and the remaining of the slave device. Processing capability, assigning a corresponding number of the slave devices to complete the plurality of subtask processing.
- the master device allocates the service to the corresponding the slave device for processing, including:
- the master device sends, to the video storage module in the video monitoring system, the allocated slave device list and the corresponding mapping relationship between the respective slave devices and the subtasks in the list;
- the master device receives the processing result reported by each of the allocated slave devices, where the allocated slave devices send a video data acquisition request to the video storage module to obtain a video code required for processing the subtask Flow, perform corresponding video processing, and send the processing result to the master device;
- the master device summarizes the processing results reported by the allocated slave devices.
- the method further includes:
- the slave device is excluded from the resource pool.
- the method further includes:
- one of the plurality of slave devices is reselected to select an idle slave device as the master device.
- a second aspect provides a service processing system, which is applied to a video surveillance system, including: a master device and a slave device, wherein the master device and the slave device form a resource pool, wherein the master device and the slave device are both video.
- Monitoring a front-end device the master device determining, as the slave device, a device in which the remaining resources of the front-end device meet a preset threshold; the master device is configured to receive a service processing request; determining resources required by the service, and Determining, according to remaining resources of each slave device in the resource pool, the slave device that meets the resource required by the service; and assigning the service to the corresponding slave device for processing.
- the determining, by the master device, that the device in the front-end device that the remaining resources meet the preset threshold is the implementation manner of the slave device includes:
- the front-end device converts the remaining resources of the user into a corresponding remaining processing capability value according to the preset remaining capability reference, and reports the remaining processing capability value to the master device;
- the master device and the slave device form the resource pool.
- the master device determines resources required by the service, and determines, according to remaining resources of each slave device in the resource pool, that the service is required to meet the service
- the slave device of the resource includes:
- the master device divides the task into multiple subtasks according to various processing capabilities required by the task, according to the size of the corresponding processing capability required to complete the multiple subtasks, and the remaining of the slave device. Processing capability, assigning a corresponding number of the slave devices to complete the plurality of subtask processing.
- the master device allocates the service to the corresponding the slave device for processing, and the implementation manner includes:
- the master device sends, to the video storage module in the video monitoring system, the allocated slave device list and the corresponding mapping relationship between the respective slave devices and the subtasks in the list;
- the master device receives the processing result reported by each of the allocated slave devices, where the allocated slave devices send a video data acquisition request to the video storage module to obtain a video code required for processing the subtask Flow, perform corresponding video processing, and send the processing result to the master device;
- the master device summarizes the processing results reported by the allocated slave devices.
- the master device is further configured to:
- the slave device When it is determined that each of the remaining processing capability values of the slave device is lower than a preset capability threshold, the slave device is culled out of the resource pool.
- a fifth possible implementation manner when the master device fails, select one of the multiple slave devices by reselecting The idle slave device acts as the master device.
- a video surveillance front-end device for use in a video surveillance system, including:
- a video collection unit for collecting video data
- a receiving unit configured to receive a service processing request when the video monitoring front-end device is a master device, and receive a service allocated by the master device when the video monitoring front-end device is a slave device;
- a remaining resource feedback unit configured to send the remaining resources of the master device to the primary device
- a slave determining unit configured to determine, when the video monitoring front-end device is a master device, a device that meets a preset threshold in the front-end device as the slave device;
- a processing unit configured to determine, according to a service processing request, a resource required by the service according to a service processing request, and determine, according to a remaining resource of each slave device in the resource pool, a service that is required to meet the service
- the slave device of the resource the service is allocated to the corresponding slave device for processing; and when the video surveillance front-end device is a slave device, the service allocated by the master device is processed;
- the master device is a video monitoring front-end device, and the master device and the slave device form the resource pool.
- the specific implementation manner of the remaining resource feedback unit is: converting the remaining resources of the video front-end device itself into corresponding residuals according to a preset remaining capability reference. Processing the capability value, and reporting the remaining processing capability value to the slave device determining unit of the master device;
- the slave device determining unit of the master device is configured to determine, as the slave device, the front end device whose remaining processing capability value meets a preset capability threshold.
- the specific implementation manner of the processing unit includes:
- each of the allocated slave devices receives the processing result reported by each of the allocated slave devices, wherein each of the allocated slave devices sends a video data acquisition request to the video storage module to acquire a video code stream required to process the subtask, and perform corresponding Video processing and sending the processing result to the master device;
- the processing unit is further configured to:
- the slave device When it is determined that each of the remaining processing capability values of the slave device is lower than a preset capability threshold, the slave device is culled out of the resource pool.
- the processing unit is further configured to:
- one of the plurality of slave devices is reselected to select an idle slave device as the master device.
- the master device is determined in the front-end device of the distributed system, and the master device determines the device whose remaining resources in the front-end device meet the preset threshold as the slave device, and then the master device and the slave device form a resource pool.
- the device may determine the slave device that meets the resources required by the service according to the resources required by the service, and according to the remaining resources of each slave device in the resource pool, so that the master device allocates the service to the corresponding slave device. Process it.
- FIG. 1 is a flowchart of an embodiment of a service processing method provided by the present invention
- FIG. 3 is a schematic diagram of a processing flow in an IPC companion line detection scenario provided by the present invention.
- FIG. 4 is a schematic flowchart of a process for performing video summary analysis by using IPC according to the present invention
- FIG. 5 is a schematic structural diagram of a service processing system provided by the present invention.
- a flow of a service processing method according to an embodiment of the present invention is applied to a video monitoring system, where the service processing process may specifically include:
- Step 101 The master device in the resource pool receives a service processing request.
- a plurality of front-end devices are usually disposed at the front end of the distributed system, and the front-end device is connected to the client for receiving user-initiated service processing requests, performing simple data processing, and performing complex analysis and calculation processes. This is done by a back-end dedicated server connected to the front-end device.
- the CPU occupancy rate is usually 10% to 30%
- the memory idle is generally within 100 MB
- the network bandwidth utilization is less than 10%
- the audio and video codec resources are generally used. 50%.
- the CPU usage is limited to 70%
- the bandwidth usage is 80%
- the codec is 100%
- the memory idle is about 10M. It can be seen that each front-end device has considerable free resources that can be utilized.
- the remaining resources of the front-end equipment in the distributed system are fully utilized, and the remaining resources are used for service processing, thereby saving the server at the back end of the system.
- one of the front-end devices is configured as a master device, and the master device determines, as the slave device, a device in which the remaining resources of the front-end device meet the preset threshold, and the master device and the slave device form a resource pool.
- the user When service processing is required, the user initiates a service processing request to the master device.
- Step 102 The master device determines resources required by the service, and according to each of the resource pools The remaining resources of the slave device determine the slave device that meets the resources required by the service.
- the primary device After the primary device receives the service processing request, it needs to determine the resources required by the service processing process, and then, according to the remaining resources of each slave device in the resource pool, determine the slave device that meets the resource requirement to perform the service. Processing until the sum of the remaining resources of the determined slave device meets the resources required by the service process.
- Step 103 The master device allocates the service to a corresponding slave device for processing.
- the service may be allocated to the corresponding slave device, and the corresponding slave device performs a specific service processing operation.
- the master device is determined in the front-end device of the distributed system, and the master device determines the device whose remaining resources in the front-end device meet the preset threshold as the slave device, and then the master device and the slave device form a resource pool.
- the device may determine the slave device that meets the resources required by the service according to the resources required by the service, and according to the remaining resources of each slave device in the resource pool, so that the master device allocates the service to the corresponding slave device. Process it.
- the master device determines, as the slave device, a device in which the remaining resources of the front-end device meet the preset threshold, and the master device and the slave device form the resource pool.
- the implementation can be as shown in Figure 2, including the following steps:
- Step 201 The front-end device converts the remaining resources of the user into the corresponding remaining processing capability value according to the preset remaining capability reference, and reports the remaining processing capability value to the master device.
- Step 202 The master device determines, as the slave device, the front end device whose remaining processing capability value meets a preset capability threshold.
- Step 203 The master device and the slave device form the resource pool.
- all the front-end devices except the master device need to report their remaining resource status to the master device.
- the remaining resources of the master device may be converted into The corresponding remaining processing capability value indicates the size of the corresponding capability by the corresponding remaining capacity value. And reporting the remaining processing capability value to the master device.
- the master device compares the remaining processing capability data reported by each front-end device with the preset capability threshold, determines the front-end device whose remaining processing capability value meets the preset capability threshold as the slave device, and includes the slave device Resource pool.
- the IPC also deploys distributed processing management software and installs software that can collect and report local resources (defined as the agent module) in all IPC clusters. You can select the master device, which is used to collect the remaining resources of each IPC.
- the master device can also be an out-of-domain device outside the IPC, and only the module for statistical analysis needs to be installed in the device.
- the resource management adopts the master-slave mode.
- the agent is responsible for collecting the remaining resource information of the device and reporting it to the master.
- the master manages each resource device and is responsible for the IPC access resource pool and task assignment.
- Each IPC agent converts the calculated residual capacity Ci of its own device into a calculated residual capacity value according to the customized remaining capability benchmark. Similarly, the memory remaining capacity is converted into a value Mo, and the network remaining bandwidth processing capability is converted into a value Wp, and the code remaining capacity is converted.
- the value Bj is converted into a value Dk, the remaining capacity of the encryption is converted into a value E1, the remaining capacity of the decryption is converted into a value DEm, and the remaining capacity is converted into a capability data such as a value Sq, which is sent to the Master through a message.
- the Master models the resources according to the distribution of resources of each IPC device, and lists the various resources of each IPC device, such as computing resources, codec resources, storage resources, encryption and decryption resources, etc., for management.
- the master calculates the remaining available capacity of each task device, and compares it with the predetermined capability thresholds to determine whether to include the task device in the resource pool.
- the rule is that if the remaining available capacity is higher than the capability threshold, the resource may be included in the resource pool. Specifically, it may be set to include the IPC in the resource pool as long as a capability preset is met, and is not allowed to be included in the resource pool when all remaining available capabilities are lower than the corresponding capability threshold.
- Each capability threshold can use a set of test experience values by default, and can also provide several typical values and be configured in different scenarios.
- the device task device can send a message to the master to report the remaining resources of the device at a fixed time. If the master does not receive a message from a task device, the master device can be kicked out of the resource pool.
- Codec remaining capacity Codec frame number (total) Codec frame number (used);
- the capability set layer is configured in the master device to classify the remaining physical resources into logical capability resources, and may include: calculating a remaining capability set, a codec remaining capability set, an encryption and decryption remaining capability set, a storage remaining capability set, and a network bandwidth remaining capability.
- the calculated residual capacity data of multiple IPCs is as follows:
- Nc is the calculated residual capacity value for serializing the calculated remaining capacity of n IPCs
- Ca is the benchmark of the capability (based on the computational power consumed by the single frame processing)
- Ci is the calculated residual capacity value reported by each IPC.
- Ca, Ba, Da, Ea, DEa, Sa, Ma, and Wa are the remaining capability reference values of the respective capabilities, and the previous coefficient may be 0, indicating that the capability is not used. According to this formula, the nominal value of each capability required for the service can be derived.
- resource pool's business capabilities are as follows:
- Nc, Nb, Nd... is the total capacity of the resource pool after serialization
- i, j, k... is the number of corresponding capabilities that need to be consumed to complete a certain service
- Pn is the service processing capability of each item. According to this, the video processing capability of the resource pool for each service can be obtained.
- the master device divides the task into multiple subtasks according to various processing capabilities required by the task, according to the size of the corresponding processing capability required to complete the multiple subtasks, and the slave device. Remaining processing capability, assigning a corresponding number of said slave devices to complete said plurality of sub- Processing.
- the master device sends the corresponding subtask to each of the allocated slave devices; the master device sends the allocated slave device list and the respective slaves in the list to the video storage module in the video monitoring system. Corresponding relationship between the device and the subtask; the master device receives the processing result reported by each of the allocated slave devices, wherein each of the allocated slave devices sends a video data acquisition request to the video storage module, Obtaining a video code stream required for processing the subtask, performing corresponding video processing, and transmitting the processing result to the master device; finally, the master device sums the processing results reported by the allocated slave devices.
- the primary device is mainly used for resource allocation, and the determining manner may include multiple types, for example, the first enabled device is used as a primary device, and the device performs resources on devices that are subsequently added to the resource pool. distribution.
- One of the free slave devices in the resource pool can be re-elected as the master device by means of election.
- election There are a plurality of types of elections, which are not specifically limited in this embodiment of the present invention. Those skilled in the art can perform specific settings according to actual application scenarios, for example, selecting the device with the largest CPU capability as the master device.
- device backups can be made to the primary device, including hot or cold backups.
- the number of backups of the primary device can be configured by the user.
- hot backup the data is backed up synchronously; when the primary device is damaged or stops working for other reasons during cold backup, the cold device re-broadcasts the command to each slave device to obtain resource information and manage resources.
- the storage device connected to the IPC device in the resource pool.
- the storage device can be directly connected to the resource pool or external to the resource pool.
- the first application scenario is IPC Companion Detection.
- the specific processing process is shown in Figure 3:
- Step 301 The user (user) starts the line detection process by using a CU (Client Unit).
- Step 302 The CU sends a line detection task to the master device in the resource pool.
- Step 303 The master analyzes the task size and type, and calculates and allocates a corresponding number of slave devices.
- the master can divide the task into multiple tasks according to various processing capabilities required. a subtask, and then according to the size of each corresponding capability required to complete the task, and the remaining processing capability of the device, allocating the slave device capable of completing the processing of each subtask, and then assigning the corresponding subtask to executing the subtask
- the slave devices, the corresponding capabilities include: computing remaining capacity, codec remaining capacity, encryption and decryption remaining capacity, storage remaining capacity, network bandwidth remaining capacity, and memory remaining capacity.
- Step 304 The master sends a corresponding subtask to the agent in the corresponding slave device.
- Step 305 The agent receiving the subtask sends a subtask that needs to be processed by the module to a control processing module (referred to herein as control) in the IPC.
- control a control processing module
- Step 306 The master reports to the video storage module the slave device list that performs the task and the assignment relationship between the slave devices and the subtasks in the list, so that the IPC accesses the video storage module to obtain the required video data.
- Step 307 The IPC sends a video data acquisition request to the video storage module through the control module to obtain a video code stream required for processing the subtask.
- Step 308 The video storage module sends a corresponding video code stream to the control module of the IPC.
- control may distribute the video code stream to the corresponding task device by time period.
- Step 309 The control receives the video code stream and performs video processing.
- Step 310 The control sends the processing result (including: alarm information, analysis result, etc.) to the agent.
- Step 311 The agent reports the processing result of the IPC to the master.
- Step 312 The master summarizes the processing results reported by the respective IPCs.
- the master can keep the order of the processing results according to the sequence of video slots carried in the processing result.
- Step 313 The master reports the summary information to the CU.
- Step 314 When the user checks the companion line detection through the CU, the video code stream acquisition request is sent to the video storage module.
- Step 315 The video storage module sends the requested video code stream to the CU.
- Step 316 The CU acquires the video code stream, and performs image assembly with the alarm data such as the track reported by the master.
- Step 317 The CU displays the splicing result.
- the code stream whose number of video channels is lower than Pn can be processed in the resource pool.
- the master device is responsible for scheduling other IPC resource devices, and notifying the video storage module to resend the video code stream to the newly added resource device.
- the real-time video resource needs to buffer the real-time stream in the memory, and the duration can be notified by the master device, which is generally the maximum duration of the resource.
- Step 401 The user initiates a video summary analysis process by using the CU.
- Step 402 The CU sends a video summary analysis task to the master in the resource pool.
- Step 403 The master analyzes the task size and type, and calculates and allocates a corresponding number of slave devices.
- the master can divide the task into multiple subtasks according to various processing capabilities required, and then according to the number of corresponding capabilities that are required to complete the task, and the remaining processing capacity of the device, the allocation can complete each sub-request.
- the slave device processed by the task can further allocate the corresponding subtask to the slave device executing the subtask, and the corresponding capabilities include: calculating remaining capacity, codec remaining capacity, encryption and decryption remaining capability, storage remaining capacity, network bandwidth remaining capability, and Memory remaining capacity, etc.
- Step 404 The master sends a corresponding subtask to the agent in the corresponding slave device.
- Step 405 The agent that receives the subtask sends a subtask that needs to be processed by the module to the control module in the IPC.
- Step 406 The master reports the slave device list and the sub-task assignment correspondence of the task to the video storage module, so that the IPC accesses the video storage module to obtain the required video data.
- Step 407 The IPC sends a video data acquisition request to the video storage module by using the control module to obtain a video code stream required by the subtask.
- Step 408 The video storage module sends a corresponding video code stream to the control module of the IPC.
- Step 409 The control receives the video code stream, and performs video summary analysis processing.
- Step 410 The control sends the video summary analysis result to the agent.
- Step 411 The control stores the video summary analysis result in the video storage module.
- Step 412 The agent reports the video summary processing result of the IPC to the master.
- Step 413 The master performs summary of the video summary processing results reported by each IPC.
- Step 414 The master reports the video summary summary information to the CU.
- Step 415 When the user views the video summary through the CU, send a video summary acquisition request to the video storage module.
- Step 416 The video storage module sends the requested video summary code stream to the CU.
- the resource may be required according to the service, and according to Each of the remaining resources of the IPC as a slave device in the resource pool determines a slave device that satisfies the resources required by the service, and thus, the master device allocates the service to the corresponding slave device for processing.
- the present invention also provides a service processing system applied to a video monitoring system.
- an embodiment of a service processing system provided by the present invention may specifically include:
- the master device and the slave device are resource pools, wherein the master device and the slave device are both video surveillance front-end devices, and the master device meets preset thresholds for remaining resources in the front-end device.
- the device is determined to be the slave device; the master device is configured to receive a service processing request; determine resources required by the service, and determine, according to remaining resources of each slave device in the resource pool, that the service is required to meet the service The slave device of the resource; assigning the service to the corresponding slave device for processing.
- the master device is determined in the front-end device of the distributed system, and the master device determines the device whose remaining resources in the front-end device meet the preset threshold as the slave device, and then the master device and the slave device form a resource pool.
- the master device receives the service processing request, the master device determines the slave device that meets the resources required by the service according to the resources required by the service, and according to the remaining resources of the slave devices in the resource pool, so that the master device allocates the service to the corresponding slave device.
- the device is processed.
- the determining, by the master device, that the device in the front-end device that meets the preset threshold is the implementation manner of the slave device includes:
- the front-end device converts the remaining resources of the user into a corresponding remaining processing capability value according to the preset remaining capability reference, and reports the remaining processing capability value to the master device;
- the master device and the slave device form the resource pool.
- all the front-end devices except the master device need to report the remaining resource status of the device to the master device.
- the remaining resources of the master device may be converted into corresponding resources according to the preset remaining capability benchmark.
- the remaining processing capacity value indicates the size of the corresponding capability by the corresponding remaining capacity value. And reporting the remaining processing capability value to the master device.
- the master device compares the remaining processing capability data reported by each front-end device with the preset capability threshold, and determines the front-end device whose remaining processing capability value meets the preset capability threshold as the slave device, and the slave device is included in the resource pool.
- the master device divides the task into multiple subtasks according to various processing capabilities required by the task, according to the size of the corresponding processing capability required to complete the multiple subtasks, and the slave device. Remaining processing capability, assigning a corresponding number of the slave devices to complete the plurality of subtask processing.
- the master device sends the corresponding subtask to each of the assigned slave devices; the master device sends the allocated slave device list and the respective slave devices in the list to the video storage module in the video monitoring system.
- the master device receives the processing result reported by each of the allocated slave devices, wherein each of the allocated slave devices sends a video data acquisition request to the video storage module to obtain Processing the video code stream required by the subtask, performing corresponding video processing, and transmitting the processing result to the master device; finally, the master device summarizes the processing results reported by the allocated slave devices.
- the IPC deploys the distributed management software in addition to the normal management software for video surveillance, and installs and collects local resources and reports
- the software (defined as the agent module), in all IPC clusters, can select the master device (master), the master device is used to count the remaining resources of each IPC.
- the master device can also be an out-of-domain device outside the IPC, and only the module for statistical analysis needs to be installed in the device.
- the resource management adopts the master-slave mode.
- the agent is responsible for collecting the remaining resource information of the device and reporting it to the master.
- the master manages each resource device and is responsible for the IPC access resource pool and task assignment.
- Each IPC agent converts the calculated residual capacity Ci of its own device into a calculated residual capacity value according to the customized remaining capability benchmark. Similarly, the memory remaining capacity is converted into a value Mo, and the network remaining bandwidth processing capability is converted into a value Wp, and the code remaining capacity is converted.
- the value Bj is converted into a value Dk, the remaining capacity of the encryption is converted into a value E1, the remaining capacity of the decryption is converted into a value DEm, and the remaining capacity is converted into a capability data such as a value Sq, which is sent to the Master through a message.
- the Master models the resources according to the distribution of resources of each IPC device, and lists the various resources of each IPC device, such as computing resources, codec resources, storage resources, encryption and decryption resources, etc., for management.
- the master calculates the remaining available capacity of each task device, and compares it with the predetermined capability thresholds to determine whether to include the task device in the resource pool.
- the rule is that if the remaining available capacity is higher than the capability threshold, the resource may be included in the resource pool. Specifically, it may be set to include the IPC in the resource pool as long as a capability preset is met, and is not allowed to be included in the resource pool when all remaining available capabilities are lower than the corresponding capability threshold.
- Each capability threshold can use a set of test experience values by default, and can also provide several typical values and be configured in different scenarios.
- the device task device can send a message to the master to report the remaining resources of the device at a fixed time. If the master does not receive a message from a task device, the master device can be kicked out of the resource pool.
- the primary device is mainly used for resource allocation, and the determining manner may include multiple types, for example, the first enabled device is used as a primary device, and the device performs resources on devices that are subsequently added to the resource pool. distribution.
- One of the free slave devices in the resource pool can be re-elected as the master device by means of election.
- election There are a plurality of types of elections, which are not specifically limited in this embodiment of the present invention. Those skilled in the art can perform specific settings according to actual application scenarios, for example, selecting the device with the largest CPU capability as the master device.
- device backups can be made to the primary device, including hot or cold backups.
- the number of backups of the primary device can be configured by the user.
- hot backup the data is backed up synchronously; when the primary device is damaged or stops working for other reasons during cold backup, the cold device re-broadcasts the command to each slave device to obtain resource information and manage Resources.
- the present invention further provides an embodiment of a video surveillance front-end device applied to a video surveillance system, and the device may specifically include:
- a video collection unit for collecting video data
- a receiving unit configured to receive a service processing request when the video monitoring front-end device is a master device, and receive a service allocated by the master device when the video monitoring front-end device is a slave device;
- a remaining resource feedback unit configured to send the remaining resources of the master device to the primary device
- a slave determining unit configured to determine, when the video monitoring front-end device is a master device, a device that meets a preset threshold in the front-end device as the slave device;
- a processing unit configured to determine, according to a service processing request, a resource required by the service according to a service processing request, and determine, according to a remaining resource of each slave device in the resource pool, a service that is required to meet the service
- the slave device of the resource the service is allocated to the corresponding slave device for processing; and when the video surveillance front-end device is a slave device, the service allocated by the master device is processed;
- the master device is a video monitoring front-end device, and the master device and the slave device form the resource pool.
- the master device When the video surveillance front-end device is applied, the master device is determined in the front-end device, and the master device determines the device whose remaining resources in the front-end device meet the preset threshold as the slave device, and then the master device and the slave device form a resource pool, and when the master device receives the resource pool, the master device receives the resource pool.
- the slave device that meets the resources required by the service may be determined according to the resources required by the service and according to the remaining resources of each slave device in the resource pool, so that the master device allocates the service to the corresponding slave device for processing. .
- the specific implementation manner of the remaining resource feedback unit is: converting the remaining resources of the video front-end device itself into corresponding residual processing capability values according to the preset remaining capability reference, and reporting the remaining processing capability value a slave device determining unit to the master device; the slave device determining unit of the master device receives the remaining processing capability value reported by each video front-end device, and the remaining processing capability value satisfies the preset capability threshold
- the front end device is determined to be a slave device.
- the specific implementation manner of the processing unit is include:
- the processing unit may be further configured to: when it is determined that each of the remaining processing capability values of the slave device is lower than a preset capability threshold, The resource pool is culled from the device.
- the processing unit may be further configured to: when the master device fails, select one of the plurality of slave devices to select an idle slave device as the master device.
- the disclosed systems, devices, and methods may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, It can be electrical, mechanical or other form.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
- the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
- the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
Claims (17)
- 一种业务处理方法,应用于视频监控系统,其特征在于,包括:资源池内的主设备接收业务处理请求;所述主设备确定所述业务所需的资源,并根据所述资源池中各个从设备的剩余资源,确定满足所述业务所需的资源的所述从设备;所述主设备将所述业务分配给相应所述从设备进行处理;其中,所述主设备与从设备均为视频监控前端设备,所述主设备将所述前端设备中剩余资源满足预置阈值的设备确定为所述从设备,所述主设备与所述从设备组成所述资源池。
- 根据权利要求1所述的方法,其特征在于,所述主设备将所述前端设备中剩余资源满足预置阈值的设备确定为所述从设备,所述主设备与从设备组成所述资源池,包括:所述前端设备根据预置的剩余能力基准,将自身的剩余资源折算为相应剩余处理能力数值,并将所述剩余处理能力数值上报至所述主设备;所述主设备将所述剩余处理能力数值满足预置能力阈值的所述前端设备确定为从设备;所述主设备与所述从设备组成所述资源池。
- 根据权利要求1所述的方法,其特征在于,所述主设备确定所述业务所需的资源,并根据所述资源池中各个从设备的剩余资源,确定满足所述业务所需的资源的所述从设备,包括:所述主设备按照所述任务所需的各种处理能力,将所述任务划分为多个子任务,根据完成所述多个子任务所需消耗的相应处理能力的大小,以及所述从设备的剩余处理能力,分配相应数目的所述从设备以完成所述多个子任务处理。
- 根据权利要求3所述的方法,其特征在于,所述主设备将所述业务分配给相应所述从设备进行处理,包括:所述主设备向分配的各个从设备发送对应所述子任务;所述主设备向所述视频监控系统中的视频存储模块发送所分配的从设备列表以及列表中的所述各个从设备与所述子任务的分配对应关系;所述主设备接收所述分配的各个从设备上报的处理结果,其中,所述分配的各个从设备向所述视频存储模块发送视频数据获取请求,以获取处理所述子任务所需的视频码流,执行相应视频处理,并将处理结果发送至所述主设备;所述主设备将所述分配的各个从设备上报的处理结果进行汇总。
- 根据权利要求2所述的方法,其特征在于,还包括:当所述主设备确定所述从设备的各项所述剩余处理能力数值均低于预置能力阈值时,将所述从设备剔除出所述资源池。
- 根据权利要求1-5中任一项所述的方法,其特征在于,还包括:当所述主设备发生故障时,在所述多个从设备中重选选择出一个空闲从设备作为主设备。
- 一种业务处理系统,应用于视频监控系统,其特征在于,包括:主设备与从设备,所述主设备与所述从设备组成资源池,其中,所述主设备与从设备均为视频监控前端设备,所述主设备将所述前端设备中剩余资源满足预置阈值的设备确定为所述从设备;所述主设备用于接收业务处理请求;确定所述业务所需的资源,并根据所述资源池中各个从设备的剩余资源,确定满足所述业务所需的资源的所述从设备;将所述业务分配给相应所述从设备进行处理。
- 根据权利要求7所述的系统,其特征在于,所述主设备将所述前端设备中剩余资源满足预置阈值的设备确定为所述从设备的实现方式包括:所述前端设备根据预置的剩余能力基准,将自身的剩余资源折算为相应剩余处理能力数值,并将所述剩余处理能力数值上报至所述主设备;所述主设备将所述剩余处理能力数值满足预置能力阈值的所述前端设备确定为从设备;所述主设备与所述从设备组成所述资源池。
- 根据权利要求7所述的系统,其特征在于,所述主设备确定所述业务所需的资源,并根据所述资源池中各个从设备的剩余资源,确定满足所述业务所需的资源的所述从设备,该实现方式包括:所述主设备按照所述任务所需的各种处理能力,将所述任务划分为多个子任务,根据完成所述多个子任务所需消耗的相应处理能力的大小,以及所述从设备的剩余处理能力,分配相应数目的所述从设备以完成所述多个子任务处 理。
- 根据权利要求8所述的系统,其特征在于,所述主设备将所述业务分配给相应所述从设备进行处理,该实现方式包括:所述主设备向分配的各个从设备发送对应所述子任务;所述主设备向所述视频监控系统中的视频存储模块发送所分配的从设备列表以及列表中的所述各个从设备与所述子任务的分配对应关系;所述主设备接收所述分配的各个从设备上报的处理结果,其中,所述分配的各个从设备向所述视频存储模块发送视频数据获取请求,以获取处理所述子任务所需的视频码流,执行相应视频处理,并将处理结果发送至所述主设备;所述主设备将所述分配的各个从设备上报的处理结果进行汇总。
- 根据权利要求8所述的系统,其特征在于,所述主设备还用于:当确定所述从设备的各项所述剩余处理能力数值均低于预置能力阈值时,将所述从设备剔除出所述资源池。
- 根据权利要求7-11中任一项所述的系统,其特征在于,当所述主设备发生故障时,在所述多个从设备中重选选择出一个空闲从设备作为主设备。
- 一种视频监控前端设备,应用于视频监控系统,其特征在于,包括:视频采集单元,用于采集视频数据;接收单元,用于当所述视频监控前端设备为主设备时,接收业务处理请求;当所述视频监控前端设备为从设备时,接收主设备分配的业务;剩余资源反馈单元,用于向所述主设备发送自身的剩余资源;从设备确定单元,用于当所述视频监控前端设备为主设备时,将所述前端设备中剩余资源满足预置阈值的设备确定为所述从设备;处理单元,用于当所述视频监控前端设备为主设备时,根据业务处理请求确定所述业务所需的资源,并根据资源池中各个从设备的剩余资源,确定满足所述业务所需的资源的所述从设备,将所述业务分配给相应所述从设备进行处理;当所述视频监控前端设备为从设备时,处理所述主设备分配的所述业务;其中,所述主设备为视频监控前端设备,所述主设备与所述从设备组成所述资源池。
- 根据权利要求13所述的设备,其特征在于,所述剩余资源反馈单元的具体实现方式为:根据预置的剩余能力基准,将所述视频前端设备自身的剩 余资源折算为相应剩余处理能力数值,并将所述剩余处理能力数值上报至所述主设备的从设备确定单元;则所述主设备的从设备确定单元,用于将所述剩余处理能力数值满足预置能力阈值的所述前端设备确定为从设备。
- 根据权利要求13所述的设备,其特征在于,当所述视频监控前端设备为主设备时,所述处理单元的具体实现方式包括:按照所述任务所需的各种处理能力,将所述任务划分为多个子任务,根据完成所述多个子任务所需消耗的相应处理能力的大小,以及所述从设备的剩余处理能力,分配相应数目的所述从设备以完成所述多个子任务处理;向分配的各个从设备发送对应所述子任务;向所述视频监控系统中的视频存储模块发送所分配的从设备列表以及列表中的所述各个从设备与所述子任务的分配对应关系;接收所述分配的各个从设备上报的处理结果,其中,所述分配的各个从设备向所述视频存储模块发送视频数据获取请求,以获取处理所述子任务所需的视频码流,执行相应视频处理,并将处理结果发送至所述主设备;将所述分配的各个从设备上报的处理结果进行汇总。
- 根据权利要求14所述的设备,其特征在于,当所述视频监控前端设备为主设备时,所述处理单元还用于:当确定所述从设备的各项所述剩余处理能力数值均低于预置能力阈值时,将所述从设备剔除出所述资源池。
- 根据权利要求13-16中任一项所述的设备,其特征在于,当所述视频监控前端设备为主设备时,所述处理单元还用于:当所述主设备发生故障时,在所述多个从设备中重选选择出一个空闲从设备作为主设备。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020167013280A KR101910537B1 (ko) | 2013-10-29 | 2014-10-29 | 서비스 처리 방법, 시스템 및 장치 |
EP14857547.5A EP3048774B1 (en) | 2013-10-29 | 2014-10-29 | Service processing method, system and device |
JP2016527181A JP6239107B2 (ja) | 2013-10-29 | 2014-10-29 | サービス処理方法及びシステム、並びに装置 |
US15/140,755 US10805231B2 (en) | 2013-10-29 | 2016-04-28 | Service processing method and system and device |
US17/011,207 US11362961B2 (en) | 2013-10-29 | 2020-09-03 | Service processing method and system and device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310526368.7A CN104580338B (zh) | 2013-10-29 | 2013-10-29 | 一种业务处理方法、系统及设备 |
CN201310526368.7 | 2013-10-29 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/140,755 Continuation US10805231B2 (en) | 2013-10-29 | 2016-04-28 | Service processing method and system and device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015062492A1 true WO2015062492A1 (zh) | 2015-05-07 |
Family
ID=53003355
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/089759 WO2015062492A1 (zh) | 2013-10-29 | 2014-10-29 | 一种业务处理方法、系统及设备 |
Country Status (6)
Country | Link |
---|---|
US (2) | US10805231B2 (zh) |
EP (1) | EP3048774B1 (zh) |
JP (1) | JP6239107B2 (zh) |
KR (1) | KR101910537B1 (zh) |
CN (1) | CN104580338B (zh) |
WO (1) | WO2015062492A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115348322A (zh) * | 2022-07-11 | 2022-11-15 | 深圳市九洲电器有限公司 | 数据处理方法、组网设备及计算机可读存储介质 |
Families Citing this family (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9467507B2 (en) * | 2011-01-03 | 2016-10-11 | Verizon Patent And Licensing Inc. | Wireless network cloud computing resource management |
US10120904B2 (en) * | 2014-12-31 | 2018-11-06 | Cloudera, Inc. | Resource management in a distributed computing environment |
CN107423129A (zh) * | 2016-05-23 | 2017-12-01 | 中兴通讯股份有限公司 | 一种分布式系统的资源配置方法及装置 |
US10873540B2 (en) * | 2016-07-06 | 2020-12-22 | Cisco Technology, Inc. | Crowd-sourced cloud computing resource validation |
US10360606B2 (en) | 2016-07-19 | 2019-07-23 | Cisco Technology, Inc. | Crowd-sourced cloud computing in a multiple resource provider environment |
CN107786619A (zh) * | 2016-08-31 | 2018-03-09 | 中兴通讯股份有限公司 | 媒体服务器调度方法、装置及系统 |
CN106452992B (zh) * | 2016-09-19 | 2020-02-11 | 新华三技术有限公司 | 一种远端多归属组网的实现方法及装置 |
CN106682590B (zh) * | 2016-12-07 | 2023-08-22 | 浙江宇视科技有限公司 | 一种监控业务的处理方法以及服务器 |
WO2018103042A1 (en) | 2016-12-08 | 2018-06-14 | Zhejiang Dahua Technology Co., Ltd. | Methods and systems for video synopsis |
WO2018161341A1 (zh) * | 2017-03-10 | 2018-09-13 | 深圳市博信诺达经贸咨询有限公司 | 基于云技术的安防监控实现的方法及装置 |
CN107493199A (zh) * | 2017-08-31 | 2017-12-19 | 郑州云海信息技术有限公司 | 一种分布式集群管理方法及系统 |
CN107453929B (zh) * | 2017-09-22 | 2020-02-14 | 中国联合网络通信集团有限公司 | 集群系统自构建方法、装置及集群系统 |
CN108073894A (zh) * | 2017-11-17 | 2018-05-25 | 杭州中威电子股份有限公司 | 一种分布式人脸特征计算方法 |
CN108052384B (zh) * | 2017-12-27 | 2022-01-18 | 联想(北京)有限公司 | 一种任务处理方法、服务平台及电子设备 |
CN108579076A (zh) * | 2018-04-16 | 2018-09-28 | 武汉康慧然信息技术咨询有限公司 | 家庭娱乐中心中虚拟现实算力增强方法 |
CN108769118B (zh) * | 2018-04-23 | 2022-01-21 | 网宿科技股份有限公司 | 一种分布式系统中主节点的选取方法及装置 |
CN108600008B (zh) * | 2018-04-24 | 2021-12-17 | 致云科技有限公司 | 服务器管理方法、服务器管理装置及分布式系统 |
US11075740B2 (en) | 2018-05-07 | 2021-07-27 | ENK Wireless, Inc. | Systems/methods of communications using a plurality of cooperative devices |
US10681716B2 (en) | 2018-05-07 | 2020-06-09 | ENK Wireless, Inc. | Systems/methods of providing increased wireless capacity, vehicular safety, electrical power wirelessly, and device control responsive to geographic position |
US11100796B2 (en) | 2018-05-07 | 2021-08-24 | ENK Wireless, Inc. | Systems/methods of improving vehicular safety |
CN110557679B (zh) * | 2018-06-01 | 2021-11-19 | 中国移动通信有限公司研究院 | 一种视频内容识别方法、设备、介质和系统 |
CN108984465B (zh) * | 2018-06-06 | 2021-08-20 | 华为技术有限公司 | 一种消息传输方法及设备 |
CN109040686B (zh) * | 2018-08-22 | 2020-12-01 | 苏宁云计算有限公司 | 一种物联网摄像系统中的软件部署方法及物联网摄像系统 |
CN109614242B (zh) * | 2018-12-20 | 2023-07-14 | 深圳市网心科技有限公司 | 一种计算能力共享方法、装置、设备及介质 |
CN109976907B (zh) * | 2019-03-11 | 2021-08-31 | 百度在线网络技术(北京)有限公司 | 任务分配方法和系统、电子设备、计算机可读介质 |
CN110650312B (zh) * | 2019-09-06 | 2021-03-16 | 佳都新太科技股份有限公司 | 基于图像监控系统的扩容方法及装置 |
CN112529761A (zh) * | 2019-09-18 | 2021-03-19 | 珠海格力电器股份有限公司 | 基于视频图像识别的并发请求的处理方法及存储介质 |
CN112787840B (zh) * | 2019-11-11 | 2022-07-22 | 华为技术有限公司 | 一种实现业务功能部署的方法、装置和系统 |
CN111555903A (zh) * | 2020-03-26 | 2020-08-18 | 浙江口碑网络技术有限公司 | 一种数据通信的方法及装置 |
CN111445213A (zh) * | 2020-03-31 | 2020-07-24 | 乌鲁木齐众维汇联信息科技有限公司 | 园区企业孵化服务的网络管理系统 |
CN111953932A (zh) * | 2020-06-30 | 2020-11-17 | 视联动力信息技术股份有限公司 | 数据处理方法、装置、终端设备和存储介质 |
CN112333447A (zh) * | 2020-11-02 | 2021-02-05 | 上海网达软件股份有限公司 | 音视频转码方法、装置、设备及存储介质 |
CN112799799A (zh) * | 2020-12-29 | 2021-05-14 | 杭州涂鸦信息技术有限公司 | 数据消费方法及装置 |
RU2771211C1 (ru) * | 2021-07-12 | 2022-04-28 | Акционерное общество "Научно-исследовательский институт "Субмикрон" (АО "НИИ "Субмикрон") | Вычислительная система с холодным резервом |
US20230222692A1 (en) * | 2022-01-07 | 2023-07-13 | Johnson Controls Tyco IP Holdings LLP | Systems and methods for sharing analytical resources in a camera network |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001117887A (ja) * | 1999-10-14 | 2001-04-27 | Nec Corp | 分散型アプリケーションサーバシステム,サービス方法および記録媒体 |
CN102541640A (zh) * | 2011-12-28 | 2012-07-04 | 厦门市美亚柏科信息股份有限公司 | 一种集群gpu资源调度系统和方法 |
CN103248659A (zh) * | 2012-02-13 | 2013-08-14 | 北京华胜天成科技股份有限公司 | 一种云计算资源调度方法和系统 |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5349682A (en) * | 1992-01-31 | 1994-09-20 | Parallel Pcs, Inc. | Dynamic fault-tolerant parallel processing system for performing an application function with increased efficiency using heterogeneous processors |
US5774668A (en) * | 1995-06-07 | 1998-06-30 | Microsoft Corporation | System for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing |
US6687651B2 (en) * | 2002-01-10 | 2004-02-03 | Fujitsu Network Communications, Inc. | Real time estimation of equivalent bandwidth utilization |
CN1251111C (zh) * | 2002-12-31 | 2006-04-12 | 联想(北京)有限公司 | 基于系统级诊断信息的负载衡量方法 |
JP3977765B2 (ja) * | 2003-03-31 | 2007-09-19 | 富士通株式会社 | グリッドコンピューティングを用いたシステムにおけるリソース提供方法,そのシステムにおける監視装置およびその監視装置用プログラム |
US7937406B2 (en) * | 2003-09-11 | 2011-05-03 | Oracle America, Inc. | Mechanism for automatically establishing a resource grid |
US7716286B2 (en) * | 2003-12-10 | 2010-05-11 | Heins Douglas B | Method and apparatus for utility computing in ad-hoc and configured peer-to-peer networks |
JP2007264794A (ja) * | 2006-03-27 | 2007-10-11 | Fujitsu Ltd | 並列分散処理プログラム及び並列分散処理システム |
US7590666B2 (en) * | 2006-06-16 | 2009-09-15 | Microsoft Corporation | Predicting capacity consumption in a memory component |
EP2100223B1 (en) * | 2006-12-05 | 2011-01-19 | QUALCOMM Incorporated | Apparatus and methods of a zero single point of failure load balancer |
JP5507136B2 (ja) * | 2009-07-09 | 2014-05-28 | 株式会社日立製作所 | 管理装置及び方法並びに計算機システム |
US8830245B2 (en) * | 2010-12-14 | 2014-09-09 | Amazon Technologies, Inc. | Load balancing between general purpose processors and graphics processors |
CN102752574B (zh) | 2011-04-18 | 2015-01-28 | 中兴通讯股份有限公司 | 一种视频监控系统及方法 |
CN102638456B (zh) | 2012-03-19 | 2015-09-23 | 杭州海康威视数字技术股份有限公司 | 基于云计算的海量实时视频码流智能分析方法及其系统 |
KR101515977B1 (ko) * | 2012-10-24 | 2015-05-06 | 주식회사 케이티 | Ip 카메라를 이용하는 클라우드 환경의 영상 감시 시스템 및 영상 감시 방법 |
-
2013
- 2013-10-29 CN CN201310526368.7A patent/CN104580338B/zh active Active
-
2014
- 2014-10-29 JP JP2016527181A patent/JP6239107B2/ja active Active
- 2014-10-29 WO PCT/CN2014/089759 patent/WO2015062492A1/zh active Application Filing
- 2014-10-29 EP EP14857547.5A patent/EP3048774B1/en active Active
- 2014-10-29 KR KR1020167013280A patent/KR101910537B1/ko active IP Right Grant
-
2016
- 2016-04-28 US US15/140,755 patent/US10805231B2/en active Active
-
2020
- 2020-09-03 US US17/011,207 patent/US11362961B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001117887A (ja) * | 1999-10-14 | 2001-04-27 | Nec Corp | 分散型アプリケーションサーバシステム,サービス方法および記録媒体 |
CN102541640A (zh) * | 2011-12-28 | 2012-07-04 | 厦门市美亚柏科信息股份有限公司 | 一种集群gpu资源调度系统和方法 |
CN103248659A (zh) * | 2012-02-13 | 2013-08-14 | 北京华胜天成科技股份有限公司 | 一种云计算资源调度方法和系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3048774A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115348322A (zh) * | 2022-07-11 | 2022-11-15 | 深圳市九洲电器有限公司 | 数据处理方法、组网设备及计算机可读存储介质 |
CN115348322B (zh) * | 2022-07-11 | 2023-07-18 | 深圳市九洲电器有限公司 | 数据处理方法、组网设备及计算机可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
JP6239107B2 (ja) | 2017-11-29 |
EP3048774B1 (en) | 2018-05-30 |
JP2016535340A (ja) | 2016-11-10 |
US10805231B2 (en) | 2020-10-13 |
CN104580338A (zh) | 2015-04-29 |
KR101910537B1 (ko) | 2018-10-22 |
US20160241486A1 (en) | 2016-08-18 |
CN104580338B (zh) | 2018-09-07 |
EP3048774A4 (en) | 2016-10-19 |
US11362961B2 (en) | 2022-06-14 |
EP3048774A1 (en) | 2016-07-27 |
KR20160073409A (ko) | 2016-06-24 |
US20200403933A1 (en) | 2020-12-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015062492A1 (zh) | 一种业务处理方法、系统及设备 | |
US11582166B2 (en) | Systems and methods for provision of a guaranteed batch | |
KR101782345B1 (ko) | 엔드-투-엔드 데이터센터 성능 제어 | |
CN106375420B (zh) | 一种基于负载均衡的服务器集群智能监控系统及方法 | |
JP6559670B2 (ja) | ネットワーク機能仮想化情報コンセントレータのための方法、システム、およびコンピュータ読取可能媒体 | |
CN108039964B (zh) | 基于网络功能虚拟化的故障处理方法及装置、系统 | |
CN104618693B (zh) | 一种基于云计算的监控视频在线处理任务管理方法及系统 | |
JP6563936B2 (ja) | クラウドに基づく仮想オーケストレーターのための方法、システム、およびコンピュータ読取可能な媒体 | |
EP3361703B1 (en) | Load balancing method, related device and system | |
CN110545258B (zh) | 流媒体服务器资源配置方法、装置和服务器 | |
CN109271243B (zh) | 一种集群任务管理系统 | |
US8799474B2 (en) | Apparatus and method to allocate limited resources | |
US20210208949A1 (en) | Centralized control server, local terminal, distributed surveillance system, surveillance method and storage medium | |
US20130305245A1 (en) | Methods for managing work load bursts and devices thereof | |
Birje et al. | Cloud monitoring system: basics, phases and challenges | |
CN113568756B (zh) | 一种密码资源协同动态调度方法和系统 | |
WO2018099090A1 (zh) | 从云计算系统中确定主调度器的方法及装置 | |
CN103269431B (zh) | 一种云转码实现方法及装置 | |
US20150079966A1 (en) | Methods for facilitating telecommunication network administration and devices thereof | |
左利云 et al. | Virtual resource evaluation model based on entropy optimized and dynamic weighted in cloud computing | |
CN115168042A (zh) | 监控集群的管理方法及装置、计算机存储介质、电子设备 | |
KR102187382B1 (ko) | 클라우드 인프라 기반의 컨테이너 가상os 통합 모니터링 운영 방법 | |
CN106844021B (zh) | 计算环境资源管理系统及其管理方法 | |
CN111160283A (zh) | 一种数据接入方法、装置、设备和介质 | |
WO2020029978A1 (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: 14857547 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2014857547 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014857547 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016527181 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20167013280 Country of ref document: KR Kind code of ref document: A |